Symptoms#
- Messages landing in spam despite previously good placement
- Bounces mentioning policy, authentication, or reputation
- Provider dashboards showing a drop in reputation or authentication pass rate
Diagnosis steps#
- Confirm the configuration is live: query DNS from an external resolver and check the sending platform's settings page.
- Send to a seed mailbox and read the full headers, especially Authentication-Results.
- Compare the domains in From, Return-Path, and DKIM d= for alignment.
- Check provider dashboards (Google Postmaster Tools, Microsoft SNDS) for reputation and error rates.
- Review recent changes: new vendors, DNS edits, list imports, volume spikes.
Likely causes#
- Requesting delisting before fixing the cause; repeat listings become harder to remove.
- Ignoring minor blocklists that some corporate gateways still use.
Fix and re-verify#
- Check your IPs and domains against major blocklists weekly.
- Identify the cause: compromised account, list purchase, spam trap hits, or a misconfigured forwarder.
- Fix the root cause and document what changed.
- Submit a delisting request through the blocklist's process with evidence of remediation.
- Monitor for relisting for 30 days.
Frequently asked questions#
How long does Spamhaus delisting take?
Often within hours for SBL and CSS if the cause is fixed. DBL domain listings can take longer.
Which blocklists matter most?
Spamhaus (SBL, XBL, DBL), SpamCop, Barracuda, and SURBL have the widest impact.