2019-07-23 23:59:08 +02:00
|
|
|
<!doctype html>
|
|
|
|
|
<html>
|
|
|
|
|
<head>
|
|
|
|
|
<meta charset="utf-8" />
|
|
|
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
|
|
|
<title>Use plaintext email</title>
|
|
|
|
|
<style>
|
|
|
|
|
body {
|
|
|
|
|
max-width: 800px;
|
|
|
|
|
margin: 0 auto;
|
|
|
|
|
font: 11pt monospace;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
ul li {
|
|
|
|
|
margin: 0.5rem 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.muted {
|
|
|
|
|
color: grey;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
pre {
|
|
|
|
|
padding-left: 1rem;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.breakdown {
|
|
|
|
|
display: flex;
|
|
|
|
|
justify-content: space-between;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.breakdown span {
|
|
|
|
|
padding: 0.5rem;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.green { background-color: rgba(0, 200, 0, 0.5); }
|
|
|
|
|
.green::before { content: '✓ '; }
|
|
|
|
|
.red { background-color: rgba(255, 50, 50, 0.5); }
|
|
|
|
|
.red::before { content: '✗ '; }
|
|
|
|
|
</style>
|
|
|
|
|
</head>
|
|
|
|
|
<body>
|
|
|
|
|
<h1>Use plaintext email</h1>
|
|
|
|
|
<p>
|
|
|
|
|
There are two main types of emails on the internet: plaintext and HTML.
|
|
|
|
|
The former is strongly preferred. This guide is brought to you by
|
|
|
|
|
<a href="https://sourcehut.org">Sourcehut</a>, an online platform for
|
|
|
|
|
software development which utilizes plaintext emails for many features.
|
|
|
|
|
</p>
|
|
|
|
|
<h2>Table of Contents</h2>
|
|
|
|
|
<ol>
|
|
|
|
|
<li>
|
|
|
|
|
<a href="#why-plaintext">Why is plaintext better than HTML?</a>
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<a href="#recommended-clients">
|
|
|
|
|
Recommended email clients for plaintext users
|
|
|
|
|
</a>
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<a href="#other-clients">
|
|
|
|
|
How to set up plaintext with other email clients
|
|
|
|
|
</a>
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<a href="#etiquette">Etiquette recommendations for plaintext emails</a>
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<a href="#implementation-recommendations">
|
|
|
|
|
Recommendations for software which sends emails
|
|
|
|
|
</a>
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<a href="#contribute">How to improve these recommendations</a>
|
|
|
|
|
</li>
|
|
|
|
|
</ol>
|
|
|
|
|
<h2 id="why-plaintext">Why is plaintext better than HTML?</h2>
|
|
|
|
|
<p>
|
|
|
|
|
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.
|
|
|
|
|
</p>
|
|
|
|
|
<h3>HTML as a vector for phishing</h3>
|
|
|
|
|
<p>
|
|
|
|
|
HTML emails allow you to make links which hide the URL behind some
|
|
|
|
|
user-friendly text. However, this is an extremely common vector for
|
|
|
|
|
phishing attacks, where a malicious sender makes a misleading link which
|
2019-07-24 01:09:38 +02:00
|
|
|
takes you to a different website than you expect. Often these websites are
|
|
|
|
|
modeled after the login page of a service you use, and will trick you into
|
|
|
|
|
entering your account password. In plaintext emails, the URL is always
|
|
|
|
|
visible, and you can more easily make an informed choice to click it.
|
2019-07-23 23:59:08 +02:00
|
|
|
</p>
|
|
|
|
|
<h3>Privacy invasion and tracking</h3>
|
|
|
|
|
<p>
|
|
|
|
|
Virtually all HTML emails sent by marketers include identifiers in links
|
|
|
|
|
and inline images which are designed to extract information about you and
|
|
|
|
|
send it back to the sender. Examine the URLs closely - the strange numbers
|
|
|
|
|
and letters are unique to you and used to identify you. This information
|
|
|
|
|
is used to hack your brain, attempting to find advertisements which are
|
|
|
|
|
more likely to influence your buying habits. HTML emails are good for
|
|
|
|
|
marketers and bad for you.
|
|
|
|
|
</p>
|
|
|
|
|
<h3>Mail client vulnerabilities</h3>
|
|
|
|
|
<p>
|
|
|
|
|
HTML is an extremely large and complicated set of specifications designed
|
|
|
|
|
without emails in mind. It's designed for browsing the world wide web, on
|
|
|
|
|
which a huge variety of documents, applications, and more are available.
|
|
|
|
|
Implementing even a reasonable subset of these standards represents
|
|
|
|
|
hundreds of thousands of hours of work, or even millions. A large subset
|
|
|
|
|
(perhaps the majority) of these features are not desirable for emails, and
|
|
|
|
|
if included can be leveraged to leak information about you, your contacts,
|
|
|
|
|
your calendar, other emails in your inbox, and so on. However, because of
|
|
|
|
|
the herculean effort necessary to implement an HTML renderer, no one has
|
|
|
|
|
built one specialized for emails which is guaranteed to be safe. Instead,
|
|
|
|
|
general purpose web browsers, with many of their features disabled, are
|
|
|
|
|
employed in most email clients. This is the number one source of
|
|
|
|
|
vulnerabilities in email clients which result in information disclosure
|
|
|
|
|
and even the execution of arbitrary malicious code.
|
|
|
|
|
</p>
|
|
|
|
|
<h3>HTML emails are less accessible</h3>
|
|
|
|
|
<p>
|
|
|
|
|
Browsing the web is a big challenge for users who require a screenreader
|
|
|
|
|
or other assistive tools to use their computer. The same problems apply to
|
|
|
|
|
email, only more so - making an accessible HTML email is even more
|
|
|
|
|
difficult than making an accessible website due to the limitations imposed
|
|
|
|
|
on HTML emails by most mail clients (which they have no choice but to
|
|
|
|
|
impose - for the security reasons stated above). Plain text emails are
|
|
|
|
|
a breeze in comparison for screenreaders to recite, especially for users
|
|
|
|
|
with specialized email clients designed for this purpose. How do you speak
|
|
|
|
|
bold text aloud? How about your inline image?
|
|
|
|
|
</p>
|
|
|
|
|
<h3>Some clients can't display HTML emails at all</h3>
|
|
|
|
|
<p>
|
|
|
|
|
Some email clients don't support HTML emails at all. Many email clients
|
|
|
|
|
are designed to run in text-only environments, like a terminal emulator,
|
|
|
|
|
where they're useful to people who spend a lot of time working in these
|
|
|
|
|
environments. In a text-only interface it's not possible to render an HTML
|
|
|
|
|
email, and instead the reader will just see a mess of raw HTML text. A lot
|
|
|
|
|
of people simply send HTML emails directly to spam for this reason.
|
|
|
|
|
</p>
|
|
|
|
|
<h3>Rich text isn't that great, anyway</h3>
|
|
|
|
|
<p>
|
|
|
|
|
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. You can still communicate your point effectively without
|
|
|
|
|
bringing along all of the bad things HTML emails come with.
|
|
|
|
|
</p>
|
|
|
|
|
<hr />
|
|
|
|
|
<p>
|
|
|
|
|
In short, HTML emails are a security nightmare, are mostly used for
|
|
|
|
|
advertising to you and tracking you, are less accessible for many users,
|
|
|
|
|
and don't offer anything especially great for it.
|
|
|
|
|
</p>
|
2019-07-24 01:30:31 +02:00
|
|
|
<img
|
|
|
|
|
src="https://sr.ht/ZWUH.png"
|
|
|
|
|
alt="Plaintext certified stamp"
|
|
|
|
|
style="float: right"
|
|
|
|
|
width="200" height="200" />
|
2019-07-23 23:59:08 +02:00
|
|
|
<h2 id="recommended-clients">Recommended email clients for plaintext users</h2>
|
|
|
|
|
<p>
|
|
|
|
|
The following email clients are known to handle plaintext especially well:
|
|
|
|
|
</p>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>
|
|
|
|
|
<a rel="noopener" href="https://aerc-mail.org">aerc</a> (TUI)
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<a rel="noopener" href="https://repo.or.cz/alpine.git">alpine</a> (TUI)
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<a rel="noopener" href="https://www.claws-mail.org/">claws mail</a> (GUI)
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<a rel="noopener" href="https://gnus.org/">Gnus</a> (emacs)
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<a rel="noopener" href="https://kde.org/applications/office/org.kde.kmail2">KMail</a> (GUI)
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<a rel="noopener" href="https://mutt.org">mutt</a> (TUI)
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
<a rel="noopener" href="http://www.squirrelmail.org/">SquirrelMail</a> (Webmail)
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<p>
|
|
|
|
|
These clients all compose plaintext emails by default, with correct
|
|
|
|
|
quoting and text wrapping settings, requiring no additional configuration
|
|
|
|
|
to use correctly.
|
|
|
|
|
<a href="#contribute">Want to add your own mail client to this list</a>?
|
|
|
|
|
</p>
|
|
|
|
|
<h2 id="other-clients">How to set up plaintext with other email clients</h2>
|
|
|
|
|
<p>
|
|
|
|
|
If your email provider's webmail doesn't have good plain text support,
|
|
|
|
|
please consider writing to <code><postmaster@yourdomain.com></code>
|
|
|
|
|
with a complaint, and using one of the <a
|
|
|
|
|
href="#recommended-clients">recommended clients</a> over IMAP & SMTP
|
|
|
|
|
instead.
|
|
|
|
|
</p>
|
|
|
|
|
<p>Jump to:</p>
|
|
|
|
|
<ul>
|
2019-07-24 00:16:13 +02:00
|
|
|
<li><a href="#afterlogic">Afterlogic</a></li>
|
|
|
|
|
<li><a href="#fastmail">Fastmail</a></li>
|
|
|
|
|
<li><a href="#gmail-web">Gmail</a></li>
|
2019-07-23 23:59:08 +02:00
|
|
|
<li><a href="#k-9">K-9 mail</a></li>
|
|
|
|
|
<li><a href="#mailspring">Mailspring</a></li>
|
|
|
|
|
<li><a href="#macos">macOS mail</a></li>
|
|
|
|
|
<li><a href="#outlook">Microsoft Outlook</a></li>
|
|
|
|
|
<li><a href="#mu4e">mu4e</a></li>
|
2019-07-24 00:16:13 +02:00
|
|
|
<li><a href="#protonmail">Protonmail</a></li>
|
|
|
|
|
<li><a href="#rainloop">Rainloop</a></li>
|
|
|
|
|
<li><a href="#roundcube">Roundcube</a></li>
|
|
|
|
|
<li><a href="#sogo">Sogo</a></li>
|
2019-07-23 23:59:08 +02:00
|
|
|
<li><a href="#sylpheed">Sylpheed</a></li>
|
|
|
|
|
<li><a href="#thunderbird">Thunderbird</a></li>
|
2019-07-24 01:30:31 +02:00
|
|
|
<li><a href="#tutanota">Tutanota</a></li>
|
2019-07-23 23:59:08 +02:00
|
|
|
</ul>
|
|
|
|
|
<p>
|
|
|
|
|
After configuring your client, be sure to review our
|
|
|
|
|
<a href="#etiquette">etiquette recommendations</a>.
|
|
|
|
|
</p>
|
2019-07-24 00:16:13 +02:00
|
|
|
<h3 id="afterlogic">Afterlogic</h3>
|
|
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="red">Compose in plaintext</span>
|
|
|
|
|
<span class="red">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="red">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<p>
|
|
|
|
|
Afterlogic does not support plain text email. Please
|
|
|
|
|
<a
|
|
|
|
|
href="https://s.afterlogic.com/forum/forum_posts.asp?TID=2438"
|
|
|
|
|
>ask them for it</a>.
|
|
|
|
|
</p>
|
|
|
|
|
<h3 id="fastmail">Fastmail</h3>
|
2019-07-23 23:59:08 +02:00
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="green">Compose in plaintext</span>
|
|
|
|
|
<span class="red">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="red">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<ol>
|
2019-07-24 00:16:13 +02:00
|
|
|
<li>Visit Settings → Customize → Preferences</li>
|
2019-07-23 23:59:08 +02:00
|
|
|
<li>Expand "Advanced Preferences" at the bottom of the page</li>
|
|
|
|
|
<li>Change "Compose Format" to "plain text"</li>
|
|
|
|
|
<li>Disable "When replying, use the same format as the original message"</li>
|
|
|
|
|
</ol>
|
2019-07-24 00:16:13 +02:00
|
|
|
<h3 id="gmail-web">Gmail</h3>
|
2019-07-23 23:59:08 +02:00
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="green">Compose in plaintext</span>
|
|
|
|
|
<span class="red">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="red">Supports bottom posting</span>
|
|
|
|
|
</div>
|
2019-07-24 00:16:13 +02:00
|
|
|
<p>
|
|
|
|
|
Gmail does not support permanently setting your plain text preference. To
|
|
|
|
|
send a plain text email once, do the following:
|
|
|
|
|
</p>
|
2019-07-23 23:59:08 +02:00
|
|
|
<ol>
|
|
|
|
|
<li>Compose a new message</li>
|
|
|
|
|
<li>On the bottom right, click the three-dotted icon</li>
|
|
|
|
|
<li>Select the plaintext option</li>
|
|
|
|
|
</ol>
|
|
|
|
|
<h3 id="k-9">K-9 mail</h3>
|
|
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="green">Compose in plaintext</span>
|
|
|
|
|
<span class="green">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="green">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<ol>
|
|
|
|
|
<li>Tap the three dots on the bottom right</li>
|
2019-07-24 00:16:13 +02:00
|
|
|
<li>Select Settings → Account settings → Sending mail</li>
|
2019-07-23 23:59:08 +02:00
|
|
|
<li>Change the Message Format to Plain Text</li>
|
|
|
|
|
<li>Select "Reply after quoted text"</li>
|
|
|
|
|
</ol>
|
|
|
|
|
<p>
|
|
|
|
|
It is also recommended that you select "Manage identities", and for each
|
|
|
|
|
identity, untick "Use Signature". This will remove "Sent from K-9" from
|
|
|
|
|
your emails.
|
|
|
|
|
</p>
|
|
|
|
|
<h3 id="mailspring">Mailspring</h3>
|
|
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="red">Compose in plaintext</span>
|
|
|
|
|
<span class="red">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="red">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<p>
|
|
|
|
|
Mailspring does not support plain text emails. Please ask them for it
|
|
|
|
|
<a
|
|
|
|
|
rel="noopener nofollow"
|
|
|
|
|
href="https://github.com/Foundry376/Mailspring/issues/52"
|
|
|
|
|
>on GitHub</a> and use a different email client.
|
|
|
|
|
</p>
|
|
|
|
|
<h3 id="macos">macOS Mail</h3>
|
|
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="green">Compose in plaintext</span>
|
|
|
|
|
<span class="red">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="red">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<ol>
|
2019-07-24 00:16:13 +02:00
|
|
|
<li>Select Mail → Preferences from the menu</li>
|
2019-07-23 23:59:08 +02:00
|
|
|
<li>Visit the "Composing" category</li>
|
|
|
|
|
<li>Change the "Message Format" (or "Format") option to "Plain Text"</li>
|
|
|
|
|
</ol>
|
|
|
|
|
<h3 id="outlook">Microsoft Outlook</h3>
|
|
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="green">Compose in plaintext</span>
|
|
|
|
|
<span class="red">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="red">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<ol>
|
2019-07-24 00:16:13 +02:00
|
|
|
<li>Select File → Options → Mail</li>
|
2019-07-23 23:59:08 +02:00
|
|
|
<li>
|
|
|
|
|
Under "Compose Messages", select "Plain Text" from the "Compose messages
|
|
|
|
|
in this format" options.
|
|
|
|
|
</li>
|
|
|
|
|
</ol>
|
|
|
|
|
<h3 id="mu4e">mu4e</h3>
|
|
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="green">Compose in plaintext</span>
|
|
|
|
|
<span class="green">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="green">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<p>
|
|
|
|
|
To enable automatic wrapping of your emails, add the following to your
|
|
|
|
|
init file:
|
|
|
|
|
</p>
|
|
|
|
|
<pre>(add-hook 'message-mode-hook 'auto-fill-mode)</pre>
|
|
|
|
|
<p>
|
|
|
|
|
You may configure the default column to wrap at by changing the value of
|
|
|
|
|
<code>fill-column</code> (the default, 70, is suitable).
|
|
|
|
|
</p>
|
2019-07-24 00:16:13 +02:00
|
|
|
<h3 id="protonmail">Protonmail</h3>
|
2019-07-23 23:59:08 +02:00
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="green">Compose in plaintext</span>
|
|
|
|
|
<span class="red">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="red">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<p>
|
|
|
|
|
<strong>Notice</strong>: Use of IMAP and SMTP with Protonmail requires
|
|
|
|
|
the use of a
|
|
|
|
|
<a
|
|
|
|
|
href="https://github.com/emersion/hydroxide"
|
|
|
|
|
rel="nofollow noopener"
|
|
|
|
|
>special third-party bridge</a>.
|
|
|
|
|
Protonmail is not recommended for this reason.
|
|
|
|
|
</p>
|
|
|
|
|
<ol>
|
2019-07-24 00:16:13 +02:00
|
|
|
<li>Visit Settings → Appearance</li>
|
2019-07-23 23:59:08 +02:00
|
|
|
<li>Set "Composer Mode" to "Plain Text"</li>
|
|
|
|
|
</ol>
|
|
|
|
|
<p>
|
2019-07-24 00:16:13 +02:00
|
|
|
It's also recommended that you visit Settings → Account → Identity and remove
|
2019-07-23 23:59:08 +02:00
|
|
|
the default email signature.
|
|
|
|
|
</p>
|
2019-07-24 00:16:13 +02:00
|
|
|
<h3 id="rainloop">Rainloop</h3>
|
2019-07-23 23:59:08 +02:00
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="green">Compose in plaintext</span>
|
|
|
|
|
<span class="red">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="red">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<ol>
|
|
|
|
|
<li>Click the "person" icon on the top-right corner and choose "Settings"</li>
|
|
|
|
|
<li>Set "Default text editor" to "Plain"</li>
|
|
|
|
|
</ol>
|
2019-07-24 00:16:13 +02:00
|
|
|
<h3 id="roundcube">Roundcube</h3>
|
2019-07-23 23:59:08 +02:00
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="green">Compose in plaintext</span>
|
|
|
|
|
<span class="red">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="red">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<ol>
|
|
|
|
|
<li>Click Settings on the top-right</li>
|
2019-07-24 00:16:13 +02:00
|
|
|
<li>Select Preferences → Composing Messages</li>
|
2019-07-23 23:59:08 +02:00
|
|
|
<li>Select "never" under "Compose HTML messages"</li>
|
|
|
|
|
</ol>
|
|
|
|
|
<p>Also consider setting "Automatically add signature" to "never".</p>
|
2019-07-24 00:16:13 +02:00
|
|
|
<h3 id="sogo">Sogo</h3>
|
2019-07-23 23:59:08 +02:00
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="green">Compose in plaintext</span>
|
|
|
|
|
<span class="red">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="green">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<ol>
|
|
|
|
|
<li>On the top-right, click the gear to open Preferences</li>
|
|
|
|
|
<li>Select the Mail tab</li>
|
|
|
|
|
<li>Change "Compose messages in" to "Plain text"</li>
|
|
|
|
|
<li>Click the green "Save" icon on the top-right</li>
|
|
|
|
|
</ol>
|
|
|
|
|
<h3 id="sylpheed">Sylpheed</h3>
|
|
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="green">Compose in plaintext</span>
|
|
|
|
|
<span class="green">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="green">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<ol>
|
2019-07-24 00:16:13 +02:00
|
|
|
<li>Open Configuration → Common preferences</li>
|
|
|
|
|
<li>Visit the Compose → Editor tab</li>
|
2019-07-23 23:59:08 +02:00
|
|
|
<li>Enable "Wrap on input"</li>
|
|
|
|
|
</ol>
|
|
|
|
|
<h3 id="thunderbird">Thunderbird</h3>
|
|
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="green">Compose in plaintext</span>
|
|
|
|
|
<span class="green">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="green">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<ol>
|
|
|
|
|
<li>Right-click the space to the right of your inbox tab</li>
|
|
|
|
|
<li>Enable the menu bar</li>
|
2019-07-24 00:16:13 +02:00
|
|
|
<li>Select Edit → Account Settings</li>
|
2019-07-23 23:59:08 +02:00
|
|
|
<li>Select the "Composition & Addressing" settings</li>
|
|
|
|
|
<li>Disable "Compose messages in HTML format"</li>
|
|
|
|
|
<li>Select "Start my reply below the quote"</li>
|
|
|
|
|
<li>Repeat this for any other email accounts</li>
|
|
|
|
|
</ol>
|
2019-07-24 01:30:31 +02:00
|
|
|
<h3 id="tutanota">Tutanota</h3>
|
|
|
|
|
<div class="breakdown">
|
|
|
|
|
<span class="green">Compose in plaintext</span>
|
|
|
|
|
<span class="red">Wraps text or format=flowed</span>
|
|
|
|
|
<span class="red">Supports bottom posting</span>
|
|
|
|
|
</div>
|
|
|
|
|
<p>
|
|
|
|
|
<strong>Notice</strong>: Use of IMAP and SMTP, open standards for email
|
|
|
|
|
clients, is not possible with Tutanota. This is not acceptable behavior
|
|
|
|
|
for an email provider and use of Tutanota is strongly recommended against
|
|
|
|
|
for this reason. Tutanota's stated reasons for not supporting these
|
|
|
|
|
protocols are lies and you would be well served by closing your account
|
|
|
|
|
there.
|
|
|
|
|
</p>
|
|
|
|
|
<ol>
|
|
|
|
|
<li>Visit Settings → Email → Formatting</li>
|
|
|
|
|
<li>Set the format to plain text</li>
|
|
|
|
|
</ol>
|
2019-07-23 23:59:08 +02:00
|
|
|
<h2 id="etiquette">Etiquette recommendations for plaintext emails</h2>
|
|
|
|
|
<p>
|
|
|
|
|
In addition to training you that HTML emails are the norm, many harmful
|
|
|
|
|
mail clients may have trained you with other bad habits. Here are some
|
|
|
|
|
tips to unlearn them:
|
|
|
|
|
</p>
|
|
|
|
|
<h3>Top posting</h3>
|
|
|
|
|
<p>
|
|
|
|
|
When you reply to an email, many email clients will include a quoted
|
|
|
|
|
version of the message you're replying to beneath the text of your reply.
|
|
|
|
|
This leads to long email threads containing the entire history of the
|
|
|
|
|
discussion in an increasingly long and nested footer on every email. This
|
|
|
|
|
is called "top posting" and is strongly discouraged.
|
|
|
|
|
</p>
|
|
|
|
|
<p>
|
|
|
|
|
Though some clients would have you believe otherwise, you can edit the
|
|
|
|
|
quoted version of the message you're replying to, and you're encouraged
|
|
|
|
|
to. Feel free to trim it down, cutting out any extra text which isn't
|
|
|
|
|
directly relevant to your reply - or removing it entirely. Write anything
|
|
|
|
|
you have to say underneath the quote it pertains to.
|
|
|
|
|
</p>
|
|
|
|
|
<ul>
|
|
|
|
|
<li><strong>A</strong>: Because it reverses the logical flow of conversation.</li>
|
|
|
|
|
<li><strong>Q</strong>: Why is top posting frowned upon?</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<h3>Wrapping your text</h3>
|
|
|
|
|
<p>
|
|
|
|
|
Email writers are encouraged to wrap their text at 72 columns by inserting
|
|
|
|
|
a newline and resuming your writing on the following line. The
|
|
|
|
|
<a href="#recommended-clients">recommended clients</a> will do this for
|
|
|
|
|
you, as well as any client shown above with "Wraps text or uses
|
|
|
|
|
format=flowed" checked. Don't worry about re-wrapping the quoted parts of
|
2019-07-24 00:16:13 +02:00
|
|
|
message you're replying to unless you want to. If your client doesn't do
|
|
|
|
|
this for you, it can easily be the most frustrating part of being a good
|
|
|
|
|
email netizen, but it's very much appreciated by recipients.
|
2019-07-23 23:59:08 +02:00
|
|
|
</p>
|
|
|
|
|
<h2 id="implementation-recommendations">
|
|
|
|
|
Recommendations for software which sends emails
|
|
|
|
|
</h2>
|
|
|
|
|
<p>
|
|
|
|
|
Thanks for your interest in making plaintext emails more accessible to
|
|
|
|
|
your users!
|
|
|
|
|
</p>
|
|
|
|
|
<h3>For senders of automated emails</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>
|
|
|
|
|
If you must use HTML, send a
|
|
|
|
|
<a
|
|
|
|
|
href="https://en.wikipedia.org/wiki/MIME"
|
|
|
|
|
rel="noopener nofollow"
|
|
|
|
|
>multipart/alternative</a>
|
|
|
|
|
email with both a plaintext and HTML version included. Your programming
|
|
|
|
|
language probably includes tools for creating these kinds of emails.
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<h3>For senders of user-authored emails</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>
|
|
|
|
|
Allow users to compose emails in plaintext, and consider making this
|
|
|
|
|
the default. When the user composes a message in plaintext, send a
|
|
|
|
|
text/plain email instead of a multipart/alternative email with a
|
|
|
|
|
generated HTML part.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
When composing a plaintext email, hard-wrap their lines at 72 columns by
|
2019-07-24 00:16:13 +02:00
|
|
|
inserting newlines at the nearest word boundary. Optionally, use
|
2019-07-23 23:59:08 +02:00
|
|
|
<a
|
|
|
|
|
href="https://www.ietf.org/rfc/rfc2646.txt"
|
|
|
|
|
rel="noopener nofollow"
|
2019-07-24 00:16:13 +02:00
|
|
|
>format=flowed</a> instead to
|
2019-07-23 23:59:08 +02:00
|
|
|
allow plaintext emails to be displayed and composed without hard
|
|
|
|
|
wrapping.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
When users reply to an email in plaintext, don't encourage top-posting
|
|
|
|
|
by leaving their cursor above the quoted message. Instead, add two
|
|
|
|
|
newlines after the quoted message and leave their cursor there. Allow
|
|
|
|
|
the user to edit the quoted message. Quote each line of the original
|
|
|
|
|
message with > and a single space, followed by the quote.
|
|
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
When users send an HTML email explicitly, convert it to text/plain and
|
2019-07-24 00:16:13 +02:00
|
|
|
send a multipart/alternative email which includes both versions.
|
2019-07-23 23:59:08 +02:00
|
|
|
</li>
|
|
|
|
|
<li>
|
|
|
|
|
When displaying multipart/alternative emails, give the user the option to prefer
|
|
|
|
|
to view the plaintext part by default.
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<p>
|
|
|
|
|
Email clients which meet all of these criteria and prefer plaintext by
|
|
|
|
|
default are entitled to a spot on our recommended clients list.
|
|
|
|
|
</p>
|
|
|
|
|
<h2 id="contribute">How to improve these recommendations</h2>
|
|
|
|
|
<p>
|
|
|
|
|
Do you want to add instructions for a new email client? Have suggestions
|
|
|
|
|
or questions? Please send a <strong>plain text</strong> email to
|
|
|
|
|
<a
|
|
|
|
|
href="mailto:~sircmpwn/public-inbox@lists.sr.ht"
|
|
|
|
|
>~sircmpwn/public-inbox@lists.sr.ht</a>. You can also
|
|
|
|
|
<a href="https://git-send-email.io">email a patch</a> to this address: the
|
|
|
|
|
code may be found on
|
|
|
|
|
<a href="https://git.sr.ht/~sircmpwn/useplaintext.email">git.sr.ht</a>.
|
|
|
|
|
</p>
|
|
|
|
|
<hr />
|
|
|
|
|
<p class="muted">
|
|
|
|
|
"But if plaintext is so good, why is this page written in HTML?"
|
|
|
|
|
<br />
|
|
|
|
|
This is a reference document, not an email, you twit.
|
|
|
|
|
</p>
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
