Deliverability Case Study: "I'm Still Sending"
This parody channels the bittersweet resilience of a sender who has been to the dark side of the inbox and clawed their way back. "I'm Still Sending" is a love letter to the slow, deliberate work of rebuilding a damaged sender reputation — a process that, much like the triumphant rock anthem it echoes, cannot be rushed. The narrator addresses an absent antagonist (the filters, the blocklists, the doubters), but the real story is one of authentication discipline and patient warmup.
Here's the technical breakdown of the rebuild journey:
Verse 1: The Filtering Wall and the Authentication Reckoning
"And there's a cold filtering wall at every I.S.P. / ... / I fixed authentication the proper way"
- The Deliverability Context: The "cold filtering wall at every I.S.P." is the daily reality of any sender with a damaged reputation. Once Gmail, Yahoo, or Microsoft has decided you're untrustworthy, every campaign hits a wall of policy filters, content scrutiny, and engagement-based throttling. Mail doesn't bounce — it just vanishes, often silently routed to spam without a single 5xx code to tell you why.
- The Fix — "Authentication the proper way": This isn't a vague gesture. Properly configured authentication means three specific things working in concert:
-
SPF (RFC 7208): A TXT record that authorizes sending IPs, staying under the 10-DNS-lookup limit to avoid
permerror.
-
DKIM (RFC 6376): 2048-bit signing keys with documented selector rotation, and a
d= domain that aligns with the visible
From header.
-
DMARC (RFC 7489): A published policy — ideally moving from
p=none (monitoring) to
p=quarantine or
p=reject once aggregate (rua) reports confirm clean alignment.
Chorus & Post-Chorus: The Reputation Rebuild
"I'm still sending after all this time / Pickin' up the pieces of my rep without you on my mind"
- The Deliverability Context: "Pickin' up the pieces of my rep" is the most honest line in the song. Sender reputation is not a single score — it's a mosaic of IP reputation (tracked via Microsoft SNDS and Google Postmaster Tools) and domain reputation (Bad/Low/Medium/High in GPT). Both must be rebuilt independently, and domain reputation now matters more than IP reputation in modern ML-based filtering at Gmail.
- The Strategy: "After all this time" is the key phrase. Reputation repair is measured in weeks, not days. A domain that has been tagged "Bad" in Google Postmaster Tools typically requires 4–8 weeks of consistent, low-volume sending to highly engaged recipients before the rating climbs back to "Medium" or "High."
Verse 2: The Warmup Comeback
"The blocks you made were meant to cut me down / But now my sending domain's got reputation all around"
- The Deliverability Context: "The blocks" refer to listings on Spamhaus (SBL/DBL/ZEN), Barracuda, or SURBL — each requiring its own delisting request and root-cause remediation. Simply requesting delisting without fixing the underlying issue (spam traps, high complaint rates, compromised credentials) results in immediate re-listing.
- The Resolution — IP and Domain Warmup: "My sending domain's got reputation all around" describes a successful warmup ramp. Best practice:
-
Start small: 200–500 messages per day to your most engaged subscribers (opens and clicks within the last 30 days).
-
Double every 2–3 days: Provided
complaint rate stays under 0.10% and bounce rate under 2%.
-
Separate subdomains: Marketing on
mail.brand.com, transactional on
brand.com — so a marketing reputation dip never poisons password resets.
Outro: The Quiet Persistence
"I'm still sending (Yeah, yeah, yeah)"
The repeated outro isn't filler — it's the truth of deliverability work. There is no dramatic finale, no
inbox placement trophy. There is only the daily discipline of authentication, the patient arithmetic of warmup, and the humility to let engagement metrics guide every send. Reputations are not won back in a single campaign; they are earned, quietly, one delivered message at a time.
Ever feel like your mail is just
vanishing from sight, ghosted by every ISP filter while your competitors waltz into the inbox? The good news, like the song says, is that you can still be sending — better than you ever did — once you rebuild your reputation from the ground up. Recovery isn't about gimmicks; it's about authentication, patience, and proving you're a sender worth trusting again.
Fix Authentication "The Proper Way"
Before you worry about reputation or warmup, you need cryptographic proof of identity. Without it, no amount of good behavior will save you from the filtering wall.
- Lock Down SPF Without Breaking It: Sender Policy Framework (SPF) lists which IPs are authorized to send for your domain via a DNS TXT record. Watch the 10-DNS-lookup limit defined in RFC 7208 — exceeding it causes a permerror that silently fails authentication. Use
-all (hardfail) once you're confident in your sending sources, not ~all (softfail) as a permanent crutch.
- Sign Everything With DKIM: DomainKeys Identified Mail (DKIM, RFC 6376) attaches a cryptographic signature using a private key, verified against a public key published at your selector's DNS record. Use 2048-bit keys — 1024-bit is considered weak by modern standards — and rotate selectors at least annually.
- Enforce DMARC With Aligned Identifiers: Domain-based Message Authentication, Reporting, and Conformance (DMARC) only passes when SPF or DKIM aligns with the visible From: domain. Start at
p=none with rua= reporting to a tool like Postmark or Dmarcian, then progress to p=quarantine and finally p=reject once your reports are clean.
- Earn the BIMI Logo: Brand Indicators for Message Identification requires an enforced DMARC policy (
p=quarantine or p=reject), an SVG Tiny PS logo, and a Verified Mark Certificate (VMC). It's the visible payoff for getting authentication right.
Pick Up the Pieces of Your Rep
Reputation is tracked separately at the IP and domain level — and once it's tanked, only consistent, measurable behavior will rebuild it.
- Live Inside Google Postmaster Tools: Google's dashboard reports domain reputation (Bad/Low/Medium/High), IP reputation, spam rate, and authentication pass rates. Treat anything below "High" as a problem to investigate, and keep your spam rate under Google's 0.10% warning threshold — 0.30% triggers severe filtering.
- Watch Microsoft SNDS for the Other Half of the Inbox: Smart Network Data Services (SNDS) shows IP status (green/yellow/red), complaint rates, and spam trap hits across Outlook and Hotmail. Pair it with the Junk Mail Reporting Program (JMRP) feedback loop to capture complaints and suppress complainers immediately.
- Suppress Hard Bounces Permanently: A 5xx response (especially 550 5.1.1 "no such user") is a permanent failure. Re-sending to hard bounces is the fastest way to hit recycled spam traps and exceed the 2% bounce threshold that triggers ISP filtering.
Warming IPs (Again) the Right Way
You can't go from zero to a million sends overnight. ISPs interpret sudden volume spikes as botnet behavior — even from authenticated, well-meaning senders.
- Ramp by Engagement, Not by Calendar: Start at 200–500 messages per day to your most engaged subscribers (opens and clicks within the last 30 days). Roughly double volume every 2–3 days, watching deferrals (4xx codes) as your signal to slow down.
- Warm the Domain Separately From the IP: A new sending domain has its own reputation curve, even on a warm IP. Use a marketing subdomain like
mail.yourbrand.com to isolate promotional reputation from your transactional yourbrand.com traffic.
- Plan for 4–8 Weeks at Volume: High-volume senders should expect a full warmup cycle to take a month or two. Cutting it short to hit a campaign deadline is the single most common cause of post-migration deliverability collapse.
Conclusion
Recovering deliverability is exactly what the song describes: picking up the pieces, fixing authentication the proper way, and warming IPs again with patience. Done right, you'll look like a trusted sender to every ISP — and you'll still be sending long after your old reputation has faded away.
Your Recovery Sender Checklist:
- Confirm SPF stays under 10 DNS lookups and DKIM uses 2048-bit keys.
- Progress DMARC from
p=none to p=reject using rua reports as your guide.
- Monitor Google Postmaster Tools and Microsoft SNDS at least weekly.
- Permanently suppress all hard bounces and FBL complainers within 24 hours.
- Warm new IPs starting at 200–500/day, doubling every 2–3 days to engaged users.
- Isolate marketing and transactional streams on separate subdomains.
Educational content. Email deliverability evolves rapidly. Platform rules (Gmail, Yahoo, etc.), engagement signals, and ESP behaviours change frequently, and real-world issues often involve conflicting signals, data quality problems, and failure modes that general best practices can’t anticipate. Content on this site is provided for informational purposes only and does not replace a thorough analysis by a qualified deliverability professional.
Terms of Use