Live data from Hacker News

Use plaintext email

useplaintext.email

11–20 of 345 posts

Re: Use plaintext email

#11
>HTML as a vector for phishing

I would disagree, You can make Text-only links look fairly harmless too. The issue is more often that people do not look at all, even in text-mail, what the link points to, not that they can't see it (plus you can hover and the browser still shows the URL once you open it)

>Privacy invasion and tracking

Only if you use an ancient and outdated client that doesn't block external resources by default or proxies them over another server.

>Mail client vulnerabilities

Only an issue if the client rolls their own HTML renderer. Outlook uses the IE Trident Engine, Thunderbird uses Firefox' engine, Gmail transforms using the Chromium engine internally. That means the email client is usually as secure as the respective browser, unless you use a mail client that rolls their own engine.

>HTML emails are less accessible

Possibly, depends on the sender. You can make them more accessible than Text though because you can prevent the screenreader from trying to read out the link or irrelevant information.

>Some clients can't display HTML emails at all

Most mail clients will usually bundle a text-version of the mail, some MTAs also do this on their own. Doesn't really matter in practise since 99.99% of people use a mail client that can display HTML.

It feels a bit like complaining that people on the highway drive so fast that you can't properly merge into the rightmost lane with your oldtimer car.

>Rich text isn't that great, anyway

And tbh, this last one basically seals it; this is a website made to rant from the personal perspective of someone who blocks mails containing any HTML from their services and has quite the history of throwing people using their lib under the bus over personal preferences.

I don't see how any of this is relevant when even the site itself admits that using a multipart mail with both text and HTML is sufficient, why should I even begin to send plaintext instead of doing that?

Unless your mailclient is garbage, it handles multipart and will understand the mail.

Re: Use plaintext email

#12
post #7
post #2

I would like to read more details about "The former is strongly preferred". Why is plain text preferred and by whom?

Keep reading the article: HTML emails are mainly used for marketing - that is, emails you probably don't want to see in the first place. The few advantages they offer for end-users, such as links, inline images, and bold or italic text, aren't worth the trade-off. and more at https://useplaintext.email/#why-plaintext

Is this true? All the people I interact with professionally are sending HTML email, probably because they all use Gmail.

Re: Use plaintext email

#13
I’d love someone to convince me I’m wrong - but I think we’ve lost this fight.

Years of use of plaintext hostile clients by people who read our emails means bottom posting or inline replies are seen as extremely strange, and impossible when you have one of those “seven email deep” threads forwarded to you. (I know, I know, “snip it down”, but sometimes I just don’t have those minutes in my day ;))

Wrapping as well has given me trouble - I'm not sure what I settled on but I went through a period of having some users see my emails come across poorly formatted. And to that note, IIRC Outlook doesn’t do a passable job with plaintext mail, instead shoving monotype text in an ugly system font. The last time I checked I don’t think it converted > into quoting and just vomited them up.

I don’t know what the solution is beyond reluctantly accepting that we have to both consume AND produce HTML email now, and make tools that do it gracefully.

Re: Use plaintext email

#14
The page is about setting up email clients to send plain text emails, but most of the reasons given why plaintext is preferable are about receiving email. The remaining reasons are either "rich text isn't that great" or are trivially solved by the client (extracting plain text from a rich text email isn't hard on non-marketing emails).

Re: Use plaintext email

#15
post #7

Earlier quoted context omitted.

Keep reading the article: HTML emails are mainly used for marketing - that is, emails you probably don't want to see in the first place. The few advantages they offer for end-users, such as links, inline images, and bold or italic text, aren't worth the trade-off. and more at https://useplaintext.email/#why-plaintext

Is this true? All the people I interact with professionally are sending HTML email, probably because they all use Gmail.

Sure, but are they sending it for a concious choice to prefer HTML, or because it's Gmail's default?

Re: Use plaintext email

#16
post #7

Earlier quoted context omitted.

Keep reading the article: HTML emails are mainly used for marketing - that is, emails you probably don't want to see in the first place. The few advantages they offer for end-users, such as links, inline images, and bold or italic text, aren't worth the trade-off. and more at https://useplaintext.email/#why-plaintext

Is this true? All the people I interact with professionally are sending HTML email, probably because they all use Gmail.

Do they use formatting?

Re: Use plaintext email

#17
post #5

Why is this a Show HN? It's just a web page, isn't it?

Probably because Sir_Cmpwn just made it. Considering his other e-mail-related website[1], I'd say that's why. [1] https://git-send-email.io/

That's not what Show HN is for. I don't submit my articles that way.

It's for things (apps etc.) you can try out. Not for essays.

Re: Use plaintext email

#18
post #8

> Rich text features desirable for end users include things like inline images, bold or italicized text, and so on. However, the tradeoff isn't worth it. Images can simply be attached to your email, and you can employ things like asterisks , /slashes/, _underscores_, or UPPERCASE for emphasis. Well, why bother writing his own post in rich text then? He has headings, bold, links, grey font at the bottom, image. Don't…

The page footer might interest you. It directly answers your question. Quoting "But if plaintext is so good, why is this page written in HTML?" This is a reference document, not an email, you twit.

Fair. I like that minimal formatting there anyway.

But often I have to communicate via email, report on complex issues, etc. It is nice to have some headings, tables, images in there.

Re: Use plaintext email

#19
post #8

> Rich text features desirable for end users include things like inline images, bold or italicized text, and so on. However, the tradeoff isn't worth it. Images can simply be attached to your email, and you can employ things like asterisks , /slashes/, _underscores_, or UPPERCASE for emphasis. Well, why bother writing his own post in rich text then? He has headings, bold, links, grey font at the bottom, image. Don't…

The page footer might interest you. It directly answers your question. Quoting "But if plaintext is so good, why is this page written in HTML?" This is a reference document, not an email, you twit.

But emails can be reference documents too! In fact I would argue most work emails that are longer than a few lines are a reference document of some sort.

Re: Use plaintext email

#20

Earlier quoted context omitted.

Is this true? All the people I interact with professionally are sending HTML email, probably because they all use Gmail.

Sure, but are they sending it for a concious choice to prefer HTML, or because it's Gmail's default?

Does it matter? The default is HTML, the majority of mail is HTML (or atleast multipart). So why does it matter if GMail defaults to what the majority is doing? Everyone (99.9999% of people) can receive and send HTML, so just do that, it's the informal standard for mail now.
Post reply on HN