Re: Headers changed in 3.1.1?
Yes, every messge (see below, too). F Daryl C. W. O'Shea wrote: version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mail.forrie.com X-Virus-Scanned: ClamAV 0.88/1345/Mon Mar 20 07:03:16 2006 on mail.forrie.com X-Virus-Status: Clean Forrest Aldrich wrote: Here are the full headers from the previous message. Notice the space after X-Spam-Status - how did that get there? I am running spamd and spamass-milter with Sendmail 8.13. Does this happen with *every* message? I cannot reproduce with my modified (to insert, rather than append headers) install of spamass-milter 0.3.0. Daryl
Headers changed in 3.1.1?
Since updating to SpamAssassin 3.1.1, I've noticed that headers are creeping into the basic message display of Thunderbird (nightly build): version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mail.myserver.com X-Virus-Scanned: ClamAV 0.88/1345/Mon Mar 20 07:03:16 2006 on mail.myserver.com X-Virus-Status: Clean Message content ... etc. I wonder if something has changed with regard to how the headers are formatted. It's always the same, starting at version. I realize this could be a Thunderbird issue; however, it seemed prudent to ask here, in case there is something I overlooked that could be tweaked. Thanks.
Re: Headers changed in 3.1.1?
Forrest Aldrich a écrit : Since updating to SpamAssassin 3.1.1, I've noticed that headers are creeping into the basic message display of Thunderbird (nightly build): version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mail.myserver.com X-Virus-Scanned: ClamAV 0.88/1345/Mon Mar 20 07:03:16 2006 on mail.myserver.com X-Virus-Status: Clean Message content ... etc. I wonder if something has changed with regard to how the headers are formatted. It's always the same, starting at version. I realize this could be a Thunderbird issue; however, it seemed prudent to ask here, in case there is something I overlooked that could be tweaked. how are you running SA? show complete headers (including the ones that go into the body).
Re: Headers changed in 3.1.1?
On Mon, Mar 20, 2006 at 12:11:55PM -0500, Forrest Aldrich wrote: I wonder if something has changed with regard to how the headers are formatted. Yes, if a message comes in with CRLF, the headers added will use CRLF. This broke at least spamass-milter, which is the only other group I've heard of having this problem so far. Otherwise 3.1.1 is the same as 3.1.0 wrt header modifications as far as I know. -- Randomly Generated Tagline: Bender: Grab a shovel. I'm only one skull short of a Mousketeer reunion. pgpCcF0IuQbRx.pgp Description: PGP signature
Re: Headers changed in 3.1.1?
Here are the full headers from the previous message. Notice the space after X-Spam-Status - how did that get there? I am running spamd and spamass-milter with Sendmail 8.13. Thanks. Return-Path: [EMAIL PROTECTED] Received: from forrie.com ([unix socket]) by forrie.com (Cyrus v2.3.1) with LMTPA; Mon, 20 Mar 2006 13:00:16 -0500 X-Sieve: CMU Sieve 2.3 Received: from mail.apache.org (hermes.apache.org [209.237.227.199]) by forrie.com (8.13.5/8.13.5) with SMTP id k2KI0EDX030062 for [EMAIL PROTECTED]; Mon, 20 Mar 2006 13:00:15 -0500 (EST) (envelope-from [EMAIL PROTECTED]) Received: (qmail 52556 invoked by uid 500); 20 Mar 2006 18:00:03 - Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm Precedence: bulk list-help: mailto:[EMAIL PROTECTED] list-unsubscribe: mailto:[EMAIL PROTECTED] List-Post: mailto:users@spamassassin.apache.org List-Id: users.spamassassin.apache.org Delivered-To: mailing list users@spamassassin.apache.org Received: (qmail 52547 invoked by uid 99); 20 Mar 2006 18:00:03 - Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Mar 2006 10:00:03 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [212.27.42.28] (HELO smtp2-g19.free.fr) (212.27.42.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Mar 2006 10:00:01 -0800 Received: from ouzoud.netoyen.net (ouzoud.netoyen.net [82.239.111.75]) by smtp2-g19.free.fr (Postfix) with ESMTP id ABD7C7321A for users@spamassassin.apache.org; Mon, 20 Mar 2006 18:59:40 +0100 (CET) Received: from [10.70.4.25] (dades.netoyen.net [10.70.4.25]) by ouzoud.netoyen.net (Postfix) with ESMTP id CFAAD790CD; Mon, 20 Mar 2006 18:52:19 + (UTC) Message-ID: [EMAIL PROTECTED] Date: Mon, 20 Mar 2006 18:59:51 +0100 From: mouss [EMAIL PROTECTED] User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: fr, en MIME-Version: 1.0 To: Forrest Aldrich [EMAIL PROTECTED] CC: users@spamassassin.apache.org Subject: Re: Headers changed in 3.1.1? References: [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.88/1345/Mon Mar 20 07:03:16 2006 on mail.forrie.com X-Virus-Scanned: ClamAV using ClamSMTP (ouzoud.netoyen.net) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Status: No, score=1.0 required=10.0 tests=RCVD_IN_SORBS autolearn=no version=3.1.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mail.forrie.com X-Virus-Status: Clean
Re: Headers changed in 3.1.1?
Forrest Aldrich wrote: Here are the full headers from the previous message. Notice the space after X-Spam-Status - how did that get there? I am running spamd and spamass-milter with Sendmail 8.13. It's a known problem. Dan Nelson (spamass-milter maintainer) says it's not spamass-milter : Libmilter should be expecting CRLF, I think, since that's what RFC 2822 messages use. Not that it ever sees EOLs except within the message body, though. Headers are just text strings with no EOL markers ( http://www.milter.org/milter_api/xxfi_header.html ). The only way a header could leak into the body would be if spamassassin added a LFLF or CRLFCRLF pair to a header line, since that's what spamass-milter uses to detect the header/boundary border. The messages spamass-milter generates for spamassassin to process always have CRLF-trailing headers. The message itself isn't touched, although it's probably also CRLF-encoded since that's RFC 2822. Headers retrieved from spamassassin are parsed by looking for LF and stripping a preceding CR if it exists, so it should be pretty tolerant of whatever spamassassin decides to do. If you run spamassassin with the '-d spamc' flag, you should be able to see the raw data sent to and received from spamassassin. Theo Van Dinter says it's not really spamassassin's problem : (Theo Van Dinter) : The problem is caused by a specific feature that was added into SpamAssassin in 3.1.1 -- namely that we'll use the same line endings that the original message uses (LF vs CRLF). spamass-milter relied on the previous behavior (always use LF), which happened to work well with what libmilter expected. So in this case, I would expect the spamass-milter code to be modified to take into account that line endings could either be CRLF (3.1.1 and beyond) or LF (3.1.0 and previous). (alternately, libmilter could be modified to handle either LF or CRLF, which would probably be easier to code, but harder to get that API changed...) But, it's broken -somewhere-, and the change was made in spamassassin. Any chance of reverting the change in spamassassin so spamass-milter works again? Carl
Re: Headers changed in 3.1.1?
Forrest Aldrich wrote: Here are the full headers from the previous message. Notice the space after X-Spam-Status - how did that get there? I am running spamd and spamass-milter with Sendmail 8.13. Does this happen with *every* message? I cannot reproduce with my modified (to insert, rather than append headers) install of spamass-milter 0.3.0. Daryl
Re: Headers changed in 3.1.1?
Carl Brewer wrote: It's a known problem. Dan Nelson (spamass-milter maintainer) says it's not spamass-milter : But, it's broken -somewhere-, and the change was made in spamassassin. Any chance of reverting the change in spamassassin so spamass-milter works again? Can you provide me with three copies of an affected message in a tarball: - the original, unscanned message - the original message after it has gone through spamass-milter - the original message after it has gone through spamc, not spamass-milter Be sure to use appropriate redirection and not copy-and-paste. Thanks, Daryl
