The Email Standards Project  is a future looking group. We’re working on improving current and future email clients so they render standard HTML and CSS more consistently. That’s the goal, but what about all of us who need to send emails out right now?

We’re often asked for advice on how to get the best results given the current state of the email client market. Here’s our top picks to get you started with building an email that will work well for your readers right now. You’ll notice they are from Campaign Monitor, which is built by the same team that started the Email Standards Project (full disclosure achieved!).

Which CSS styles can I use in my emails?

Our email ACID test doesn’t cover everything, and it is more focused on individual, current clients. For the bigger picture see the Guide to CSS support in email clients (2008).

You may notice some differences, where support is spotty for certain elements and we’ve tested in different ways. Watch out for an expanded ACID test later this year to provide more clarity.

What are the best practices for designing emails?

For general advice on what to put into your emails, what not to, and how to approach it see the Email design guidelines.

Are there tested email layouts I can use?

To save time in working out a structure that does not fall apart in one of the popular email clients, you can start with free, tested email templates that you can take, modify and reuse.

Which email clients are people actually using?

At Campaign Monitor we’ve been collecting statistics from millions of emails sent out, and compiled an email client popularity report (the unsurprising news is that Outlook still dominates).

pFirst there were desktop email clients, with their various differing capabilities. Then webmail clients became popular, making a free email address accessible to just about anyone. Today#8217;s biggest growing area is mobile email clients on devices like the iPhone and Blackberry. /p p When you design and build an email you can#8217;t know for sure which email client will be displaying it for any particular person. To find out the HTML and CSS rendering capabilities of mobile email clients, Gregg Oldring of a href="http://www.mailoutinteractive.com/"Mailout Interactive/a took our a href="http://www.email-standards.org/acid-test"email acid test/a and put it to work. /p p Gregg has a href="http://isendemailforaliving.blogspot.com/2008/12/mobile-email-rendering.html"posted his results on his blog/a and they are well worth checking out. He ran our acid test through a BlackBerry Bold, a BlackBerry Curve, a BlackBerry Pearl, an iPod Touch running the iPhone 2.1 Software Upgrade, an iPhone running 2.2 Software Upgrade, a Treo running Palm OS and a Treo running Windows. /p p a href="http://isendemailforaliving.blogspot.com/2008/12/mobile-email-rendering.html"img src="http://www.email-standards.org/images/uploads/mobile-testing.jpg" style="border: 0;" alt="image" width="400" height="300" //a /p p Gregg#8217;s results provide some interesting details - changes in rendering between iPhone software in 2.1 and 2.2 that actually break some parts of our test, for example. He also goes on to make a couple of suggestions for emailing to mobile clients, basically simplifying and reducing the width. /p p Make sure to click through and see a href="http://isendemailforaliving.blogspot.com/2008/12/mobile-email-rendering.html" the full mobile email results/a. Thanks Gregg for your work! If you#8217;ve run your own tests, we#8217;d love to hear about it, please comment below. /pimg src="http://feeds.feedburner.com/~r/EmailStandardsProject/~4/506669332" height="1" width="1"/

pWelcome to 2009! While most of us are enjoying the marvels and advances of the new millenium, a href="http://www.email-standards.org/clients/"HTML email rendering is still back in the 1990s/a, hanging out with structural tables and inline styles. /p p When we a href="http://www.email-standards.org/blog/entry/stand-up-for-web-standards-in-html-email/"launched/a the Email Standards Project, we had a huge amount of support from people like you, web designers who were sick of having to deal with huge variations in the way their emails looked in the many different email clients. Although many people doubted that we could change things, we all felt something had to be done. /p p Since then, we have worked with a href="http://www.email-standards.org/blog/entry/the-impact-of-longhand-vs-shorthand-css/"worked with Yahoo!/a to improve their (already excellent) results, and talked to a href="http://www.email-standards.org/blog/entry/gmail-appeal-update-we-have-contact/"developers at Google/a about improving Gmail, and a href="http://www.email-standards.org/blog/entry/lotus-notes-update-ibm-responds/"IBM/a about improving Lotus Notes. /p p It#8217;s a slow process, but there is far more useful discussion of HTML email than there ever was before we started, and the signs are there for real change. We want to say thank you to all of you who have blogged about the project, contributed your own findings, spoken to contacts at email client developers, tweeted about us and more. /p p It is your efforts that have got us this far, and we#8217;ll be relying on your help this year too. Here#8217;s a quick outline of what we#8217;ve got planned for 2009: /p ul listrongUpdated, more detailed email client testing/strong #8212; We#8217;re going to extend our testing to cover more elements and design techniques. We#8217;ll also look at adding other popular email clients. However, we#8217;re still not going to test older versions, only the ones which have a chance of being updated./li listrongProjects to get attention from client developers/strong #8212; After our a href="http://www.email-standards.org/blog/entry/project-gmail-grimace-video-live/"Gmail Grimaces/a got us in touch with a couple of Google engineers, we had lots of suggestions to do something similar for the Outlook team. We#8217;ll search for ways to reach the right people./li listrongOpen conversation with email program providers/strong #8212; As far as possible, we want to open up the conversation between designers of HTML emails, and email client providers. If we can understand each other better, we have more chance of things progressing. /li /ul p In broad terms, those are the things we#8217;ll be focusing on. Of course, we#8217;ll continue to keep you up to date with changes in the email rendering landscape through this blog. If you have any suggestions, requests or questions, please leave them in the comments. You can also a href="http://www.campaignmonitor.com/blog/post/2450/email-standards-join-our-faceb/"join our Facebook group/a to keep up to date. /p p Let#8217;s make 2009 a good year for HTML email designers! /pimg src="http://feeds.feedburner.com/~r/EmailStandardsProject/~4/503824315" height="1" width="1"/

If you’re interested, you can grab the new beta by visiting the Windows Live blog. The new version of Windows Live Mail doesn’t seem to be any different in rendering our acid test compared to previous versions since most of the changes seem to be part of their Windows Live Suite. This is good news though since Windows Live Mail is actually a very decent mail application and we can only hope the rest of Microsoft’s mail teams are taking notes.

Just a quick note to mention that my opinion piece in .net Magazine (as mentioned earlier) has now been published on the magazine site. We should see some more interest in the Email Standards Project  from this!

When we first tested .mac, it had a lot of problems. Our email ACID test did not render very well at all, and we ranked support overall as ‘Improvement Recommended’. This was slightly suprising given then excellent rendering abilities of the Mac desktop Mail client.

So after the release of the new Mobile Me, and after the associated outages and glitches, we were very keen to run the test again. The good news is that the results were dramatically improved. Nearly all of the previous problems had been corrected, and the email rendered almost perfectly.

Background colours and images are correct, positioning of elements works well, and even list images show up. The one oddity is what you can see in the thumbnail; headings. We found that while our H1 tag rendered perfectly, H2, H3 and below would not accept styling from a stylesheet in the head.

There’s no obvious explanation for why that would be the case, but during our testing and fiddling we were not able to get it to work at all. Lower level headings remained stubbornly unaffected by margins, background colors, padding and more.

Perhaps someone from the Mobile Me team can explain? Overall though, the rendering is hugely improved, and has earned an ‘Excellent’ rating. This is another great example of how webmail clients don’t need to render poorly.

Thanks to everyone who emailed us about Mobile Me, including Georg Stadler and Stefan Kremer who both sent in screengrabs.

View the full report for Mobile Me.

Our testing with different versions of Lotus Notes has turned up mixed results so far, so we were interested to see that an iPhone version of the widely used software was in the works.

IBM has announced Lotus Notes for the iPhone will be released in 2008. According to the official site, it will “combine with the flexibility and connectivity of the Apple iPhone. To be built on the time tested IBM Lotus Domino Web Access infrastructure, users will be able to quickly access email, calendars, and contacts through the rich Apple iPhone user experience.”

The existing Apple Mail application built in to the iPhone does a very good job of rendering HTML and CSS, so we’ll be watching with interest to see how this new version of Notes does. If you have access to it, we’d love to hear from you once the product is released.

We've tested the major market email clients with our acid test so far, the ones we get the most complaints and questions about. There are plenty of other email programs out there though, on the web and on desktops.

We've received a lot of requests for people to be able to test their own preferred email client, so here's your chance. Just add your email address (the one associated with the email client you want to test) to the list below, and we will send a copy of the ACID test to that address right away.

Please send me your email ACID test

Email:

We're always interested in hearing about email client support for HTML and CSS. In the future, we may well increase our official testing to include other clients too. Thanks again for your support of the Email Standards Project.

We’ve posted about recent changes in paragraph spacing that many people have noticed in Yahoo! Mail. An update on the Yahoo! Mail blog confirms they are aware of some problems.

Just a quick update for those of you concerned about the spacing in HTML emails.  Our engineers have sleuthed out the problem, and a fix will be rolling out in the coming weeks. 

Thanks to the Yahoo! team for being open about these issues and for actively working on them — a model which other email client providers would do well to follow.

Novell Groupwise is the third biggest player in the corporate email market behind Outlook Exchange and Notes. A while ago we heard from a Groupwise product manager at Novell, Alex Evans, who wanted to test against our email acid test. We sent Alex the email, and he soon had some great news for us.

Novell Groupwise, in it’s current version 7, renders the acid test perfectly, which puts it right up with Apple Mail and Yahoo Mail in terms of support for modern HTML and CSS.

This is for the Windows version of Groupwise. The excellent result also applies to the WebAccess version, and although the testing has not been completed, Linux and OSX version are also expected to meet the same levels.

Great job Novell team! We appreciate your efforts in building your product, and also in being prepared to test your client against our emails. We look forward to similar results for some other email clients in the not too distant future!