Hit send on an email and it feels instant. It isn’t. Between that click and the message landing in an inbox, it passes through at least four separate servers, gets encrypted, signed, looked up in DNS twice, scanned for spam, and stamped with a header at every stop.
Chapter 2 walks that path in the order it actually happens. It starts with your mail client submitting the message to a Mail Submission Agent on port 587 — not port 25, which is reserved for server-to-server traffic, a distinction that trips up more people than you’d expect. From there: a TLS handshake negotiates encryption, DKIM signs the message before it hits the outbound queue, a DNS lookup finds the recipient’s mail server via its MX record, and the sending and receiving MTAs have a short conversation on port 25 to hand the message off.
That’s where authentication checks happen — SPF, DKIM, DMARC, all evaluated by the receiving server before the message goes anywhere near a spam filter. Then filtering, final delivery to the mailbox, and IMAP retrieval when you actually open your inbox.
The chapter’s real payoff is the section on Received headers. Every server that touches a message adds one, stacked in reverse chronological order, and read correctly they’re a complete audit trail of where an email has been. Get the reading order wrong (top-to-bottom instead of bottom-to-top) and the whole trail inverts — a mistake that shows up constantly in forum troubleshooting threads.
It closes with bounce messages: what happens when step 9 fails, and how the ESMTP capability set changes what’s possible in the conversation. If you’ve ever wondered what actually happens in the fraction of a second after you hit send, this is the chapter that answers it with real header examples, not a flowchart.