Exchange 2003: Two SMTP Connectors (one w/Smart Host, one w/o) Not Working As Expected
Posted on 2013-05-13
We are running Exchange 2003 in a simple environment (one Exchange server, no front-end server). We use the McAfee Email Protection Service (formerly MX Logic) to scan our outbound email, which is accomplished by configuring our SMTP connector to send through a Smart Host that routes all email through McAfee. We have a need to send all emails from one individual directly out to the Internet via SMTP rather than through McAfee. To accomplish this, I have created a second SMTP connector that is configured to "Use DNS to route each address space on this connector." I gave it a higher cost than our primary connector, setup the * address space, and configured the Delivery Restrictions as required to only allow emails from the user in question to send through the connector (and deny them from sending through the primary connector). I did make the necessary change to the registry to process restrictions on the connectors.
The emails sent from that user are most definitely going through the new connector, as I can see in the "Queues" view in ESM. However, viewing the headers of the email on the recipient end reveal that the emails are still going through McAfee. It seems as if they use the correct connector, but still use the Smart Host setting from the primary connector. I have confirmed that I do NOT have a Smart Host configured on the SMTP Virtual Server.
Both connectors are sharing the same Virtual Server. Both also use the same Local Bridgehead server, of course. Do I have to create a second VS specifically for the connector that I want to deliver directly to the Internet? Any other suggestions?
Please let me know if there is any more information I can provide to assist in troubleshooting this. Thanks!