The Complete Guide to Email Deliverability
Deliverability is the difference between your email landing in the inbox or disappearing into spam. This guide covers everything you need to know, from authentication basics to reputation protection that runs on its own.
Email deliverability is the measure of whether your emails successfully reach the recipient's inbox rather than being filtered to spam, bounced, or silently discarded. It is distinct from email delivery, which simply means the receiving mail server accepted the message. An email can be "delivered" to the server but still end up in the spam folder. Deliverability depends on three main factors: sender authentication (SPF, DKIM, DMARC), domain and IP reputation with major ISPs like Gmail, Yahoo, and Outlook, and engagement patterns such as open rates and complaint rates. According to industry data, roughly one in five legitimate emails never reaches the intended inbox. sendmsg.io addresses this through its Reputation Shield system, which continuously monitors ISP signals and adjusts sending volume and speed to protect domain health before deliverability problems escalate.
What Is Email Deliverability?
Email deliverability is the ability to place your emails in the recipient's inbox, not their spam folder, not blocked, not silently discarded. It is distinct from email delivery, which simply means the receiving server accepted your message. An email can be "delivered" and still end up in spam.
Deliverability is determined by a combination of factors: your sending domain's reputation, your IP reputation, your email authentication configuration, the content of your messages, recipient engagement history, and the policies of each receiving ISP. None of these factors exist in isolation. They interact in ways that make deliverability a continuous challenge rather than a one-time setup.
21%
of legitimate emails never reach the inbox globally
(Validity Deliverability Benchmark Report, 2024)
$1.2M
average annual revenue loss from deliverability issues
(Emarsys Email Marketing Revenue Impact Study)
45%
of all email is classified as spam by ISPs
(Cisco Talos Intelligence, 2024)
Email Authentication Essentials
Authentication is the foundation of deliverability. Without it, ISPs have no way to verify that you are who you claim to be.
SPF (Sender Policy Framework)
SPF tells receiving servers which IP addresses are authorized to send email on behalf of your domain. It is a DNS TXT record that lists allowed senders. When a server receives your email, it checks the SPF record to verify the sending IP is permitted.
Without SPF, anyone can send email claiming to be from your domain. Spammers exploit this constantly, which is why ISPs check SPF on every incoming message.
DKIM (DomainKeys Identified Mail)
DKIM attaches a cryptographic signature to every email you send. The receiving server uses a public key published in your DNS to verify that the message was not altered in transit and originated from your domain.
DKIM signatures survive email forwarding, which is a significant advantage over SPF. Together, SPF and DKIM provide complementary verification.
DMARC (Domain-based Message Authentication)
DMARC builds on SPF and DKIM by telling ISPs what to do when authentication fails. You define a policy: none (monitor), quarantine (send to spam), or reject (block entirely). DMARC also provides reporting so you can see who is sending email using your domain.
Google, Yahoo, and Apple all require DMARC for bulk senders. Without a DMARC policy, your emails are more likely to be filtered.
BIMI (Brand Indicators for Message Identification)
BIMI displays your brand logo next to your emails in supporting inboxes (Gmail, Yahoo, Apple Mail). It requires a verified DMARC policy at enforcement level and a Verified Mark Certificate (VMC).
While not required for deliverability, BIMI increases recipient trust and engagement. It signals to ISPs that you take authentication seriously.
Domain Reputation vs IP Reputation
Historically, ISPs judged senders primarily by IP address reputation. If an IP sent spam, it got blocked. This led to the practice of "IP warming": gradually building trust on a new IP address.
Modern ISPs (particularly Gmail, which processes over 40% of global email (Litmus Email Client Market Share, 2024)) have shifted emphasis to domain reputation. Your sending domain's history of engagement, complaints, and bounces carries more weight than the IP it is sent from. This shift has major implications for how you manage deliverability.
Reputation Comparison
Weight in ISP decisions
~80% (based on ISP feedback loop data and industry analysis)
Persistence
Follows domain permanently
Weight in ISP decisions
~20%
Persistence
Tied to infrastructure
Understanding and Managing Bounces
Bounces are messages that the receiving server refuses to accept. They are the most straightforward deliverability signal, and one of the most damaging when rates climb too high.
Hard Bounces
Permanent failures caused by invalid email addresses, non-existent domains, or permanently blocked recipients. Hard bounces should trigger immediate removal from your sending list. Any hard bounce rate above 2% is a serious problem.
Soft Bounces
Temporary failures caused by full mailboxes, server outages, or messages that are too large. Soft bounces should be retried, but repeated soft bounces to the same address over time should be treated as hard bounces.
Blocks
Active rejections from ISPs based on reputation. Blocks differ from bounces in that the rejection is about you, not the recipient. A block from Gmail or Yahoo means they have decided your sending is unwelcome. This is the most severe deliverability signal.
Bounce Rate Thresholds
Complaint Feedback Loops: The Highest-Weight Signal
When a recipient clicks "Report Spam" in their inbox, the ISP sends a complaint notification back to the sender through a feedback loop (FBL). This is the most damaging signal for your domain reputation. A single complaint carries more weight than dozens of bounces.
Major ISPs including Gmail (via Google Postmaster Tools), Yahoo, Outlook, and AOL provide FBL data. The critical threshold for most ISPs is a 0.1% complaint rate, which is just 1 complaint per 1,000 emails sent. Exceeding this consistently will lead to inbox placement rates dropping dramatically.
Register for FBLs
Set up feedback loop registrations with all major ISPs. This is the only way to receive complaint data programmatically.
Act Immediately
Every complaint should trigger an unsubscribe for that recipient. Continuing to email someone who has complained is the fastest path to being blocked.
Track Trends
A rising complaint rate, even below 0.1%, is an early warning. Monitor the trend, not just the current number. Address causes before crossing thresholds.
The Warmup Problem
Every new sending domain starts with zero reputation. ISPs know nothing about your domain, and their default posture is suspicion. Sending a high volume of email from an unknown domain is one of the most common patterns of spam, which is exactly why ISPs treat it as a red flag.
Proper warmup means starting with a very low sending volume and increasing it gradually over several weeks. At each stage, the ISPs observe your engagement metrics: are recipients opening your emails? Are they clicking links? Are they complaining? This data builds your domain's reputation profile.
The Risk of Skipping Warmup
Without Warmup
- ✕Immediate ISP blocks on high-volume sends
- ✕Emails land in spam even when content is legitimate
- ✕Domain reputation damaged before it had a chance to build
- ✕Recovery takes 4-8 weeks of careful remediation
With Built-in Warmup
- Volume scales safely as ISPs learn your patterns
- Engagement monitored at each stage before advancing
- Automatic pause if negative signals are detected
- Full sending capacity reached in 3-5 weeks safely
sendmsg.io's Smart Warmup handles this entire process. New domains are placed on a warmup schedule with progressive volume increases, engagement gates at each tier, and automatic pausing if signals deteriorate.
Monitoring vs Active Protection
Most email platforms show you dashboards. sendmsg.io acts on the data for you.
Traditional Monitoring
Standard email platforms give you analytics dashboards showing open rates, bounce rates, and delivery statistics. This information is valuable, but it requires someone to watch it, interpret it, and take action.
- —You see the data, but you have to decide what to do
- —Reports are typically delayed by minutes or hours
- —Requires manual throttling when problems appear
- —Weekend and off-hours issues go unnoticed
- —Human reaction time is measured in hours; ISP decisions in seconds
Active Protection
sendmsg.io's Reputation Shield closes the gap between detection and action. It processes the same signals, but responds to them on its own, as they happen, without waiting for human interpretation.
- Signals processed and acted upon within seconds
- Sending speed adjusted based on health score
- Volume limits recalculated dynamically
- Protection is active 24/7, including weekends and holidays
- Gradual recovery prevents the "on/off switch" problem
Email Deliverability Best Practices
Ten actionable practices that form the foundation of strong email deliverability.
Authenticate every sending domain
Set up SPF, DKIM, and DMARC for every domain you send from. Without authentication, ISPs have no way to verify your identity.
Maintain list hygiene rigorously
Remove hard bounces immediately. Regularly clean inactive subscribers. A clean list is the foundation of good deliverability.
Warm up new domains gradually
Never send at full volume from a new domain. Start small and increase over weeks as ISPs build trust in your sending patterns.
Monitor bounce rates continuously
Keep hard bounce rates below 2% and soft bounce rates below 5%. Spikes in either are early warning signs of deliverability problems.
Process complaint feedback loops
Register for ISP feedback loops and act on complaints immediately. Even a 0.1% complaint rate can trigger ISP filtering.
Segment your sending by type
Separate transactional and promotional email onto different domains or subdomains. Promotional reputation issues should not affect transactional delivery.
Avoid sudden volume changes
ISPs interpret sudden spikes in volume as potential abuse. Ramp up gradually and avoid sending large campaigns without lead time.
Include easy unsubscribe mechanisms
One-click unsubscribe headers (RFC 8058) are now required by major ISPs. Making it easy to unsubscribe reduces complaint rates.
Send to engaged recipients first
When sending large campaigns, prioritize recipients who have recently opened or clicked. High initial engagement improves ISP confidence.
Automate your reputation protection
Manual monitoring cannot react fast enough. Use systems that detect and respond to deliverability signals as they happen.
Put Deliverability on Autopilot
Understanding deliverability is important. Having it handled for you is better. sendmsg.io takes care of authentication, warmup, monitoring, and protection so you can focus on your message.