Email moves through a chain of servers, not directly from your inbox to theirs
When you hit send on an email, your message does not travel straight to the recipient. Instead, it bounces through at least two separate mail servers — one that accepts it from you, and one that holds it until the other person retrieves it. Understanding this chain matters because it explains why emails sometimes take time to arrive, why they occasionally vanish, and what actually happens when you click send.
The process starts on your device. Your email client — whether that is Gmail in a browser, Outlook on your computer, or Apple Mail on your phone — connects to your mail provider's outgoing mail server, also called an SMTP server (straightforward Mail Transfer Protocol). You authenticate with your password. The server accepts your message and takes responsibility for delivering it. From that moment, the email is no longer just on your device; it exists on your provider's infrastructure.
Your outgoing server then looks up where to send the message. It reads the recipient's email address, extracts the domain (the part after the @), and queries the internet's mail routing system to find that domain's incoming mail server. If you are sending to someone at gmail.com, your server contacts Google's mail servers. If you are sending to a company domain, it contacts that company's mail infrastructure. This lookup and handoff usually takes seconds.
Key Takeaways
- Your email provider's outgoing server (SMTP) accepts your message and routes it to the recipient's incoming server (IMAP or POP3), not directly to their device.
- The recipient's mail server stores your message until they log in and retrieve it, which is why they do not see it when ready even after you send it.
- Email addresses contain routing information — the domain part tells the internet which server should receive the message.
- Authentication, encryption, and spam filtering happen at multiple points in the chain, which is why some emails are delayed or rejected.
- You can send email through your provider's web interface, a desktop client, or a mobile app — the underlying mechanics are the same.
What happens on the recipient's server
Once the recipient's mail server receives your message, it stores it in their mailbox on that server. The message sits there until the recipient logs in and retrieves it. This is a crucial difference from how many people imagine email works: the recipient does not receive a notification that a message exists. Instead, their email client — Gmail, Outlook, Apple Mail, or whatever they use — periodically checks their mail server and downloads new messages.
The recipient's server uses either IMAP (Internet Message Access Protocol) or POP3 (Post Office Protocol 3) to hand over messages. IMAP is more common now because it keeps a copy on the server even after the recipient reads the message, so they can access it from multiple devices. POP3 downloads the message to the device and typically deletes it from the server, which is why older setups sometimes lost emails if someone checked mail on two different computers.
The delay between when you send and when they see it depends on how often their client checks for new mail. Gmail in a browser checks constantly, so messages appear within seconds. A desktop client set to check every five minutes will show the email within five minutes. A phone that checks mail only when opened might not show it for hours. The email itself arrived at the server when ready; the delay is on the retrieval side.
Authentication and spam filtering along the way
Modern email systems check your identity at multiple points. When you connect to your outgoing server, you authenticate with your password or an app-specific token. This proves you are authorized to send mail from that address. Without this step, anyone could send email claiming to be you.
The recipient's server also checks your identity — not by asking you directly, but by verifying cryptographic signatures attached to your message. The most common system is SPF (Sender Policy Framework), which checks whether the server sending the message is authorized to send mail for your domain. DKIM (DomainKeys Identified Mail) adds a digital signature to the message itself. DMARC (Domain-based Message Authentication, Reporting and Conformance) tells the recipient's server what to do if these checks fail — accept it anyway, mark it as suspicious, or reject it outright.
Spam filters run on the recipient's server and sometimes on yours. They scan the message content, check the sender's reputation, look for phishing patterns, and compare the message against known spam databases. A message that passes authentication but looks like spam might land in a spam folder instead of the inbox. This is why legitimate emails sometimes disappear: a filter made a mistake, or the sender's domain has a poor reputation.
The difference between web mail and client-based email
When you use Gmail, Outlook.com, or Yahoo Mail in a web browser, you are accessing your mailbox directly on the provider's server. You log in, and the website shows you the messages stored there. When you send an email, the browser connects to the provider's SMTP server on your behalf. The mechanics are identical to using a desktop client; the interface is just different.
A desktop client like Outlook, Apple Mail, or Thunderbird works differently in appearance but the same way underneath. You configure it with your email address, password, and the addresses of your provider's SMTP and IMAP servers. The client stores a local copy of your messages and syncs with the server periodically. When you send, it connects to SMTP. When you check mail, it connects to IMAP and downloads new messages. The advantage is that you can read old messages even without an internet connection, because they are stored locally.
Mobile apps work the same way as desktop clients, except they are designed to use less data and battery. They check for mail less frequently unless you have push notifications enabled, which requires the app to maintain a constant connection to the mail server.
Why emails sometimes take time or get lost
Email is not instantaneous, despite feeling that way most of the time. Several things can cause delays. If your outgoing server is busy or the recipient's server is temporarily unreachable, your server will queue the message and retry it periodically — usually for 24 to 48 hours. If the recipient's server rejects the message (because of authentication failure, spam filtering, or a full mailbox), your server bounces it back to you with an error message.
Emails also get lost when they land in spam folders and are never retrieved. This happens more often with automated emails (receipts, notifications, password resets) than with person-to-person mail. The recipient never sees a notification that the message arrived, so they do not know to look for it.
Large attachments can also cause problems. Some mail servers reject messages over a certain size, typically 25 to 50 megabytes. If you send a 100 MB file, it will bounce. This is why cloud storage links (Google Drive, Dropbox, OneDrive) are more reliable than attachments for large files.
How to send email from different devices and services
You can send email from any device or service that can connect to your mail provider's SMTP server. This is why you can check the same email account on your phone, your laptop, and a web browser — they all connect to the same underlying mailbox on the provider's server.
Some services let you send email on your behalf without giving them your password. Gmail, Outlook, and Yahoo all support OAuth, a system that lets you authorize an app to send mail without sharing your actual password. When you connect a third-party service (like a form submission tool or a scheduling app) to your email account, you usually grant it permission through OAuth rather than typing your password into the app.
You can also set up email forwarding, where messages sent to one address automatically get forwarded to another. This happens on the mail server side, not on your device. If you forward mail from work to personal, the work server receives the message, then when ready sends it to your personal server. The recipient sees it coming from your work address, not your personal one, unless the forwarding is set up to rewrite the sender.
Setting up email on a new device
To set up email on a new phone or computer, you need four pieces of information: your email address, your password (or an app-specific password if your provider requires one), your incoming mail server address, and your outgoing mail server address. For major providers, most clients have these built in — you just type your email and password and the client fills in the rest.
For a work email or a custom domain, you will need to ask your IT department or email provider for the server addresses. They usually look like mail.company.com or smtp.company.com. The incoming server uses IMAP or POP3 (IMAP is standard now). The outgoing server uses SMTP, almost always on port 587 with encryption enabled.
Once configured, the client will read your existing messages from the server. If you set it to IMAP, it will sync with the server continuously, so messages you read on one device will show as read on another. If you set it to POP3, it will read messages to that device only, and they will not sync across devices.
Frequently Asked Questions
Can someone read my email while it is in transit between servers?
Modern email uses encryption (TLS) between servers, so the message is scrambled in transit. However, the message is stored unencrypted on both your provider's server and the recipient's server. If either server is compromised, the message can be read. End-to-end encryption (like PGP or Signal) encrypts the message so that only the recipient can decrypt it, but this requires both parties to set it up.
Why do I sometimes get emails I never sent?
Your email address may have been spoofed — someone sent a message with your address in the "from" field. This is straightforward to do because SMTP does not verify who is actually sending the message, only that the sending server is authorized to send mail from that domain. If your domain has weak authentication (no SPF, DKIM, or DMARC), spoofing is trivial. The recipient's spam filter should catch most spoofed mail, but some gets through.
What is the difference between CC and BCC?
CC (carbon copy) adds recipients whose addresses are visible to everyone on the email. BCC (blind carbon copy) adds recipients whose addresses are hidden from other recipients. The BCC recipients receive the message, but no one else knows they got it. This is useful for sending the same message to many people without revealing everyone's email address.
Can I unsend an email after I hit send?
Most email providers offer an undo feature, but it only works for a few seconds after you send — usually 5 to 30 seconds depending on the provider. After that window closes, the message has left your server and is on its way to the recipient's server. Some providers let you recall a message if the recipient has not read it yet, but this only works if both people use the same provider and the recipient's client supports recall.
Why do emails sometimes arrive out of order?
Emails are not may provide to arrive in the order you send them, especially if you send multiple messages in quick succession. Each message takes its own path through the internet and may experience different delays. Additionally, if you send an email, then the recipient replies, then you send another email, the reply might arrive before your second message. This is why email threads group messages by conversation rather than by send time.