Why Email Headers Look the Way They Do (RFC 822 to RFC 5322)

Internet mail's header conventions are a fossil record of the ARPANET. In November 1977 David Crocker, John Vittal, Kenneth Pogran, and Austin Henderson published RFC 733, the first widely adopted standard for the format of ARPA network text messages. Crocker returned alone in August 1982 with RFC 822, which refined the syntax for the larger and more heterogeneous Internet that was replacing the original ARPANET. RFC 822 codified the now-familiar "Header-Name: value" colon-delimited form, the CRLF line terminator, the blank line separating headers from body, and the Received header trace chain that mail relays prepend on the way through. Every Received line is essentially a hop record stacked on top of the message as it travels. RFC 822 assumed a strictly 7-bit US-ASCII transport, which matched the SMTP envelope protocol Jon Postel published the same month as RFC 821. That assumption broke as soon as users wanted to send accented characters, non-Latin scripts, images, and program binaries. Rather than redesign the message format, Nathaniel Borenstein and Ned Freed bolted on MIME starting with RFC 1341 (1992) and finalized it in RFCs 2045 through 2049 (1996). MIME added new headers (Content-Type, Content-Transfer-Encoding, MIME-Version), the multipart container concept for attachments, and two content encodings that smuggle 8-bit data through 7-bit pipes: Base64 for binary blobs and Quoted-Printable for mostly-ASCII text with a few high bytes. Non-ASCII header values are wrapped in the encoded-word syntax of RFC 2047. RFC 2822 (2001, Resnick) and RFC 5322 (2008) tightened the grammar and marked legacy constructs as "obsolete syntax" that parsers must still accept but generators must not emit. The format itself is essentially frozen. A clean redesign is impossible in practice because every Mail Transfer Agent, spam filter, DKIM signer, archival store, and forensic tool on the planet parses these exact bytes. Replacing the format would mean rewriting every one of them simultaneously, and email's value comes from universal reach across that uncoordinated swarm of implementations. So the 1982 syntax persists, with MIME and authentication headers layered on top like geological strata.