The DEFAULT way that Exchange operates with send connectors is the send connectors are used to control which email goes to which send connector based on the TO: domain. With the CloudPanel Agent it changes this behavior and controls which email goes to which send connector based on the FROM: domain.
So with the Route by Sender product you can send all emails from one domain to a specific send connector and then all emails from a different domain to a difference send connector as long as the domains are different.
By default the TransportAgent.dll.config file has this setting in it:
<add key="RoutingDomain" value="nexthopdomain.com" />
This setting is telling the agent that ALL emails leaving Exchange and going to another domain that *IS* an accepted domain within the Exchange environment to hit the SEND CONNECTOR that has the “Address Space” domain set to “nexthopdomain.com”
For the rest of your domains you will add a new setting for each domain and tell it which send connector to go to. Lets say you want the domain knowmoreit.com to go to a send connector that has teh address space domain set to customfake-knowmoreit.com… then you would add the following line in the config file:
<add key="knowmoreit.com" value="customfake-knowmoreit.com" />
* YOU MUST HAVE A SMART HOST FOR THIS TO WORK. DNS DOES NOT WORK *
Hi Jacob.
Thanks so much the the info. Most of it is what i understand from the original documentation.
I have tried to get it working today but was not as succesfull.
We are trying to avoid it to add a new line to the code for every Domain and then having to restart services during production etc. We currently have over 500 clients so for us to do this is very time consuming.
Currently ClientA can send ClienTB a mail which routs internally. We need those mails to go out via Mimecast and then back in so that we can attach Branding.
Our main objective would be to send all Domains to the same SendConnector which points to the Branding platform and then sends out via SMTP AUTH.
So basically we need:
Clienta – hellocloud.co.za
ClientB – Domain hybridclouds.co.za
Clientc – Domain o-it.co.za
and many more to all point to send connector X which will have a smart host point to the branding server.
I hope that makes sense 🙁
I setup a lab with 2013 and multi tenant setup using the above domains.
With out setup up a send connector, internal mails work 100%
I then install, enable and configure the Transport agent. Restart the Transport Service and mails stops working. NDR, unknown domain.
I then configure a send connector called Cloudpanel and set it to nexthopdomain.com
I leave the rest of the settings as per default. (MX record routing etc)
I then create a send connector for each of accepted domain as per standard configuration all pointing to their respective smart hosts.
This then sends the mails to the queue under “unknown domain”
any ideas?
Thanks so much.
Regards
On your LAB you have to be using a smart host on the send connector. The value for RoutingDomain is the DEFAULT that it sends all internal to internal mail to. That way you don’t have to specify each domain in the config file. You only need to specify extra domains if you want specific domains to go to a DIFFERENT send connector.
Also restarting the transport agent service during production is no problem because it won’t actually affect or be noticable to users.
Please send me screenshots of your Send Connector setup and the config file you setup (support@knowmoreit.com)
