So that the sending of your emails work, it is imperative to have up-to-date lists with valid addresses. If necessary, you are likely to end up with a high rebound…
When an email campaign does not produce the expected results, SMTP error codes can often provide very useful answers. Indeed, these codes generated during the sending or delivery of emails…
Email deliverability: the complete guide to reaching the inbox
Since February 2024, Google and Yahoo have required senders of more than 5,000 daily messages to keep their complaint rate under 0.3%, or face outright rejection of their campaigns. Email deliverability refers to a message's ability to reach the recipient's primary inbox, not just a server that technically accepts the message. The fastest lever to pull remains list hygiene: a list verified before each campaign limits the hard bounces that can tank a sender's reputation in just a few days.
Your campaigns end up in the spam folder even though nothing changed in your email tool's settings, and the dashboard still shows everything green. This mismatch rarely comes from the sending platform itself. It plays out in domain authentication, IP reputation, and list cleanliness, the three areas this guide covers below. Nine mistakes come up most often in deliverability best practice audits, including missing authentication and a list that's never been verified. See the details in the most common deliverability mistakes.
Domain authentication: SPF, DKIM, DMARC, and BIMI
Technical authentication determines whether a message even gets to the content analysis stage of spam filters. SPF authorizes specific servers to send on behalf of the domain, DKIM signs each message with a cryptographic key, and DMARC tells mailbox providers what to do with a message that fails both checks. Since 2024, Google and Yahoo have required at least a p=none DMARC policy for any high-volume sender, with a recommendation to move to p=quarantine and then p=reject once aggregate reports have been analyzed. The BIMI protocol adds the brand logo to the inbox, but it's reserved for domains already authenticated under a strict DMARC policy. Configuring these DNS records correctly, and understanding the purpose of a Return-Path separate from the From field, prevents outright rejection before the filter even evaluates the message content. See how to customize the sender's DNS and the exact role of the Return-Path.
Sender reputation: the score that decides everything
Every sending domain and IP carries a reputation score calculated by mailbox providers based on the history of previous sends. This score drops quickly after a spike in hard bounces, a high complaint rate, or a shared IP used by unreliable senders, and it only recovers slowly, often over several weeks. Google Postmaster Tools is the go-to tool for tracking this score on the Gmail side: it shows domain reputation, IP error rate, and complaint rate, to be compared against the 0.1% threshold Google recommends for high-volume senders.
The spam complaint threshold Google recommends for high-volume senders remains 0.1%, well below the 0.3% rejection threshold set in February 2024 for any send of more than 5,000 daily messages to Gmail addresses.
The table below summarizes the most commonly used Sender Score ranges and the action to take for each one.
| Score Range | How Mailbox Providers Read It | Action to Take |
|---|---|---|
| 80–100 | Trusted sender, primary inbox placement favored | Maintain current sending cadence and list quality |
| 60–80 | Watch zone, filtering varies by mailbox provider | Audit complaints and sending frequency |
| 30–60 | High risk of being marked as spam | Clean the list and cut volume before the next campaign |
| 0–30 | Possible blocking before delivery | Switch sending IP or domain and restart with a gradual IP warming |
These ranges aren't a legal standard, just a benchmark shared by most mailbox providers; some providers, particularly in the North American market, apply slightly different thresholds based on their own internal models. See how to monitor your Sender Score, how to set up Google Postmaster Tools, and how to fix a damaged sender reputation.
List hygiene: the area general guides gloss over
Most deliverability guides cover authentication and reputation in detail but rarely devote more than a paragraph to list quality itself, even though it's the only piece that gets fixed before sending rather than after. A hard bounce flags an address that no longer exists: the receiving server rejects that specific message immediately and permanently. Once hard bounces exceed 2% of the volume sent, they start to damage sender reputation; above 5%, anti-spam systems trigger automatic alerts.
Spam traps make the problem worse: these are addresses deliberately recycled or created by mailbox providers to identify senders who don't maintain their list, and hitting just one can be enough to tank a reputation score that had been stable for months. Verifying the list changes the nature of the problem. It turns emergency repair into measurable upfront prevention, rather than discovering hard bounces after the campaign has already gone out. That's what CaptainVerify does: test every address before sending and strip spam traps and dead addresses, hard bounces included, from the list before they ever reach the recipient's server. Before ramping up volume for an upcoming campaign, running a verification test on a sample of the list is enough to quantify the real risk instead of discovering it in production.
See how to clean an email list, why you should validate your emails before sending, what to do with inactive contacts, and how to spot spam traps.
Bounces and SMTP errors: reading the codes before they pile up
Every bounce returns an SMTP code specifying the reason for rejection, from 550 5.1.1 for a nonexistent address to 421 for a temporarily unavailable server. Confusing a soft bounce (a temporary rejection caused by a full inbox or an overloaded server) with a hard bounce, a permanent rejection, leaves dead addresses circulating in the list for months. Retrying a soft bounce after a few hours makes sense; retrying a hard bounce doesn't, and it just inflates the rejection rate of the next campaign.
For transactional flows, the logic shifts again: an order confirmation or password reset email needs to get through even when marketing volume slows down or reputation takes a hit, which often calls for a dedicated IP or subdomain. See how to handle bounces, why SMTP rejections rise or fall, the causes of undelivered emails, and deliverability specific to transactional emails.
Engagement and the promotions tab: staying in the primary inbox
Once the message is delivered, the next challenge is landing in the primary inbox rather than Gmail's promotions tab. This classification depends mainly on content and on how recipients behaved with previous sends; technical authentication alone isn't enough to guarantee primary inbox placement. Open and click rates factor into this classification, as does the domain's overall reputation.
Since June 2024, the one-click unsubscribe link carried by the List-Unsubscribe header has become mandatory for any commercial or promotional send to Google and Yahoo: its absence now risks outright message rejection, not just a vague drop in engagement. See inbox placement at high volume, how to set up the List-Unsubscribe header, and why emails land in the promotions tab.
Blocklists: monitor before you need to get delisted
An IP or domain blacklisted by a blocklist like Spamhaus has some of its sends silently rejected, with no notification to the sender, which makes the problem hard to diagnose without dedicated monitoring. The most common causes are usually a spike in complaints, an unverified list sent all at once, or a shared IP compromised by another sender in the same pool. The delisting process varies from one blocklist to another: some automate removal after a few days without repeat offenses, others require a form and a written justification.
See which blocklists to monitor or ignore and how to get an IP or domain delisted.
Frequently asked questions about email deliverability
What is a good email deliverability rate?
Above 95% of messages reaching a receiving server without bouncing, the deliverability rate is considered healthy by most ESPs. This figure says nothing about primary inbox placement: a successfully delivered email can still land in spam or promotions.
Does open rate affect deliverability?
Open rate reflects recipient engagement, a signal mailbox providers watch but one that doesn't decide a message's classification on its own. Sender reputation and domain authentication carry more weight.
How long does it take to restore good deliverability after an IP is blacklisted?
It depends on the blocklist involved and the cause of the block: a few hours for automatic removal once the issue is fixed, several weeks when domain reputation needs to be rebuilt through a gradual sending ramp-up.
Should you verify a purchased or acquired list before using it?
A list whose origin you don't fully control almost always contains outdated addresses or spam traps. Verifying it before the first send limits the risk of immediately damaging the reputation of a new domain or an already well-established one.
For precise definitions of every technical term mentioned in this guide, see the email deliverability glossary.