The hidden history of the history of email

01Before Tomlinson: the systems nobody remembers

The standard history of email begins in 1971 with Ray Tomlinson sending a message between two computers on the ARPANET. But email existed before Tomlinson. In the 1960s, users on time-sharing systems like MIT Compatible Time-Sharing System (CTSS) had mailbox features. A user could leave a message in another user mailbox, and the system would notify the recipient at login. These local mailboxes were the true origin of electronic mail. They were not network email because the messages never left the machine, but they established the concept: a digital message left for a specific user to read later.

Several other systems developed similar features independently. The SNDMSG command on the TENEX operating system, the MAIL command on the TOPS-10 system, and internal messaging on the IBM System/360 all provided local electronic mail in the late 1960s and early 1970s. These systems are forgotten because they were local and proprietary. None of them could send messages to users on other systems. What Tomlinson did was connect these isolated mailboxes by writing a program called SNDMSG that could send messages across the ARPANET. He combined the local mailbox concept with network delivery. The local systems did not disappear because Tomlinson invented network email; they disappeared because the network eventually connected everyone, making local-only systems irrelevant.

02The forgotten protocols that almost won

SMTP was not the only protocol for electronic mail, and it was not the obvious winner. In the 1980s, there were at least four competing protocols for network email. UUCP (Unix-to-Unix Copy Protocol) was used for dial-up email between Unix machines and powered the early Usenet. BITNET was a store-and-forward network used by IBM mainframes at universities. FidoNet was a dial-up network used by personal computer bulletin board systems. And X.400 was the official standard, approved by the International Organization for Standardization, that was supposed to replace everything else.

X.400 is the most interesting of the losers. It was a sophisticated protocol that handled addressing, routing, and delivery with far more structure than SMTP. It was backed by governments and major corporations. It was the official international standard. And it lost. It lost because it was complex, expensive to implement, and required centralized administration. SMTP was simple, free to implement, and required no central authority. The market chose simplicity. By the mid-1990s, X.400 was dead, and SMTP was the standard. The lesson is that the technically superior protocol does not always win. The protocol that is easiest to implement, easiest to understand, and easiest to deploy usually wins, even if it is less capable. SMTP won not because it was better, but because it was simpler.

03The political battle: who owns the mail?

In the 1980s and 1990s, a political battle raged over who would control email. On one side were the internet advocates, who believed email should be an open system based on SMTP, with no central authority and no gatekeeper. On the other side were the commercial online services, who wanted email to be a closed system that they controlled. CompuServe, Prodigy, AOL, and MCI Mail all operated their own email systems that were initially not connected to the internet. If you were on CompuServe, you could send mail to other CompuServe users but not to someone on the internet. The services wanted to keep their users inside their walled gardens, where they could charge for every message.

The internet won this battle, but it took a decade. The turning point came in the early 1990s, when commercial online services began offering internet email gateways to retain users who were leaving for internet service providers. Once the gateways were open, the walled gardens collapsed. Users could send mail from AOL to the internet and back. The services lost their monopoly on electronic messaging. The lesson of this battle is that openness eventually wins, but it takes time, and it requires users who are willing to leave closed systems for open ones. The internet email advocates were right: an open system with no gatekeeper would eventually reach more people than any closed system could. But they were right only because the internet was allowed to grow without interference from the companies that wanted to control it.

04The role of RFC 524: a document that changed everything

In 1973, RFC 524 was published. It was titled "A Proposed Official Mail Protocol" and it was the first serious attempt to standardize email on the ARPANET. The document was written by Kenneth Pogran and it laid out the principles that would eventually become SMTP. It proposed that email should be a store-and-forward system, that messages should have structured headers, and that the protocol should be simple enough for any system to implement. RFC 524 was not the final standard, but it set the direction. It was followed by RFC 561, RFC 680, and eventually RFC 788 and RFC 821, each one refining the protocol until it became the SMTP we use today.

The RFC process itself is part of the hidden history. The Request for Comments series was not a standards body in the traditional sense. It was a community of engineers who wrote documents, circulated them, argued about them, and revised them. There was no central authority, no regulatory body, no enforcement mechanism. The RFCs worked because the engineers who wrote them also implemented them, and the implementations had to interoperate. If your implementation did not work with everyone else implementation, you fixed it. This informal, consensus-based process produced a better protocol than any formal standards body did. X.400 was produced by a formal standards body and was technically superior. SMTP was produced by a community of engineers and was practically superior. The RFC process is one of the reasons the internet works, and email was its first great success.

05The lost features: what email was supposed to do

Early email pioneers imagined features that never made it into the final protocol. Jon Postel proposed a rich-text email format in the late 1970s that would have included structured formatting, embedded images, and interactive elements. The idea was abandoned because the technology to support it did not exist yet and the bandwidth to transmit it was not available. MIME (Multipurpose Internet Mail Extensions), which eventually enabled attachments and rich content in email, was not introduced until 1992. The gap between what email could do in the 1970s and what it can do today is the result of decisions made by engineers who were constrained by the technology of their time.

Other lost features include mail tracking, which would have told senders when their message was read, and mail recall, which would have allowed senders to retract a message after sending it. Both were proposed and both were rejected. Mail tracking was rejected as a privacy violation. Mail recall was rejected as technically infeasible in a store-and-forward system. These decisions shaped email into what it is today: a system that is simple, reliable, and privacy-respecting, but one that lacks features that users of modern messaging systems take for granted. The history of email is not just a history of what was built; it is a history of what was considered and rejected, and those rejections define the system as much as the features that were included.

06How the narrative got simplified

The history of email as most people know it is a simplified story. It goes like this: Ray Tomlinson invented email in 1971 by sending a message between two computers and choosing the @ symbol for the address. This story is true, but it is incomplete. It reduces a complex history of competing systems, abandoned protocols, and political battles to a single moment of invention. The simplification is not malicious; it is how history usually works. Complex processes get reduced to simple narratives, and individuals get credit for collective achievements. Tomlinson himself was modest about his role. He said he was just the person who put two existing things together: the local mailbox feature and the network delivery mechanism.

The full history of email involves dozens of engineers, multiple competing protocols, and a decades-long battle between open and closed systems. The simplified narrative obscures the most important lessons: that standards are chosen, not inevitable; that the technically superior solution does not always win; and that the persistence of a few engineers who believed in an open system shaped the communication infrastructure that the entire world now depends on. The hidden history of email is not just about forgotten systems and protocols. It is about how decisions made by a small community of engineers in the 1970s and 1980s determined how billions of people would communicate fifty years later.

07What the hidden history tells us

The hidden history of email tells us that infrastructure is never inevitable. The email system we have today, with SMTP as its protocol and the @ symbol as its addressing convention, was not the only possible outcome. If X.400 had won, email would be more structured but less universal. If the walled gardens had survived, email would be more controlled but less free. If the RFC process had not existed, email might have been standardized by a formal body and arrived later, with more features but less reach. The history of email is a history of paths taken and paths not taken, and the paths not taken are as important as the ones that were.

Understanding this history matters because the same dynamics are playing out today in other technologies. The battle between open and closed systems continues in social media, in instant messaging, in artificial intelligence, and in every technology that connects people. The lessons of email are the lessons of infrastructure: simplicity wins over complexity, openness wins over control, and the decisions made by a small group of engineers today will shape how billions of people communicate for decades to come. The hidden history of email is not just a story about the past. It is a warning about the future.