Deliverability Recovery: Step-by-Step After a Reputation Crash

Stop the Bleeding

When deliverability crashes, the first priority is stopping the damage. Every email you send to an unengaged recipient while your reputation is damaged makes recovery harder.

Immediate Actions (Day 1)

1. Reduce volume by 75%. Send only to recipients who engaged (opened or clicked) in the last 30 days.
2. Pause all automated campaigns except critical transactional email.
3. Check blacklists. Search all sending IPs on MXToolbox or similar. If listed, start delisting immediately.
4. Verify authentication. Send a test email and inspect headers. Confirm SPF, DKIM, and DMARC all pass with alignment.
5. Check Postmaster Tools and SNDS. Document current reputation status as your baseline.

Don't try to "send through" a reputation crash. More volume makes it worse.

Diagnose the Root Cause

Before rebuilding, understand what caused the crash. The recovery strategy depends on the cause.

Common Causes and Diagnosis

Symptom	Likely Cause	How to Confirm
Sudden drop across all providers	Blacklisting	Blacklist check tools
Gradual decline over weeks	Engagement decay / list quality	Postmaster Tools trend, engagement metrics
Gmail-specific drop	Domain reputation damage	Postmaster Tools showing Low/Bad
Outlook-specific drop	IP reputation damage	SNDS showing Yellow/Red
Post-campaign crash	Bad list segment or content	Correlate with specific campaign send
Post-migration crash	Warmup failure	New IP/domain not properly warmed

Practitioner note: In 80% of the deliverability recovery cases I handle, the root cause is list quality — not authentication, not blacklists, not content. The sender accumulated inactive subscribers for months, eventually hit spam traps, and reputation degraded slowly until it fell off a cliff. The crash feels sudden, but the decay started long before.

The Recovery Sequence

Phase 1: Fix Infrastructure (Days 1-3)

Authentication: Verify and fix SPF, DKIM, and DMARC. Run a Mail-Tester check to confirm a 9-10/10 score.

Blacklists: Submit delisting requests for any active listings. Spamhaus, Barracuda, SpamCop each have different processes.

Technical: Verify reverse DNS, HELO/EHLO configuration, TLS support, and List-Unsubscribe header.

Phase 2: Clean the List (Days 3-7)

Remove hard bounces. Every address that hard bounced in the last 90 days gets suppressed.

Remove complainers. Anyone who filed a spam complaint gets permanently suppressed.

Run validation. Pass your remaining list through a validation service. Remove invalid, risky, role-based, and disposable addresses.

Apply aggressive sunset. Remove anyone who hasn't engaged in 90 days (not 180 — recovery requires a tighter threshold).

Segment by engagement:

• Tier 1: Clicked in last 30 days
• Tier 2: Opened in last 30 days (non-Apple)
• Tier 3: Engaged in last 60 days
• Tier 4: Everything else (do not send)

Phase 3: Rebuild Sending (Weeks 1-4)

Start sending only to Tier 1 — your most engaged recipients. This is your warmup phase.

Week 1: Tier 1 only. Watch reputation daily. Send your best content.

Week 2: If reputation improves, add Tier 2. Monitor for any regression.

Week 3: If still improving, add Tier 3. Volume should now be 50-60% of pre-crash levels.

Week 4: Gradually increase to full volume for engaged recipients. Tier 4 stays suppressed permanently.

Practitioner note: The hardest part of recovery is convincing stakeholders to accept reduced volume for 4-6 weeks. Marketing teams want to "make up" for lost sends. But every email to an unengaged recipient during recovery delays the timeline. I frame it as: "You can lose 4 weeks now, or lose 4 months if we don't recover properly."

Phase 4: Monitor and Stabilize (Weeks 4-8)

Daily monitoring:

• Postmaster Tools reputation (target: Medium trending to High)
• SNDS status (target: Green)
• Bounce rates per campaign (target: below 0.5%)
• Complaint rates per campaign (target: below 0.1%)

Weekly monitoring:

• Inbox placement tests
• Blacklist scans
• Engagement trends by provider

Success criteria:

• Postmaster Tools reputation back to "High"
• SNDS status solid "Green"
• Inbox placement rates above 85% across providers
• Complaint rate stable below 0.1%

When to Consider a Fresh Start

Sometimes domain reputation is so damaged that recovery takes longer than starting fresh. Consider a new sending subdomain if:

• Domain has been blacklisted 3+ times in 12 months
• Postmaster Tools has shown "Bad" for 8+ weeks despite remediation
• DMARC reports show significant unauthorized use of your domain
• Recovery hasn't shown improvement after 8 weeks of proper remediation

A new subdomain (e.g., switching from mail.example.com to news.example.com) starts with neutral reputation. You'll still need proper warmup but skip the reputation baggage.

Practitioner note: Fresh starts work for the sending subdomain, but your organizational domain still carries history. If example.com itself is burned (not just mail.example.com), ISPs still associate the new subdomain with the parent domain. In those cases, a full domain strategy review is needed.

Preventing the Next Crash

After recovery, implement these safeguards:

1. Sunset policy — automated removal of inactive subscribers
2. Re-engagement campaigns — running continuously, not quarterly
3. Automated monitoring with alerts on complaint and bounce thresholds
4. Engagement-based sending — send frequency matched to engagement level
5. Regular inbox placement testing — weekly seed tests

If you're in the middle of a deliverability crash and need expert diagnosis and a recovery plan, schedule an emergency deliverability audit.

Sources

• Google: Email Sender Guidelines
• Google: Postmaster Tools
• Microsoft: SNDS
• Spamhaus: Blocklist Removal
• M3AAWG: Remediation Best Practices

---

v1.0 · March 2026