How Email Delivery Works

This article explains what happens between pressing send and a message arriving, which is useful background for almost every email problem.
Your Client Connects to the Outgoing Server
Your mail client authenticates against the SMTP server and hands over the message. A failure here is a settings or password problem, and nothing has left your computer yet.
The Server Looks Up Where to Deliver
The sending server reads the recipient domain and looks up its MX records to find which server accepts mail for it. Wrong or missing MX records stop delivery at this point.
The Receiving Server Checks Who You Are
The recipient checks your SPF, DKIM and DMARC records to decide whether the message really came from your domain. Failing these is the most common reason legitimate mail lands in spam.
The Message Is Scored
Content, links, sending history and the reputation of the sending IP address all contribute to a score that decides inbox, spam folder or rejection.
Delivery or Bounce
Accepted mail goes to the mailbox. Rejected mail produces a bounce message containing a code explaining why, which is the most useful diagnostic you will get.
Why Delivery Is Not Instant
Receiving servers sometimes defer a message deliberately, asking the sender to try again shortly. This is called greylisting and it delays a first message from a new sender by several minutes.
What This Means in Practice
Most delivery problems are one of three things: authentication records, sender reputation, or content that scores badly. Checking them in that order resolves the majority.
Next: How to Fix Email Bounceback Errors (Non-Delivery Reports) covers reading the codes.