X.400 (1984) standardized message recall, read receipts, encryption, and multilingual support years before SMTP gained any of them, but lost anyway.
Key Takeaways
X.400 prescribed outcomes (“what must be possible”); SMTP described exact implementation steps. The 266-page spec vs. 68-page RFC 821 gap reflects this directly.
X.400 had message recall, delivery scheduling, read receipts 15 years early, body-part encryption, and file attachments 8 years before SMTP supported them.
Interoperability was X.400’s stated mission and its fatal flaw: even X.400-to-X.400 messages between different vendor implementations frequently failed to exchange.
X.400 addresses (C=no; ADMD=; PRMD=uninett; O=uninett; S=alvestrand; G=harald) had six valid RFC-documented formats; SMTP’s user@domain had one.
By 1994, X.400 had interconnected 1 million mailboxes; internet email had 25 million users the same year. The committee standard never escaped the telecom walled garden.
Hacker News Comment Review
The one substantive comment points out that X.400’s most-cited advantage, read receipts, is now effectively broken in practice anyway: security scanners fire tracking pixels and auto-click unsubscribe links, undermining both features at scale.
Notable Comments
@jgalt212: notes unsubscribe links now require captcha gates because scanners auto-trigger them, making X.400’s early read-receipt win a moot point today.