Check these headers and the Spamassassin 2.43 results (real email addresses
DELETED):
Received: from out005.verizon.net ([206.46.170.143] verified)
by ctgusa.com (CommuniGate Pro SMTP 4.0.1)
with ESMTP id 1052087 for DELETED; Mon, 23 Dec 2002 12:27:03 -0500
Received: from 2hgnl01 ([138.88.118.143]) by out005.verizon.net
(InterMail vM.5.01.05.20 201-253-122-126-120-20021101) with ESMTP
id <20021223172703.KMEC19422.out005.verizon.net@2hgnl01>
for <DELETED>; Mon, 23 Dec 2002 11:27:03 -0600
Message-ID: <014401c2aaa8$be804460$5916fea9@2hgnl01>
SPAM: RCVD_IN_OSIRUSOFT_COM (1.4 points) RBL: Received via a relay in
relays.osirusoft.com
SPAM: [RBL check: found
143.118.88.138.relays.osirusoft.com., type: 127.0.0.3]
SPAM: X_OSIRU_DUL (2.6 points) RBL: DNSBL: sender ip address in in a
dialup block
SPAM: X_OSIRU_DUL_FH (2.4 points) RBL: Received from first hop dialup
listed in relays.osirusoft.com
SPAM: [RBL check: found
143.118.88.138.relays.osirusoft.com., type: 127.0.0.3]
(I upped the OSIRU scores to force a hit.)
Seems wrong. I see a Verizon dsl user at 138.88.118.143 relaying through the
proper Verizon smtp host at 206.46.170.143. So why did SA do a check on the
first hop at 138.88.118.143?
--
John McCauley
CTGi, Oakton, VA, USA
Www.ctgusa.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
