How One Protocol Sends Billions of Emails – SMTP Explained

Email is a foundational pillar of the internet, powering everything from user authentication (OTP and login verification) to marketing campaigns and complex e-commerce platforms. Despite its critical role in distributed system design, the underlying machinery is frequently ignored by modern developers. This guide explores the Simple Mail Transfer Protocol (SMTP), its internal architecture, the multi-hop relay chain, and how retrieval protocols like IMAP and POP3 complete the email lifecycle.

1. Why Do We Need SMTP in System Design?

In modern software engineering, systems rarely operate in complete isolation. Most production applications must communicate asynchronously with users for vital operational tasks.

• System Requirements: Applications routinely require mechanisms to send password reset links, one-time passwords (OTPs), verification emails, invoice notifications, and automated billing receipts.
• The Scalability Challenge: Designing a robust CRM or e-commerce platform requires scaling email dispatch alongside core application workloads. Failing to account for email infrastructure bottlenecks leads to dropped notifications and broken user trust.
• Industry Standard Base Layer: Modern managed email services (such as AWS SES) rely directly on SMTP as their foundational transport layer.

2. Core Mental Model: The Postal Service Analogy

To understand how email transmission works across disparate networks, think of sending a physical letter through the postal service:

• The Mail User Agent (MUA) acts as your personal stationery and envelope. It is the client interface (like Outlook, Gmail, or your application's SDK) used to compose the message.
• The Mail Submission Agent (MSA) is like dropping your letter into a local neighborhood mailbox or handing it directly to the post office desk clerk to verify postage and formatting.
• The Mail Transfer Agent (MTA) represents the fleet of postal trucks and sorting hubs that inspect the destination address, query routing maps, and hand the letter off across multiple regional hubs until it reaches the destination city.
• The Mail Delivery Agent (MDA) is the local mail carrier who places the sorted letter directly into the recipient's physical mailbox or PO box.
• POP3/IMAP Protocols act as the recipient walking out to their porch mailbox to inspect, read, or retrieve their delivered mail.

3. What is SMTP? (Definition and Characteristics)

SMTP (Simple Mail Transfer Protocol) is the technical standard and networking protocol used for transmitting electronic mail over a network.

• Cross-Hardware Compatibility: Like other core networking protocols, SMTP allows computers and servers to exchange data seamlessly regardless of their underlying hardware or operating system.
• A Push Protocol: SMTP is exclusively a transport and push protocol. It moves email messages from one server to another across the internet. It is not designed for reading or retrieving emails.
• TCP Foundation: SMTP operates directly on top of the TCP (Transmission Control Protocol) network stack. A reliable TCP connection is established between the client and the email server before any commands or payloads are transmitted, guaranteeing ordered and error-checked data delivery.

4. The 3 Loosely Coupled Systems of Email Architecture

Email infrastructure is not a monolithic program; it is composed of three distinct, loosely coupled subsystems operating together:

1. SMTP Server & Relay Chain: Handles the outward transmission, routing, and multi-hop transport of messages across the internet.
2. Receiving & Storage System: Composed of the mail server and mailbox storage (managed by the Mail Delivery Agent), holding messages securely until retrieved.
3. Retrieval & Synchronization System: Protocols (POP3 and IMAP) that allow end-user clients to connect, sync, and read stored messages.

5. Step-by-Step Evolution: Inside the SMTP Relay Chain

When an email is dispatched from a client application or email user agent, it passes through an orchestrated sequence of specialized software components:

Step A: Mail User Agent (MUA) Initialization

The user (or application code) creates the email headers and body via an email client. The client connects directly to the email provider's SMTP server over TCP.

Step B: Mail Submission Agent (MSA) Intake

The MSA receives the initial email batch from the MUA. Its primary job is to validate syntax, check authentication credentials, and ensure the message complies with basic submission standards before routing.

Step C: Mail Transfer Agent (MTA) & DNS Resolution

The MTA takes the email from the MSA and determines how to route it across the network:

• DNS Lookups: The MTA queries Domain Name System (DNS) records to locate the recipient domain's routing instructions.
• MX Records: Specifically, SMTP looks for Mail Exchange (MX) records associated with the recipient's domain name. These records indicate exactly which mail servers are authorized to accept messages for that domain.
• IP Translation: The MTA maps the domain name to the recipient mail server's IP address and initiates a TCP connection to push the payload to the next hop in the delivery chain.

Step D: Mail Delivery Agent (MDA) Storage

Once the email reaches the destination server, the Mail Delivery Agent (MDA) accepts the message from the MTA and stores it directly inside the recipient's designated mailbox storage.

6. Accessing Messages: IMAP vs. POP3

Once an email is safely stored in the recipient's mailbox by the MDA, the user needs a protocol to read it. Two primary protocols serve this function: IMAP and POP3.

IMAP (Internet Message Access Protocol)

IMAP is the modern, recommended standard for users who need to check their emails across multiple devices (phones, laptops, tablets) simultaneously.

• Server-Side Storage: When you read an email using IMAP, the message remains stored on the remote email server. The client only downloads a preview (subject line, sender name) until you explicitly click to open the body.
• Multi-Device Synchronization: Actions taken on one device (such as marking an email as read, flagging, or moving to a folder) synchronize across all connected devices in real time.
• Internet Dependency: Because emails are not permanently stored locally, an active internet connection is required to view message bodies and attachments.

POP3 (Post Office Protocol version 3)

POP3 is an older protocol that downloads email messages directly from the server to a single local device.

• Local Download & Delete: POP3 contacts the email server, downloads all new messages onto the local machine (PC or Mac), and then deletes them from the server completely (unless configured otherwise).
• Single-Device Access: Once downloaded, the email resides exclusively on that specific computer and can only be accessed offline from that machine.
• Server Storage Conservation: Because messages are wiped from the remote server upon download, server storage overhead is drastically minimized. However, if the local hardware fails without a backup, all historical emails are permanently lost.

7. Comparative Synthesis: IMAP vs. POP3

8. Summary and Key Takeaways

• Critical Infrastructure: SMTP is the foundational push protocol powering global email transmission; ignoring it in system design leads to brittle notification and authentication pipelines.
• TCP Foundation: SMTP operates directly on top of reliable TCP connections, ensuring structured, ordered handshakes between sending and receiving mail servers.
• A Push Protocol: SMTP is strictly engineered for transporting and pushing mail across servers; it is never used for reading or retrieving inbox messages.
• Three Loosely Coupled Systems: Email architecture separates concerns into the SMTP Relay Chain, Receiving/Storage (MDA), and Retrieval/Sync (IMAP/POP3).
• The Multi-Hop Relay Pipeline: Emails travel through a specialized sequence of software agents: MUA (Client) -> MSA (Submission) -> MTA (Transfer & DNS/MX Resolution) -> MDA (Delivery & Storage).
• DNS MX Records: MTAs query domain MX (Mail Exchange) records to resolve destination domain names into target server IP addresses.
• IMAP for Multi-Device Sync: IMAP leaves messages on the server, acting as an intermediary, making it ideal for multi-device access and real-time synchronization.
• POP3 for Local Storage: POP3 downloads messages locally and removes them from the server, conserving remote storage but tying access to a single physical device.