Scoped Send Connector or Configure Sender Based Routing? - Smarthost conundrum based on internal senders email address.
Thursday, December 01, 2011 5:47 PM
I've been asked to set up routing to two different smart hosts based on the internal senders email address in a single AD Domain but across different AD sites. I have AD site one which basically has all email routing out via the internet. My new site, Site 2 has a need for email to be sent to through a different smart host on a secure email system.
The second AD site has it's own hub transport and mailbox server. Users from site 2 have a different email address than those in Site 1 and all their email needs to route through a different smart host than those users in site 1.
My first thoughts were should I create a scoped send connector for the hub transport on site 2 that uses smart host 2 so that all email (*) from that site will use this connector and therefore not go anywhere near site 1 regardless of the senders email address being used? Likewise as it is a scoped connector site 1 would not even know that there was a connector at site 2 and would not use it. I would expect site 1 to carry on as normal.
Then I have read that whilst Exchange 2007 and 2010 does not have anything in the GUI or Powershell to configure sender based routing it can be programmed to do so. I saw an article on another site that basically runs some C# code which configures the transport service to check the senders address for a variable and if it matches, push that message to a send connector of a made up name domain that is configured to use the smart host that you want. Whilst it all looks rather funky, I'm a C# novice and modifying Exchange DLLs sounds rather too scary.
Would the scoped connector work better as they are different CAS/Mailbox/Transport servers in different AD sites? Well I ask the question would it work at all? I don't have a pre-prod to test any of this out!
Thursday, December 01, 2011 6:45 PM
There is no sender based routing in 2007/2010. There are 3rd party products you can buy. Some are free with routing agents.
See this for some alternatives. http://social.technet.microsoft.com/Forums/en-AU/exchangesvradmin/thread/6974a39d-2b74-4185-ac1c-29ee698b9ce6
However, as you have 2 AD sites, each with their own HUB, andit happens that users at each site have different email addresses, then I would consider a scoped connector for each site as you have mentioned. This should work.
Monday, December 05, 2011 12:37 PMThanks Sukh, the scoped connector seems the most sensible option. I've got it all setup for testing on Wednesday afternoon. I'll let you know how I get on.
Sunday, December 11, 2011 4:06 AMModerator
Tuesday, December 13, 2011 3:12 PMHi there. Still a work in progress as I need to make changes to firewalls but I'll keep you posted on this one. Next test is due on Thursday. EDIT: Still a work in progress I'm afraid!!!
Tuesday, January 22, 2013 12:30 PM
Hi, You can make it with combination of Contact, Transport Rule and Send Connector.
1. Create a Distribution Group(Ex. ABC-Users@yourdomain1.com) and add members into the group.
2. Create Contact with dummy domain name (Ex. abc@TestRelay.com)
3. Create a Transport Rule as below:
“From a Member of "Distribution Group(Ex. ABC-Users@yourdomain1.com)"
redirect the message to to “contact (Ex. abc@TestRelay.com)"
4. Create a Send connecter to forward email having domain name of the contact to specific gateway
Ex: Address Space = TestRelay.com
Monday, February 25, 2013 6:19 PM