How an Email Travels from Your Outbox to Their Inbox: Delivery Basics and Spam Classification
"Why do my emails land in the spam folder?" To answer that, you first need to understand the full path an email takes from sending to delivery. This article uses a courier analogy to explain SMTP, receiving servers, IMAP/POP3, email headers, and the three mechanisms — SPF/DKIM/DMARC — that decide an email's "identity trustworthiness".
1. The Courier Analogy
Think of email as a package:
- Sender: your email client (Gmail, Outlook, self-hosted mailbox);
- Receiving server: the other party's post office (the mailbox server for their domain);
- SMTP: the truck that carries packages (the sending and relay protocol);
- IMAP/POP3: how the recipient picks up mail from the post office (receiving protocols);
- Email headers: the waybill showing sender, recipient, and stops along the way;
- Spam classification: the post office checks the sender's identity (SPF/DKIM/DMARC), then decides whether to deliver or drop it into the "junk area".
2. The Delivery Path, Segment by Segment
- Sending: you write the email and click send; the client hands it to the "outgoing SMTP server";
- Outgoing server authentication: the server confirms you are a legitimate user (identity check);
- DNS lookup: based on the recipient domain (e.g., gmail.com), the sending server queries DNS for the recipient's mail server address (MX record);
- SMTP delivery: the sending and receiving servers establish an SMTP connection and transfer the message;
- Receiving server processing: the server runs spam checks and virus scanning;
- Storage: the message is stored in the recipient's mailbox;
- Retrieval: the recipient fetches it from the server with IMAP or POP3.
For how MX records relate to DNS, see Domain DNS Records Basics.
3. Sending Protocol and Receiving Protocols
SMTP (Simple Mail Transfer Protocol): handles "sending" and "relaying", commonly on ports 25/465/587. To send mail from your own site, you configure SMTP on the server. See SMTP Configuration Guide.
IMAP and POP3: handle "receiving".
- IMAP: mail stays on the server, syncs across devices, and read/deleted state is consistent in real time — recommended for daily use;
- POP3: downloads mail to the local device and deletes it from the server — fits single devices and limited space.
4. What Is in an Email Header
In the full source of an email, the "header" records key information:
From/To/Subject: sender, recipient, subject;Date: the timestamp;Message-ID: the unique identifier;Received: a record of every server the message passed through (the delivery trail);Return-Path: the bounce address;- Authentication headers:
Authentication-Results, recording the SPF/DKIM/DMARC verification results.
How to view them: "Show original" in Gmail, "View source" in Outlook. The delivery trail is hidden in the Received lines.
5. Why It Is Classified as Spam: SPF / DKIM / DMARC
The receiving server asks three questions, each mapped to one mechanism:
| Mechanism | Question It Asks | What It Does |
|---|---|---|
| SPF | "Was this email really sent from this IP?" | Declares in DNS which IPs may send mail for your domain |
| DKIM | "Has this email been tampered with?" | Verifies message integrity with a digital signature |
| DMARC | "What if both SPF and DKIM fail?" | Defines the failure policy (quarantine/reject) and collects reports |
If any of the three is missing, or they disagree, the email is easily marked as spam or rejected outright. This is the most common reason for low business-mailbox delivery rates. To configure them, see SPF/DKIM/DMARC Setup Guide.
Other factors affecting delivery: sender IP reputation, spammy words in content, too-high image ratio, bounce rate, and how often users click "spam". To systematically improve delivery, see Email Deliverability Optimization.
6. Delivery Failures: Bounces and Silent Drops
When an email is not delivered, a few cases are common:
- Hard bounce: the address or domain does not exist; the receiving server returns it explicitly, and you usually get a bounce notice quickly;
- Soft bounce: the mailbox is full or the server is temporarily unavailable; delivery is retried later and only fails after repeated attempts;
- Silent drop: the most hidden case — the receiving server accepts the email but quietly discards it (common with a reject DMARC policy or a blacklisted IP); the sender gets neither a bounce nor a delivery confirmation.
To judge the real delivery result, check the sending service's delivery logs (e.g., event records from SendGrid/Mailgun) and the Authentication-Results header. For systematic bounce troubleshooting, see Email Bounce Reason Analysis.
7. FAQ
Q1: I send from my own server, why does everything go to spam? The most common cause is SPF/DKIM/DMARC missing or misconfigured, followed by poor server IP reputation (a shared IP previously abused). Configure the three first, then worry about content.
Q2: Can SMTP and IMAP replace each other? No. SMTP handles sending, IMAP/POP3 handle receiving — you configure both.
Q3: Why does my recipient never get the mail and I get no bounce? It may be silently dropped by the receiving server (common when the DMARC policy is reject, or the IP is blacklisted). Check DNS configuration and the Authentication-Results header.
Q4: Do I need a professional service for bulk marketing mail? For bulk campaigns, use a dedicated email service (they maintain IP reputation, auto-unsubscribe, and compliant templates); bulk sending from your own server is easy to get fully blacklisted.