Email Standards Project
A friend recently pointed me to email-standards.org, because Internet Mail and its standards are some of my favorite subjects. I was, however, quite surprised when I found out what that web site was all about.
When I hear "e-mail standards", I think of RFC 2822, Microsoft's Thread-Index crap, SPF or maybe the Netiquette.
The "Email Standards Project" is about none of them.
When you go to their homepage, it lists some mail clients and their state
, which is either Excellent
, Average
or Poor
.
I did what maybe everyone would be doing first:
Find my own client, Mutt, in that list.
It wasn't there, although it is in my opinion one of the most standards-compliant clients out there.
So I had a look on what they were testing the clients for, and wondered why they called their test suite acid test, like a famous other one.
Then I found out why.
The project that calls itself "Email Standards Project" is not about e-mail standards, but about the level of CSS in HTML e-mail support in various clients. Their goal is to become a kind of reference for newsletter designers and to push mail client vendors to support more CSS than they do right now.
While I think that this is a nice thing for people who really need it, I have two big problems with the project as it is right now:
- Their website completely lacks information about why HTML mail might probably be a bad thing and how to stop annoying people who cannot or do not want to read HTML in their mails. (Hint: Make all the content in the mail available as plain text as well, don't just display "click here to read this in your browser" or "your client does not support HTML". If the project is about CSS because CSS improves accessibility, then don't forget that plain text is accessibility as well.)
- The project name is just wrong. It should be something like "HTML Email Standards Project" or "Rich Newsletter Formatting Project". E-mail standards are something completely different. On the other hand, Microsoft's company name is as sucky, and they make lots of money. Bloatysoft wouldn't sound too good anyway.
Concerning everything else that project does: Yeah, nice, keep it up. I don't really care, because I hate HTML mail from the bottom of my soul, but if it helps the poor designers who are forced to write "rich e-mail", then so be it. But please, just add some information on how to keep people like me from pulling their hair out because of HTML-only mail.
