Your message dated Mon, 21 Mar 2005 10:28:34 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#300558: spamassassin: Sarge SA can't parse Received
headers from Sarge Exim4
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 20 Mar 2005 14:09:24 +0000
>From [EMAIL PROTECTED] Sun Mar 20 06:09:24 2005
Return-path: <[EMAIL PROTECTED]>
Received: from projectile.ca (pyloric.projectile.ca) [64.26.176.14]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DD17M-0004XX-00; Sun, 20 Mar 2005 06:09:24 -0800
Received: from msherman by pyloric.projectile.ca with local (Exim 4.44)
id 1DD16r-00054K-5D
for [EMAIL PROTECTED]; Sun, 20 Mar 2005 09:08:53 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Marc Sherman <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: spamassassin: Sarge SA can't parse Received headers from Sarge Exim4
X-Mailer: reportbug 3.8
Date: Sun, 20 Mar 2005 09:08:53 -0500
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: spamassassin
Version: 3.0.2-1
Severity: normal
According to the analysis of 290927, and upstream's fix for their bug
3949, the SA currently shipping in Sarge can't parse the Received
headers created by Sarge's default MTA, Exim4.
The patch currently attached to 290927 doesn't fix the parsing problem,
it just avoids incorrectly reporting an unparsed Received header as a
trusted relay.
I'm tempted to mark this bug important, since it's an incompatibility
with a base package, but I'll leave that to your judgement.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (900, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)
Versions of packages spamassassin depends on:
ii debconf 1.4.30.11 Debian configuration management sy
ii libdigest-sha1-perl 2.10-1 NIST SHA-1 message digest algorith
ii libhtml-parser-perl 3.45-1 A collection of modules that parse
ii perl [libstorable-perl] 5.8.4-8 Larry Wall's Practical Extraction
ii spamc 3.0.2-1 Client for SpamAssassin spam filte
-- debconf information excluded
---------------------------------------
Received: (at 300558-done) by bugs.debian.org; 21 Mar 2005 15:30:03 +0000
>From [EMAIL PROTECTED] Mon Mar 21 07:30:03 2005
Return-path: <[EMAIL PROTECTED]>
Received: from projectile.ca (pyloric.projectile.ca) [64.26.176.14]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DDOqw-0004M3-00; Mon, 21 Mar 2005 07:30:02 -0800
Received: from wlan.projectile.ca ([192.168.23.1] helo=[192.168.23.50])
by pyloric.projectile.ca with esmtpsa
(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32)
(Exim 4.44)
id 1DDOqR-0002or-HV; Mon, 21 Mar 2005 10:29:31 -0500
Message-ID: <[EMAIL PROTECTED]>
Date: Mon, 21 Mar 2005 10:28:34 -0500
From: Marc Sherman <[EMAIL PROTECTED]>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kjetil Kjernsmo <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Bug#300558: spamassassin: Sarge SA can't parse Received headers
from Sarge Exim4
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL
PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 2
Kjetil Kjernsmo wrote:
>
> You can do this by taking a message you see misfires, save it to a file,
> say test.msg and go
> spamassassin -D < test.msg
> on it.
>
> You'll get a long debug log. I don't really know what the interesting
> part of it is, but you could try posting everything up to (but not
> including) debug: ---- MIME PARSER START ----
Thanks for pointing that out to me. It seems I was sadly mistaken about
this bug, and quite possibly about 290927 as well.
Here's what looks like the relevant info from a debug run on the message
I reported in 290927:
debug: looking up PTR record for '61.52.78.187'
debug: PTR for '61.52.78.187': ''
debug: received-header: parsed as [ ip=61.52.78.187 rdns=
helo=64.26.176.14 by=pyloric.projectile.ca ident= envfrom= intl=0
id=1CqZBF-0001JN-Hv auth= ]
debug: looking up A records for 'pyloric.projectile.ca'
debug: A records for 'pyloric.projectile.ca': 192.168.23.5
debug: looking up A records for 'pyloric.projectile.ca'
debug: A records for 'pyloric.projectile.ca': 192.168.23.5
debug: received-header: 'by' pyloric.projectile.ca has reserved IP
192.168.23.5
debug: received-header: 'by' pyloric.projectile.ca has no public IPs
debug: received-header: relay 61.52.78.187 trusted? yes internal? no
debug: metadata: X-Spam-Relays-Trusted: [ ip=61.52.78.187 rdns=
helo=64.26.176.14 by=pyloric.projectile.ca ident= envfrom= intl=0
id=1CqZBF-0001JN-Hv auth= ]
debug: metadata: X-Spam-Relays-Untrusted:
So in fact, it is correctly parsing the Received header. The problem is
that for some reason, it thinks 61.52.78.187 is a trusted relay. Why's
that? My gut feel is that 290927 is not, in fact, the same as
upstream's 3949.
Ugh.
- Marc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
