Spamhaus new email sender requirements in November
Spamhaus is tightening its email sender requirements, pushing for proper DNS configuration, SPF/DKIM/DMARC authentication, and forward-confirmed reverse DNS for every sending IP. Commenters largely agree these are long-standing best practices and already enforced by major providers like Google and Microsoft, but worry they further marginalize small or home-hosted mail servers that lack control over IP space and reverse DNS. The changes highlight broader tensions between anti-spam effectiveness, the power of large email platforms and blocklist operators, and the viability of independent email hosting.
DMARC, SPF, DKIM and Policies
- Some run DMARC with
p=noneand wonder if that satisfies requirements; one claim says this “voids” SPF/DKIM, but others explicitly say that’s incorrect and that large providers still check alignment regardless of policy. - Confusion over whether DMARC can reduce security; others insist DMARC is about policy/enforcement, not disabling SPF/DKIM checks.
Spam Sources and “Too Big to Fail” Providers
- Many report most spam arriving from Gmail/Outlook-style consumer addresses or from infrastructure on Google/AWS/Azure.
- Some argue this is survivorship bias: people mostly see spam from big providers because others are blocked earlier.
- “Legal spam” and marketing lists are highlighted as a major annoyance, often hard to fully unsubscribe from.
Blocklists, Microsoft, and Operational Pain
- Several describe Microsoft’s reliance on Spamhaus causing false positives: minor HELO misconfigurations or subnets periodically blocked, with opaque and slow delisting processes.
- Tools like SNDS are described by some as useless or uninformative; Spamhaus support is reported as better than Microsoft’s.
Self‑Hosting, Residential IPs, and Reverse DNS
- A central tension: Spamhaus’ HELO/PTR/FCrDNS requirements conflict with hobbyists self‑hosting mail on residential connections.
- Many note that residential IPs and dynamic IPs are already widely distrusted; some claim “most of the internet” effectively blocks them.
- Suggested workarounds: use a VPS with proper rDNS, pay ISP for static IP + custom PTR, or use cheap SMTP relay services.
- Some consider blanket distrust of residential IPs unfair, but others point to botnets and abuse from those ranges.
Are the New Spamhaus Requirements Reasonable?
- One side: These are long‑standing best practices; anyone serious about email should already meet them. They mainly affect bulk senders and compromised systems.
- Other side: Requirements are seen as protectionist “security theater” that disproportionately harms small/self‑hosted setups and reinforces dominance of big mail providers.
Effectiveness and Future Directions
- Debate over whether strict HELO/PTR checks meaningfully reduce spam or just add toil.
- Some think AI and modern tooling make domain/email configuration trivial even for spammers, so reputation/IP‑based approaches will dominate anyway.
- A few envision user‑side or LLM‑based filtering and more restrictive, whitelist‑style personal email policies as longer‑term answers.