Is HTML E-mail Still Evil?
Charlie Campbell asks: "My boss is pretty adamant about getting HTML newsletters to our clients; and, I'm pretty adamant about finding an alternative. I can understand the benefits in HTML mail from a designer's (mine) and marketing standpoint (that of my boss); yet, based on foreseeable issues with recipient software, mail filters, dial-up connections, etc. I feel that the risks outweigh the benefits. We've all heard this a million times... but is it now an outdated concern? Should I trust our client-base to be fully equipped for such a mailer? Should I worry about improper delivery marring our professional image? Is there anyone documenting the issue from a current-day perspective?"
I doubt that it will cause a professionalism problem. Anyone who cannot read HTML emails know that they exist and that they can't read them and will therefore, not think of your company as being non-professional. It is a good idea to allow the recipient to choose whether he wants HTML formatted news or plain-text, but the current position is not as bad as it may seem.
I don't mind HTML email, personally, but when I have a choice, I opt for the plain-text version. I think that's the key--allow people to receive your newsletters, receipts, or whatever in the format they want, and things should be fine.
I'd also default to HTML mailings, simply because the people who bitch loudest about HTML (non-pejorative) are also probably capable of finding the preference for plaintext themselves.
Yes.
Hundreds of thousands of email content publishers ask their users whether they want plain-text or HTML versions. Even if most users don't understand the question, they're used to being asked. Why don't you try that and then just publish one version of your newsletter to each of the resulting lists?
99% of business email is HTML. Nobody cares about the "evil" of HTML mail except a few crusty old geeks. Last I checked, even Mozilla defaults to sending HTML mail.
Keep in mind that business people come from the tradition of using propriety mailers like Lotus ccMail, Lotus Notes, and MSMail, and saw no reason to remove functionality when switching to Internet mail. These people just don't care about the archaic 7-bit Internet olden days. (And, yes, HTML in mail was a design mistake, but as of yet it's the only way to get colored fonts and pictures in your mail, so that's what's used.)
Just make sure include a text/plain part, so if your recpients want to drop the HTML, they have that option.
Whenever I hear the word 'Innovation', I reach for my pistol.
If you're targetting savvy developers (ie, me), then they probably wont read your crappy html mail (and I'd probably unsubscribe even if it were text, but that's really a different issue). But if you were targetting my mom, she'd probably not notice or care. In fact, she might like the html version with its pretty pictures or whatever.
The best way is to send both a text part and an HTML part and let the client decide how they want to see it. I made sure my client automatically shows me the text part if there are both.
-David
There. Now go play some cool javascript games!
The right way to do ethics is to forget stupid dogmas like "HTML email is evil" and base your decisions how your actions affect other people. Like a lot of other technologies, HTML email can be misused; specifically, senders can breach security with script-based malware, and privacy with graphic-based tracking cookies. If you don't engage in these abuses yourself, where's the ethical issue?
If you're concerned about security of your own users, you might tell them, "don't accept HTML email". But even that's serious overkill -- Thunderbird is perfectly capable of blocking security and privacy penetration while still accepting HTML email. Outlook is less impressive that way, but Microsoft software is hardly the gold standard for security.
"HTML email is evil" is standard geek bigotry. We're able to get by with pure-text message, anybody who can't is an asshole. Its time to remember that the whole world doesn't revolve around us.
I get email and news alerts on my pager and phone, html versions are a pain in the ass.
;)
HTML does not belong in emails, unless its porn.
the html coded email is 1/2 of it, and the plain text version saying the same exact thing is the other 1/2 of the email. Thus, you essentially triple the size of each email, if you include all the html tags.
Additionally, even simple graphics will bloat this monstrously when they are encoded into the email. And more than likely the Boss wants an html newsletter because he wants to work some graphics magic.
I have a modest suggestion for Charlie: do up a sample email newsletter with very simple graphics (like maybe the company logo and perhaps one other line drawing), send it to yourself, then print the message source. When you and your boss can see exactly what happens when images are encoded for emailing, then the two of you can come up with a reasonable approach.
But by all means, consider letting your customers choose a plaintext version if they want to keep their inbox trim and svelte.
Putting the html version on the web with a link from a plaintext version is probably a good option for a lot of businesses.