We wanted to give a bit more insight into the Warning from our SMTP Diagnostic tool about ‘Reverse DNS does not match SMTP Banner’.
The short answer is that the reverse IP address name is not contained in the server HELO or EHLO banner. In the example below, the string “someotherdomain.com” is not found anywhere in the server banner, which is reporting “example.com“. This is only a warning, and in some cases you may have no control over this. However, if you have the ability to make these match, you should. Some mail servers look for this and use it to mark messages you send as questionable. Most mail systems will not reject your messages outright, but this may effect your spam score increasing the likelihood your messages will be marked as spam.
In other words, it is a best-practice you should endeavor to follow. It doesn’t mean you are a bad person or won’t be able to send email.
220 mx.example.com StrongMail SMTP Service at Wed, 09 Sep 2009 17:00:01 -0700
Not an open relay.
0 seconds – Good on Connection time
0.156 seconds – Good on Transaction time
OK – 1.2.3.4 resolves to mail.someotherdomain.com
If you are not sure where to access your SMTP banner in your mail server, read below for some helpful hints. We do not advise making ANY changes to your mail server if you are not the system administrator or confident in making these changes.
Configure SMTP banner Exchange 2003
- Open Exchange system manager.
- Expand your administrative group (”First administrative group” by default).
- Expand Servers.
- Expand “YourServersName”.
- Expand Protocals container.
- Select SMTP container.
- On the right window, right click the Default SMTP virtual Server (Or the name you set your SMTP Server) and select Properties.
- Select the Delivery Tab.
- Click the Advanced button.
- Under the Fully Qualified Domain Name (FQDN) type mail.yourdomain.com (The A/Host record you created in DNS for your mail server)
- Click Apply and OK again to accept the changes
Configure SMTP banner Exchange 2007/2010
- Open the Exchange management console.
- Select the Organisation Configuration container.
- Select Hub Transport container.
- On the right select the Send Connectors tab.
- Right click your send connector and select properties.
- On the General tab under the Set the Fully Qualified Domain Name (FQDN) this connector will… type the A record domain name you created. Which in our case is mail.yourdomain.com. Click OK.
- Under the Server Configuration container click the Hub Transport container.
- In the Right window Select the properties of the Receive Connector under Receive Connectors tab.
- On the General tab under the Set the Fully Qualified Domain Name (FQDN) this connector will… type the A record domain name you created. Which in our case is mail.yourdomain.com. Click OK.
To verify these changes we would recommend using our SMTP Diagnostic Tool again.
Thanks for an excellent tool!
When displaying the warning in question, it might be helpful to include the actual value of the SMTP banner in the diagnostic output. Currently it just warns that it doesn’t match the reverse DNS.
Scratch that, I guess I must be going blind 🙁
Does it show the banner? I must be blind too, because I don’t see it. I changed my banner info in the SMTP properties of my Exchange 2003 server, and then updated all PTR files. I’m still getting the warning but I don’t know what the banner is currently showing.
Once you do the SMTP test on our website you can see the banner. It usually starts with 220 domain.com etc. Your server has the banner masked and that is why you are still receiving the error. For more details on that error check out this forum post: http://www.google.com/url?q=http%3A%2F%2Fcommunity.mxtoolbox.com%2Fforums%2Fviewtopic.php%3Ff%3D5%26t%3D13170&sa=D&sntz=1&usg=AFrqEzf6jcMD3cAyPgn67Qo9H90nAgFh-A
Thank you,
Wendy
Are there directions on fixing this on Mac OS X Lion Server?
Unfortunately we don’t have access to that type of server. If anyone can help Ben out, please feel free to post directions!
The SMTP Tool now shows the change I made. However mail being sent does not.
Is a restart required?