Configurable 'X-Bogosity' message

[Adrian Otto]

David,

I think you meant to type "SPAM_HEADER_NAME". That's the new configurable
constant that I added with a corresponding function to set it in the
configure script.

By changing the lexer's processing of X-Spam to only processing the header
that matches SPAM_HEADER_NAME we do get the added benefit of identifying
messages that have already been run through SpamAssasin or similar programs.

Thank you Graham for your input!

Adrian

> -----Original Message-----
> From: David Relson [mailto:relson at osagesoftware.com]
> Sent: Sunday, October 06, 2002 2:50 PM
> To: Graham Wilson
> Cc: bogofilter-dev
> Subject: Re: Configurable 'X-Bogosity' message
>
>
> gram,
>
> When bogofilter was adding its own "X-Spam-Status" line, any previously
> existing lines that began with "X-Spam-*" were being removed.
> Imagine how
> confusing it would be if a spammer put in a "Status:  All is
> good" line and
> we were putting in "this is spam".  To avoid having conflicting
> lines like
> this, bogofilter will remove lines that start with "X-Bogosity"
> or whatever
> SPAM_HEADER_LINES is set to.
>
> David
>
>
> At 05:41 PM 10/6/02, Graham Wilson wrote:
> >On Sun, Oct 06, 2002 at 03:11:45PM -0400, David Relson wrote:
> > > So, the default has changed from "X-Spam-Status" to
> "X-Bogosity".  I'll
> > > update lexer.l which handles the task of removing
> > > SPAM_HEADER_LINES.  Although the old lexer.l removed lines
> beginning with
> > > "X-Spam-*:", I think that the new version will be slightly
> more limited.
> >
> >ive found that the keeping x-spam-* lines in the message is a good
> >thing. some of the spam that i get has had a header like that add by
> >spamassassin and the tests that it lists in that header are marked by
> >bogofilter with very high probability for being spam.
> >
> >--
> >gram
>
>