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.
Thank you for releasing this. This is extremely helpful when we are in the middle of migrating a new client to hosted exchange. now we can still email the client at their existing exchange server – and bypass the local exchange email.
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?
Hi Jacob
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:
For example:
administrator@hellocloud.co.za sends a mail to peter@o-it.co.za.
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 peter@o-it.co.za 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 (peter@o-it.co.za)
The domain name in the email address is incorrect. Check the address.
Really hope that you can assist.
Regards
