Update on FixOutlook.org campaign

Last week I mentioned that the Email Standards Project has started a website (FixOutlook.org) and a twitter campaign to pressure Microsoft to use a HTML compliant rendering engine for Outlook. Currently Outlook uses the HTML engine in MS Word and that engine is not fully compliant with of the HTML standards as published by W3C.org.
Microsoft did reply to the FixOutlook.org campaign on the MSDN Developer blog. The money quote, which they bolded for emphasis in the original post:

There is no widely-recognized consensus in the industry about what subset of HTML is appropriate for use in e-mail for interoperability.

The thing is, if Microsoft had built a compliant HTML rendering engine into Word, it wouldn’t matter which subset the Outlook developers wanted to implement, everything would all render correctly.
This point was more eloquently made by the Email Standards Project in their reply to Microsoft.

[W]e are in no way advocating that Microsoft shift from using Word to create or render HTML emails. We’re asking that the HTML produced by the Word engine be standards compliant. This in turn will ensure that the engine will correctly render standards-based emails.

As anyone who has attempted to export a Word document to HTML knows, the Word HTML engine is horribly non-compliant and generates HTML that even Internet Explorer renders wrong sometimes. There are a number of programs out there that convert Word HTML to W3C compliant, readable HTML. Sadly, Microsoft has never seemed to have any interest in writing a correct HTML engine for Word.

Related Posts

Changes at Comcast

I can usually tell when one of the ISPs makes some change to their incoming spam filtering just by my call volume. The past few weeks the ISP in most of my calls has been Comcast. And, what do you know, they have made changes to how they are filtering email.
According to their bounce message, Comcast is using ReturnPath’s proprietary SenderScore product to filter mail. Reports on thresholds vary, but IPs with SenderScores of 70 and below have been blocked with messages similar to:

Read More

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.

Read More

Blocklists and standards

I received a comment this morning on my post about e360 v. Spamhaus, which I think brings up a point that deserves a post of it’s own. Skinny says:

Read More