Configurable 'X-Bogosity' message

[David Relson]

Matthias,

When bogofilter was using "X-Spam-Status" as its marker, it made sense to 
ignore lines beginning with "X-Spam-".  Now that we're using a configurable 
SPAM_HEADER_NAME (with "X-Bogosity" as default value), it makes sense to 
ignore lines beginning with SPAM_HEADER_NAME.  I've just commited my 
lexer.l change to CVS.

It'll be interesting to see if any of SpamAssassin's header lines become 
spam indicators :-)

David

At 07:05 PM 10/6/02, Matthias Andree wrote:
>On Sun, 06 Oct 2002, David Relson wrote:
>
>I'll object for now. We should NOT pay attention to other X-Spam-
>headers (but we should pass them through unless they match the one we
>use), because there's potential to let errors in other spam
>classification software propagate into bogofilter's judgement. I haven't
>set down with pen & paper to look how big the impact would be if we
>scored on Spamassassin's headers or something, but it's just a feeling
>that it's the wrong thing to do.
>
>And if we deviate from the X-Spam- naming scheme, it makes stripping the
>headers (for other tools) more difficult, but if X-Bogosity is the kind
>of project identity that's required, then so be it.

I think it's a good idea to strip "X-Bogosity" headers, as it lessens the 
opportunity for spammers to forge an "All O.K." header.  We can change our 
minds at some future time and decide to strip "X-Spam-" headers.


>--
>Matthias Andree