Email Deliverability Explained: How Email Reaches the Inbox and How Sender Reputation Works

You can write the perfect email to the perfect list and still reach almost nobody, because a message that is "delivered" is not necessarily seen. It may land in spam, the promotions tab, or be silently throttled by the receiving server. Deliverability is the technical and behavioural discipline of getting legitimate email into the inbox — and since major mailbox providers tightened their rules for bulk senders, it is no longer optional knowledge.

This guide explains how email travels from send to inbox, how spam filters and reputation systems decide where it lands, how IPs and domains build reputation, the bulk-sender requirements every marketer must meet, and the list and header practices that keep you in good standing. Companion guides cover email authentication — SPF, DKIM, DMARC and beyond and deliverability monitoring and troubleshooting.

The Basics

What Email Deliverability Actually Means, Technically

Deliverability is the ability to get email into recipients' inboxes. Technically it has two layers: delivery — the receiving server accepts the message — and inbox placement — the mailbox provider puts it in the inbox rather than spam or another folder. Deliverability depends on authentication (proving you are who you say you are), reputation (your history as a sender), content and, increasingly, recipient engagement.

Understanding the Journey of an Email From Send to Inbox

1. Your email platform or mail server (an MTA) prepares the message and looks up the recipient domain's mail servers through DNS MX records.
2. It opens a connection, usually encrypted with TLS, and the receiving server checks your IP address against reputation data and blocklists.
3. The receiver verifies authentication: SPF, DKIM and DMARC.
4. It accepts or rejects the message — or temporarily defers it.
5. Filters evaluate reputation, content and engagement signals to choose the inbox, spam or another folder.
6. Recipients' actions (opening, replying, deleting, marking as spam) feed back into future decisions.

How Inbox Placement Differs From Delivery

Email platforms often report a "delivery rate" of 98–99%, which only means receiving servers accepted the messages. Accepted mail can still land in spam. Inbox placement — the share reaching the inbox — is what matters and is measured separately through seed tests, mailbox provider tools and engagement trends.

What Is an MTA and How Does It Affect Deliverability?

A Mail Transfer Agent (MTA) is the software that sends and relays email between servers. Your email service provider runs MTAs on your behalf; large senders sometimes run their own. MTA configuration affects deliverability through connection handling, retry logic for deferred mail, throttling per receiving domain, TLS support and how bounces are processed. A well-run MTA adapts sending speed to each mailbox provider's signals.

Understanding TLS in Email Transmission

TLS encrypts email in transit between servers, protecting it from interception. Major mailbox providers expect it, and Gmail's bulk-sender requirements include TLS. Most email platforms use opportunistic TLS automatically; MTA-STS lets receiving domains require it (see our authentication guide).

Understanding Rate Limiting and Throttling by Receiving Servers

Mailbox providers limit how fast they accept mail from a sender, especially new or low-reputation ones. Temporary deferrals (4xx responses) are a signal to slow down, not a failure — the sending MTA should retry later. Sudden volume spikes from a sender with little history are a classic spam pattern and commonly trigger throttling.

How Filtering Decisions Are Made

What Spam Filters Actually Look At

Modern filtering weighs many signals:

• Authentication: do SPF, DKIM and DMARC pass and align with the visible From domain?
• Reputation: of the sending IP, domain and even links and images included
• Engagement: do recipients open, reply and keep the mail — or delete and report it?
• Complaints: the rate at which recipients click "report spam"
• List quality: bounces and spam traps hit
• Content and formatting: broken HTML, link shorteners, mismatched links, deceptive subject lines
• Consistency: stable volume and sending patterns

Old-style keyword rules ("never say FREE") matter far less than reputation and engagement.

Engagement-Based Filtering and How Technical Signals Interact With It

Mailbox providers increasingly personalise filtering by how each recipient — and recipients overall — interact with your mail. Strong authentication and reputation earn you the chance to reach the inbox; engagement determines whether you stay there. Sending to people who never open drags performance down for everyone on your list, which is why list hygiene is a deliverability tactic, not just tidiness.

Understanding Bounce Types: Hard Bounces vs Soft Bounces

• Hard bounces are permanent failures — the address does not exist, or the domain is invalid. Remove these immediately; repeatedly sending to invalid addresses damages reputation.
• Soft bounces are temporary — a full mailbox, a server issue, or a message too large. Retry, but suppress addresses that keep soft-bouncing over several campaigns.
• Block bounces happen when the receiver refuses mail because of reputation or policy — a warning sign to investigate.

Understanding Feedback Loops (FBLs) With ISPs

Feedback loops send complaint data — when a recipient marks your email as spam — back to the sender, so you can remove that person. Many providers offer FBLs (Microsoft, Yahoo and others); Gmail instead provides aggregate spam-rate data in Postmaster Tools and a feedback-loop header for large senders. Always suppress complainers immediately.

Sender Reputation

Understanding Sender Score and Domain Reputation

Mailbox providers maintain their own internal reputation scores for sending IPs and domains, based on complaints, bounces, spam traps, engagement and authentication. Third-party scores (such as Sender Score) estimate IP reputation from data networks. They are useful indicators, but the reputation that matters is the one each mailbox provider holds privately — which you see indirectly through inbox placement and tools like Google Postmaster Tools.

Domain Reputation vs IP Reputation: What's the Difference?

IP reputation belongs to the sending server's address; domain reputation follows the domain in your From address, DKIM signature and links — wherever you send from. Domain reputation has become increasingly important because it travels with you: switching IPs or providers does not escape a poor domain reputation. Protect your domain as your most important deliverability asset.

Shared IP vs Dedicated IP: Technical Tradeoffs

Reputable providers manage shared pools carefully, and shared IPs often perform better for small senders, because a dedicated IP needs steady volume to maintain a reputation.

What Is IP Warming and Why It Still Matters

A new IP has no reputation, and mailbox providers are wary of unknown senders sending large volumes. IP warming gradually increases volume over weeks, starting with your most engaged recipients, so providers see consistent, wanted mail before volume grows. The same principle applies to new sending domains.

Building an IP Warm-Up Schedule Step by Step

1. Start small: a few hundred to a few thousand emails per day to your most engaged subscribers.
2. Increase gradually: roughly 20–50% per day or every few days, depending on results.
3. Spread across mailbox providers and watch each separately — Gmail, Microsoft and Yahoo may respond differently.
4. Watch signals daily: deferrals, bounces, complaints, opens and placement.
5. Pause or slow down when deferrals or complaints rise.
6. Reach full volume over two to six weeks, depending on list size and reputation.

Using a Subdomain Strategy to Protect Your Root Domain

Sending different mail streams from different subdomains — for example news.example.com for marketing and mail.example.com for transactional email — separates their reputations, so a struggling marketing campaign does not hurt password resets and receipts. Subdomains still inherit some association with the parent domain, so they are not a way to hide poor practices.

Requirements and List Practices

Understanding the Google and Yahoo Bulk Sender Requirements

Since February 2024, Gmail and Yahoo require bulk senders (Google defines this as sending around 5,000 or more messages a day to Gmail accounts) to:

• Authenticate with SPF and DKIM, and publish a DMARC policy (at least p=none)
• Align the From domain with SPF or DKIM
• Support one-click unsubscribe for marketing and subscribed messages, and honour unsubscribes within two days
• Keep spam complaint rates low — below 0.3%, with under 0.1% the recommended target
• Have valid forward and reverse DNS for sending IPs and use TLS

All senders need at least SPF or DKIM, valid reverse DNS and low complaint rates. Microsoft announced comparable requirements for high-volume senders to its consumer mailboxes in 2025. Treat these as the baseline.

Implementing One-Click Unsubscribe (RFC 8058) Correctly

One-click unsubscribe lets mailbox providers show an "Unsubscribe" link that works with a single click, without the recipient visiting a page. Implementation requires two headers:

• List-Unsubscribe: <https://example.com/unsubscribe/abc123> (an HTTPS URL; a mailto option can be included too)
• List-Unsubscribe-Post: List-Unsubscribe=One-Click

The URL must accept a POST request and unsubscribe immediately, with no login or confirmation page. The message must be DKIM-signed with these headers covered by the signature.

List-Unsubscribe and List-Unsubscribe-Post Headers Explained

List-Unsubscribe has existed for years and tells clients how to unsubscribe (by email or URL). List-Unsubscribe-Post signals that the URL supports one-click POST requests. Mailbox providers use them to display native unsubscribe buttons — which is good for deliverability, because people who can unsubscribe easily are less likely to hit "report spam".

Structuring Email Headers for Better Deliverability

Beyond unsubscribe headers, keep headers clean and consistent: a From address on your own authenticated domain, a recognisable From name, a monitored Reply-To, correct Message-ID and Date headers, proper MIME structure with both HTML and plain-text parts, and no deceptive or mismatched information. Consistency in From name and address helps recipients and filters recognise you.

List Hygiene: Technical Approaches to Suppression and Validation

• Use confirmed opt-in for new subscribers where practical.
• Validate addresses at signup to catch typos and fake addresses.
• Suppress hard bounces, repeat soft bounces, complainers and unsubscribes immediately and permanently.
• Sunset inactive subscribers: re-engage people who have not engaged in months, then remove those who stay inactive.
• Never buy or rent lists — they contain spam traps and people who never agreed to hear from you.

Why Email Deliverability Is Never "Set and Forget"

Reputation changes with every campaign, mailbox providers update their filtering, lists decay as people change addresses, and new requirements arrive. Monitor key metrics continuously, review authentication when you add new sending tools, and treat deliverability as an ongoing responsibility.

The Bottom Line

Deliverability rests on three pillars: authentication that proves who you are, reputation earned by sending wanted mail consistently, and engagement from recipients who actually want your emails. Meet the bulk-sender requirements, warm up new infrastructure gradually, separate mail streams sensibly, and keep your list clean — then monitor, because the inbox has to be earned every time you send.

Next step: Set up authentication correctly with our email authentication guide.