Email Protocols·Lesson 1 of 8

Email Protocols

01

The Short Answer

Email feels like one thing, but under the hood it takes a team of separate s to make it work. A protocol is just an agreed set of rules that lets two computers understand each other. Three protocols do almost all the work of email: SMTP sends your message out, and POP3 or IMAP fetches messages that have arrived for you. One protocol pushes mail away from you; the other two pull mail toward you.

The one-line summary

SMTP = sending mail (push it out). POP3 and IMAP = receiving mail (pull it in). You almost always use SMTP together with one of the other two — never one instead of the other.

📮

The postal service, split into jobs

Think of the physical mail system. When you drop a letter in the mailbox, a carrier picks it up and relays it from office to office until it reaches the right town — that outbound, hand-it-off job is SMTP. Getting letters that arrived for you out of your PO box is a different job entirely — that's what POP3 and IMAP do. Sending and collecting are two separate tasks, handled by different rules.

02

The Two Jobs of Email

Every email system has to do two fundamentally different things: get a message you wrote out to its destination, and let you read messages that have arrived for you. Those two jobs are why there's more than one protocol. Here are the three you'll meet, and which job each one handles:

📤Sending

SMTP

Simple Mail Transfer Protocol. Pushes your outgoing message from your app to your mail server, and from server to server, until it reaches the recipient's mail server.

📥Receiving

POP3

Post Office Protocol version 3. Downloads incoming mail from the server to one device, and by default removes it from the server afterwards.

🔄Receiving

IMAP

Internet Message Access Protocol. Keeps incoming mail on the server and syncs it across all your devices, so everything stays in step.

03

Where These Protocols Live

All three are application-layer protocols, which just means they're the rules that email programs speak directly — the layer closest to you, not the low-level machinery that moves raw data around. Underneath, they all ride on top of a reliable delivery service called TCP (Transmission Control Protocol), which guarantees the message arrives complete and in order. They also follow the : your email app is the client, and it always talks to a mail server that stores and forwards messages.

04

The Three at a Glance

Before diving into each protocol on its own, it helps to see them side by side. Notice that SMTP is the odd one out — it's the only one for sending — while POP3 and IMAP are two different answers to the same question of how you fetch your mail:

SMTPPOP3IMAP
Main jobSend / relay mailDownload mailAccess & sync mail
DirectionOutgoingIncomingIncoming
Keeps mail on serverN/A (in transit)No (deletes by default)Yes
Good forAll outgoing emailOne device, offlineMany devices in sync
🚫

"SMTP is the protocol that handles all my email, both sending and receiving."

SMTP only pushes mail toward its destination — it cannot pull messages out of your mailbox. Fetching mail so you can read it is a separate job done by POP3 or IMAP. A working email account uses SMTP for outgoing mail and one of the other two for incoming.

Q:Name the three main email protocols and say what each one does.

A: SMTP (Simple Mail Transfer Protocol) sends and relays outgoing mail. POP3 (Post Office Protocol version 3) downloads incoming mail to a single device, usually deleting it from the server. IMAP (Internet Message Access Protocol) keeps mail on the server and syncs it across all your devices. In short: SMTP sends; POP3 and IMAP receive.

Quick Revision Cheat Sheet

SMTP: Simple Mail Transfer Protocol — sends & relays outgoing mail

POP3: Post Office Protocol v3 — downloads mail to one device

IMAP: Internet Message Access Protocol — keeps & syncs mail on the server

Send vs receive: SMTP sends; POP3 and IMAP receive

They work together: SMTP + (POP3 or IMAP), never one instead of the other

Layer: Application-layer protocols running over TCP