Spamhaus new email sender requirements in November

computer23 90 points 82 comments November 16, 2026
www.spamhaus.org · View on Hacker News

Discussion Highlights (16 comments)

superkuh

>Do not remain at p=none permanently. Starting with p=none is acceptable, but we recommend having an enforcement policy. I've published a DMARC record that basically says to ignore DMARC and do nothing. I wonder if this will be enough. v=DMARC1;p=none;adkim=r;aspf=r;pct=0 I have no plans to ever change from none.

jwr

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.

computer23

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/

raggi

so can I get COI enforced and bad actors actually punished, or is this just gunna smash the little guys again? can i get recruiter list spam punished?

albertgoeswoof

These techniques rely on it being hard (or at least long winded) to setup a domain and server properly, such that spammers (who are self selected to be lazy) won’t do it right and give up quickly. But with AI, it’s easy to get DKIM, DMARC, HELO etc. set up perfectly for almost no effort (maybe fcrdns is a bit more complex as it’s a manual process at most ISPs) I think we are in the end going to go back to it just being based on IP (v4) reputation, and this is all theatre.

BLKNSLVR

> 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.

sneak

Being picky about what is sent in HELO/EHLO seems like useless nitpicking toil that will not prevent any spam.

nubinetwork

> requirement for every sending IP to have a valid HELO, a reverse DNS (PTR) record, and a matching A record. How was this not the default? If you're going to send me mail, I already check all of those... and I also check to see if you hold a MX. If your DNS is _that_ bad, I probably don't want your spam anyways...

xmddmx

Can someone clarify, do these rules apply only to people running their own mail transport? Or does it also apply to people sending mail through their mail hosting company (when that company is not Google or Microsoft). Specific example: I run servers "at home" that send mail through SMTP. I have forward DNS properly set up, but my reverse DNS is syn-123-123-123-123.res.spectrum.com My mail servers are, however, sending the mail through my mail host (DreamHost) and so I'm hoping that not having reverse DNS at home won't be a problem. Am I reading the Spaumhaus rules correctly?

jiveturkey

wait, these are all only just now new? what has taken them so long?

cowlevel

Spamhaus is effectively a protection racket. However, these specific requirements are extremely reasonable.

logicallee

There are a few more requirements: - You may no longer send mail pretending to be a real person or company that you're not. In the past, it was possible to set yourself as any sender. This is no longer allowed. - You may no longer send out canvassing emails that purport to express a business interest, investor interest, collaboration, or job offer if you are not prepared to immediately follow through. That means no more job spam and scams where you are in no way in any position or have any interest in hiring someone. Likewise, you may no longer send fake investor spam that you're interested in investing in someone, whereas in reality you have zero ability or interest in doing so. Interfering with other people's business relationships has always been a serious offense. It is now a criminal liability. If someone is doing business with someone else, reaching out, or starting to, you may not under threat of criminal liability in any way interfere with that relationship - not even through attempting to influence or manipulate the recipient. Regarding blocking or screening of certain mail that could be legitimate but may be lower value than some other mail that is more important: currently there is no guidance that every single sent or received mail must go through 100% of the time. We value that there is a certain bar or threshold, because when there isn't then it's a hundred spam calls a day, a hundred spam emails, evverything is spam. However, the advice is, therefore, when something is allowed through, then you should be prepared to allow it to progress naturally. It doesn't make sense to carefully curate relationships and what gets through, only to stop them if the recipient attentively reads the curated feed and engages with the sender on the terms they've set. I really hate when I take the time to respond to someone who reached out to me, and then my response goes to a black hole. Thank you for improving the Internet and cutting down on spam and scams.

johnea

This may be a new requirement by spamhaus, but this is an old school standard config practice for serving email...

greatgib

It is not detecting spam anymore but imposing their rules on all mail servers that sucks a lot because I'm quite sure that the majority of mail servers with random HELO are legit senders. And no one cares about the HELO for good reasons for decade

nikolay

I checked my site with Codex and it failed due to Cloudflare and Resend.

azinman2

Is it possible anymore to even acquire an IP address that’s clean and use it to self host?

Semantic search powered by Rivestack pgvector
13,334 stories · 126,150 chunks indexed