At 08:31 -0700 21 May 2002, Professional Software Engineering
<PSE-L(_at_)mail(_dot_)professional(_dot_)org> wrote:
At 18:57 2002-05-20 -0500, Aaron Schrab did say:
No, I mean that your previous reply (the one with Message-ID
5(_dot_)1(_dot_)0(_dot_)14(_dot_)2(_dot_)20020520103843(_dot_)07724bd0(_at_)mail(_dot_)professional(_dot_)org).
It's ironic
because the very message in which you described a way of determining
that a reply isn't spam would have failed the very test that it
described.
Why?
OK, it can be made to work. I guess I should have said that many
implementations of the technique would not have caught the message in
question.
Received and Content-Type both get split across multiple lines. Procmail
and formail comprehend them (and this "broken" header too) just fine. The
Procmail and formail don't care about the content of the headers, so
they handle it fine. For tools that actually work with the content, the
header I previously quoted is indeed broken. Although it is allowed to
continue a header field onto additional lines, line breaks are only
allowed in places that white space is allowed. This does not include
introducing a new line in the middle of a word (or message-id). This
especially applies to structured fields, which includes the In-reply-to
field.
It's fairly easy to work around this bug in Eudora for these purposes,
since only a very simple check is being done against the In-reply-to
header. But the real reason I care about this problem is that it broke
threading in older versions of mutt, recent versions work around this
stupidity. But pipermail (at least the version used for the archives of
this list) doesn't work around this problem. I have no idea if mhonarc
or other programs which attempt to do threading have been adjusted to
cope with this.
--
Aaron Schrab aaron(_at_)schrab(_dot_)com http://www.schrab.com/aaron/
Real programmers can write assembly code in any language. :-)
--Larry Wall
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail