You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2006/05/10 12:03:09 UTC
Re: Nasty bug? in 3.1.1 headers inserting?
Daryl C. W. O'Shea writes:
> On 5/9/2006 2:16 PM, Theo Van Dinter wrote:
>
> > There's some difference of opinion around this question, but my general
> > opinion is that there should be an update to spamass-milter which
> > properly handles the newlines either way. I'm not sure whether or not
> > that's happened yet.
>
> As discussed in this SA bug:
>
> http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4844
>
> this spamass-milter bug has a (confirmed to work) patch that fixes the
> problem with spamass-milter:
>
> http://savannah.nongnu.org/bugs/?func=detailitem&item_id=16164
>
>
> I do not know if there is an updated spamass-milter release. I'm
> assuming there isn't since their bug is still open.
by the way this is a FAQ, too.
http://wiki.apache.org/spamassassin/SaMilter030CorruptMsgs
--j.
RE: Nasty bug? in 3.1.1 headers inserting?
Posted by Sietse van Zanen <si...@wizdom.nu>.
Thanks for all of your replies.
Think I should have kept a closer eye on the milter. I use DAG WIers packages for RHEL3 and he doesn;t have the 0.3.1 available yet. Never cared to look whether there was an update of the milter and therefor missed the issue.
Appologies for any inconveniences on the mailing list. I will compile the milter tonight, as I first have to dig up the source for the sendmail version I'm using.
Furthermore I did some digging in RFC822, and this is what I found:
3. LEXICAL ANALYSIS OF MESSAGES
3.1. GENERAL DESCRIPTION
A message consists of header fields and, optionally, a body.
The body is simply a sequence of lines containing ASCII charac-
ters. It is separated from the headers by a null line (i.e., a
line with nothing preceding the CRLF).
Esto, the \r followed by the \n is against the RFC (Two line feeds is a CRLF on a null line), as it should be followed by a white space (or tab). I don't know exactly if it is spamassassin inserting this sequence or the milter. But if it's spamassassin it should be corrected there I think. If it's the milter it's already been fixed.
So in the end the Exchage server is actually adhering the RFC, who would've guessed that. :-)
-Sietse
________________________________
From: Justin Mason [mailto:jm@jmason.org]
Sent: Wed 10-May-06 12:03
To: Daryl C. W. O'Shea
Cc: users@spamassassin.apache.org
Subject: Re: Nasty bug? in 3.1.1 headers inserting?
version=3.1.1
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on zpm.wizdom.nu
X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on zpm.wizdom.nu
X-Virus-Status: Clean
Return-Path: users-return-41141-sietse=wizdom.nu@spamassassin.apache.org
X-OriginalArrivalTime: 10 May 2006 10:04:19.0072 (UTC) FILETIME=[1A4A5000:01C67419]
Daryl C. W. O'Shea writes:
> On 5/9/2006 2:16 PM, Theo Van Dinter wrote:
>
> > There's some difference of opinion around this question, but my general
> > opinion is that there should be an update to spamass-milter which
> > properly handles the newlines either way. I'm not sure whether or not
> > that's happened yet.
>
> As discussed in this SA bug:
>
> http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4844
>
> this spamass-milter bug has a (confirmed to work) patch that fixes the
> problem with spamass-milter:
>
> http://savannah.nongnu.org/bugs/?func=detailitem&item_id=16164
>
>
> I do not know if there is an updated spamass-milter release. I'm
> assuming there isn't since their bug is still open.
by the way this is a FAQ, too.
http://wiki.apache.org/spamassassin/SaMilter030CorruptMsgs
--j.