To any of you running SpamAssassin 2.60+ with SendMail and spamass-milter
0.2.0 I am curious as to whether the -notfirsthop rules (such as Dynablock)
are working correctly for you. (I'm aware of its move to SORBS) When
SpamAssassin processes email through spamass-milter it's rarely matching
Dynablock and sometimes even falsely matches it. If I take the same email
after it's reached my server and process it manually with SpamAssassin
(spamassassin -D -t < email.txt) then it correctly matches Dynablock. Since
the incoming email is passed to the milter prior to SendMail adding its
Received: headers (to my knowledge), spamass-milter 0.2.0 constructs a
Received: header itself to pass to SpamAssassin so that SpamAssassin can
take the information into consideration. This header is only used by
SpamAssassin as spamass-milter does not send this header back to Sendmail.
Sendmail continues to add its own header as it normally does. I've scoured
the regex code that parses the Received: headers and the specific header
that spamass-milter inserts does appear to match one of the regexes so that
the pertinent information can be parsed.
Here's a sample header of an email that got through. Names and IPs have
been changed somewhat to protect the innocent:
Received: from me (my.cable.address.comcast.net [68.46.27.0])
by spamfilter.mydomain.com (8.12.8/8.12.8) with SMTP id
hBCKiXws021742
for [EMAIL PROTECTED]; Fri, 12 Dec 2003 15:44:45 -0500
Date: Fri, 12 Dec 2003 15:44:33 -0500
From: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
X-Spam-Status: No, hits=-1.0 required=5.0 tests=BAYES_00,DATE_MISSING,
FROM_NO_LOWER autolearn=no version=2.61
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on
spamfilter.mydomain.com
$ host 0.27.46.68.dnsbl.sorbs.net.
0.27.46.68.dnsbl.sorbs.net has address 127.0.0.10
"spamfilter.mydomain.com" resolves to a global IP address, not a private
(reserved) one.
I posted this problem to the list a month or two ago looking for solutions
and despite the responses I did not find anything that solves this problem.
I'm interested now in seeing whether other people are experiencing this
problem (spamassassin called through a milter not working while working when
called other ways). Since Dynablock works correctly when the final email is
processed manually yet does not work when the email is passed through the
milter (and the pseudo Received: header added) I still suspect the problem
may be with parsing spamass-milter's psuedo header, but I've been unable to
determine for sure after looking at SpamAssassin's header parsing code.
All feedback is appreciated.
Thanks.
Brian
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
