Hello,
I have downloaded the demo of routebysender, but when clicking the “Install” button and after “Please wait” it goes to “Stopped” (See picture)
No transport agent “RouteBySender” is added.
I am using Exchange server 2016 on Windows server 2016.
Any ideas?!
That doesn’t look like our route by sender product. I think you may have someone elses product.
I thought that it was the same….sorry.
Is it possible to have a demo of your product?
In a “DAG” setup, do I need This product on every server?
Jacob Dixon 2018-10-16 07:06
All transport agents will need to be installed on all transport servers.
Jacob,
I bought the RouteBySender but getting an Error (see picture)
Jacob Dixon 2018-10-17 06:24
There are two downloads. One for 2010 and one for 2013/2016. Also you need to run the Exchange shell as administrator or it won’t work.
Can you tell what version of Exchange and what CU you are on?
Jacob Dixon 2018-10-17 06:25
Another thing you may have to do is right click the DDL and go to the properties and choose Unblock. Windows may be blocking it due to it coming from another machine
Jacob,
I’m on 2016 CU 10 on Windows Server 2016.
I also unblocked the zip file, but did this after your post and getting the same error.
It is not possible to delete the TransportAgent.dll from the “Public” Folder.
Jacob Dixon 2018-10-17 06:48
Can you email me at jdixon@knowmoreit.com and let me remote in and look?
Before we do that did you setup the config file first?
Jacob,
The only setting i changed : <add key=”RoutingDomain” value=”*” />
Access4IT Topic starter
2018-10-17 06:56
I guess that it is possible to set a smarthost later through ECP?
Jacob Dixon 2018-10-17 07:00
You should setup the send connectors or set the InternalRoutingOn to False until you are ready. You could test by putting a domain in the config with the InternalRoutingOn set to False.
Jacob,
It works now!! Great…
Internal Out of Office is dropped. Is it possible that the external is send out?
Jacob Dixon 2018-10-18 09:25
No, unfortunately we do not have a good way to stop the OOF, then extract the external OOF and send that.
Is it correct when setting InternalRoutingOn to True that internal Out of Office are send again to internal tenants
Jacob Dixon 2018-10-18 09:25
No, setting InternalRoutingOn will process all emails that are internal (meaning from an accepted domain in Exchange to an accepted domain in Exchange if it is to a different domain name). If you turn this on you must have a send connector scoped to the default routing domain setting in the config.
Jacob,
When turning InternalRoutingOn to True and set the scoping on my send connector to the same as the config RoutingDomain still getting the internal OOF.
Am i missing something?
Jacob Dixon 2018-10-19 09:55
You can turn on the debug key to see more information in the event viewer. Turning on InternalRoutingOn just makes it process domains not specifically listed but ONLY for emails that are sent from and to accepted domains on your environment. Now, if the email from and to is the to the same domain then that will be allowed through, well because you would want it to be.
Hello,
It doesn’t matter which setting i make in the config (InternalRoutingOn: False/True) Allways getting as shown in the picture. OOF messages are dropped btw…
Do i need to disable these?
