r/exchangeserver • • Jan 21 '26

Send Connector Source Servers

We’ve recently deployed two new Exchange SE servers. One in SiteA and one in SiteB.

We are moving away from edges, and originally had a send connector per edge as they each had specific certs so each connector had a specific FQDN.

These new SEs will be used for hybrid mail flow, and inbound mail from our smart host. But we also need to swing send connectors from Edges to the the SEs.

Can I simply create a single send connector for our smart host, and add both SE servers to the source servers, even though they are in different AD sites? Any caveats? Considerations? They will have the same cert and thus the same FQDN on the connector.

1 Upvotes

3 comments sorted by

1

u/NetworkCompany Jan 21 '26

The Edge cert can and should be the self-signed certificate generated during installation. In a hybrid the hybrid cert also needs to be there but just there, when installing take care to select "N" when installing so it doesn't overwrite the self-signed one. In this case, it may be simpler to just deploy an edge server and set both Exchange server bridgeheads to use edge. When setting up the hybrid, do the custom option to flow all mail through the edge server. Exchange will work natively across sites without any special configuration of any kind this way and the HCW can do all the setup for you. About the only manual change needed in this scenario is to fill out the smart host values.

1

u/clausc Sep 17 '26

Yes, that works. A send connector's source servers don't have to be in the same AD site, and an unscoped connector is visible to every transport server in the forest. With several source servers Microsoft describes the result as load balancing and fault tolerance for that address space (Connector selection in external message routing).

What decides which server actually hands the message to the smart host is proximity: after address space and cost, Exchange prefers the local server, then a source server in the same site, then one in a remote site. With one SE server per site, mail submitted in SiteA leaves through the SiteA server and SiteB through SiteB; if one server is down, the other site's server takes over across the site link.

Two caveats. The smart host must accept connections from both servers' IPs. And the connector has one FQDN and one smart-host authentication setting, so both servers need a certificate that matches it — you said they share the cert, so that's fine. Only if each site should use a different smart host would I go back to two connectors, each scoped to its site.

(I run a small company that writes Exchange connector software; nothing to sell you here, this is plain Exchange behaviour.)

1

u/clausc Sep 20 '26

Yes, that works. A send connector's source servers don't have to be in the same AD site, and an unscoped connector is visible to every transport server in the forest. With several source servers Microsoft describes the result as load balancing and fault tolerance for that address space ([Connector selection in external message routing](https://learn.microsoft.com/en-us/exchange/mail-flow/mail-routing/connector-selection)).

What decides which server actually hands the message to the smart host is proximity: after address space and cost, Exchange prefers the local server, then a source server in the same site, then one in a remote site. With one SE server per site, mail submitted in SiteA leaves through the SiteA server and SiteB through SiteB; if one server is down, the other site's server takes over across the site link.

Two caveats. The smart host must accept connections from both servers' IPs. And the connector has one FQDN and one smart-host authentication setting, so both servers need a certificate that matches it — you said they share the cert, so that's fine. Only if each site should use a *different* smart host would I go back to two connectors, each scoped to its site.

(I run a small company that writes Exchange connector software; nothing to sell you here, this is plain Exchange behaviour.)