1982: SMTP: The Protocol That Standardized Email

Every day, more than 350 billion emails travel across the internet. They flow between Gmail and Outlook, from corporate servers to personal inboxes, across continents and through countless network hops. Every single one of those emails is transmitted using a protocol that was written in 1982 by a man who believed in keeping things simple. Its name tells you everything you need to know: Simple Mail Transfer Protocol — SMTP.

The Wild West of Early Email

By the early 1980s, email was already popular on ARPANET, but it was a mess. Different computer systems used different protocols, different address formats, and different routing methods. Sending an email from one type of system to another often required awkward gateways and manual intervention. It was like having a dozen different postal systems in the same country, each with its own address format and its own fleet of trucks that couldn’t use anyone else’s roads.

Several email protocols competed for dominance: FTP-based mail transfer (yes, the file transfer protocol was used to send email), the Mail Transfer Protocol (MTP), and various proprietary systems. The result was fragmentation. You could email people on your network, but reaching people on other networks was unreliable at best.

Jon Postel and RFC 821

Enter Jon Postel, one of the most influential figures in internet history. Postel was a computer scientist at the University of Southern California’s Information Sciences Institute (ISI) and served as the editor of the RFC (Request for Comments) series — the documents that define how the internet works. He was also the person who managed IANA, the Internet Assigned Numbers Authority, essentially serving as the internet’s chief administrator for decades.

In August 1982, Postel published RFC 821, which defined the Simple Mail Transfer Protocol. The document was 68 pages of clear, precise specification that laid out exactly how one computer should transfer email to another computer. Published alongside it was RFC 822 by David Crocker, which defined the format of email messages themselves — the headers, the body, the structure.

Together, RFC 821 and RFC 822 became the twin pillars of modern email.

How SMTP Works

Postel designed SMTP around a beautifully simple conversation model. When one server wants to send an email to another, they engage in a text-based dialogue that reads almost like human conversation:

The sending server connects and says HELO (yes, with one L — engineers in the 1980s were fond of abbreviations). The receiving server responds. The sender says who the mail is from (MAIL FROM), who it’s going to (RCPT TO), and then transmits the message data (DATA). The receiver acknowledges each step with numeric response codes — 250 for “OK,” 550 for “mailbox not found,” and so on.

This simplicity was intentional. Postel’s famous dictum, known as the Robustness Principle, states: “Be conservative in what you send, be liberal in what you accept.” This philosophy made SMTP incredibly resilient. Servers didn’t need to be perfect — they just needed to follow a few basic rules.

The Extensions: ESMTP and Beyond

The original SMTP was deliberately minimal. It handled plain text messages with ASCII characters and not much else. As email grew, so did the demands placed on the protocol.

In 1995, RFC 1869 introduced Extended SMTP (ESMTP), which allowed servers to advertise and negotiate additional capabilities. This extension framework enabled crucial features without breaking the original protocol: STARTTLS for encryption (1999), SMTP AUTH for authentication (1999), 8BITMIME for international characters, and many others.

The genius of the extension system was that it was backward compatible. A modern mail server can still talk to a server running basic SMTP from 1982. New capabilities are negotiated, not required. This backward compatibility is a major reason why email has survived and thrived for over four decades while countless other communication technologies have come and gone.

The Security Problem

There’s a catch to SMTP’s simplicity: it was designed in an era of trust. The original protocol included no encryption, no authentication, and no way to verify that the sender was who they claimed to be. When SMTP was created, ARPANET was a small community of researchers who all knew each other. There was no reason to build in defenses against impersonation or eavesdropping.

This lack of built-in security is the root cause of nearly every email security problem we face today. Spam, phishing, spoofing, business email compromise — all of these exploit the fact that SMTP doesn’t natively verify identity. The authentication systems we’ve bolted on since (SPF in 2003, DKIM in 2007, DMARC in 2012) are all patches on a protocol that was never designed to resist abuse.

Why It Matters

SMTP is one of the oldest protocols still in daily use on the internet. It predates HTTP (1991), DNS (1983 in its modern form), and the World Wide Web itself. More than four decades after Postel wrote RFC 821, SMTP remains the backbone of global email communication.

Jon Postel passed away on October 16, 1998, at the age of 55. By then, his protocol had already delivered billions of messages. Today, it delivers hundreds of billions daily, connecting 4.5 billion email users worldwide. If the internet has a founding document for human communication, it’s RFC 821.

Understanding how SMTP works isn’t just history — it’s essential knowledge for anyone serious about email deliverability today. The authentication layers built on top of SMTP (SPF, DKIM, DMARC) are now mandatory for bulk senders. Learn more about how these systems evolved in our SPF, DKIM, and DMARC history.

Infographic

Share this visual summary. Right-click to save.

Frequently Asked Questions

What is SMTP and when was it created?

SMTP (Simple Mail Transfer Protocol) was defined in RFC 821, published in August 1982 by Jon Postel. It standardized how email is transmitted between servers across the internet.

Is SMTP still used today?

Yes. SMTP is still the foundation of all email transmission. While extensions like ESMTP, STARTTLS, and authentication layers have been added, the core protocol from 1982 still powers every email sent today.

Why was SMTP important for email?

Before SMTP, different email systems couldn't communicate with each other. SMTP created a universal language that any mail server could use to send messages to any other mail server, making email truly global.