How Does Email Delivery Work?
Email delivery is a relay race across servers that finishes in seconds. Your app hands the message to your provider, which finds the receiver server, passes spam and fraud checks, and drops it into the right mailbox. Your friend app then fetches it for reading.
Several old but sturdy systems cooperate in this race: SMTP for sending, DNS for addressing, authentication standards for trust, and IMAP or webmail for reading. This guide traces one message through every handoff and explains delays, bounces, and failures along the way. (IETF RFC 5321)
The short version: SMTP transport, DNS addressing, authentication trust, filter judgment, and mailbox sync chain every message in seconds. Read bounce codes by stage and most mail mysteries solve themselves without guesswork. (Google Support)
The Email Path in Simple Steps
Follow one message from send button to inbox. Your mail app connects to your provider outgoing server with your login, encrypted by TLS where available. The provider accepts the message and reads the destination domain from the address. It asks DNS for that domain MX records, which name the receiving servers in priority order. It opens an SMTP conversation with the top choice, introduces itself, names sender and receiver, and transfers the content. The receiver runs fraud and spam checks before accepting. Accepted mail waits in mailbox storage until the reader app collects it. Each hop logs results, so postmasters can trace any message later. DNS lookups power the addressing step of this race.
Normal delivery finishes in seconds across these hops. Anything slower means queues, greylisting, or failures described below.
SMTP: How Mail Is Sent
SMTP is the simple text conversation servers hold to move mail. Commands arrive in order: greeting, sender address, receiver address, message data, then quit. Replies use three digit codes where 250 means approved and 550 means refused. Authentication lets traveling users prove account ownership before sending, blocking open relays that spammers once abused. TLS wrapping through STARTTLS encrypts the hop where both sides support it, though some legs still travel plain. Size limits, often around tens of megabytes, reject oversized attachments early. Understanding these commands demystifies bounce messages, which quote the failing command and code directly.
SMTP cares about transport, not content. Spam judgment happens in separate filter layers after arrival.
DNS and MX Records
MX records are the postal addresses of email. Each domain publishes a ranked list of servers allowed to receive its mail, and senders try them top down until one accepts. Priority numbers let owners split load and name backup servers for outages. Missing or wrong MX records cause the classic cannot receive mail fault despite working websites, since web and mail records live separately. TTL values control how fast record changes spread during provider moves. Verification strings in TXT records sit beside MX entries to prove domain control to new providers. Senders cache MX answers briefly, so fixes propagate within the TTL window. Our DNS record guide decodes every record type involved.
Check MX records first whenever a domain sends fine but receives nothing. The answer usually hides there.
SPF, DKIM and DMARC Checks
Three standards separate real mail from forgeries. SPF publishes which servers may send for a domain, and receivers reject mismatches. DKIM adds a cryptographic signature in the message header that survives forwarding and proves content stayed intact. DMARC ties both together with a domain policy telling receivers to quarantine or reject failures, plus reports back to owners. Together they power the brand logos and checkmarks readers see in modern inboxes. Domains without all three invite exact domain spoofing of their name. Deployment order runs SPF first, then DKIM signing, then DMARC from monitoring to enforcement. Skipped steps explain most why is my mail rejected mysteries. (IETF RFC 7208)
Authentication protects the domain reputation, which is why providers increasingly require it for bulk senders.
Spam Filters and Queues
Filters score every arrival before the inbox ever sees it. Content checks weigh links, wording, images, and attachments against spam patterns. Reputation checks weigh the sending address history, complaint rates, and blocklist presence. Authentication results feed the score heavily, so aligned mail starts with credit. Greylisting temporarily rejects unknown senders once, expecting real servers to retry while spam engines rarely bother. Queues hold mail through outages and retry on schedules for hours or days. Soft bounces mean try again later, while hard bounces mean stop forever for dead addresses. Final placement weighs all scores against the receiver personal history with the sender.
Filters make mistakes in both directions daily. Understanding their inputs is the only way to fix placement problems.
IMAP, POP and Final Delivery
Delivery ends when reader apps collect stored mail. IMAP syncs folders across phone, computer, and webmail, keeping read states matched everywhere. POP downloads and usually deletes server copies, suiting single device archives. Webmail reads server storage directly through the browser with no protocol sync at all. Push services notify phones of arrivals instantly where supported. Deleted messages often rest in trash folders for weeks before true erasure. Storage quotas block new arrivals silently when full, a common mystery for old accounts. Choose IMAP for modern multi device life and keep an eye on quota warnings. For the login side of mailbox access, see how account authentication works.
The mailbox is the finish line of delivery and the start of your own organizing, filtering, and deleting habits.
Quick Comparison Table
The delivery chain stages and what each one decides.
| Stage | System | Decides | Failure sign |
|---|---|---|---|
| Sending | SMTP plus TLS | Acceptance for transport | Immediate send error |
| Addressing and trust | DNS MX, SPF, DKIM, DMARC | Routing and legitimacy | Bounces, spam folder |
| Reading | IMAP, POP, webmail | What you see | Missing mail, full quota |
Steps You Can Follow Today
No setup needed to understand delivery, but the map fixes future mail mysteries.
- Read bounce messages fully: the code names the failing stage.
- Check MX records when a domain cannot receive anything.
- Set up SPF, DKIM, and DMARC before sending newsletters.
- Prefer IMAP so all devices share one mailbox state.
- Watch storage quotas on old accounts that stop receiving.
Common Questions
Why do emails sometimes arrive hours late?
Queues and greylisting cause most delays. The sender server retries on schedule through outages and past full mailboxes. Greylisting adds one deliberate first delay per new sender. Big providers also throttle unknown senders gradually. Hours long delays almost always clear alone. Day long delays deserve a look at bounce lines and blocklists.
What is the difference between spam and phishing?
Spam is unwanted bulk mail, usually ads, while phishing is fraud wearing trusted disguises to steal logins or money. Filters catch much of both, but phishing needs user judgment too. Check sender addresses letter by letter and never log in through message links. Report phishing to the provider so filters learn faster.
Can email be encrypted?
Transport encryption between servers is now common but not universal, and content stays readable on each server hop. True message secrecy needs OpenPGP or S/MIME, rarely used outside careful circles. Most users should assume providers can read stored mail. For chats needing real secrecy, end to end encrypted messengers fit better than mail.
Why do my newsletters land in spam?
Weak authentication, new domains, spammy wording, and purchased lists trigger filters fast, as the spam placement guide details. Fix authentication first, then clean wording and lists. Ask readers to move one issue to the inbox and reply once. Steady engagement rebuilds sender reputation over weeks.
Final Takeaway
Email delivery chains SMTP transport, DNS addressing, authentication trust, filter judgment, and mailbox sync into seconds of invisible teamwork. Read bounces by stage and most mysteries solve themselves. Continue with why emails go to spam and how account authentication works to master both ends of the mailbox.