Special Header Processing
The X-Campaign header is a special feature of Easy-SMTP that allows message recipients to be tagged with a CampaignName in delivery reporting results. For example, if you're using Easy-SMTP to send a welcome message to new users of your forum, you can set 'X-Campaign: Forum Users' in your message and recipients will be added to the 'Forum Users' list in your account.
To use X-Campaign, just set X-Campaign: [CAMPAIGN NAME] in the headers of your message.
... Date: 24 July 2011 08:00:00 X-Campaign: Forum Users Subject: Welcome to the Acme Company forum! ...
The X-Tracking header is used to enable link tracking in a message. Link tracking is not enabled for messages by default, the X-Tracking header must be sent with a value of '1' for tracking to be turned on for a message.
... Date: 24 July 2011 08:00:00 X-Tracking: 1 Subject: Welcome to the Acme Company forum! ...
The x-dkim-options header is used to specify the domain with which the message should be signed. It requires at least the 's' and 'i' values be specified.
See here for Custom DKIM signing/registration.
... Date: 24 July 2011 08:00:00 x-dkim-options: s=k1; i=[email@example.com] From: firstname.lastname@example.org Subject: Welcome to the Acme Company Forum!
Separating message channels
If you're sending both transactional and marketing messagse - whether your marketing messages are sent from Reachmail's UI or not - it's a good idea to distinguish between message types as much as possible. Aol, Gmail and Yahoo all recommend individualzing marketing and transactional channels. The simplest way to do so is by making use of Domain Keys Identified Mail (DKIM).
DKIM uses public / private key pairs to authenticate and identify messages. Using one signature for transactional and one for marketing messages helps mail providers differentiate and identify your messages.
To setup signing of your messages contact email@example.com and request DKIM keys for your sending domain. You will receive a 'transactional' and a 'marketing' key. They keys should be installed in the DNS of your sending domains on a sub-domain for the appropriate channel. In the example below, the sub-domains 'transact' and 'messages' are used to identify the channels.
_domainkey.messages.domain.tld IN TXT "t=y; o=~;" k1._domainkey.messages.domain.tld IN TXT "k=rsa; p=<marketing key>;" _domainkey.transact.domain.tld IN TXT "t=y; o=~;" k1._domainkey.transact.domain.tld IN TXT "k=rsa; p=<transactional key>;"
Once this setup is complete, you'll need to remember to always use the approriate domains for the channel you're messaging from and include x-dkim-options in the message header. In other words, when sending transactional emails, always send from <some.user>@transact.domain.tld including the header x-dkim-options: s=k1; i=<some.user>@transact.domain.tld.
Note: The sub-domains should also be capable of routing incoming messages. If that's not possible for some reason, make sure to specify a valid Reply-To address.
Text vs. HTML messages
By default, Easy-SMTP will treat all incoming messages a plain text unless HTML is specified in the Content-Type header. If you are sending HTML messages but are seeing the HTML code in the message body when viewing the message in a mail user agent, your sending mechanism is likely omitting the Content-Type header.
Subject: New forum posting Content-Type: text/html