How Email Is Delivered

The journey a message takes, from your outbox to someone else's inbox.

Email feels instant, but behind a single click a message is passed between servers, checked for spam, and filed away — usually within seconds, sometimes not.

SMTP: the delivery language

Mail servers talk to one another using SMTP (Simple Mail Transfer Protocol). When you send a message, your mail app hands it to your provider's outgoing server, which looks up where it needs to go and then relays it onward.

Finding the destination: MX records

To deliver a message to someone@example.com, the sending server asks DNS for the MX (mail exchanger) records of example.com. Those records list the servers willing to accept mail for that domain, in priority order, so the sender knows where to connect.

The journey of a message

1. You write a message, and your mail app sends it to your outgoing server.
2. That server looks up the recipient's MX records.
3. It connects to the recipient's mail server and hands the message over.
4. The recipient's server runs spam and virus checks, then files the message in the inbox.
5. If delivery fails, the sending server retries for a while, and eventually returns a bounce.

Why spam filters are so cautious

Email was designed in an era of trust, without built-in proof of who sent a message. In response, modern receivers lean on sender authentication — technologies with names like SPF, DKIM and DMARC — which let them verify that a message really did come from the domain it claims. These checks are a big part of why genuine mail sometimes lands in a spam folder by mistake.

Why it isn't always instant

Retries, temporary greylisting, and queues at a busy receiving server can all add delay. Usually the message arrives in seconds; occasionally it takes minutes. If it truly never arrives, a bounce message is normally the explanation.