Outreaches
Technical infrastructure

Email deliverability deep dive: complete technical guide

Master email deliverability: ISP filtering algorithms, SPF/DKIM/DMARC implementation, sender reputation management, spam triggers, infrastructure setup, and troubleshooting. Achieve 95%+ inbox placement.

18 min read
December 6, 2025

Table of contents

Key Takeaways

  • Deliverability is 35% sender reputation, 25% authentication, 20% content, 15% engagement, 5% infrastructure
  • SPF, DKIM, DMARC are non-negotiable - without them, 40-70% of emails land in spam folders
  • Domain warmup takes 6+ weeks - rushing it destroys reputation permanently and cannot be easily recovered
  • Monitor inbox placement rate (target 95%+), spam complaints (<0.1%), bounce rate (<2%) daily
  • High-risk spam triggers: all caps, 'FREE/GUARANTEED', excessive punctuation!!!, money symbols $$$
  • Use subdomain for outreach (mail.yourdomain.com) to protect main domain reputation from risks

Email deliverability fundamentals: what ISPs really check

The deliverability reality: Email deliverability isn't about whether your email gets delivered (delivery rate) - it's about whether it lands in the inbox or spam folder. You can have 98% delivery but only 50% inbox placement if half your emails go to spam. ISPs use complex algorithms weighing dozens of factors to make this decision in milliseconds.

Understanding what ISPs (Gmail, Outlook, Yahoo, etc.) actually check when deciding inbox vs spam placement is critical for cold outreach success. Here's the weighted breakdown of factors that usually determine where your emails land:

ISP Algorithm Factor Weighting

These percentages represent the typical weight ISPs assign to each factor when determining inbox vs spam placement

Sender reputation

Weight in algorithm:
What they check:
Time to optimize:
35%
Historical sending behavior, complaint rates, engagement patterns
6-12 weeks

Authentication

Weight in algorithm:
What they check:
Time to optimize:
25%
SPF, DKIM, DMARC alignment and proper configuration
1-2 days

Content quality

Weight in algorithm:
What they check:
Time to optimize:
20%
Spam trigger words, formatting, text-to-image ratio
Immediate

Engagement signals

Weight in algorithm:
What they check:
Time to optimize:
15%
Opens, clicks, replies, forwards vs deletes and spam reports
2-4 weeks

Infrastructure

Weight in algorithm:
What they check:
Time to optimize:
5%
IP reputation, DNS configuration, sending patterns
1-2 weeks
The 6-week reality: Notice that the highest-weighted factors (sender reputation and engagement) take 6-12 weeks to optimize. This is why domain warmup and gradual scaling are non-negotiable. You can fix authentication in days, but reputation takes months. There are no shortcuts that actually work long-term.

This weighting explains why many outreach campaigns fail despite "perfect" technical setup. Having SPF/DKIM/DMARC configured correctly (25% weight) won't save you if your sender reputation is poor (35% weight) or engagement signals are negative (15% weight). You need excellence across all factors.

Inbox placement rate
95%+
Target for mature setup
Spam folder rate
<5%
Maximum acceptable
Bounce rate
<2%
Per campaign target
Spam complaint rate
<0.1%
Critical threshold
Open rate
25-40%
Cold outreach baseline
Domain reputation
70+
Google Postmaster score

Authentication protocols: SPF, DKIM, DMARC deep dive

Email authentication protocols are your proof of legitimacy to ISPs. Without them, 40-70% of your emails land in spam regardless of content quality. Here's exactly how to configure each protocol correctly with step-by-step instructions for major providers.

Critical authentication facts:
  • Without SPF: 40-60% of emails go to spam automatically
  • DKIM failure: 50-70% spam placement rate
  • DMARC adds 15-25% deliverability improvement + protects brand from spoofing
  • All three must work together - having only SPF or only DKIM isn't enough
  • DNS propagation takes 10-60 minutes, full ISP recognition takes 24-48 hours

SPF (Sender Policy Framework) - Complete Setup Guide

What SPF does

SPF verifies that emails from your domain are sent from authorized servers. ISPs check your SPF record to confirm the sending IP is allowed to send on your behalf. Without it, ISPs assume spoofing/spam.

Common SPF mistakes

  • Too many DNS lookups (10 limit)
  • Using +all instead of ~all or -all
  • Multiple SPF records (only one allowed)
  • Forgetting to add new sending services

Google Workspace (Gmail)

1
Login to your domain registrar

Go to your domain provider (GoDaddy, Namecheap, Cloudflare, etc.)

Navigate to DNS Management section
2
Add new TXT record

Click 'Add Record' or 'Add DNS Record' button

Select record type: TXT
3
Configure SPF record

Enter these exact values:

Copy this value:
v=spf1 include:_spf.google.com ~all
Host/Name field: @ (or leave blank for root domain) TTL: 3600 (or 1 hour)
4
If you use additional email services

Add their SPF includes BEFORE ~all

Copy this value:
v=spf1 include:_spf.google.com include:servers.mcsv.net include:spf.protection.outlook.com ~all
Warning: Each 'include:' counts toward 10 DNS lookup limit. Use SPF flattening if you exceed this.
5
Save and verify

Save the DNS record and wait 10-60 minutes for propagation

Test with: dig TXT yourdomain.com or use MXToolbox SPF checker

Microsoft 365 (Outlook)

1
Access DNS settings

Go to your domain registrar's DNS management panel

Look for DNS, Name Servers, or Advanced DNS settings
2
Create TXT record

Add new TXT record with these values:

Copy this value:
v=spf1 include:spf.protection.outlook.com ~all
Name/Host: @ or root domain TTL: 3600 seconds
3
For multi-service setup

Combine multiple services in one SPF record:

Copy this value:
v=spf1 include:spf.protection.outlook.com include:_spf.google.com ~all
Warning: NEVER create multiple SPF records - combine all into one record
4
Validate configuration

Use Microsoft's Remote Connectivity Analyzer

Visit testconnectivity.microsoft.com and run SPF test

Cold email platforms (Instantly, Smartlead, Lemlist)

1
Get your platform's SPF include

Find SPF instructions in your platform's DNS settings or documentation

Instantly: include:spf.instantly.ai Smartlead: include:_spf.smartlead.ai Lemlist: include:_spf.lemlist.com
2
Combine with existing SPF

Add platform SPF to your existing record (don't create a new one)

Copy this value:
v=spf1 include:_spf.google.com include:spf.instantly.ai ~all
Warning: Place platform include BEFORE ~all mechanism
3
Update DNS at your registrar

Find existing SPF TXT record and edit it (or create if none exists)

Host: @ | Type: TXT | Value: [combined SPF record]
4
Verify in platform

Return to your cold email platform and click 'Verify DNS' or 'Check Authentication'

Platform should show green checkmark for SPF within 1 hour
Verify your SPF setup

Use these free tools to confirm your SPF configuration is correct:

DKIM (DomainKeys Identified Mail) - Complete Setup Guide

What DKIM does

DKIM cryptographically signs your emails using a private key, allowing ISPs to verify emails haven't been tampered with using the public key in your DNS. This proves authenticity and prevents email modification.

Common DKIM mistakes

  • Not publishing public key in DNS
  • Key rotation not implemented
  • Signature breaks due to email forwarding
  • Multiple selectors configured wrong

Google Workspace

1
Generate DKIM key in Google Admin

Login to admin.google.com

Go to: Apps → Google Workspace → Gmail → Authenticate email
2
Click 'Generate new record'

Select your domain and click 'Generate new record'

Google will create a unique DKIM selector (usually 'google' or random string) Key length: 2048-bit (recommended)
3
Copy DKIM record details from Google

Google shows you DNS Host name and TXT record value - these are unique to your domain

Click 'Copy' button next to both: • DNS Host name (e.g., google._domainkey) • TXT record value (long string starting with v=DKIM1...)
Google generates a unique DKIM key pair for your domain. The public key will be a long string starting with 'v=DKIM1; k=rsa; p=MI...' that you must copy exactly as shown.
4
Add to DNS at your registrar

Go to your domain registrar's DNS management

Create new TXT record: 1. Paste the DNS Host name from Google (e.g., google._domainkey) 2. Paste the full TXT record value from Google 3. Set TTL: 3600
Warning: Copy the EXACT value from Google - do not modify it. Even one character wrong will break DKIM.
5
Activate in Google Admin

Return to Google Admin console

Click 'Start authentication' button Wait 24-48 hours for Google to verify and activate
6
Verify DKIM is working

Send test email to a Gmail account

Open email → Click three dots → Show original → Check for 'DKIM: PASS'

Microsoft 365

1
Access Microsoft 365 admin center

Login to admin.microsoft.com

Navigate to: Settings → Domains → Select your domain
2
Enable DKIM signing

Go to: Security → Email Authentication Settings → DKIM

Toggle 'Enable' for your domain
3
Get DKIM CNAME records from Microsoft

Microsoft shows two CNAME records to create - these are unique to your domain

Copy both CNAME records shown by Microsoft: Record 1: Host: selector1._domainkey Points to: selector1-[yourdomain-com]._domainkey.[tenant].onmicrosoft.com Record 2: Host: selector2._domainkey Points to: selector2-[yourdomain-com]._domainkey.[tenant].onmicrosoft.com
Microsoft uses two selectors for key rotation. The exact values will be shown in your Microsoft 365 admin panel.
4
Add CNAME records to DNS

Create both CNAME records at your domain registrar

For each CNAME record: 1. Type: CNAME 2. Host: [paste from Microsoft] 3. Points to: [paste from Microsoft] 4. TTL: 3600
Warning: Create both CNAME records exactly as shown in Microsoft 365. Do not use TXT records.
5
Enable signing in Microsoft 365

Return to Email Authentication Settings

Click 'Enable' to start DKIM signing (wait 15-60 minutes)

Cold email platforms

1
Access DNS settings in platform

Login to your cold email platform (Instantly, Smartlead, etc.)

Go to: Settings → Domains → Select domain → DNS Configuration
2
Copy DKIM record provided by platform

Platform generates a unique DKIM key for your domain and shows the exact DNS record to add

Look for 'DKIM Record' section Click 'Copy' button to copy the DKIM TXT record value
Each platform uses different selectors: • Instantly: instantly._domainkey • Smartlead: s1._domainkey or smartlead._domainkey • Lemlist: lemlist._domainkey The platform will show you both the Host/Name and Value to use.
3
Add to DNS registrar

Go to your domain registrar and create new TXT record

1. Name/Host: [copy from platform, e.g., instantly._domainkey] 2. Type: TXT 3. Value: [paste DKIM string from platform starting with v=DKIM1...] 4. TTL: 3600
Warning: Paste the exact value from your platform - even small changes will break DKIM signing.
4
Verify in platform

Return to cold email platform and click 'Verify' or 'Check DNS'

Should show green checkmark within 10-60 minutes If fails, check for typos in DNS record
5
Test DKIM signing

Send test email from platform

Use mail-tester.com or check raw email headers for 'DKIM-Signature:' header
Verify your DKIM setup

Use these free tools to confirm your DKIM configuration is correct:

DMARC (Domain-based Message Authentication) - Complete Setup Guide

What DMARC does

DMARC tells ISPs what to do when SPF or DKIM fail (none/quarantine/reject) and sends you reports about authentication failures. This protects your brand from spoofing and gives visibility into deliverability issues.

Common DMARC mistakes

  • Starting with p=reject (too aggressive)
  • Not monitoring DMARC reports
  • Missing subdomain policy (sp=)
  • Wrong or missing reporting addresses

Universal DMARC setup (all providers)

1
Ensure SPF and DKIM are working first

DMARC requires SPF and DKIM to be properly configured

Warning: DO NOT set up DMARC until SPF and DKIM both pass. Check with mail-tester.com first.
2
Start with monitoring policy (p=none)

Create basic DMARC record to collect data without blocking emails

Copy this value:
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com; ruf=mailto:dmarc-forensics@yourdomain.com; pct=100
Host/Name: _dmarc.yourdomain.com (or just _dmarc) Type: TXT TTL: 3600
3
Set up email addresses for reports

Create email addresses to receive DMARC reports

Create: dmarc-reports@yourdomain.com for aggregate reports (RUA) Optional: dmarc-forensics@yourdomain.com for failure details (RUF)
4
Add DMARC record to DNS

Go to your domain registrar's DNS management

Create TXT record: Host: _dmarc Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com TTL: 3600
5
Monitor reports for 2-4 weeks

Check daily DMARC aggregate reports sent to your email

Look for: ✓ SPF pass rate ✓ DKIM pass rate ✓ Alignment issues ✓ Sources of email
6
Gradually increase policy strictness

After confirming SPF/DKIM pass consistently, strengthen policy

Copy this value:
Week 1-2: p=none (monitoring)
Week 3-4: p=quarantine; pct=10 (quarantine 10%)
Week 5-6: p=quarantine; pct=50
Week 7+: p=quarantine; pct=100 (or p=reject if confident)
Warning: p=reject blocks ALL failing emails - only use when SPF/DKIM pass rate is 99%+
7
Final production DMARC record

Recommended DMARC policy for cold outreach

Copy this value:
v=DMARC1; p=quarantine; sp=quarantine; pct=100; rua=mailto:dmarc-reports@yourdomain.com; adkim=r; aspf=r; fo=1
p=quarantine: Failed emails go to spam sp=quarantine: Subdomain policy adkim=r & aspf=r: Relaxed alignment (recommended) fo=1: Generate forensic reports for all failures
Verify your DMARC setup

Use these free tools to confirm your DMARC configuration is correct:

Authentication ROI: Implementing SPF, DKIM, and DMARC correctly usually improves inbox placement by 30-50% immediately. This is the highest-ROI deliverability fix because it's quick (1-3 days) and has massive impact. Do this before anything else if your authentication isn't perfect.

Sender reputation: the invisible score that determines inbox placement

Sender reputation is the single most important deliverability factor (35% of the algorithm), yet it's mostly invisible. ISPs maintain reputation scores for your sending domain and IP based on historical behavior, engagement, and complaints. Here's what actually matters:

Domain Reputation

Domain age

Target: 6+ months old

High

Historical sending volume

Target: Consistent growth pattern

High

Domain purpose

Target: Dedicated to email sending

Medium

Blacklist presence

Target: Zero listings

Critical

IP Reputation

IP warmup status

Target: Fully warmed (6+ weeks)

High

Shared vs dedicated

Target: Dedicated for high volume

Medium

IP age and history

Target: Clean history, 3+ months

High

Reverse DNS setup

Target: Properly configured PTR

Medium

Engagement Metrics

Open rate

Target: 25-40% for cold outreach

High

Click-through rate

Target: 2-5% minimum

Medium

Reply rate

Target: 5-10% target

Very High

Spam complaints

Target: <0.1% (1 per 1000)

Critical

List Quality

Bounce rate

Target: <2% per campaign

Critical

Hard bounce rate

Target: <0.5%

Critical

Catch-all addresses

Target: Minimal usage

Medium

Email verification

Target: 100% verified before send

High
Reputation monitoring tools: Google Postmaster Tools shows your domain reputation score (Low/Medium/High) for Gmail. Microsoft SNDS provides IP reputation data for Outlook.com. Both are free and essential for monitoring. Check them weekly minimum during warmup, monthly once established.

The challenge with sender reputation is that it's cumulative and slow-changing. One bad campaign can damage reputation you spent months building, but recovering from poor reputation takes 6-12 weeks of perfect behavior. This is why list quality, proper warmup, and engagement optimization matter so much.

Reputation recovery timeline

  1. 1Week 1-2: Identify and stop reputation-damaging behavior (high bounces, spam complaints, low engagement)
  2. 2Week 3-4: Reduce sending volume 50%, switch to highly engaged segments only, verify all recipients
  3. 3Week 5-8: Gradually increase volume 20% per week if metrics improve, maintain <0.1% complaints
  4. 4Week 9-12: Return to normal volume if inbox placement >90%, continue monitoring closely
  5. 5Month 4+: Reputation usually fully recovered if maintaining good practices, can resume growth

Note: This assumes you fixed the root cause. If you continue the same behavior, reputation will never recover.

Content optimization: avoiding spam triggers and improving engagement

Email content accounts for 20% of deliverability decisions. Even with perfect authentication and good reputation, spam-triggering content gets filtered. Here's what ISPs actually flag:

High-risk spam triggers (avoid always)

These words and patterns trigger spam filters aggressively. Using them usually results in 50-80% spam placement:

FREE
GUARANTEED
NO RISK
100% FREE
URGENT
ACT NOW
LIMITED TIME
EXPIRES
CASH BONUS
EXTRA INCOME
MAKE MONEY
All caps subject lines
Multiple exclamation marks!!!
Excessive use of $$$$ or money symbols

Medium-risk triggers (use sparingly)

These can work in context but raise spam scores. Use maximum 1-2 per email:

Click here
Click below
Order now
Unlimited
Special promotion
As seen on
Compare rates
One time
Apply now
Subject lines with Re: or Fwd: (when not replies)
Questions in subject line???

Content structure issues

Technical content problems that hurt deliverability:

  • Large images with minimal text (image-heavy emails)
  • All-image emails with no text version
  • Broken HTML or CSS
  • JavaScript or forms in email body
  • Shortened URLs (bit.ly, tinyurl) without context
  • Attachments in cold outreach emails

Formatting problems

Design and formatting issues that trigger filters:

  • Excessive use of red or bright colors
  • All caps paragraphs or sentences
  • Multiple font colors in short email
  • Massive font sizes (especially in subject)
  • Poor text-to-image ratio (aim for 60:40)
  • Hidden text (white text on white background)
Content best practices:
  • Keep text-to-image ratio at 60:40 or higher (mostly text)
  • Use 1-2 short paragraphs max, keep total length 50-150 words
  • One clear call-to-action, avoid multiple links
  • Personalize beyond just {'{'}firstName{'}'} - reference specific company info
  • Write like a human - contractions, conversational tone, no corporate jargon
  • Test every email template with mail-tester.com before sending (target 8+/10)

Remember: content optimization is about passing filters AND driving engagement. Even if your email reaches the inbox, low engagement (no opens, clicks, or replies) damages future deliverability. Write emails that recipients actually want to read and respond to, not just emails that avoid spam filters.

Infrastructure setup: domains, IPs, and sending patterns

Infrastructure is only 5% of the deliverability algorithm, but getting it wrong breaks everything else. Here's how to set up domains, IPs, and sending patterns correctly:

Domain Strategy

Use subdomain for cold outreach

High

Why: Protects main domain reputation from outreach risks

How: outreach.yourdomain.com or mail.yourdomain.com

Multiple sending domains for scale

High

Why: Distribute volume, reduce per-domain risk, improve deliverability

How: 1 domain per 1,000 emails/day target volume

Domain age before outreach

Medium

Why: New domains lack reputation and trust with ISPs

How: Wait 30-60 days after registration, age domains before warmup

Match From address to domain

Critical

Why: Mismatched From/sending domains hurt authentication

How: firstname@outreach.yourdomain.com sends from that domain

IP Configuration

Dedicated IPs for volume >100k/month

High

Why: Full control over reputation, not affected by other senders

How: One dedicated IP per sending domain

IP warmup schedule

Critical

Why: Cold IPs sending high volume = instant spam filtering

How: 6-week progressive warmup: 50→500→2000→10000 emails/day

Reverse DNS (PTR) records

High

Why: ISPs verify IP matches claimed sending domain

How: PTR record: mail.yourdomain.com points to sending IP

Monitor IP blacklists

Critical

Why: Blacklisted IPs have 90%+ spam placement rate

How: Daily monitoring: MXToolbox, Spamhaus, SURBL checks

Sending Patterns

Consistent daily sending schedule

High

Why: Erratic patterns (silent for days, then spike) trigger filters

How: Send same time daily, maintain consistent volume ±20%

Gradual volume increases

High

Why: Sudden volume spikes indicate compromised account or spam

How: Increase volume max 20-30% per week

Time zone appropriate sending

Medium

Why: Sending at 3 AM recipient time looks automated and spammy

How: Send 8 AM - 6 PM recipient's local time

Rate limiting per recipient domain

Medium

Why: Too many emails to same company = spam to that company's filters

How: Max 3-5 emails/hour to single recipient domain

Infrastructure mistakes to avoid:
  • Using your main company domain for cold outreach (protects reputation with subdomain)
  • Sending from brand new domain without warmup (6-week warmup is mandatory)
  • Shared IP for high volume >50k/month (get dedicated IP for control)
  • Inconsistent sending schedule (erratic patterns trigger spam filters)
  • Overloading single domain with >2000 emails/day (split across multiple domains)
  • No reverse DNS setup (ISPs check PTR records, missing = major red flag)

The most common infrastructure mistake is trying to scale too fast on too few domains. Plan for 1 sending domain per 1,000-1,500 emails/day target volume. If you want to send 5,000 emails/day, you need 4-5 warmed domains. This distributes risk and maintains deliverability at scale.

Initial Setup (Week 1)

  • Purchase and configure dedicated sending domain(s)
  • Set up SPF, DKIM, DMARC records correctly
  • Configure reverse DNS (PTR) for sending IPs
  • Implement email verification service
  • Set up Google Postmaster Tools and Microsoft SNDS

Warmup Period (Weeks 2-7)

  • Start with 50-100 emails/day to engaged contacts
  • Gradually increase volume 20-30% weekly
  • Monitor inbox placement rate daily
  • Track authentication pass rates
  • Maintain <0.1% spam complaint rate

Production Launch (Week 8+)

  • Scale to target volume (1000-2000/day per domain)
  • A/B test email content for engagement
  • Monitor deliverability metrics 3x weekly minimum
  • Check blacklists weekly
  • Review and optimize based on engagement data

Ongoing Maintenance

  • Weekly deliverability metrics review
  • Monthly deep dive into DMARC reports
  • Quarterly list cleaning and verification
  • Regular content spam score testing
  • Continuous monitoring of ISP reputation scores

Monitoring and recovery: fixing deliverability problems fast

Even with perfect setup, deliverability problems happen. The key is catching them early and knowing how to recover quickly. Here's how to monitor effectively and troubleshoot common issues:

Essential deliverability tools

Testing & Monitoring

Mail-tester.com

Pre-send spam score testing

Free (3 tests/day)

Key features: Spam score, authentication check, content analysis

GlockApps

Inbox placement testing

$49/mo+

Key features: Real inbox testing, spam folder tracking, ISP-specific results

Google Postmaster Tools

Gmail reputation monitoring

Free

Key features: Domain reputation score, spam rate, authentication status

Microsoft SNDS

Outlook.com deliverability data

Free

Key features: IP reputation, spam trap hits, complaint rates

Email Verification

FindyMail

Email validation and enrichment

$49/mo+

Key features: Real-time verification, catch-all detection, deliverability scoring

ZeroBounce

Email list cleaning

Pay per validation

Key features: Spam trap detection, abuse email detection, bounce prediction

NeverBounce

Bulk email verification

$0.008/email

Key features: Real-time API, bulk verification, auto-bounce removal

Clearout

Email validation with deliverability focus

$0.0012/email

Key features: Catch-all detection, greylisting check, MTA validation

Domain & IP Management

MXToolbox

DNS and blacklist monitoring

Free + paid

Key features: Blacklist monitoring, DNS lookup, SMTP diagnostics

Warmup Inbox

Automated domain warmup

$15/inbox/mo

Key features: Gradual volume increase, engagement simulation, reputation building

MailReach

Deliverability monitoring + warmup

$25/mo+

Key features: Inbox placement tracking, warmup automation, spam folder monitoring

Folderly

Email deliverability platform

$120/mo+

Key features: Template spam check, domain reputation, deliverability fixes

Authentication & Security

DMARC Analyzer

DMARC monitoring and reporting

Free + paid

Key features: DMARC report aggregation, SPF/DKIM alignment tracking

Postmark DMARC Digests

DMARC report parsing

Free

Key features: Weekly digest emails, authentication failure alerts

EasyDMARC

Complete DMARC management

$8/mo+

Key features: DMARC record generator, SPF flattening, monitoring

PowerDMARC

Enterprise DMARC solution

$30/mo+

Key features: Threat intelligence, BIMI support, forensic reports

Monitoring schedule:

Catch deliverability problems before they become critical:

  • Daily: Bounce rate, spam complaints, inbox placement rate (during warmup and first 3 months)
  • 3x per week: Open rates, authentication pass rates, engagement metrics (after warmup)
  • Weekly: Blacklist checks (MXToolbox), Google Postmaster reputation score, DMARC reports
  • Monthly: Deep dive into deliverability trends, list cleaning, domain reputation review
  • Quarterly: Full infrastructure audit, email verification of entire database, update processes

Common deliverability problems and recovery plans

Sudden drop in inbox placement

Symptoms you'll see:

  • Open rates dropped >50%
  • Emails appearing in spam folders
  • Bounce rate increased

How to diagnose:

  1. 1Check spam complaints - did you hit a spam trap?
  2. 2Review recent email content - new spam triggers?
  3. 3Verify authentication - SPF/DKIM/DMARC still passing?
  4. 4Check blacklists - domain or IP listed?

Recovery steps:

  1. 1Pause campaigns immediately to prevent further damage
  2. 2Run email through spam checkers (Mail-tester, GlockApps)
  3. 3Request blacklist removal if listed (usually 24-72 hours)
  4. 4Reduce sending volume by 50% and slowly rebuild
  5. 5Switch to highly engaged segments only for 1-2 weeks

Typical recovery time: 2-4 weeks typically

High bounce rate (>5%)

Symptoms you'll see:

  • Many invalid email addresses
  • Hard bounces increasing
  • Soft bounces not resolving

How to diagnose:

  1. 1List quality issue - purchased list or old data?
  2. 2Email verification not done or failed
  3. 3Catch-all addresses marked as valid
  4. 4Company domains changed or defunct

Recovery steps:

  1. 1Stop sending immediately - high bounces kill reputation fast
  2. 2Re-verify entire list through validation service
  3. 3Remove all bounced addresses permanently
  4. 4Implement real-time email verification
  5. 5Set up bounce handling automation

Typical recovery time: Immediate stop, 1 week to clean list

Authentication failures

Symptoms you'll see:

  • DMARC failing
  • SPF softfail or fail
  • DKIM signature invalid

How to diagnose:

  1. 1DNS records not propagated (can take 24-48 hours)
  2. 2SPF record exceeds 10 DNS lookup limit
  3. 3DKIM keys rotated but not updated
  4. 4Sending service not included in SPF

Recovery steps:

  1. 1Use DNS checker to verify record propagation
  2. 2Flatten SPF record to reduce lookups
  3. 3Regenerate and publish new DKIM keys
  4. 4Update SPF to include all sending sources
  5. 5Test with mail-tester.com before resuming

Typical recovery time: 1-3 days for DNS propagation

Low engagement (opens/clicks)

Symptoms you'll see:

  • <15% open rate
  • Minimal clicks
  • No replies
  • But emails reach inbox

How to diagnose:

  1. 1Content not relevant to recipients
  2. 2Subject lines not compelling
  3. 3Targeting wrong ICP or personas
  4. 4Sending at wrong times

Recovery steps:

  1. 1This is not a deliverability issue - emails reaching inbox
  2. 2A/B test subject lines extensively
  3. 3Improve personalization and relevance
  4. 4Segment list by persona and customize messaging
  5. 5Review ICP targeting criteria

Typical recovery time: Ongoing optimization, 2-3 weeks for noticeable improvement

Prevention vs recovery: Recovery from deliverability problems usually takes 4-8 weeks of perfect behavior. Prevention (proper warmup, list verification, engagement monitoring) takes the same time but maintains consistent results. Always invest in prevention rather than relying on ability to recover from problems.

The key to deliverability success isn't avoiding problems entirely (they'll happen) - it's catching them early through consistent monitoring and having recovery playbooks ready. Most major deliverability disasters happen because teams didn't notice problems for weeks, allowing damage to compound. Daily monitoring during warmup and 3x weekly after launch prevents this.

Frequently asked questions

Need help with email deliverability?:

At Outreaches, we manage complete email deliverability setup: domain acquisition and warmup, SPF/DKIM/DMARC configuration, IP reputation management, inbox placement monitoring, and ongoing optimization. Our clients usually achieve 95%+ inbox placement and maintain it long-term.

Schedule deliverability audit

Ready to implement these strategies?

Let's build your systematic outreach process from scratch. From signal-driven data to booked meetings.

Continue reading