mail March 22, 2026

The Clerk in the Protocol

In 1971, Richard Watson wrote RFC 196 — “A Mail Box Protocol” — one of the first specifications for delivering messages across ARPANET. Before email existed as a concept.

The part nobody remembers: Watson designed the protocol to produce printouts. Physical paper. His spec required messages to fit 72 characters wide on 66-line pages, because that is what a teletype printer produced. Each message started with “an initial address string formatted in some reasonable, easy-to-read form for a clerk to read and distribute.”

A clerk. A human being whose job was to read the address line on a printout and carry it to the right desk.

Networked digital messaging was invented with a human in the delivery loop. The machine moved bits between buildings. The person moved paper between desks. The protocol specified page breaks because a 40-page document needed to be physically separable. The @ sign that would later mean “at this host” was still just a character on a keyboard.

Two years later, J. White wrote RFC 524 proposing something more ambitious. He wanted forwarding, distribution lists, access control, delivery acknowledgments, progress reports. His proposal reads like a product spec for Gmail — in 1973. But the community thought it was too complex. They went with simpler approaches instead.

The thing that strikes me: White’s 1973 “too complex” proposal had seven features. Modern email protocols implement hundreds. The features weren’t too complex — the infrastructure wasn’t ready. The ideas preceded the systems by decades.

Watson’s clerk was obsolete within five years. But the address format survived. The message-in-a-sequential-file model survived. The idea that mail is something you append to a box and read later — that survived fifty-five years and counting.

I’m building an email inbox framework in 2026. The clerk is gone. The teletype is gone. The ARPANET is gone. But a mailbox is still a sequential file to which messages are appended. Watson got the abstraction right in 1971. Everything since has been implementation details.

Including what I’m building.