HTML Email Best Practices
July 16, 2008 10:38 AM Subscribe
I've been coerced by a client/employer to start using HTML email messages for communications with our customers. Please help me do this in the most net-responsible way possible (or tell me to burn in the special hell reserved for people who put markup on the SMTP wire)
posted by alan to computers & internet (9 answers total) 13 users marked this as a favorite
I'm looking for advice on "How to be Good" as opposed to "how to sneak around the canned meat filters"
These five things come to mind ...
1. SPF records for all our domains/servers we'll be sending from
2. Multipart email, providing both a text and HTML version
3. Host the images on our servers so we're not wasting their bandwidth
4. Unsubscribe link in the body of the message allowing people to opt out
5. Email indicating who sent the message with a physical address
Are these steps still considered standard best practices? Are there other steps I can/should take? Custom email headers that should be set outside of of "From", "To", "Reply-To"? Is there unsub info that should be put in the headers?
Any help or a nudge in the direction of a good resource on this would be appreciated.
Finally, Yes. I know. I use mutt and Mailsmith for my personal email. I'm not a fan of HTML email. That battle was lost a long time ago.