INFO: R[5] Client Name DNS Lookup - ns0.myserver.com [217.xxx.xx.xxx] INFO: R[5] EHLO - mail01.myserver.com
WARNING: R[5] Connection rejected - Deny Connection for ns0.myserver.com [217.xxx.xx.xxx] (PTR record does not match HELO/EHLO string)
An aggressive rule bound to reject tons of badly setup legit mailservers.
And to be clear, the fault here is with the badly setup mail servers, NOT with his rule. And an mail admain that whines "I can't follow best practice because whine, sniffle, bluster, blah" needs to get out of the mail business, or get ready to spend a lot of time trying to get his mail delivered.
They tell me it's because the EHLO request doesn't match the DNS Name Lookup......... they suggest you need to set the EHLO response to be ns0.myserver.com too.
Please can anyone help me find out how do I change the EHLO response to match the client dns lookup
We have setup a ptr record to point to both domain names
Also, would it be correct (as per RFC/SMTP standards) for our email to be blocked because EHLO response does not match DNS lookup or is it just a very strict rule for blocking spam.
Just very strict, but they are insisting on "best practice", which is their choice:
IP must have PTR domain name which an A record matching the IP.
HELO domain domain must match the SMTP greeting hostname.
and all 4 hostname above should be the same.
Len
_____________________________________________________________________ http://MenAndMice.com/DNS-training: Atlanta; Orlando; San Jose IMGate.MEIway.com: anti-spam gateway, effective on 1000's of sites, free
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
