Q

Exchange email sent to a domain using SPF authentication is returned

Learn how to properly set up an Exchange Server environment to route SMTP traffic through an external spam and virus filter to avoid email routing snafus.

Our incoming and outgoing email goes through an offsite spam/virus/content filter. We are using network address translation (NAT) to map our internal network (Exchange 2000 Server) to an external public IP address. All SMTP traffic should flow between the external IP of the Exchange server and the offsite IP address. Our MX record points to the offsite address. The Sender Policy Framework (SPF) is configured with the offsite IP. Email traveling this route goes to all domains including those using SPF authentication.

Everything I've mentioned above is working fine. We are running a sniffer on our network gateway, which displays SMTP traffic between the Exchange server and the offsite server. However, it appears that some SMTP traffic is sent directly from the external network gateway IP to the destination domain IP.

Email that is sent directly to a domain using SPF authentication is being returned, since the SPF addresses do not match. If the destination domain is not using SPF, then the email is able to get through. Internal clients using Microsoft Outlook are not the problem.

If multiple email messages are sent, one will go through the gateway and the other will go through Exchange Server. Email sent to AOL.com, Yahoo.com, etc., tend to go out through the gateway instead of the Exchange server. Why is this happening?

Thank you for the very clear summary of the problem you are experiencing. It sounds like you may have another Exchange server that is attempting to use DNS to route messages. All Exchange servers should use the smart host specified on your SMTP connector, which should be configured to point to the external mail security service. Note: Until you create an SMTP connector, this is the default behavior in Exchange 2000 Server and Exchange Server 2003.

You can create a firewall rule to prevent all servers -- with the exception of the SMTP host -- from sending outbound mail through port 25. You should then begin to see mail queue up on the offending Exchange server.

If you don't want to go to that extreme, you can use Winroute.exe on your Exchange server to extract the link state information to verify external mail routes. Based on the configuration you described, all outbound mail should be going to a smart host at the service provider site. Also, you should enable message tracking on your Exchange servers so that you can track the messages to see where they are being routed.

Do you have comments on this Ask the Expert Q&A? Let us know.

Ask an Exchange Server question in our forum.

This was first published in September 2008
This Content Component encountered an error

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchWindowsServer

SearchEnterpriseDesktop

SearchCloudComputing

SearchSQLServer

Close