Route by Sender / Transport Agent
This is a transport agent for Exchange 2010 and 2013 that can control the routing on a per sender domain in your Exchange environment.
By default Exchange will never send internal to internal emails out a send connector to the internet. This causes an issue with multi-tenant environments due to some data being leaked such as internal Out of Office messages.
This agent will make sure internal to internal Out of Office messages that are to separate domains never reach the other end and allows you to control which send connector emails from internal to internal or even internal to external go out on. This is especially useful if you use email encryption due to a lot of vendors using different FQDN/Ports to do branding.
If you are interested in beta testing let me know. This product will be for sale for $295 when it is completed.
I was just wondering if this connector will work in this situation.
We have a client which is part of a franchise. We download their emails using pop into exchange and are currently using another route by domain transport agent to send out via their central SMTP server. We are also using website panel and their inter-tenant agent to send inter-tenant emails back out and in.
I am just migrating to Cloud Panel and Exchange 2013. This works for every situation except when one of our other customers wants to email someone in another franchise of the company we do not host. In this case no matter what I do it will always be treated as an inter-tenant email, rather than sent out to the franchise central SMTP server. The email will then bounce saying address not found when it tries to send back into my Exchange.
Will this work by routing any emails sent to the domain configured with its own SMTP server as well as from, before applying the inter-tenant rules to solve this problem?
This transport agent will make every internal to internal email go out the send connector except if to the same domain.
I'm classifying internal to internal as an email FROM a domain in the list of accepted domains and TO a domain in the list of accepted domains.
I had a little trouble following your example but is the problem is both users in the franchise are using the same domain?
We just purchased your transport agent and I have implemented into our 2013 lab. I was wondering if you can maybe assist in clearing something up for me?
we have a hex/multitenant platform. I need to send all mails externally.
Currently all customers have their own Send Connector pointing to Mimecast using SMTP auth.
I need to ensure that all mails go through these send connectors:
firstname.lastname@example.org sends a mail to email@example.com.
Hellocloud.co.za has a send connector
smarthost points to mimecast with username and password
Address space hellocloud.co.za
When I send a mail from administrator@hello cloud to firstname.lastname@example.org I get the following error in queue viewer : Unreachable Domain 2:2:A matching connector cannot be found to route the external recipient. <no matching connector>
I am using the default .dll config. After reading the setup guide again, I created a new send connector and used
addressspace: nexthopdomain.com cost1
Restarted the Transport service.
The mails then leave the queue but the administrator@hellocloud gets an NDR :Delivery Failed to these recipient or groups: Peter Pan (email@example.com)
The domain name in the email address is incorrect. Check the address.
Really hope that you can assist.
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 *
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"
Thanks so much.
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 (firstname.lastname@example.org)