[PATCH] invalid end of header

[David Relson]

At 09:56 PM 5/20/03, Jeremy Blosser wrote:

>On May 17, David Relson [relson at osagesoftware.com] wrote:
> > Here's a patch to detect a message header terminated by an blank, but
> > non-empty, line.  Give it a try and let me know how well it works for you.
>
>Sorry, but I can't really try this one.  I don't think these kind of blank
>lines are actually what we're seeing (see my other mails), and I can't
>stick a not-completely-tested (i.e., not in a stable version) patch on
>those servers unless I *know* it's going to fix a critical problem.
>They're too high profile.
>
>For now we're catching messages immediately after bogofilter sees them and
>forcing the first found X-Bogosity line to the top of the header, via sed.
>That prevents us from having bogosity lines in the body when the message
>gets to disk.
>
>Thanks.

Jeremy,

A quick scan of my April spam showed a group of messages from ahsss at mxdat 
(unknown [290.236.11.xxx]).  In all of them the Subject: line is followed 
by a line with 1 space and that is followed by an empty line (just a 
'\n').  Using the patch I sent to you, bogofilter puts its "X-Bogosity:" 
line after "Subject:" and before the <space><nl> line.

I'll look a bit further to see if I find other patterns.  At the moment the 
lexer change looks like it does what I intended.

David