Deliverability Case Study: "Blocklisted"
Track 05 of Click Through is the album's lowest point and its most instructive moment. Every warning Marcus dismissed across Tracks 01 through 04 converges on a single Monday morning. The sends go out. Nothing delivers. Postmaster shows domain score in the red. The inbox Marcus declared war on two tracks ago is now completely unreachable — not because of the Promotions tab, but because of everything he chose not to fix.
The outro lands the album's central irony: Marcus spent Tracks 02 through 04 fighting the Promotions tab. He cannot reach the Promotions tab now. He cannot reach any tab.
Verse 1: The Cascade
"Google Postmaster — the score is red / Sender reputation — completely bled"
Domain blocklisting is not a single event triggered by a single campaign. It is the endpoint of a reputation decline that compounds over weeks. The cascade Marcus experienced:
- Weeks 1–2 (Tracks 01–02): 40% bounce rate on a cold send with missing authentication. Domain has no positive reputation history, and the first interactions are mostly bounces and a 0.3% complaint rate.
- Weeks 2–3 (Tracks 02–03): Resends to non-openers and a purchased list of 50,000 names. Spam traps in the purchased list begin triggering. Complaint rate climbs with each additional send to disengaged subscribers.
- Week 4 (Track 04): Complaint rate reaches 0.28% and continues upward. Gmail Postmaster domain reputation drops from Low to Bad. Mail begins being deferred or rejected before delivery confirmation.
- Monday (Track 05): 0.32% complaint rate crossed during a high-volume send. Domain-level enforcement activated. All mail from the domain rejected.
No single campaign caused this. The domain was already failing when Marcus thought he was succeeding.
Verse 2: Spam Traps
"The spam traps hit — I didn't even know"
Spam trap hits are invisible to the sender. There is no bounce code, no error message, no notification from the trap operator. The sender continues sending to what appears to be a valid address while the trap operator records each hit and reports it to
blocklist maintainers. The damage accumulates silently until it surfaces as a reputation drop or a blocklist listing.
The purchased list Marcus acquired in Track 03 was the source. Purchased lists are the primary vector for pristine spam trap exposure. Pristine traps — addresses that have never opted into anything — exist only in harvested, scraped, or commercially sold databases. A single pristine trap hit is treated by major blocklists as strong evidence of illegitimate list acquisition practices.
Bridge: What the Postmortem Shows
"Point-three-two — the cliff I said I'd beat"
Domain blocklisting leaves a clear postmortem. When Marcus opens Postmaster Tools and scrolls through the history, he sees the same numbers that appeared in Tracks 01 through 04 — but this time as an arc, not individual data points. The 40% bounce rate that was "filters being mean." The 0.3% complaint rate he shook off. The creeping dashboard he watched without acting. They form a single story.
The outro completes the inversion of Track 02. Marcus's declared enemy — the Promotions tab — is now the place he cannot reach. The tab was never the problem. Authentication was the problem. Consent was the problem. Engagement was the problem. All of that is recoverable. The domain, for now, is not.
A blocklisted domain is recoverable, but recovery takes weeks of disciplined low-volume sending and a complete rebuild of list quality and sending practices. Understanding how blocklisting works — and how to check for it, request removal, and prevent recurrence — is essential operational knowledge for any sender.
How Domain Blocklisting Works
Blocklisting operates at multiple layers, and each layer has different operators and different implications:
- Gmail Postmaster domain reputation: Gmail's internal reputation score (Bad / Low / Medium / High) determines delivery outcomes at Gmail specifically. A "Bad" score means Gmail is rejecting or spam-foldering most of your mail. This is not a traditional blocklist — it is Gmail's own reputation system, and removal requests do not apply.
- Spamhaus (DBL, ZEN): Spamhaus maintains the most widely used domain and IP blocklists. A Spamhaus DBL listing means your domain is blocked at providers that use Spamhaus data, which includes most major ISPs and corporate mail infrastructure. Spamhaus has a formal removal/delisting process, but repeat listings result in permanent blocks.
- Barracuda, SORBS, UCEPROTECT: Secondary blocklist operators. Less universally adopted but still impactful at specific providers. Each has its own removal process.
A single send can trigger multiple simultaneous blocklist listings if the
complaint rate,
spam trap hits, and reputation damage are severe enough.
Checking Your Blocklist Status
After any reputation incident, run a full blocklist check before attempting to resume sending:
- MXToolbox Blacklist Check: Checks against 100+ blocklists. Run it against your sending domain and your sending IPs separately — both can be listed independently.
- Spamhaus Lookup Tool: Check your specific domain and IP at spamhaus.org. Spamhaus listings are the highest-impact and require direct attention.
- Google Postmaster Tools: Not a blocklist, but shows your reputation tier and spam rate trend. A "Bad" rating here overrides everything else for Gmail delivery.
Requesting Removal
Each blocklist operator has different processes and criteria:
- Spamhaus: Provides an online removal request form. You must correct the underlying problem (spam trap hits, complaint rate, etc.) before requesting removal. Repeat requests without fixing the underlying issue result in permanent listing.
- Gmail Postmaster: There is no removal request process for Gmail reputation. Recovery requires sustained low-volume sending to a highly engaged segment over weeks — typically 30–60 days of rebuilding before reputation tiers improve.
- Other blocklists: Most provide a self-service removal request. Some require a waiting period after the problem is corrected.
Preventing Recurrence
A blocklisting event is the clearest possible signal that the list acquisition, sending practices, or complaint management process is broken. Returning to normal sending volume without fixing these problems leads to a second blocklisting, usually faster than the first:
- Never send to a purchased, rented, or scraped list. Ever.
- Remove hard bounces within 24 hours of any campaign. Every hard bounce that sits on the list is a future spam trap.
- Act on complaint rate warnings at 0.05%, not at 0.10%. By the time the warning fires, the underlying damage is already compounding.
- Build a suppression list and honor it permanently. Unsubscribers, complainers, and chronically inactive subscribers belong on a suppression list that is applied to every future send, from every sending infrastructure, on every domain.
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 