What the history of email teaches us about the world

01Standards are chosen, not inevitable

The first lesson of email is that standards are chosen, not inevitable. The email system we have today, with SMTP as its protocol and the @ symbol as its addressing convention, was not the only possible system. X.400 was the official international standard, backed by governments and major corporations. It was technically superior, more structured, and more capable. It lost to SMTP because SMTP was simpler and easier to implement. The choice was not made by a standards body or a regulator. It was made by the market: by the engineers who implemented SMTP instead of X.400, by the companies that deployed SMTP servers instead of X.400 gateways, and by the users who chose systems that spoke SMTP instead of systems that spoke X.400.

This lesson applies to every technology that connects people. The standard that wins is not the one that is technically best. It is the one that is easiest to adopt. This is why HTTP won over Gopher, why TCP/IP won over OSI, and why SMTP won over X.400. In each case, the simpler, more open, easier-to-implement standard defeated the more sophisticated, more controlled, harder-to-implement alternative. The lesson is that if you want a standard to be adopted, make it simple. The world chooses simplicity over sophistication, every time, because simplicity is what enables adoption, and adoption is what makes a standard universal.

02Openness defeats control

The second lesson is that openness defeats control. In the 1980s and 1990s, the major online services, CompuServe, AOL, Prodigy, and MCI Mail, tried to control electronic messaging. They built walled gardens where users could only communicate with other users on the same service. They charged for every message. They controlled the user experience. And they lost. They lost because users wanted to reach everyone, not just the people on the same platform. They lost because the open email system, with no gatekeeper and no charge per message, was more valuable than any closed system could be.

This lesson is being relearned today. Modern messaging platforms, Slack, Teams, WhatsApp, Telegram, Signal, iMessage, are all walled gardens. They are all trying to control electronic messaging the same way CompuServe and AOL did thirty years ago. The history of email predicts that they will eventually fail, because users want to reach everyone, and openness is what enables that. The walled gardens will either open up or be replaced by something that is open. The process will take years, and it will be resisted by the companies that benefit from control, but the outcome is predictable. Openness defeats control, because openness is what users want, and users eventually get what they want.

03Infrastructure becomes invisible

The third lesson is that infrastructure becomes invisible when it works. Email is one of the most used technologies in the world, and it is almost invisible. You do not think about SMTP when you send an email. You do not think about DNS when you look up an address. You do not think about IMAP when you check your inbox. The infrastructure works in the background, and you only notice it when it breaks. This is the mark of successful infrastructure: it disappears. The telephone network disappeared. The power grid disappeared. The water system disappeared. Email disappeared.

The invisibility of infrastructure is a problem, because it means people do not understand the systems they depend on. They do not know how email works, who maintains it, or what keeps it running. They do not know that the email system is not owned by anyone, that it is maintained by a community of engineers, and that it works because of a set of protocols that were designed forty years ago. The invisibility of email is a sign of its success, but it is also a vulnerability. If people do not understand the infrastructure they depend on, they cannot defend it. They cannot resist attempts to control it. They cannot appreciate the work that goes into maintaining it. The lesson of email is that the best infrastructure is invisible, but the invisibility comes with a cost: the systems that matter most are the ones we think about least.

04Simplicity scales

The fourth lesson is that simplicity scales. SMTP was designed to be simple, and that simplicity is what allowed it to scale. A protocol that is easy to implement can be implemented by anyone. A protocol that is easy to understand can be debugged by anyone. A protocol that is easy to deploy can be deployed by anyone. When anyone can implement, debug, and deploy a protocol, it spreads. SMTP spread because it was the simplest email protocol, not because it was the best. The same principle applies to every infrastructure technology. The technologies that scale are the technologies that are simple enough to be adopted by everyone, not the technologies that are sophisticated enough to handle every edge case.

Simplicity is not just about the protocol. It is about the entire system. Email is simple to use: you type a message, enter an address, and press send. It is simple to understand: messages are like letters, and the @ symbol tells you where the mailbox is. It is simple to trust: the system has been working for forty years, and everyone has an email address. The simplicity of email is not a limitation; it is a feature. It is the feature that made email the most used communication tool in history. The lesson is that if you want to reach billions of people, make your technology simple. Simplicity is what scales, and scale is what changes the world.

05Small groups can shape the world

The fifth lesson is that small groups can shape the world. The email system that billions of people use today was designed by a small community of engineers in the 1970s and 1980s. Jon Postel wrote the Robustness Principle. Ray Tomlinson chose the @ symbol. Jonathan B. Postel and others refined the protocol through the RFC process. These were not corporate executives or government officials. They were engineers who cared about a system and who were willing to build it. The decisions they made, the protocols they designed, and the principles they followed determined how the world would communicate for the next fifty years.

This lesson is both inspiring and sobering. It is inspiring because it means that a small group of people can build something that changes the world. It is sobering because it means that the choices made by a small group of people today will determine how the world works for decades. The engineers who built email did not know that their system would be used by billions of people. They were solving a local problem: how to send messages between computers on the ARPANET. The system they built solved that problem so well that it scaled to the entire world. The lesson is that the systems we build today, no matter how small their original purpose, may become the infrastructure that the world depends on tomorrow. We should build accordingly.

06The tradeoff between openness and safety

The sixth lesson is that openness and safety are always in tension. Email is an open system, and its openness is what makes it valuable. But its openness is also what makes it vulnerable. Spam, phishing, and malware are the direct consequences of an open system that anyone can use. The email community has spent thirty years fighting these threats, and the fight will never end, because the openness that enables them is the same openness that makes email valuable. Every attempt to make email safer must be balanced against the risk of making it less open.

This tradeoff is not unique to email. It is the fundamental tradeoff of every open system. The open web has the same tradeoff: anyone can publish anything, which means anyone can publish misinformation. Open source software has the same tradeoff: anyone can contribute code, which means anyone can introduce vulnerabilities. Open APIs have the same tradeoff: anyone can use them, which means anyone can abuse them. The lesson of email is that you cannot eliminate this tradeoff. You can manage it, with filters, authentication, and education, but you cannot eliminate it without also eliminating the openness that makes the system valuable. The challenge is to find the right balance, and the right balance is never static. It changes as the threats change, as the technology changes, and as the community changes. Managing this balance is the ongoing work of every open system.

07The systems that connect us are shaped by choices

The final lesson is the most important one: the systems that connect us are shaped by choices, and those choices matter more than the technology. Email works because a group of engineers chose simplicity over complexity, openness over control, and interoperability over lock-in. They could have made different choices. X.400 could have won. The walled gardens could have survived. The @ symbol could have been something else. The protocol could have been more complex, more capable, and less widely adopted. The email system we have is the result of choices, and those choices were made by people who cared about the system and who were willing to build it their way.

This lesson matters because we are making the same choices today, in different technologies. We are choosing between open and closed systems in social media, in messaging, in artificial intelligence, and in every technology that connects people. The choices we make will determine how people communicate for the next fifty years, just as the choices made by the email pioneers determined how we communicate for the last fifty. The history of email is not just a history of a technology. It is a reminder that infrastructure is built by people, that the choices those people make matter, and that the systems we depend on are never inevitable. They are the products of decisions, and those decisions are ours to make.