Skip to main content

Adding an X-header in an Exchange Routing Transport Agent in Exchange 2007

This week I’ve been looking at Transport Agents which are the replacement to Transport Event Sinks in Exchange 2007. After the initial struggle of finding some decent information to get going these Agents are surprising easy to code and have a bunch of powerful functions that are more readily available then they were when compared to SMTP transport Event Sinks.

Getting Start info

If you’re looking for info on getting start the first place is this simple sample . One piece of advice is before you look at installing a Transport Agent making sure you know how to disable or remove one first.

There are two types of Transport Agents Routing and SMTP which one you use really depends where in the Transport Pipeline you want to intercept the message. I choose a Routing Transport agent because I wanted to be able to add an X-header to a message regardless of whether the message arrived via SMTP or if it was sent locally on a Mailbox server (if you are looking to do this in a SMTP Transport agent there is a X-header Sample in the Exchange 2007 SDK). The Transport Architecture document describes the process of Mail routing via the Hub server.

Once you get over modifying the subject you may want to start modifying the rest of the message this is where it starts getting hard and the information starts to get a little scarcer. Depending on what type of message you’re dealing with you may need to cope with MIME and TNEF formats. The later being a slightly harder thing to deal with for serialized messages most of the time MIME should be enough. So I would recommend reading the following MIME Architecture document from the SDK. Being able to deal with a serialized message in the MimeDocument Class is pretty cool and very powerful. You should always be carefully that any modifications you do make to a message aren’t going to mean that message breaks the Email RFC’s.

Getting down to the code

There are a number of different events you can hook into with a Transport Agent the one I was interested in was the OnSubmittedMessage. The event occurs just after the message is submitted because I only want to modify the headers content conversion shouldn’t really be an issue. The code is rather simple it first looks to see if there is a Xheader within the message already with the Name i want to use. If there isn't it creates a new Text header and inserts it before the last header in the current header list in the root MIME document.

I’ve put a download of the Transport Agent here the the main code itself is the following Event Handler

public class XHeaderRoutingAgent : RoutingAgent
{
public XHeaderRoutingAgent()
{ base.OnSubmittedMessage += new SubmittedMessageEventHandler(XHeaderRoutingAgent_OnSubmittedMessage);
} void XHeaderRoutingAgent_OnSubmittedMessage(SubmittedMessageEventSource esEvtsource, QueuedMessageEventArgs qmQueuedMessage)
{
MimeDocument mdMimeDoc = qmQueuedMessage.MailItem.Message.MimeDocument;
HeaderList hlHeaderlist = mdMimeDoc.RootPart.Headers;
Header mhProcHeader = hlHeaderlist.FindFirst("X-MyProcess");
if (mhProcHeader == null)
{
MimeNode lhLasterHeader = hlHeaderlist.LastChild;
TextHeader nhNewHeader = new TextHeader("X-MyProcess", "Logged00");
hlHeaderlist.InsertBefore(nhNewHeader, lhLasterHeader);
}

}

}

Labels:

Popular posts from this blog

Export calendar Items to a CSV file using Microsoft Graph and Powershell

For the last couple of years the most constantly popular post by number of views on this blog has been  Export calendar Items to a CSV file using EWS and Powershell closely followed by the contact exports scripts. It goes to show this is just a perennial issue that exists around Mail servers, I think the first VBS script I wrote to do this type of thing was late 90's against Exchange 5.5 using cdo 1.2. Now it's 2020 and if your running Office365 you should really be using the Microsoft Graph API to do this. So what I've done is create a PowerShell Module (and I made it a one file script for those that are more comfortable with that format) that's a port of the EWS script above that is so popular. This script uses the ADAL library for Modern Authentication (which if you grab the library from the PowerShell gallery will come down with the module). Most EWS properties map one to one with the Graph and the Graph actually provides better information on recurrences then...
Read more

Downloading a shared file from Onedrive for business using Powershell

I thought I'd quickly share this script I came up with to download a file that was shared using One Drive for Business (which is SharePoint under the covers) with Powershell. The following script takes a OneDrive for business URL which would look like https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filename.txt This script is pretty simple it uses the SharePoint CSOM (Client side object Model) which it loads in the first line. It uses the URI object to separate the host and relative URL which the CSOM requires and also the SharePointOnlineCredentials object to handle the Office365 SharePoint online authentication. The following script is a function that take the OneDrive URL, Credentials for Office365 and path you want to download the file to and downloads the file. eg to run the script you would use something like ./spdownload.ps1 ' https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filen...
Read more

Sending a MimeMessage via the Microsoft Graph using the Graph SDK, MimeKit and MSAL

One of the new features added to the Microsoft Graph recently was the ability to create and send Mime Messages (you have been able to get Message as Mime for a while). This is useful in a number of different scenarios especially when trying to create a Message with inline Images which has historically been hard to do with both the Graph and EWS (if you don't use MIME). It also opens up using SMIME for encryption and a more easy migration path for sending using SMTP in some apps. MimeKit is a great open source library for parsing and creating MIME messages so it offers a really easy solution for tackling this issue. The current documentation on Send message via MIME lacks any real sample so I've put together a quick console app that use MSAL, MIME kit and the Graph SDK to send a Message via MIME. As the current Graph SDK also doesn't support sending via MIME either there is a workaround for this in the future my guess is this will be supported.
Read more
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.