I have now run into 2 cases that my clients are getting bounce backs from spam filters because of an incorrect name (or Inverse DNS) when it identifies itself trying to deliver email. This is a new developement and is starting to spread it seems. In this particular case, I have a Win 2k3 server, with Exchange 2k3. The server is on the domain and is newman.sell-thru.local. My MX record is mail.sell-thru.com at 207.8.51.58 with a reverse dns entry of mail.sell-thru.com. The problem as stated by Grande isas follows: <newman.sell-thru.local #5.7.1 smtp;550 5.7.1 abc@grandecom.net... Denied. Please see http://www.grandecom.net/support/faq/?cat=30&ip=207.8.51.58> When i look at the link it tells me that my Inverse DNS is incorrect. That the fact it identifies itself as newman.sell-thru.local instead of mail.sell-thru.com it is being rejected. This is the second time I've come across this in a month, and I'm lost. Is there a setting on Exchange that I'm suppose to tell newman that when it talks to the outside world to identify itself as mail.sell-thru.com? If I should be posting this in DNS area, I apologize, but since this only partains to my exchange servers I am posting it in here. Thanks for any insight. Dennis

Hi, Please open ESM, expand Servers, expand Protocols, right click Default SMTP Virtual Server, select Properties, in the Delivery tab, click Advanced button, change the Fully-qualified domain name option as mail.sell-thru.com, click OK. After that, please restart SMTP and Microsoft Exchange Routing Engine. Then check this issue. Thanks Allen

Thanks Allen, this is correct. To add to this I was then able to check this using telnet newman 25, and it responded with mail.sell-thru.com. I did find an article at http://www.amset.info/exchange/dnsconfig.aspthat was very helpful. Thanks for the response!!!Dennis