Email deliverability is the ability of a sender’s messages to reach the recipient’s inbox, rather than being rejected by the receiving server, filtered into the spam folder or hidden in a secondary tab. In email marketing, it determines whether any campaign metric can be meaningful at all: a message that never reaches the inbox cannot be opened, clicked or converted.
Deliverability is decided by mailbox providers such as Gmail, Outlook and Yahoo, which weigh sender authentication, sender reputation and recipient engagement. The sender cannot control the filters directly, but it fully controls the inputs those filters evaluate.
Delivery versus deliverability
Delivery and deliverability are often confused but measure different things. Delivery only means that the receiving server accepted the message; deliverability, also called inbox placement, describes where the accepted message ended up.
| Metric | What it measures | Where the data comes from |
|---|---|---|
| Delivery rate | Share of sent messages accepted by receiving servers | Email service provider reports |
| Bounce rate | Share of messages rejected permanently or temporarily | Bounce codes returned by servers |
| Inbox placement rate | Share of delivered messages that land in the inbox | Seed list tests and panel data |
| Spam complaint rate | Share of recipients who mark a message as spam | Feedback loops and postmaster tools |
A campaign can show a delivery rate above 98% and still perform poorly if a large share of those messages land in spam. This is why experienced email marketers monitor inbox placement and complaints, not only the delivery figure in the sending platform.
Email authentication
Authentication proves to mailbox providers that a message really comes from the domain it claims. Since 2024, Gmail and Yahoo require bulk senders, defined by Gmail as those sending around 5,000 or more messages a day to its users, to authenticate with SPF and DKIM and to publish a DMARC policy.
| Standard | What it does | Typical configuration |
|---|---|---|
| SPF | Lists servers allowed to send for a domain | A DNS TXT record including the sending platform |
| DKIM | Adds a cryptographic signature to each message | A public key in DNS, a private key at the sender |
| DMARC | Tells receivers what to do when SPF or DKIM alignment fails | Policy of none, quarantine or reject, with reports |
| BIMI | Displays a verified brand logo in supporting inboxes | Requires DMARC enforcement and often a certificate |
The key concept is domain alignment: the domain in the visible From address must match the domain authenticated by SPF or DKIM. Many deliverability problems come from sending through a platform that signs with its own domain instead of the brand’s, which passes authentication but fails DMARC alignment.
Sender reputation and engagement
Mailbox providers maintain a reputation score for sending domains and IP addresses based on how recipients and spam filters react to past mail. Domain reputation has become more important than IP reputation, because the domain follows the brand across sending platforms.
| Signal | Healthy range or behavior | Effect when poor |
|---|---|---|
| Spam complaint rate | Below 0.1%, never reaching 0.3% | Rapid spam-folder placement or blocking |
| Hard bounce rate | Well below 2% per campaign | Signals outdated or purchased lists |
| Spam trap hits | None | Blocklisting and severe reputation damage |
| Positive engagement | Opens, replies, moving mail to the inbox | Lower engagement weakens inbox placement |
| Volume consistency | Gradual changes in sending volume | Sudden spikes look like spam behavior |
New domains and dedicated IP addresses need warming: sending volume is increased gradually over several weeks, starting with the most engaged recipients. Skipping this step makes even legitimate mail look like a spam campaign to providers.
List quality and permission
Deliverability starts at list acquisition. Lists built through clear consent, ideally with double opt-in, contain valid addresses and people who expect the mail, which keeps bounces and complaints low.
- Never buy or rent lists: they contain invalid addresses, spam traps and people who never consented.
- Practice email list hygiene: remove hard bounces immediately and suppress long-term inactive subscribers.
- Run sunset policies: send a re-engagement sequence to inactive contacts, then stop mailing those who do not respond.
- Make unsubscribing easy: bulk senders must support one-click unsubscribe and honor requests within two days.
- Segment by engagement: send more often to active readers and less often to fading ones.
A visible, working unsubscribe link reduces complaints, because recipients who cannot leave easily often use the spam button instead, which damages reputation far more than an unsubscribe.
Diagnosing deliverability problems
Deliverability problems usually appear as a sudden drop in opens or clicks on a specific mailbox provider. Segmenting results by recipient domain is therefore the first diagnostic step.
| Symptom | Likely cause | Recommended fix |
|---|---|---|
| Drop at one provider only | Reputation issue with that provider | Check its postmaster tools and reduce volume to unengaged users |
| DMARC failures in reports | Misaligned or missing authentication | Configure custom DKIM and SPF for the sending platform |
| Rising hard bounces | Old or poorly collected addresses | Validate lists and fix signup forms |
| Blocklist listing | Spam trap hits or complaint spikes | Find the source segment, clean it and request delisting |
| Promotions tab placement | Normal classification of marketing mail | Focus on engagement rather than trying to bypass tabs |
Open rates are now an unreliable deliverability signal, because privacy features such as Apple Mail Privacy Protection preload images and register opens automatically. Clicks, replies, conversions and postmaster dashboards give a more trustworthy picture.
In plain words
Email deliverability is whether your email actually lands in the inbox. Sending a message is easy; getting it past the filters that protect people from spam is the hard part.
Mail services act like a doorman who remembers every sender. If you prove who you are, send only to people who asked for your messages and rarely get reported, the doorman lets you in. If people keep marking your mail as spam, you end up waiting outside.
A real-world example
An online fashion retailer notices that clicks on its weekly newsletter have fallen sharply, but only among Gmail recipients. Its sending platform still reports a delivery rate of about 99%.
Google Postmaster Tools shows a spam complaint rate approaching 0.3% and a falling domain reputation. The team finds two causes: the newsletter is signed with the platform’s shared DKIM domain instead of the brand’s own, and a large segment of contacts has not opened or clicked in over a year. The retailer sets up custom DKIM and a DMARC policy, moves inactive contacts into a re-engagement sequence and stops mailing those who do not respond.
Over the next six weeks, the complaint rate falls well below 0.1%, domain reputation recovers and Gmail clicks return to their earlier level, even though the list is now smaller.