Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an Exchange 2010 environment where there are multiple Edge servers; the FQDN of each server ("serverX.domain.local") is different from the name used in the corresponding public MX record ("").

I have configured each server with two Receive Connectors, one for talking with the Hub servers (which uses the server's real name) and one for talking with the Internet (which uses the server's public name). This works as expected.

Howewer, the Send Connector created by EdgeSync for outbound messages is a global one, shared by all Edge servers; so it can only be configured with a single name to use for outbound HELO commands, or no one at all. If I leave the field blank, each Edge server will use its real (private) name. If I fill it in, each server will use the same name.

Is there any way to configure the outbound Send Connector so that each Edge server uses its public name in outbound HELO commands?

share|improve this question
Short of not using EdgeSync and manually modifying the connectors I don't think so. But reading this:… it seems that you might be able to suppress auto creation and be able to manually specify the send connectors still using EdgeSync, maybe? – TheCleaner Feb 15 '13 at 19:44
up vote 0 down vote accepted

I couldn't find any way to do it, so I'm posting this "it's not possible" as the accepted answer.

If anyone can come up with a better answer, I'll be very glad to accept it...

share|improve this answer

I'm looking for this too. The only way I found is to bind the SMTP connector to a different port, and NAT from the router with a set of IP/port to the connector's specific port... It's ugly but it's working as long as you have a different IP for each domain...

share|improve this answer

Haven't found any built-in way to do this with Exchange but you can do it with a 3rd party product: MultiSendcon allows you to have different outgoing HELO/EHLO domain names depending on the sender email address. You can also use it to route traffic to go out via different local IP addresses or through different smarthosts depending on the sender address or sender domain..

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.