Email is a relay race. One protocol sends the message. Another stores it. Another proves it is not a scam wearing a fake mustache. Once you see the parts, email stops feeling like magic and starts looking like a very patient postal system.
TLDR: SMTP sends email, while IMAP and POP3 help you read it. For example, when Maya sends a 2 MB invoice to 40 clients, SMTP moves it out, IMAP lets her see replies on her phone and laptop, and SPF/DKIM/DMARC help stop fake copies. In many business inboxes, more than 45% of incoming mail can be spam or phishing, so these standards matter a lot.
The short version: who does what?
- SMTP: Sends email from one place to another.
- IMAP: Keeps your mail on the server and syncs it across devices.
- POP3: Downloads mail to one device. Old-school, but still used.
- MIME: Lets email carry images, files, and fancy text.
- TLS: Encrypts email connections.
- SPF, DKIM, and DMARC: Help prove a sender is real.
Think of email as a tiny package trip. You write a note. Your app hands it to a sending server. That server checks the address. Then it passes the note through the internet until it lands at the recipient’s mail server.
SMTP: the outgoing mail truck
SMTP stands for Simple Mail Transfer Protocol. It is the main way email gets sent.
When you hit Send, SMTP takes over. It does not care if your message is sweet, boring, or a passive-aggressive “just checking in.” It just moves the mail.
SMTP usually does this:
- Your email app connects to an SMTP server.
- The server checks your login.
- It reads the recipient address.
- It asks DNS where that recipient gets mail.
- It hands the message to the right mail server.
SMTP is great at sending. It is not great at storing. That is not its job. Asking SMTP to manage your inbox is like asking a delivery driver to organize your desk drawer.
Common SMTP ports include:
- 25: Server-to-server mail transfer.
- 587: Sending mail from apps, usually with login and TLS.
- 465: Older secure SMTP style, still often supported.
IMAP: your synced mailbox brain
IMAP stands for Internet Message Access Protocol. It lets you view and manage email on the server.
This is why your phone, laptop, tablet, and webmail all show the same inbox. Delete a message on your phone, and it disappears on your laptop too. Mark it unread at work, and it still looks unread at home.
Honestly, it feels like a small miracle until sync gets stuck for 18 seconds and you wonder if your “sent” message went into a black hole.
IMAP is best when:
- You use more than one device.
- You want folders to stay in sync.
- You need search across old mail.
- You want your messages backed up on the mail server.
Common IMAP ports:
- 143: IMAP, often upgraded with STARTTLS.
- 993: IMAP over TLS.
POP3: the “grab it and go” option
POP3 stands for Post Office Protocol version 3. It downloads mail from the server to your device.
In the old days, this made sense. People had one computer. Storage on servers was small. You connected, grabbed your mail, and often removed it from the server.
POP3 can still be useful. Some people like having local copies. Some small systems use it because it is simple. But for modern life, it can feel clumsy.
The annoying part? If POP3 is set to delete mail after download, your desktop may get the email, while your phone sees nothing. Great. Now your inbox has trust issues.
Common POP3 ports:
- 110: POP3, often upgraded with encryption.
- 995: POP3 over TLS.
IMAP vs POP3: which should you use?
| Feature | IMAP | POP3 |
|---|---|---|
| Best for many devices | Yes | No |
| Mail stays on server | Yes | Sometimes |
| Works well offline | Somewhat | Yes |
| Simple setup | Good | Very simple |
For most people, IMAP wins. It fits modern work. It keeps mail in sync. POP3 is fine for special cases, but it is not the friendly default anymore.
MIME: why email can carry more than plain text
Early email was plain text. No attachments. No bold text. No cat photos. Sad times.
MIME fixed that. It stands for Multipurpose Internet Mail Extensions. MIME tells email apps how to package and display different content types.
Thanks to MIME, an email can include:
- PDF files
- Images
- HTML layouts
- Calendar invites
- Plain text backup versions
That last one matters. A good HTML email should also include a plain text version. Some apps block images. Some tools strip formatting. Plain text saves the day.
TLS: the privacy jacket
TLS stands for Transport Layer Security. It encrypts the connection between your email app and the server.
Without TLS, messages can be exposed while they travel between systems. With TLS, the connection is wrapped in encryption. That makes spying much harder.
But here is the catch. TLS protects the trip between servers. It does not always mean the final stored message is encrypted. If you need full message privacy, look at end-to-end encryption tools like PGP or S/MIME.
SPF, DKIM, and DMARC: the bouncers at the email club
Scammers love email. It is cheap. It is quick. It reaches everyone from CEOs to grandmas.
So email needs identity checks.
- SPF says which servers may send mail for a domain.
- DKIM adds a digital signature to prove the message was not changed.
- DMARC tells receiving servers what to do when SPF or DKIM fails.
Picture a fake email that claims to be from your bank. SPF asks, “Did this mail come from an approved bank server?” DKIM asks, “Was the message changed?” DMARC says, “If it fails, reject it or send it to spam.”
DNS and MX records: email’s address book
Before SMTP can deliver a message, it needs to know where to send it. That is where DNS helps.
A domain’s MX records tell the internet which mail servers receive email for that domain. If you send mail to alex@example.com, SMTP checks the MX records for example.com.
No good MX records? Mail may bounce. Or vanish into error messages that look like they were written by a robot having a bad lunch.
Other email standards worth knowing
- JMAP: A newer protocol for mail, contacts, and calendars. It is built for speed and modern apps.
- Exchange ActiveSync: Used by many business systems to sync mail, calendars, and contacts.
- CalDAV: Syncs calendars.
- CardDAV: Syncs contacts.
- S/MIME: Adds signing and encryption for messages.
- PGP: A strong way to encrypt and sign email, though setup can be fiddly.
A simple real-life example
Sam writes an email in Gmail to Priya at a company address.
- Sam hits Send.
- SMTP sends the message from Gmail’s server.
- DNS finds Priya’s company MX records.
- The company mail server receives it.
- SPF, DKIM, and DMARC check if it looks real.
- MIME tells Priya’s app how to show the text and attachment.
- IMAP syncs the message to Priya’s phone and laptop.
That all happens in seconds. Most of the time, nobody notices. Which is good. Email should be boring when it works.
Quick setup advice
- Use IMAP unless you have a clear reason to use POP3.
- Use SMTP port 587 for sending from an email app.
- Turn on TLS wherever possible.
- Set up SPF, DKIM, and DMARC for any custom domain.
- Keep a plain text version in marketing emails.
- Test sending and receiving after every DNS change.
Email is old, but it still works because these standards split the work. SMTP sends. IMAP and POP3 retrieve. MIME adds attachments. TLS protects connections. SPF, DKIM, and DMARC fight fakes. It is not glamorous. It is more like plumbing. But when the plumbing breaks, everyone suddenly cares.
