Email could have been X.400 times better

Original Article ↗ Hacker News Discussion ↗

Email’s dominance by the simple SMTP protocol is contrasted with the far more ambitious but unwieldy X.400 standard, which promised features like built‑in read receipts, message recall, prioritized delivery, and rich routing metadata. Commenters argue that X.400’s telco-style, centrally coordinated, metered model and opaque specifications made it impractical compared to SMTP’s open, decentralized, “good enough” approach, even if some X.400 capabilities still survive in niches like aviation and EDI. The thread also uses examples like spam, unsubscribe mechanics, and ATM vs Ethernet to illustrate how simpler, openly implemented protocols tend to win in practice over complex top‑down designs.

Unsubscribe Links, Trackers, and Email Scanners

  • Several commenters say email read-tracking and “one-click unsubscribe” are badly degraded by security scanners that prefetch links and images.
  • Others argue the real problem is spam and unethical mailing practices, not scanners.
  • Strong sentiment that unsubscribe must be easy and not gated by CAPTCHAs; if it is, many will mark as spam instead.
  • Some note standard headers like List-Unsubscribe (and related POST variants) are more robust and supported by infrastructure (e.g., required for bulk deliverability), though client UX support is mixed.
  • Disagreement over whether scanners actually submit unsubscribe forms vs. just following links; some suspect poor implementation (GET with side effects) and business incentives behind using CAPTCHAs.

Read Receipts, Tracking, and Privacy

  • Commenters distinguish between protocol-level read receipts and tracking pixels.
  • Many disable remote content to avoid tracking, but others point out scanners can defeat this by preloading images/links anyway.
  • Some are explicitly glad stronger read receipts “died,” seeing them as privacy-invasive and marketer-friendly.

X.400 vs SMTP: Complexity, Features, and Failure

  • Broad agreement that SMTP “won” because it was simple, open, and easy to implement and debug.
  • X.400 required explicit routing configuration and complex addressing; SMTP leverages DNS and simple domain-based routing.
  • Many describe X.400 and related ITU/OSI stacks as overengineered, expensive, poorly documented, and often only partially implemented.
  • Features like recall, guaranteed deletion, or protocol-level multicast are criticized as either impossible to truly guarantee or better handled at endpoints (mailing lists).
  • Several share painful operational stories of X.400, Novell connectors, “bang path” routing, and legacy EDI/X.400 systems still limping along.

Standards Culture: ITU/OSI vs IETF/Internet

  • Repeated theme: complex, committee-driven telco standards (X.400, X.25, ATM, OSI) lost to simpler, “worse is better” Internet protocols.
  • IETF’s open RFCs and accessible implementations contrasted with costly, obscure ITU specs.
  • Some note X.509 and pieces of X.500/LDAP persist, but often in ways that ignore the original grand architecture.

Email Properties and Alternate Histories

  • Several value email’s immutability and distrust features like recalls or auto-destruct.
  • Discussion of hypothetical paid “e-stamp” email to fight spam: some see it as reducing spam; others say micropayments would stifle organic communication and users would flee to free channels.