NetFlow Lab/Protocol Labs/Mail
Simulated
Mission

Follow one email from Alice’s laptop to Bob’s phone — and name the protocol at every box.

the whole journey · three protocols, one emailready
Alice’s mail app
alice@example.com · Thunderbird
idle
SMTP · 587
her app must hand it to a server
Alice’s outgoing server
smtp.example.com · port 587
waiting
SMTP · 25
Internet
out of her provider, across the internet
Bob’s incoming server
mx.corp.net · port 25
waiting
DNSwho takes mail for corp.net?
delivery target
Bob’s mailbox
/var/mail/bob · on the server
empty
— nothing has arrived yet —
the box is where SMTP is aiming
empty

This box is the destination of the whole SMTP journey — not Bob’s phone.

IMAP · 993
Bob has to come and ask
IMAP · 993
second device, same account
Bob’s outgoing server
smtp.corp.net · port 587
waiting
SMTP · 587
a reply needs SMTP again
Bob’s phone
IMAP 143 plain / 993 TLS · reads in place
offline · nothing waiting for it
Bob’s laptop
same account, second device
not checked yet
the four answers a beginner actually needs
who moves mail between servers
SMTP · 587 then 25

always — push only, never pulls anything

who takes it out of the mailbox
IMAP · 143 or 993

143 is the original plaintext port; 993 is the same IMAP wrapped in TLS — pull only, it cannot send

where the mailbox lives
the server

devices hold copies of it

what the second device sees
— not checked yet —

run the journey to the laptop step

journey_control
How Bob picks his mail up
not started
1Alice writes the mail and hits Send—
2Laptop → her own outgoing serverSMTP 587
3Which server owns corp.net mail?DNS
4Her server → internet → Bob’s incoming serverSMTP 25
5Written into Bob’s mailbox — SMTP is doneSMTP ends
6Phone opens the mailbox where it liesIMAP 993
7He reads it — and the laptop already knowsIMAP 993
8Bob replies — and IMAP cannot carry itSMTP 587
Think first · step 1 of 8

Nothing has left Alice’s laptop yet. What has to happen before any protocol gets involved?

in plain words · start here

Three protocols, three jobs. SMTP carries the mail from Alice as far as Bob’s server and stops. Then IMAP or POP3 — Bob’s choice — gets it out of the mailbox and onto his screen. Press Send and watch each box light up.

SMTP 25/587 pushes · IMAP 143/993 or POP3 110/995 pulls · nothing does both
what the two computers actually said
nothing on the wire yet — press Send and the plain-text commands appear here, line by line
the three mistakes everyone makes

“Email is one protocol.” It is three jobs. SMTP pushes mail towards a mailbox. IMAP or POP3 pulls it out of one. No protocol does both.

“SMTP delivers to Bob.” SMTP stops at Bob’s server. His phone was offline the whole time and nothing waited for it.

“POP3 always deletes downloaded mail.” It does not. RETR downloads; DELE marks a message for removal, and QUIT commits that removal. This demo deliberately shows delete-after-download. IMAP additionally provides server-side folders and shared state across devices.

deeper dives · DNS lab · TCP lab