What most of them are doing is looking at the PTR record of the sending IP and compare it to what you announce in your HELO. And making sure they match. They do this because it is very effective at weeding out zombied machines. The SMTP HELO of the infected machine is not going to match the PTR of the IP.
What they are doing is suggested by the RFC's, but not required. So this is an easy fix for you. Just look at the PTR of each of your public IP addresses that your email servers use. Then go into Exchange and adjust the HELO to match. Hopefully you have exchange 2003, it is a really easy fix. It is in the SMTP properties as 'masquerade domain' JK -----Original Message----- From: On Behalf Of April Fleming Subject: MX records and Reverse DNS lookup It is my understanding that many email servers will do a reverse dns lookup on incoming email to ensure a valid domain when sifting out spam etc. Thus, I must ensure that my email server which is sending out email must have an MX record so the Reverse DNS lookup will suceed. What I would like to know is whether the weight given the MX record will affect the reverse dns lookup. If I have email being sent from email server 3 (don't ask why, it isn't the point :) and that email server is weighted 15, will the email servers I am sending out to accept the email? Example MX 5 Email server 1 MX 10 Email server 2 MX 15 Email server 3 Thank you! April _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
