conv.

All stories
TechQuiet 10d · day 14

Fastmail publishes explainer on how email encryption actually works

A Fastmail blog post breaking down TLS, PKI and opportunistic server-to-server encryption circulates alongside an older computer.rip history of email's security gaps.

newest coverage 10d agosummary written 10d ago7 pieces109 likes & upvotes23 comments RedditHacker NewsMastodon

What to know

  • Fastmail's explainer separates email encryption into distinct layers — client-to-server TLS, PKI/Certificate Transparency for server authentication, and opportunistic server-to-server TLS — each defending against different threats.
  • Server-to-server delivery relies on 'opportunistic TLS,' which falls back to unencrypted transmission if the receiving server doesn't support encryption, leaving a known gap.
  • A separate computer.rip essay frames these weaknesses as inherited from email's 1960s–1990s origins, designed for a trust-based internet rather than today's adversarial one.
  • Coverage is limited to blog posts and low-engagement reposts across Hacker News, Reddit and Mastodon, with minimal discussion generated so far.

Fastmail Email provider and author of the blog postcomputer.rip Blog publishing the historical email-security essaynziring Reddit commenter

Fastmail publishes explainer on how email encryption actually works
fastmail.com

How it unfolded 4 developments, newest first · click a bar or a number to jump postscomments

Peak 2 pieces in 3h at Nov 1, 1 AM; 7 pieces over 14 days (6 posts · 1 comment) Oct 29, 5 AM — 1 piece · 1 post — Reddit 1Oct 29, 8 AM — 1 piece · 1 post — Reddit 1Oct 29, 11 AM — quietOct 29, 2 PM — quietOct 29, 5 PM — quietOct 29, 8 PM — quietOct 29, 11 PM — quietOct 30, 2 AM — quietOct 30, 5 AM — quietOct 30, 8 AM — quietOct 30, 11 AM — quietOct 30, 2 PM — 1 piece · 1 post — Hacker News 1Oct 30, 5 PM — 1 piece · 1 comment — Reddit 1Oct 30, 8 PM — quietOct 30, 11 PM — quietOct 31, 2 AM — quietOct 31, 5 AM — quietOct 31, 8 AM — quietOct 31, 11 AM — quietOct 31, 2 PM — quietOct 31, 5 PM — quietOct 31, 8 PM — quietOct 31, 11 PM — quietNov 1, 1 AM — 2 pieces · 2 posts — Mastodon 2Nov 1, 4 AM — quietNov 1, 7 AM — quietNov 1, 10 AM — quietNov 1, 1 PM — 1 piece · 1 post — Mastodon 1Nov 1, 4 PM — quietNov 1, 7 PM — quietNov 1, 10 PM — quietNov 2, 1 AM — quietNov 2, 4 AM — quietNov 2, 7 AM — quietNov 2, 10 AM — quietNov 2, 1 PM — quietNov 2, 4 PM — quietNov 2, 7 PM — quietNov 2, 10 PM — quietNov 3, 1 AM — quietNov 3, 4 AM — quietNov 3, 7 AM — quietNov 3, 10 AM — quietNov 3, 1 PM — quietNov 3, 4 PM — quietNov 3, 7 PM — quietNov 3, 10 PM — quietNov 4, 1 AM — quietNov 4, 4 AM — quietNov 4, 7 AM — quietNov 4, 10 AM — quietNov 4, 1 PM — quietNov 4, 4 PM — quietNov 4, 7 PM — quietNov 4, 10 PM — quietNov 5, 1 AM — quietNov 5, 4 AM — quietNov 5, 7 AM — quietNov 5, 10 AM — quietNov 5, 1 PM — quietNov 5, 4 PM — quietNov 5, 7 PM — quietNov 5, 10 PM — quietNov 6, 1 AM — quietNov 6, 4 AM — quietNov 6, 7 AM — quietNov 6, 10 AM — quietNov 6, 1 PM — quietNov 6, 4 PM — quietNov 6, 7 PM — quietNov 6, 10 PM — quietNov 7, 1 AM — quietNov 7, 4 AM — quietNov 7, 7 AM — quietNov 7, 10 AM — quietNov 7, 1 PM — quietNov 7, 4 PM — quietNov 7, 7 PM — quietNov 7, 10 PM — quietNov 8, 1 AM — quietNov 8, 4 AM — quietNov 8, 7 AM — quietNov 8, 10 AM — quietNov 8, 1 PM — quietNov 8, 4 PM — quietNov 8, 7 PM — quietNov 8, 10 PM — quietNov 9, 1 AM — quietNov 9, 4 AM — quietNov 9, 7 AM — quietNov 9, 10 AM — quietNov 9, 1 PM — quietNov 9, 4 PM — quietNov 9, 7 PM — quietNov 9, 10 PM — quietYesterday, 1 AM — quietYesterday, 4 AM — quietYesterday, 7 AM — quietYesterday, 10 AM — quietYesterday, 1 PM — quietYesterday, 4 PM — quietYesterday, 7 PM — quietYesterday, 10 PM — quietToday, 1 AM — quietToday, 4 AM — quietToday, 7 AM — quietToday, 10 AM — quietToday, 1 PM — quietToday, 4 PM — quiet 12–34
Oct 30Oct 31Nov 1Nov 2Nov 3Nov 4Nov 5Nov 6Nov 7Nov 8Nov 9now · 7:39 PM ET
  1. 4

    Mastodon bots repost the Fastmail encryption explainer

    Automated curation accounts on Mastodon shared the Fastmail blog post and linked back to the original Hacker News thread.

    • hkrn@mstdn.social

      Understanding Email Encryption L: https://www. fastmail.com/blog/email-encryp tion/ C: https:// news.ycombinator.com/item?id=5 0310038 posted on 2026.10.30 at 16:55:56 (c=0, p=3)

      hkrn@mstdn.socialMastodon10d agoview on Mastodon ↗
    1 more of the top 2 · 2 posts in this stretch
    • hn100@social.lansky.name

      Understanding Email Encryption Link: https://www. fastmail.com/blog/email-encryp tion/ Discussion: https:// news.ycombinator.com/item?id=5 0310038

      hn100@social.lansky.nameMastodon10d agoview on Mastodon ↗
    all of them →
  2. 3

    Commenter nziring praises the article's historical grounding

    A reader who lived through the protocols' development responds positively to the piece on Reddit.

    “I enjoyed the article, since I lived through most of that history and studied many of the protocols and formats listed.”
    — nziring

    • I enjoyed the article, since I lived through most of that history and studied many of the protocols and formats listed.

      nziringr/programming12d agoview on r/programming ↗
  3. 2

    Fastmail explains layered email encryption on its blog

    Fastmail's post breaks down TLS for client-to-server transport, PKI and Certificate Transparency for authenticating servers, and 'opportunistic TLS' for server-to-server delivery, noting each defends against a different threat model.

    “PKI combined with Certificate Transparency provides strong, practical assurance that your encrypted connection terminates at the server you intended to reach.”
    — Fastmail
  4. 1

    Redditors resubmit the computer.rip email-security essay

    The computer.rip piece on email's history and security shortcomings was posted to Reddit twice within a few hours, drawing no comments.

    “The internet existed within a context of trust.”
    — computer.rip, blog author · source
  5. background

    computer.rip publishes history of email's insecure design — An essay traces email's origins to 1960s mainframe and ARPANET systems and Ray Tomlinson's addressing scheme, arguing the protocol's trust-based era design left it poorly suited to today's adversarial internet.

What people are saying 0 voices from 0 sites · best of 3 · verbatim