Email feels like sending a text, but underneath it is closer to the postal service. I write a message, hand it to a series of carriers, and it waits in a mailbox until the other person collects it. No single company owns email, and that is part of why it still works across different providers. Here is the journey, step by step.
An address has two parts
Every email address has a name on the left and a domain on the right, separated by the at sign. The domain tells the sending system which organization should receive the message, much like a town name on an envelope. The name on the left tells that organization which mailbox to use. When I press send, my email app does not deliver the message itself. It hands it to my mail provider’s outgoing server, which takes responsibility for the next stage.
Sending uses SMTP
Sending is handled by a protocol called SMTP, the Simple Mail Transfer Protocol. Think of SMTP as the language of post offices talking to each other. My provider’s server looks up the recipient’s domain in the Domain Name System and asks which server accepts mail for that domain. Then it connects to that server and offers the message. If the receiving server is busy, my provider will usually try again later rather than giving up at once. That retry habit is one reason email is so resilient.
Receiving is a separate job
Once the message arrives, it is stored in the recipient’s mailbox on their provider’s server. It does not go straight to their phone or laptop. When they open their mail app, the app uses a different protocol, usually IMAP, to read what is stored there. IMAP keeps the message on the server and shows me a copy, so I can read the same inbox from my phone and my computer and see the same folders and read states. An older protocol called POP worked differently: it often downloaded messages and removed them from the server, which made switching devices much messier.
Why spam filters mostly work
Spam filters are not one clever trick. They are layers of checks. First, a receiving server can check whether the sending server is allowed to send mail for its claimed domain, using records published by the domain owner. It can also check whether the sender has a bad reputation for sending unwanted mail. Then content filters look for patterns: suspicious links, misleading headers, known scam wording, or attachments that behave badly. Finally, my own actions help. When I mark something as spam, or rescue a message from the spam folder, the system learns a little more about what I consider wanted mail.
Why some mail still slips through
Filters mostly work because most spam is sent in bulk by similar methods, so it is easy to recognize. The harder cases are messages written to look like ordinary mail from a real business, or a message from a newly created domain with no bad history yet. Attackers also adapt quickly, changing wording and sending addresses. That is why no filter can be perfect without also blocking legitimate mail. Providers have to balance the two errors: letting a bad message through, or hiding a good one. The spam folder exists because of that balance, and it is worth glancing at when an expected message does not arrive.
Attachments, size, and delay
An attachment travels inside the message, encoded as text, which makes the message larger than the file alone. Large messages take longer to send, store, and download, and some providers set size limits. That is why a huge video file can fail by email while a link to the same file works fine. Delay can also come from greylisting, where a server briefly refuses a first attempt from an unknown sender and accepts a retry, or from a busy receiving server. Email was designed for reliable delivery, not instant delivery.
The simple picture
So the full picture is this: I compose a message, my app hands it to my provider’s SMTP server, that server finds the recipient’s mail server, and the message waits in a mailbox. The recipient’s app then uses IMAP to read it from wherever they happen to be. Spam filters sit at the gates, checking identity, reputation, and content. It is not glamorous, but it is a good design: open standards, independent providers, and a system built to keep trying. That is why email, for all its clutter, still quietly carries so much of the world’s work.