Home
This repository shows how to implement various types of Exchange Transport Agents that interacts with the transport pipeline.
Transport Agents can execute at different stages of the Transport Pipeline and, depending on which stage they are called, offer different possibilities. Refer to the picture below to understand what are the transport events which could be enriched by your custom code.
For more details on Transport Agents you can refer to the official Microsoft documentation here.
For the chronologically order list of events that are triggered, please refer to the official documentation here.
In this Wiki you'd find for each sample included in the Transport Agent repository a description of what each does.
The sample includes:
- AutoResponderAgent: Sends an automatic response to emails directed to a mailbox or address that is being deprecated/removed
- DomainReroutingAgent: Rewrite the routing domain to be a differnt one (can be used to re-route traffic via a specific send connector matching the domain name space)
- HeaderAgent: Insert a custom header with a custom value in the header of every message that traverse the mail server
- NDRAgent: Drops Non-Delivery Report (NDR) that contains in the body the word "DELETE"
- RecipientDomainRewriteAgent: For any message sent to an address whose domain part is "contoso.com", it redirect the message to the same recipient on domain "tailspin.com"
- SenderDomainRewriteAgent: For any message received from an address whose domain part is "contoso.com", it changes the sending domain and make the message appear from "tailspin.com"
- TaggingAgent: Redirect a message to somebody+text@domain to somebody@domain, implementing Plus Addressing