Support Forums

Route By Sender Tra…
 
Notifications
Clear all

[Solved] Route By Sender TransportAgent

13 Posts
2 Users
0 Likes
4,694 Views
0
Topic starter

Hi,
today we made a testinstallation with a simple config:

<add key=”DebugOn” value=”False”/>
<add key=”RoutingDomain” value=”nexthopdomain.com”/>
<add key=”BlockInternalOutOfOffice” value=”True”/>
<add key=”TestDomain.de” value=”relay_TestDomain.de”/>

We created 2x SendConnectors with RoutingDomain “nexthopdomain.com” and “relay_TestDomain.de”.

Eventlog shows:
Loading settings from configuration file
Attempting to open config file at C:\Program Files\Microsoft\Exchange Server\V15\Public\TransportAgent.dll.config
Default routing domain is nexthopdomain.com
Blocking internal out of office: True
Adding domain mapping for TestDomain.de to routing domain relay_TestDomain.de

All outbound traffic still runs through the SendConnector with “*”. If I disable this SendConnector, all outbound mails stay in queue with error “No connector to route traffic” (translated!?!)

Did we miss something?

5 Answers
0
Topic starter

Now it works!
Our mistake was to remove “*” on the Internet-SendConnector which is the same relay as for “nexthopdomain.com”

The dokumentations ist not realy clear about routing. Routing now works like this:

internal -> external –> “*”
internal -> internal –> “NextHopDomain.com”
internal by Sender xxx –> “relay_xxxx.com”
internal by Sender yyy –> “relay_yyy.com

0

Did you add this transport agent to ALL transport servers?

Netzwerker@syscon.biz Topic starter 2018-01-18 09:16

Test-Environment has only one Ex16

Jacob Dixon 2018-01-18 10:10

Can you set the DEBUG to true and look in the event logs for a test email you send. It should give us more information about what it is doing.

Netzwerker@syscon.biz Topic starter 2018-01-18 10:36

<e067937bfeb3400c8a1b0c8d3c3c7f52@xxxxx.de>:: OnResolvedMessage triggered
Checking the X-MS-Exchange-Organization-AuthAs header from Netzwerker@xxxxx.de
AuthAs header value was Internal. Checking if message is a system message
Message was NOT a system message. Checking if header is in the ignored headers list
Getting the sender email and sender domain.
Message is from email Netzwerker@xxxxx.de with domain xxxxx.de. Checking if sender’s domain is in accepted domains list
Internal domain that we are processing is from Netzwerker@xxxxx.de
Processing total of 1 recipient(s)
From: Netzwerker@xxxxx.de, To: Netzwerker@external.de, Is internal to internal: False, Is to same domain: False
MAPI class is ipm.note

Jacob Dixon 2018-01-18 12:21

It isn’t detecting it as internal to internal mail for that domain. Do you have that domain in Exchange as an accepted domain?

0
Topic starter

This is our Main Test Domain. It is in accepted Domains.

Jacob Dixon 2018-01-19 07:39

We made need to a do a remote session. If your domain is domain1.de and it is an accepted domain which you listed in the XML file, then if a domain is explicitly listed in the XML it will route it to the send connector you setup with the fake domain name *IF* you are emailing to a different domain. If you are emailing from domain1.de to domain1.de then it won’t change that routing

0
Topic starter

The sending domain is not explicitly in the XML, all e-mails from this domain should get through the default sendconnector “nexthopdomain.com”.

We can make a TemViewer Sssion if you want on monday afternoon gmt. Give me an info on our e-mail address …

Jacob Dixon 2018-01-19 10:13

They will only go to the nexthopdomain.com if it is internal to internal. So:

  • Internal to internal between different domains by default will go to the nexthopdomain.com send connector if that is what you configured in the XML
  • If you configured the domain specifically in the XML then it will always send email to the custom send connector you specified
  • If it is internal to external mail flow then it will go out a default send connector (which in your case is *)
Jacob Dixon 2018-01-22 10:00

I’m available from now until the end of the day if you want me to take a look. But keep in mind the transport agent only routes internal to internal domains out the nexthopdomain.com send connector unless you specifically specify the domain in the configuration file then it routes all of them.

0
Topic starter

Sorry, wasn`t in the office yesterday.

Our config should look like:

Default internal-> external –> SendConnector “Internet”
TestDomain.de -> external –> SendConnector “relay_TestDomain”
Test2Domain.de -> external –> SendConnector “relay_Test2Domain.de”

How should the .xml File look like?
The SendConnectors contains “Internet” or “relay_TestDomain” aso. as destinationDomain.

Jacob Dixon 2018-01-23 12:33

Your configuration should have:

<add key=”TestDomain.de” value=”relay_TestDomain”/>
<add key=”Test2Domain.de” value=”relay_Test2Domain.de”/>

You should have two send connectors scoped to relay_TestDomain and the other one scoped to reply_Test2Domain.de.

Let me know if you want to screen share

Share: