logoalt Hacker News

Spamhaus new email sender requirements in November

58 points • by computer23 • yesterday at 9:47 PM • 47 comments • view on HN

Comments

jwr • yesterday at 9:59 PM

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.

➕ show 3 replies
albertgoeswoof • yesterday at 10:14 PM

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.

➕ show 2 replies
BLKNSLVR • yesterday at 10:31 PM

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

➕ show 6 replies
xmddmx • yesterday at 11:41 PM

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?

computer23 • yesterday at 10:02 PM

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/

➕ show 1 reply
nubinetwork • yesterday at 11:08 PM

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

raggi • yesterday at 10:06 PM

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?

sneak • yesterday at 10:56 PM

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

➕ show 1 reply
superkuh • yesterday at 9:54 PM

>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.
➕ show 1 reply
djgrillmaster • yesterday at 10:30 PM

[dead]