The DUL account, relayed through the ISP. The ISP's IP should be checked in the DUL, not the end-user. I agree about all the RFC junk, but Bellsouth.net is not my domain. They are a fairly large (in the Southeast US) ISP and really should have a clue. Unfortunately, they don't. The REPORT showed the 207... address in the DUL list also, and I that is probably the root of the problem.
Thanks for the input anyhow. Dan -----Original Message----- From: Michael Scheidell [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 24, 2007 6:18 PM To: Dan Barker; users@spamassassin.apache.org Subject: RE: Why DUL hit? The reverse dns. (and helo) Received: from hubert382f6e2f (adsl-065-012-175-061.sip.asm.bellsouth.net[65.12.175.61]) by bellsouth.net (frfwmhc01) with SMTP Aol won't accept email from something like that either. To fix: assign a dns name, fwd and reverse, then set it up in your mail server and dns servers. While you are at it, your biggest problems are the RFC ones. Assign a valid postmaster, abuse and make sure your contact info for whois is right. That is a total higher score much larger than the dul list. -- Michael Scheidell, CTO SECNAP Network Security Corporation Keep up to date with latest information on IT security: Real time security alerts: http://www.secnap.com/news _________________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(tm). For Information please see http://www.spammertrap.com _________________________________________________________________________
