The history of email explained: the ideas that matter

01Asynchrony: the most powerful idea

The most powerful idea in the history of email is asynchrony. Email does not require both parties to be present at the same time. You send a message; the recipient reads it when they are ready. This idea was not new. Postal mail is asynchronous. Answering machines are asynchronous. But email made asynchrony the default for digital communication, and that default has shaped how we work, how we think, and how we interact. Asynchronous communication is less interruptive than synchronous communication. It allows the recipient to choose when to engage. It allows the sender to compose their thoughts carefully. It creates a record of the conversation that can be searched, archived, and referenced later.

The power of asynchrony is not just in convenience. It is in what it enables. Collaboration across time zones requires asynchrony. Formal communication that needs to be documented requires asynchrony. Communication with large groups, where it is impossible for everyone to be present simultaneously, requires asynchrony. Email was the first digital system to make asynchrony practical at scale, and it remains the best system for it. The rise of instant messaging, video calls, and real-time collaboration tools has not eliminated email because these tools serve a different purpose. They are for synchronous communication, and synchronous communication is not always what people need. The idea that communication should be asynchronous by default is the idea that made email, and it is the idea that keeps email relevant.

02Simple protocols, complex systems

The second idea that matters is simplicity. SMTP is a simple protocol. It defines a small number of commands: HELO to greet, MAIL FROM to specify the sender, RCPT TO to specify the recipient, DATA to send the message body, and QUIT to disconnect. The entire protocol can be implemented in a few hundred lines of code. This simplicity is what made SMTP universal. Any system could implement it. Any developer could understand it. Any server could run it. The complexity of email, the spam filtering, the authentication, the encryption, the storage, the search, the threading, the rendering, all of that complexity is outside the protocol. The protocol itself remains simple.

The idea that protocols should be simple is one of the foundational principles of internet engineering. It is sometimes called the Robustness Principle, or Postel Law, after Jon Postel, who wrote it in RFC 760: be conservative in what you send, be liberal in what you accept. The principle says that protocols should be simple and implementations should be tolerant. Simple protocols are easy to implement correctly. Tolerant implementations can handle the inevitable variations and errors that occur in real-world use. This combination, simple protocol plus tolerant implementation, produces systems that are both interoperable and robust. Email is the proof of this principle. SMTP is simple enough that it has been implemented thousands of times, and tolerant enough that those implementations can all talk to each other despite their differences.

03Interoperability: the idea that created universality

The third idea that matters is interoperability. Email was designed so that any system could exchange mail with any other system. This was not the norm in the 1980s. Most communication systems were closed. CompuServe users could only talk to CompuServe users. AOL users could only talk to AOL users. The idea that a user on one system should be able to send a message to a user on a completely different system was radical. It required a common protocol that all systems could implement, and it required a willingness to give up the control that came with a closed system.

Interoperability is the idea that created universality. Because email is interoperable, any email user can reach any other email user. This is not true of any other digital communication tool. You cannot send a Slack message to a Teams user. You cannot send a WhatsApp message to a Signal user. These systems are not interoperable, and their users are trapped in silos. The idea that interoperability is more valuable than control is the idea that made email universal, and it is the idea that most modern communication platforms have rejected. They rejected it because interoperability means you cannot lock users in. But the history of email shows that interoperability is what users actually want. They want to reach everyone, not just the people on the same platform. The walled gardens of modern messaging are the same walled gardens that email defeated thirty years ago, and they will eventually be defeated for the same reason.

04Openness: the idea that created innovation

The fourth idea that matters is openness. Email was designed as an open system. No one owns it. No one controls it. No one can prevent you from running an email server or sending email to anyone else. This openness is what enabled the innovation that built the email ecosystem. Webmail was invented because anyone could build a web interface for email. Spam filters were invented because anyone could build a filtering system. Mobile email clients were invented because anyone could build a client. The protocol was open, and the ecosystem grew around it organically, without permission from any central authority.

Openness is not just a technical property. It is a political one. An open system is one where innovation does not require the permission of a gatekeeper. This is why the open internet produced more innovation than the closed online services that preceded it. And it is why email, as an open system, produced more innovation than any closed messaging system. The lesson of openness is that the best ecosystems are the ones that nobody controls. The people who built email did not try to control it. They built a protocol and let the world build on top of it. The result was an ecosystem of clients, servers, filters, and services that no single company could have created. Openness is not just an idea; it is a strategy for building systems that are larger than any single organization could build alone.

05Store and forward: the idea that enabled reliability

The fifth idea that matters is store-and-forward. Email does not require a direct connection between sender and receiver. The message is stored at each intermediate step and forwarded when the next step is available. This idea was born from necessity: in the 1970s, computers were not always on and networks were not always available. Store-and-forward guaranteed delivery despite unreliable infrastructure. But the idea turned out to be valuable even when the infrastructure became reliable. It decoupled the sender from the receiver, allowing each to operate at their own pace. It created a buffer that absorbed delays, outages, and differences in capacity. It made email resilient in a way that real-time communication systems are not.

Store-and-forward is also the idea that made email scalable. A real-time system needs capacity for all simultaneous connections. A store-and-forward system needs capacity for the average rate of messages, not the peak. Messages can be queued during peak periods and delivered during quiet periods. This is why email can handle 320 billion messages per day without collapsing. The system does not need to process every message instantly; it needs to process them eventually. Store-and-forward is the idea that turned a communication system into a reliable, scalable infrastructure. It is the idea that enabled email to grow from a few dozen messages on one mainframe to the most used communication system in history.

06The ideas in tension

These ideas do not always work together harmoniously. Simplicity and security are in tension: adding authentication, encryption, and spam filtering makes the protocol more complex. Openness and safety are in tension: an open system that anyone can use is also a system that anyone can abuse. Interoperability and innovation are in tension: maintaining compatibility with old systems limits the changes you can make. The history of email is the history of these tensions being managed, not resolved. Each tension represents a tradeoff, and the tradeoffs have been made pragmatically, case by case, by the engineers who maintain the system.

The management of these tensions is what makes email a living system rather than a static standard. The protocol has evolved over forty years, with each evolution representing a decision about which tension to address and how. The decisions were not always optimal, and they were not always made by the right people, but they were made in the open, by a community of engineers who cared about the system. The history of email is a story of ideas in tension, managed by a community of practitioners, evolving over decades. It is not a story of a perfect system. It is a story of a system that works because its ideas are sound and its community is committed.

07Why these ideas matter beyond email

The ideas that shaped email matter beyond email because they are the ideas that shape all digital infrastructure. Asynchrony is the idea behind message queues, event-driven architecture, and the entire pattern of web-scale computing. Simplicity is the idea behind REST APIs, HTTP, and the web itself. Interoperability is the idea behind open standards, open source, and the entire open web movement. Openness is the idea behind the internet, the world wide web, and every system that allows innovation without permission. These ideas were first demonstrated at scale in email, and they have been repeated in every successful digital infrastructure since.

The history of email is not just a history of a communication tool. It is a history of the ideas that made digital infrastructure possible. The engineers who built email were the first to demonstrate that a simple, open, interoperable, asynchronous system could scale to serve the world. The web repeated the pattern. Internet telephony repeated the pattern. Cloud computing repeated the pattern. Every time a digital infrastructure succeeds at scale, it succeeds because it follows the ideas that email proved: keep the protocol simple, make it interoperable, keep it open, and let the ecosystem grow organically. The ideas that matter in the history of email are the ideas that matter in the history of the internet, and they will matter for as long as we build systems that connect people.