[spambayes-dev] Proposed fourth X-Spambayes-Classification header value

[Tim Stone]

I'm working on this problem that crops up in pop3proxy and hammie where 
malformed headers cause the parser to raise an uncaught exception, 
rendering spambayes more helpless than a baby seal.  It's no problem to 
catch the exception, but what to do with the message is the issue.  I have 
two suggested approaches:

1. Assume that the mail is spam.

2. Add a new possible value to the classification header, something like 
'unclassifiable'.

Other alternatives, votes, or general booing and hissing?

-- 


c'est moi - TimS