Transport agent compatibility, Exchange 2007/2013/2016 RRS feed

  • Question

  • Hello,

     We have a custom transport agent that was written for us, for use with an Exchange 2007 server, and it uses .NET.   We are planning to do a migration to Exchange 2016 -- First, migrating to Exchange 2013, and then to Exchange 2016.   

     We're not sure if our transport agent, that is running under Exchange 2007, will work, however with newer versions.   It does a fairly simple task of looking for messages with a tag in the subject, and when found, copies the message text and then makes a call to an external database to save the body text.

     Should we expect that the agent would work with 2013 and 2016?  Fortunately we do have the source project for the agent, so we can recompile it if necessary.



    Wednesday, April 13, 2016 2:58 PM

All replies

  • >> Should we expect that the agent would work with 2013 and 2016?

    As a best practices thing no without testing you should not expect a Transport Agent to work the agent should go back to the developer who should then certify it will work on the versions of Exchange your going to upgrade to.

    It will probably work if you enable support for legacy agents but as Transport Agent processes every mail that pass through a Hub server and a Transport agent with an issue will stop mail flow, getting your developer to certify that its all okay and there are no breaking changes would be the recommended way of going about this to ensure you don't have an disruption to the service.


    Thursday, April 14, 2016 6:20 AM