My Third-Party Transport Agent Cannot be Triggered. RRS feed

  • Question

  • I created a third-party transport agent, and installed it on my exchange server, but only when I logon MSExchangeTransport service by local system account can the transport agent be triggered. Who can help me, and tell me what's the minimum privilege should be to run my transport agent normally. The transport agent just realize the function of getting the mail object and serializing it.
    Friday, May 20, 2016 9:53 AM

All replies

  • The Transport Agent Server runs under Network Service https://msdn.microsoft.com/en-au/library/windows/desktop/ms684272(v=vs.85).aspx privilege by default which means the directory where you assembly is located needs to allows this account access (this is not allowed by default on user created directories so it need to be added).


    Tuesday, May 24, 2016 4:16 AM
  • Thanks for your reply, I tried it, and gave the full control to network service account, but it didn't work for me.Is it the only condition for this issue?
    Thursday, May 26, 2016 2:34 AM
  • What do you mean 'didn't work', What is the exact error you get ?

    Friday, May 27, 2016 1:57 AM