BLOG

Email standards and formatting

There is a lot of buzz on twitter and the email blogs today about Microsoft’s decision to use the HTML rendering engine from MS Word in Outlook 2010 instead of the HTML rendering engine from Explorer. The people behind the Email Standards Project have set up FixOutlook.org and are asking people to join twitter to and tweet the fixoutlook.org URL to send a message to Microsoft.

I’ve been thinking about this much of the morning, and considering Microsoft’s history with implementation of standards. Microsoft has never really followed many of the Internet standards. They adopt what they like, and create new “standards” that work with MS products. This has worked for them, given their position in the market. Companies and software developers that wanted to interoperate with Microsoft software had to comply with Microsoft, Microsoft never had to comply with them.

I find it extremely unlikely that this effort will cause Microsoft to deviate from their course. Based on Microsoft’s history, the solution is not for Microsoft to change rendering in Outlook, but for everyone else to change how they do things.

Mark Brownlow blogged on the topic, too, and makes another of his insightful points. Email marketers and email designers are not an important user group to Microsoft. Instead, they’re focused on the actual people who use Outlook to send and receive email.

Put your email user cap on. The vast majority of messages you consider truly important are nothing more than text and maybe the odd image or attachment. Mails from friends, family and work colleagues, and simple transactional emails.

Of course there will be exceptions, but the vast majority of “important” messages received by Outlook 2007 users look fine. A few bulk marketing emails may look a little weird as not everyone has adpated to the constraints imposed by Outlook 2007. But do these users care?

In my own case, I prefer emails that actually have useful content without images. My email client defaults to images off, and unless marketers put a little effort into giving me something useful without images, I’m not going to load images. Can’t bother to design something I can read? I’m not going to bother to click “load images” and read your mail. Look at these two mails I received this morning:

Screenshots of mail I received this morning

Can you guess which one I clicked through and made a purchase from?

I’m not going to tell you formatting isn’t important, because clearly it is. But formatting should take a back seat to content and relevancy. Window dressing isn’t going to engage users, content will engage users. A pretty email is just a pretty email. I useful and relevant email, now that’s something recipients want.

Comment:

Your email address will not be published. Required fields are marked *

  • HE.net DNS problems

    Hurricane Electric had a significant outage of their authoritative DNS servers this morning, causing them to return valid responses with no results for all(?) queries. This will have caused delivery problems for any mail going to domains using HE.net DNS - which will include some of their colocation customers, as well as users of their free services - but also will have caused reverse DNS to fail for most servers hosted by Hurricane Electric worldwide, so if any of your mail is being sent from HE hosted machines you may have seen problems. (We're HE customers so we noticed. Still happy with them as a vendor.)No Comments


  • 65.0.0.0/8 DNS issues

    If you're sending email from any address beginning with a 65 - in 65.0.0.0/8 - it's possible you'll see some delivery problems. Something appears to be broken with dnssec signatures for the reverse DNS zone, leading queries for reverse DNS to fail for anyone using a dnssec aware DNS resolver (which is almost everyone).1 Comment


  • Our green bar certificate is going away

    Later today we'll be switching from an Extended Validation ("green bar") SSL certificate to a Domain Validation certificate. This isn't exactly a planned change but I'm waiting for responses from Comodo before I go into it too much. I'll share some more details next week.3 Comments


Archives