blob: 38967cdedc4811a103c8b68c202cefeb04cb2c71105ea3d9e72614521c4df255 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
---
title: "[Website] Use Plaintext Email"
date: 2022-09-28T00:00:00
draft: false
makerefs: false
---
In October of 2020, I wrote "Using Email"[1], an entry about how to get the most out of email. If I rewrote it today, I'd mention the email guide at the website useplaintext.email[2], which teaches good email etiquette.
A lot of what is considered good etiquette just boils down to pointless and often oppressive cultural expectations. For instance, not putting your elbows on the dinner table, excusing others for sneezing, asking a woman's parents for permission to marry her, and store clerks being forced to stand rather than sit.
useplaintext.email promotes the good kind of etiquette though, the etiquette for which there's good reason to follow. I won't reiterate the information that's already on the website. I encourage everyone to just go directly to the website.
My email client intentionally doesn't render HTML since I don't believe there's an HTML renderer out there that's safe to use in an email client. So HTML emails sometimes cause me problems.
I don't mind getting emails from people who don't follow email etiquette as long as the emails are in plaintext and written in English or Spanish. What bugs me is getting HTML-only emails with so much HTML I can't even find the relevant information. These kinds of emails usually come from businesses/online services. Usually I can grep the right keywords to find what I need, but sometimes not.
I hope email etiquette becomes more standard so these inconveniences go away. Since most users stick to program defaults, I think the burden is mostly on developers of email clients and email server administrators to make this change.
Link(s):
[1: Using Email](/2020/10/29/using-email/)
[2: Use Plaintext Email](https://useplaintext.email)
|
