Hello,

I just upgraded to 3.1.1 on a NetBSD box via pkgsrc, and
am using sendmail 8.13.5 with spamass-milter 0.3.0, and sendmail
is configured to use cyrus imapd as its local delivery agent.

Since I upgraded, I'm seeing bits of the X-Spam-Header message
in my mail bodies, like this :

To: Carl Brewer <[EMAIL PROTECTED]>
Subject: Re: boing 2
References: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on rollcage2.bl.echidna.id.au
X-Virus-Status: Clean
X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00

        autolearn=ham version=3.1.1
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on
        rollcage2.bl.echidna.id.au


It looks like sometimes spamassassin (or spamass-milter?) is
adding a cr/lf in the X-Spam-Status header, which makes it
leak out into the body of the mail. This wasn't happening with 3.0,
and is new behaviour with 3.1.1.

my config dir contains the following rulesets :

-rw-r--r--  1 root  wheel  15311 Mar 15 18:38 72_sare_redirect_post3.0.0.cf
-rw-r--r--  1 root  wheel   1059 Mar 15 00:41 init.pre
-rw-r--r--  1 root  wheel    642 Mar 15 18:30 local.cf
-rwxr-xr-x  1 root  wheel   1642 Mar 15 18:37 update.pl
-rw-r--r--  1 root  wheel   1869 Mar 15 00:41 user_prefs.template
-rw-r--r--  1 root  wheel   2398 Jan 11 09:42 v310.pre



spamass-milter and spamd are running as follows :

root 5861 0.0 2.1 21756 21860 ? I 6:38PM 0:01.81 perl: spamd child root 7658 0.0 2.0 20012 21444 ? Ss 6:38PM 0:01.81 /usr/pkg/bin/perl -T -w /usr/pkg/bin/spamd -H -c -d -r /var/run/spamd.pid root 13207 0.0 0.0 2272 1132 ? IWsa 9:54AM 0:02.96 /usr/pkg/sbin/spamass-milter -u nobody -r -1 -p /var/run/spamass.sock -f root 15359 0.0 0.7 20012 7408 ? I 6:38PM 0:00.01 perl: spamd child


I've tried a number of things in local.cf :

score SPF_HELO_FAIL 10.000
report_safe 0
remove_header all X-Spam-Status

But this hasn't removed the header or fixed the leak into the
message body.

Any suggestions?

Thanks!

Carl





Reply via email to