digg

umm... duh...

The article points out a problem that should be rather obvious. If anyone who sends HTML e-mail has never heard for programs that don't be default show html e-mail they really are in a world all to themselves. I think the article is a waste of space and unecessary. This to a company sending mass html e-mails is like a wiki-howto that teaches 25 year olds how to breath while sleeping.

since gmails big security hole, I think allowing HTML and CSS should be up to the user. duh.

This part of the article really says everything that needs to be said about HTML emails;

Add a text-based link to a web-based version of your email that will reveal your email in the browser in all its glory.

If you want people to see formatting and images and stuff like that, then send them a link.

I'm working on a system designing templates for permission based email. I keep running into this problem where it is trivial if your email and it's design (with html, css, and images) will display in their email client. It has caused a lot of headaches and I found this article to understand where I'm coming from. I picked up a few tips from this! =)

Just as an aside, I've noticed in the last few minutes here that someone is running through the comments here and giving thumbs-down to anyone who expresses an opinion that is anti HTML in email.

It would be nice if other diggers would counter that and at least bring the dissenting comments back up to +1 where they started.

Digg: solid, well-written article. The images must *enhance* the email, not *comprise*.

HTML email is an atrocity, end of story. Email is for plain text, not rtf, doc, pdf, html, executable scripts, or anything else. If you want to send someone something other than text, that's what attachements are for.

I don't really care if my emails look pretty. I just want the people to read what I'm saying. I don't want them to look at the pretty colors and pictures, if I wanted that I'd send them a website.

HTML does not belong to emails. period.

Agree! HTML doesn't belongs in emails. I mean, who ever wants to send a URL that doesn't get line wrapped! Or wants to reply with changes written in a different color, or wants to use different fonts for program code and discussion?</sarcasm>

We did a regression on CSS with just under 1100 variations, and found that just about 65% of the combinations were found to be acceptable though not identical. Based on the first standard deviation of browsers and platform usage, that amounts to hitting a page display target in about 88% of the cases. Most of our clients find that number acceptable for broad marketing. Others, armed with our analysis, can hit narrower targets (for example a client that sells Mac software is a little more interested in how Safari works than how Netscape works).

When you design better pages, and avoid vertain common pitfalls, you can reach a broader audience than most people think. It's just not as easy as cranking out a heavily formatted page from Front Page and thinking its going to look the same on everyone's browser.

You could, you know, STOP SENDING ***** emails!

@richardyork

You just don't get it. HTML mail is a complete waste of network resources. There are no advantages other than simple prettiness. It's complicated, and renders like crap in most situations. UTF-8 should be the only thing you bother with.

Mutt 1.4.2.1i *mmmmm*

HTML in an email is a plague, much like a capsLOCK key. Get the tools to remove it.
If you need to send me a table, or graphics, or multicolor documents, use PDF.

I think there's definitely a place a for HTML email. It looks a lot more polished than plain text especially for publishing legitimate newsletters where you can achieve a magazine feel.

What I dislike about HTML email is the fact that is gets abused. For example, by spammers who send meaningless emails with hidden HTML tags that log your page views and then propogate your email address to all of their mailing lists and their affiliate's lists etc etc. It's the invasion of privacy that sucks.

Good article. I don't think CSS in HTML emails is nearly as important compared to websites. But it definitely helps for easier updates and cleaner code. It will be nice when all email clients catch up with full CSS support (including positioning).

And regardless on how you personally feel about HTML emails, you know your client/supervisor/manager or CEO will want them, so you might as well get use to it.

- my first digg.

Sigh.

For the record, this article was not written as a debate on HTML email vs. Plain Text. It is about how to write HTML emails well. The issue of whether or not to do it is outside of the scope and should be moot by now. HTML emails are not going to go away. Sorry, not going to happen. The best we can hope for is improvements in security, standards, methods and implementation. Cope.

* Yes, I know that HTML email gets abused by spammers. So does every other exploitable resource in the web-connected world. It's a profit-motive thing.

* Yes, HTML email complicates things and renders differently in different environments. Too bad. Code it, test it, adjust it, work it.

There are legitimate uses of HTML email. Really, there are. If you want to live in an all-text world, hey, go for it. You can do it. But your boss probably doesn't. Neither does the marketing department, nor do the majority of consumers.

As for me, my email subscriptions are always *plain text*. It's my preference. But I don't pretend that my preferences are the same as everyone else's.

Fa-sho...

Nice indeed. Is anyone able to open this link?

I think HTML emails have their place. Adding nice enhancing imagery and color really allows the reader to be (potentially) more efficient at digesting the information. For certain kinds of emails, I find it similar to browsing the web with CSS and images turned off. Sure, it's possible, but it's certainly not very fun and definitely more difficult to scan the pages looking for what you need.

Plus, it's nice to add a little subtle branding to your messages.

So, my important keywords here were enhancing and subtle.

At any rate, I think the article was quite helpful for people who haven't ever had to deal with rich emails before.

As I'm new to writing HTML formatted emails, this article provided a good overview. Now I check what my emails look like in my browser with images turned off. As far as checking compatibility in multiple email clients, I decided to use MailChimp.com as my Newsletter manager/bulk mailing service. They have a fantastic tool (Inbox Inspector) for automatically checking compatibility in the most widely used mail clients AND firewalls/SPAM filters. They go further to provide you with fixes. How disappointing it would be for a customer to subscribe to my newsletter and not be able to receive it because my email was intercepted by their SPAM filters. Here's a link if this is helpful to anyone else: http://www.mailchimp.com/add-ons/inboxinspector/

when images blocked i do this way

http://www.weather.com/search/partner?Keywords=%22 ...
http://www.medicalnewstoday.com/newssearch.php?key ...
http://www.weather.com/search/partner?Keywords=%22 ...
http://www.medicalnewstoday.com/newssearch.php?key ...
http://www.medicalnewstoday.com/newssearch.php?key ...