Email Hardening Guide
This page provides a comprehensive guide to securing email communications, which is crucial for both personal and organizational cybersecurity. Proper email security can mitigate risks associated with a variety of cyber threats.
Introduction to Email Security
Section titled “Introduction to Email Security”Email systems are common targets for cyber threats such as phishing, malware, and unauthorized access. Enhancing email security involves implementing strong security measures, using the right tools, and educating users on potential risks.
Common Email Threats
Section titled “Common Email Threats”-
Phishing and Spear Phishing: Deceptive emails that attempt to collect sensitive information. See the Phishing Defender Guide.
-
Malware: Malicious software distributed through email attachments or links.
-
Spam: Unsolicited emails that can clog inboxes and potentially lead to phishing or malware.
Email Services
Section titled “Email Services”Email services are critical for communication but come with inherent risks. Selecting a secure email provider and using tools like aliasing services can significantly enhance privacy and security.
Recommended Email Providers
Section titled “Recommended Email Providers”For a more expansive guide and the source to this section, see PrivacyGuides
-
Disroot: More than just email and focused on privacy and security allowing smtp, imap, and gpg/pgp. It takes several days to have your account request approved but it is real.
-
Proton Mail: Offers end-to-end encryption and advanced security features.
-
Tuta (formerly Tutanota): Provides secure, encrypted email storage and messaging.
-
Mailbox.org: Focused on privacy and ad-free service.
-
StartMail: Easy-to-use encrypted email for businesses and individuals.
Recommended Email Clients
Section titled “Recommended Email Clients”For a more expansive guide and the source to this section see PrivacyGuides
Email Aliasing
Section titled “Email Aliasing”For a more expansive guide and the source to this section see PrivacyGuides Email aliasing provides an additional layer of privacy by hiding your primary email address and generating unique addresses for different services.
Benefits of Email Aliasing
Section titled “Benefits of Email Aliasing”-
Hides your “main” email address from marketers and trackers.
-
Shields your inbox from spam and correlating accounts.
-
Allows you to turn off or delete aliases when no longer needed.
Recommended Email Aliasing Services
Section titled “Recommended Email Aliasing Services”-
SimpleLogin: Free and premium aliasing, owned by Proton and integrated with Proton Mail. It’s open source and can be self-hosted (our guide).
-
addy.io (formerly AnonAddy): Open-source aliasing with a free plan.
For choosing between providers and aliasing by threat model, see the Email Anonymity Guide.
Using Aliases
Section titled “Using Aliases”-
Generate a unique alias for each website or service.
-
Enable replies to be sent from aliases for added privacy.
-
Consider paid aliasing services and additional features for custom domains.
Email Encryption
Section titled “Email Encryption”Two different things often get conflated under “email encryption”:
- Transport encryption (TLS) — encrypts the SMTP/IMAP/POP3 connection between mail servers and between you and your provider. Default at major providers since the mid-2010s. Doesn’t protect message contents from the providers themselves. Modern hardening: MTA-STS (forces TLS between servers) and DANE (DNSSEC-anchored TLS validation).
- End-to-end encryption (E2EE) — your client encrypts the message; only the recipient’s client can decrypt it. Your provider, network adversaries, and any party in between see ciphertext only. This is what people usually mean by “encrypted email.”
For E2EE, the open standard is OpenPGP (also called PGP). Proton Mail and Tuta offer E2EE between users of their own service — Proton Mail uses OpenPGP under the hood (so it interoperates with external PGP users), Tuta uses its own scheme (it does not).
PGP-Capable Email Clients
Section titled “PGP-Capable Email Clients”| Client | Platform | Hardware-key OpenPGP | Notes |
|---|---|---|---|
| Thunderbird (115+) | Desktop | ✅ via external gnupg | Native OpenPGP since v78 — Enigmail is no longer needed. Set mail.openpgp.allow_external_gnupg=true for smartcard / YubiKey support; the bundled keyring handles software-only keys. |
| Mutt / NeoMutt | Terminal | ✅ | Delegates everything to gpg-agent. Cleanest hardware-key workflow once configured. |
| Apple Mail + GPG Suite | macOS | ✅ | GPG Suite installs gpg-agent and integrates with Mail. Occasional breakage on macOS major upgrades — many users have drifted to plain Homebrew gnupg. |
| Thunderbird for Android + OpenKeychain | Android | ✅ over USB-C and NFC | F-Droid: net.thunderbird.android + org.sufficientlysecure.keychain. The K-9 → Thunderbird rebrand completed late 2024; don’t run both. |
| Mailvelope | Browser webmail (Gmail, Yahoo, etc.) | ⚠️ via local gnupg bridge only | Adds PGP to webmail without a desktop client. Browsers can’t drive a smartcard directly over WebUSB/WebHID — Mailvelope shells out to local gnupg, which has to be set up separately. |
| Proton Mail (web + native) | All | ❌ | Proprietary in-browser PGP keystore. Cannot use an external smartcard. Long-standing feature request. |
| Tuta | All | ❌ | Different E2EE scheme; not OpenPGP. |
| Outlook | All | ❌ for OpenPGP | S/MIME only — usable with a YubiKey’s PIV slot via Windows CSP, but that’s S/MIME, not OpenPGP. |
Mobile reality check
Section titled “Mobile reality check”The right answer depends on whether you want software-stored keys on the phone or a hardware smartcard (YubiKey, Nitrokey).
- Software-key OpenPGP on Android — Thunderbird-for-Android + OpenKeychain works with keys stored in OpenKeychain’s encrypted vault. Standard
.ascimport/export. - Software-key OpenPGP on iOS — iPGMail (~$4, actively maintained — v2025.39.1 Nov 2025) is the recommended option. Imports/exports
.asc, keys stored in the iOS Keychain (Face/Touch ID gated), share-sheet workflow because iOS forbids Mail.app plugins. Canary Mail is the alternative if you want OpenPGP baked into the mail client itself (subscription). - Hardware-smartcard OpenPGP on Android — works: Thunderbird-for-Android + OpenKeychain drives a YubiKey or Nitrokey over USB-C or NFC. Setup is fiddly the first time; reliable once configured.
- Hardware-smartcard OpenPGP on iOS — dead path as of 2026. No iOS app drives the OpenPGP applet on a YubiKey 5Ci (Lightning) or USB-C iPhone. If you specifically need smartcard-backed PGP from a phone, that phone is Android.
For the broader mobile picture — including all the F-Droid + Play Store Android options, the OpenKeychain maintenance-mode caveat, and Termux/GnuPG power-user setups — see the Mobile Hardening Guide → OpenPGP / GPG Apps section.
PGP Key Management Basics
Section titled “PGP Key Management Basics”- Use subkeys. One offline master key that only certifies; separate Sign, Encrypt, and Authenticate subkeys for daily use. Master stays on encrypted offline storage; only subkeys go on your daily-driver machine or hardware key. Compromise of one subkey doesn’t burn your whole identity.
- Set an expiry. 1–2 years is reasonable. You can extend it before it expires. Forces you to think about rotation.
- Export a revocation certificate immediately after generating the master, and store it offline. This is the only way to tell the world to stop trusting your key if you ever lose access to the master.
- Publish your public key to keys.openpgp.org (the modern verified-email keyserver — no SKS-style key-flooding) or share the
.ascfile directly. - Refresh periodically with
gpg --refresh-keysto pick up revocations and key updates from correspondents.
The step-by-step walkthrough for all of this lives in SSH & GPG Keys → GPG (OpenPGP) Keys. Same key material applies to both email and Git commit signing — generate once, use everywhere.
Best Practices for Email Security
Section titled “Best Practices for Email Security”Use Strong, Lengthy Passwords
Section titled “Use Strong, Lengthy Passwords”-
Create passwords with a minimum of 16 characters that include a mix of letters, numbers, and symbols. Refer to the Manager Guide.
-
Avoid using easily guessable passwords such as sequential letters or numbers.
Enable Multi-Factor Authentication (MFA)
Section titled “Enable Multi-Factor Authentication (MFA)”- Enable MFA on all email accounts. Email is the recovery anchor for most other accounts, so it deserves the strongest factor you have — ideally a passkey or a hardware security key (YubiKey, Nitrokey). A TOTP authenticator app (Aegis on Android, Ente Auth cross-platform) is the fallback. Avoid SMS — SIM-swap attacks specifically target email-reset flows. See the MFA Guide for the full hierarchy.
Regularly Update Security Settings
Section titled “Regularly Update Security Settings”-
Ensure your email software and applications are up-to-date to protect against known vulnerabilities.
-
Regularly review your email account settings to ensure they align with the latest security practices.
Be Cautious with Email Attachments and Links
Section titled “Be Cautious with Email Attachments and Links”-
Always verify the sender’s email address and be wary of unexpected attachments or links.
-
Use email scanning tools to detect malicious attachments and links before opening them.
Use Secure Connections
Section titled “Use Secure Connections”-
Ensure HTTPS is enabled when accessing email online.
-
Use a reliable VPN service when accessing email on public or unsecured Wi-Fi networks.
Password Management
Section titled “Password Management”- Strongly consider using a password manager to generate and store complex passwords. This is essential for maintaining strong security across multiple accounts. See the Manager Guide.
Countermeasures for Email Threats
Section titled “Countermeasures for Email Threats”Organizational Level
Section titled “Organizational Level”-
Phishing Awareness Training: Regularly train staff to recognize and properly handle phishing attempts.
-
Server-side filtering: Scan mail before it reaches inboxes: attachment and link scanning, spam filtering, and quarantine. Hosted providers include this; self-hosted servers use filters such as Rspamd and ClamAV. Publish SPF, DKIM and DMARC so others can’t spoof your domain (Email DNS Authentication).
Personal Level
Section titled “Personal Level”-
Security Apps: Utilize apps that help identify and block phishing and spam on personal devices.
-
Educational Resources: Continuously educate yourself about email security through resources and updates. Example: Stay Safe Online’s Email Security Tips.
Offline synthetic header exercise
Section titled “Offline synthetic header exercise”Use Python 3 (standard library only) from the monorepo root. These three original
fixtures use fictional .invalid domains; no mail account, delivery, DNS lookup,
attachment viewer or provider access is needed.
python3 -B apps/wiki/scripts/triage_email_headers.py apps/wiki/scripts/fixtures/email/good.emlpython3 -B apps/wiki/scripts/triage_email_headers.py apps/wiki/scripts/fixtures/email/phish-replyto.emlpython3 -B apps/wiki/scripts/triage_email_headers.py apps/wiki/scripts/fixtures/email/phish-authfail.emlpython3 -B -m unittest discover -s apps/wiki/scripts/tests -p 'test_email_header_triage.py'Compare each report with apps/wiki/scripts/fixtures/email/answer-key.json:
good.emldecodes the folded encoded-word to René. Comparevalueswithraw_values, which retains the original encoded word and folding. From is the claimed author, Reply-To the reply destination, and Return-Path<>a valid empty envelope reverse-path used for bounces, not a missing header. Exit 0.phish-replyto.emlhas three different author/reply/bounce domains and a forged authentication pass. The differences are observations, not a verdict of malice. Every Authentication-Results claim remains an unverified assertion. Exit 0.phish-authfail.emlhas two From fields, missing Reply-To/Return-Path, and repeated contradictory authentication claims. Both authors and both claims remain visible; duplicate singleton identity makes the input invalid. Exit 1.
Ask: where would a reply go, where would a bounce go, and what evidence would be needed to trust an authentication service? This parser cannot verify SPF, DKIM, DMARC, sender ownership or authenticity. A valid parse is not a safe-message verdict. Missing identity fields are explicitly marked and do not alone make input invalid.
For real mail, trust an Authentication-Results assertion only when you know it
was added by your receiving mail system: identify its authserv-id and the
trusted delivery path, not merely a pass string or its position in the header
list. That receiving system must remove incoming headers that claim its own
identity before adding its results; otherwise a sender can forge an apparent
local verdict. Other Authentication-Results fields are untrusted claims in
this exercise. See RFC 8601 §5,
RFC 7489 and
Email DNS Authentication for the
receiving-side SPF/DKIM/DMARC checks and alignment policy. The final delivery
system normally writes Return-Path from the SMTP envelope reverse-path;
that field alone does not authenticate the displayed From address.
The reader stops at the blank header/body separator using unbuffered binary I/O; no logical body reads or Python buffer preread is needed. It never renders the body or attachments. Bounds are 65,536 header bytes (excluding the separator), 8,192 bytes per physical header line (including its line ending), and 256 fields. Missing separator, structural/address defects and limit overflow return a bounded invalid report (exit 1); usage is exit 2. Use only these synthetic examples, not private messages. See also the Purple Team guide.
Additional Resources
Section titled “Additional Resources”Related
Section titled “Related”- SSH & GPG Keys — full GPG/OpenPGP key generation, subkey strategy, and hardware-key (YubiKey/Nitrokey) setup; same key works for email and Git commits
- MFA Guide — passkeys, hardware security keys, and TOTP for protecting your email account itself
- ProtonMail Bridge on Linux — connect a desktop client to Proton Mail’s encrypted mailbox
- Email Anonymity Guide — providers and aliasing matched to your threat model
- Phishing Defender Guide — recognising and reporting phishing
- Running Your Own Email — for people who manage a domain’s mail