<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/spamhaus-new-email-sender-requirements-in-november-tboj7sfjk" -->

---
title: Spamhaus new email sender requirements in November
description: Spamhaus lays out the technical and behavioral requirements email senders must meet to avoid being listed as spam sources. Starting November 2026, every...
canonical: https://daily.dev/posts/spamhaus-new-email-sender-requirements-in-november-tboj7sfjk
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Spamhaus new email sender requirements in November | daily.dev
og:description: Spamhaus lays out the technical and behavioral requirements email senders must meet to avoid being listed as spam sources. Starting November 2026, every...
og:url: https://daily.dev/posts/spamhaus-new-email-sender-requirements-in-november-tboj7sfjk
og:image: https://api.daily.dev/og/posts/tBOJ7SFjK.png
og:image:alt: Spamhaus new email sender requirements in November
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Spamhaus new email sender requirements in November

**[Hacker News](https://daily.dev/sources/hn)** · 16 min read · 0 upvotes · 0 comments

## Summary

Spamhaus lays out the technical and behavioral requirements email senders must meet to avoid being listed as spam sources. Starting November 2026, every sending IP will need a valid HELO, a reverse DNS (PTR) record, and a matching A record. Senders must use confirmed opt-in, publish SPF, DKIM and DMARC records, keep SPF under the 10 DNS lookup limit, use DKIM keys of at least 1024 bits (2048 recommended), and keep bounce rates below 5%. Domains registered within the past 24 hours fall into the Zero Reputation Domains list, and new IPs or domains must be warmed up gradually before full-volume sending.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.spamhaus.org/sender-guidelines>

## Questions this post answers

### What DKIM key length does Spamhaus recommend for email authentication?

Spamhaus requires a minimum 1024-bit DKIM key length but recommends 2048-bit keys for every outbound message. The 'd=' domain on the DKIM signature must match the domain on the header From, and keys should be rotated at least annually, or immediately if a key is suspected compromised.

_Developers configuring DKIM for outbound mail can check current authentication guidance on daily.dev._

### How many DNS lookups can an SPF record use before it fails?

SPF records must stay within a 10 DNS lookup limit, counting all nested include statements plus mechanisms like a, mx, ptr, exists, and redirect. Exceeding the limit returns a PermError, which counts as neither a pass nor a fail, meaning SPF cannot authenticate mail or satisfy DMARC alignment.

_Anyone debugging SPF failures can track authentication pitfalls like this one on daily.dev._

### What is the minimum IPv6 allocation size required for sending email reputation purposes?

Sending IPv6 addresses must fall within an allocation of /64 or larger, matching RFC 6177's guidance that senders should be able to obtain at least a /64, and that space must have valid reverse DNS. Allocations smaller than /64 or lacking reverse DNS are frequently associated with spammer misuse.

_Teams planning IPv6 mail infrastructure can keep up with sending requirements like this on daily.dev._

## Community take

How the wider developer community reacted, aggregated from 1 discussion and 140 comments across hackernews (as of 2026-11-17).

**TL;DR:** Most of the debate centers on self-hosted/residential mail servers being effectively locked out by the reverse-DNS and FCrDNS requirements, with many arguing these rules just formalize what big providers already enforce while others call them protectionist theater that does little against actual spammers.

**Sentiment:** 10% positive · 35% mixed · 55% skeptical

**The case for**

- The requirements mostly codify best practices (valid PTR, SPF/DKIM/DMARC) that reputable mail admins have followed for over a decade.
- Unambiguous sender identification reduces the ability of bad actors to hide behind shared or laundered infrastructure.
- Setting up SPF/DKIM/DMARC is considered straightforward with modern tooling and not a real barrier for legitimate senders.

**The pushback**

- Self-hosters on residential ISP connections often cannot control PTR records, locking them out of compliance through no fault of their own.
- Some see this as protectionism/security theater that burdens small senders while having little effect on actual spammers, who can automate compliance just as easily.
- Big providers like Google, Microsoft, and Amazon are described as major spam sources that face little accountability despite their scale.
- Microsoft's reliance on Spamhaus combined with slow, opaque delisting/support processes (SNDS) is a recurring frustration.
- Spamhaus is distrusted by some as having outsized, unaccountable influence over email deliverability, akin to a 'protection racket.'

**By community**

- hackernews (heated): A long, contentious thread split between people defending the new rules as overdue formalization of existing best practice and others arguing they unfairly exclude small/residential self-hosters while barely touching real spam sources.

**Hottest debate:** Whether locking out residential/self-hosted mail servers via reverse-DNS requirements is a reasonable anti-spam measure or unfair protectionism that doesn't actually stop spam.

**Open questions**

- Can residential ISP customers realistically get custom PTR records, and which ISPs actually support this?
- Will requiring FCrDNS and SPF-compliant HELO domains meaningfully reduce spam volume, or just push legitimate small senders to relays/VPS providers?
- How should individuals practically route mail when they host multiple domains on one residential connection with only one usable PTR?

**Highlights**

> > Publish forward-confirmed reverse DNS for every sending IP > Every sending IP must have a reverse DNS entry pointing to a fully qualified domain name (FQDN). That hostname must, in turn, resolve back to the same sending IP address. This is known as forward-confirmed reverse DNS (FCrDNS). An IP with missing or mismatched reverse DNS is treated as suspicious and is one of the most common reasons for an IP to be considered for listing. I self-host an email server behind my ISPs connection, and so I do not own the IP address that I send mail from, therefore I can't satisfy the reverse DNS requirement.
> — [BLKNSLVR on hackernews · 17 comments](https://news.ycombinator.com/item?id=50524389)

> It's a stupid policy that will lead to many false positives among small installations, while having zero impact on actual spammers. A lot of modern spam policing is just protectionism of a duopoly masking as security theatre.
> — [elric on hackernews · 3 comments](https://news.ycombinator.com/item?id=50528377)

> These requirements are standard practice. Half the internet, including all of the big providers, already rejects your mail if you don't meet them. Spamhaus is late to the party, probably because it doesn't actually have any way to check these since it isn't the one receiving the email.
> — [cowlevel on hackernews · 1 comments](https://news.ycombinator.com/item?id=50529458)

> Most of my spam is through Google, Amazon and Microsoft. They don't care: they are "too big to fail" at this point. Nobody will block Google, right? We've allowed them to grow this way by preferring convenience.
> — [jwr on hackernews · 3 comments](https://news.ycombinator.com/item?id=50523967)

> Anyone else having their email blocked by Microsoft and Spamhaus? Microsoft Office 365 relies on Spamhaus and was blocking my email because the HELO on the mail server was mydomain.com instead of mailserver.mydomain.com. Once the problem was fixed, it took time for Spamhaus to re-scan the mail server and take the mail server off the block list. And it took more time for Microsoft to stop blocking mail. https://check.spamhaus.org/
> — [computer23 on hackernews · 2 comments](https://news.ycombinator.com/item?id=50524014)

**Source threads**

- [hackernews](https://news.ycombinator.com/item?id=50523784) · 132 points · 140 comments

## Similar posts on daily.dev

- [SPF, DKIM, and DMARC explained for developers](https://daily.dev/posts/spf-dkim-and-dmarc-explained-for-developers-mbs1noovg) · Flavio Copes · 2 upvotes · 1 comments
- [Email Deliverability Issues in 2026: 9 Common Problems and Fixes](https://daily.dev/posts/email-deliverability-issues-in-2026-9-common-problems-and-fixes-zqgpuodut) · Security Boulevard · 0 upvotes · 0 comments
- [Relaying outbound mail: DKIM, client IPs, and visibility](https://daily.dev/posts/relaying-outbound-mail-dkim-client-ips-and-visibility-lm5r3yjpy) · /dev/io · 0 upvotes · 0 comments
- [Email is crazy](https://daily.dev/posts/email-is-crazy-y6xb4vf9s) · Lobsters · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#dns](https://daily.dev/tags/dns)

[View this post on daily.dev](https://daily.dev/posts/spamhaus-new-email-sender-requirements-in-november-tboj7sfjk)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Spamhaus new email sender requirements in November","url":"https://daily.dev/posts/spamhaus-new-email-sender-requirements-in-november-tboj7sfjk","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/spamhaus-new-email-sender-requirements-in-november-tboj7sfjk"},"datePublished":"2026-11-17T04:33:01.486Z","dateModified":"2026-11-17T18:44:52.288Z","description":"Spamhaus lays out the technical and behavioral requirements email senders must meet to avoid being listed as spam sources. Starting November 2026, every...","image":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","thumbnailUrl":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/spamhaus-new-email-sender-requirements-in-november-tboj7sfjk","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,dns","timeRequired":"PT16M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"Spamhaus new email sender requirements in November"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/spamhaus-new-email-sender-requirements-in-november-tboj7sfjk#faq","mainEntity":[{"@type":"Question","name":"What DKIM key length does Spamhaus recommend for email authentication?","acceptedAnswer":{"@type":"Answer","text":"Spamhaus requires a minimum 1024-bit DKIM key length but recommends 2048-bit keys for every outbound message. The 'd=' domain on the DKIM signature must match the domain on the header From, and keys should be rotated at least annually, or immediately if a key is suspected compromised. Developers configuring DKIM for outbound mail can check current authentication guidance on daily.dev."}},{"@type":"Question","name":"How many DNS lookups can an SPF record use before it fails?","acceptedAnswer":{"@type":"Answer","text":"SPF records must stay within a 10 DNS lookup limit, counting all nested include statements plus mechanisms like a, mx, ptr, exists, and redirect. Exceeding the limit returns a PermError, which counts as neither a pass nor a fail, meaning SPF cannot authenticate mail or satisfy DMARC alignment. Anyone debugging SPF failures can track authentication pitfalls like this one on daily.dev."}},{"@type":"Question","name":"What is the minimum IPv6 allocation size required for sending email reputation purposes?","acceptedAnswer":{"@type":"Answer","text":"Sending IPv6 addresses must fall within an allocation of /64 or larger, matching RFC 6177's guidance that senders should be able to obtain at least a /64, and that space must have valid reverse DNS. Allocations smaller than /64 or lacking reverse DNS are frequently associated with spammer misuse. Teams planning IPv6 mail infrastructure can keep up with sending requirements like this on daily.dev."}}]}
```

