technologybriefs
9:48in productionCh. 1 · What SMTP actually is/ 9:48 · ceiling 15 min
Systems · Internet culture

Simple Mail Transfer Protocol

1982

SMTP is not an email protocol—it’s a relay protocol that assumes trust, ignores identity, and outsources security to later layers.

SMTP is a minimal, text-based relay protocol. It enables interoperable server-to-server mail exchange but provides no sender identity, no encryption, and no delivery guarantees. Its longevity stems from its narrow scope—not its completeness.

SystemsInternet cultureComputingInfrastructureThe internetComputing across the network →
Chapters & takeaways4
  1. 1:04
    What SMTP actually is

    SMTP is a standard for server-to-server mail relay—not end-user email.

  2. 2:38
    Origins: from ARPANET to RFC

    It began in 1980 as a replacement for FTP mail, formalised in RFC 788 in 1981.

  3. 4:13
    The client gap

    User clients don’t use SMTP directly—they submit to servers on ports 465 or 587, after ESMTP, submission, and AUTH were added years later.

  4. 5:58
    Where the protocol stops

    SMTP handles only one leg of the journey: server-to-server relay. Everything else requires extensions or separate protocols.

Worth your time?

Yes. Study the whole thing.

3.5/ 5
What works
  • server-to-server message routing
  • human-readable command-response flow
  • port 25 as universal MTA exchange point
What does not
  • authenticate senders
  • encrypt traffic by default
  • guarantee delivery
  • support user-level submission without extensions
Study it if
  • email infrastructure engineers
  • protocol developers
  • security auditors
Skip it if
  • application developers assuming secure email out-of-the-box
  • product managers treating SMTP as a user-facing feature
The written brief1 min read

What it is and the problem it solves

SMTP is an Internet standard protocol for transmitting email between servers. It solves the problem of interoperable, store-and-forward message routing across heterogeneous networks.

How it works

SMTP is a text-based, connection-oriented protocol that runs over TCP. It defines how mail servers and message transfer agents exchange messages using a series of human-readable commands and responses.

What works

Server-to-server message relaying works reliably. The command-response syntax is simple and robust. Port 25 remains the universal channel for mail exchange between MTAs.

What does not

SMTP does not authenticate senders by default. It does not encrypt traffic unless extended with STARTTLS or run over TLS-wrapped ports. It does not guarantee delivery, prevent spoofing, or handle end-user authentication.

What it changes

SMTP replaced FTP as the dedicated transport for email on ARPANET. It established a standardised, server-to-server relay model that persists today—despite requiring decades of extensions to support basic security and submission workflows.

Is it worth your time

Yes—if you maintain email infrastructure, debug delivery failures, or design systems that interoperate with legacy mail routing. No—if you assume modern email security or user identity is built in.

Same field · Systems4 of 61
9:26
3GPP19983GPP is a standards body, not a technology. It delivers specifications—not hardware, software, or services. Its value lies in its method, not its output.
9:54
5G5G is a defined cellular standard—not a monolithic upgrade. Its real-world impact depends entirely on deployment mode, spectrum choice, and backhaul investment. It enables new use cases only where standalone architecture and mid-band spectrum converge. Elsewhere, it functions as a marketing label atop LTE infrastructure.
10:34
Radio broadcasting1895Radio broadcasting did not exist in 1895. Its foundational audio transmissions began in 1906. Its first scheduled, repeatable, commercial services appeared in 1919–1920. Its regulatory definition arrived in 1921. The gap between ‘demonstration’ and ‘service’ was fourteen years—and it was bridged not by invention, but by regulation, licensing, and infrastructure investment.
8:50
Amazon Web Services2006AWS launched S3 in March 2006 as its first generally available Infrastructure-as-a-Service offering. It evolved from internal Amazon platform standardisation efforts beginning in the early 2000s. Its first developer-facing web services shipped in July 2002. Simple Queue Service (SQS) launched in beta in November 2004 and became generally available in July 2006. EC2 followed in August 2006. AWS was the first cloud provider to build infrastructure specifically for U.S. government security and compliance requirements, launching GovCloud in 2011.
Up next in Technology

Sonar

Paul Langevin · 9:59

Langevin’s sonar worked in theory but failed in war — and that gap defined modern underwater sensing.

Play nextBack to Systems
9:59