How Does Email Work

Email is a system for sending messages between people across the internet, and although it feels instant and simple, a single message quietly travels through several specialized computers called mail servers, using the same packets, addresses, and protocols the how-the-internet-works topic described — email is simply one of the oldest and most important applications built on top of the internet. An email address has two parts split by the `@` sign — a user name and a domain, as in `[email protected]` — and the domain is what tells the system which organization's mail servers are responsible for that person, looked up through the same DNS phone book that web addresses use. When you press Send, your email program (the client) hands the message to your provider's outgoing mail server using a protocol called SMTP (Simple Mail Transfer Protocol), whose only job is moving mail from one server to the next. That outgoing server reads the recipient's domain, asks DNS which mail server handles mail for `example.com`, and delivers the message to it — so email is fundamentally server-to-server relay: your message hops from your provider's server to the recipient's provider's server, rather than going straight to their device. The recipient's server then stores the message in their mailbox and simply waits, which is why email works even when the other person's phone is off — the message sits safely on a server until they come to collect it. Collecting it is the receiving half, and it uses a different protocol: with IMAP (the modern choice) the messages stay on the server and your devices sync to it, which is why the same inbox looks identical on your phone and laptop; the older POP protocol instead downloaded messages to one device and typically removed them from the server. This store-and-forward, server-to-server design is also why email has two stubborn problems. The first is spam and phishing, the unwanted and deceptive mail the staying-safe-online topic warned about, which exists precisely because anyone can send to anyone; providers fight it with filters and with authentication checks that verify a message really came from the domain it claims. The second is privacy: a plain email can be read by the servers that relay it, which is why reputable providers now encrypt messages in transit between servers, using the same kind of encryption introduced earlier. Putting the whole journey together: you type an address, SMTP relays the message server to server with DNS pointing the way, the recipient's server holds it until they fetch it over IMAP, and the message appears in their inbox — a quiet multi-step relay across the internet that the earlier topics already gave you every piece to understand.