Hacker news

  • Top
  • New
  • Past
  • Ask
  • Show
  • Jobs

Spamhaus new email sender requirements in November (https://www.spamhaus.org)

146 points by computer23 4 days ago | 148 comments | View on ycombinator

BLKNSLVR 4 days ago |

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

albertgoeswoof 4 days ago |

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.

cowlevel 3 days ago |

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

computer23 4 days ago |

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/

johnea 3 days ago |

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

superkuh 4 days ago |

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

greatgib 3 days ago |

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

tete 3 days ago |

In all reality though most spam that isn't trivially detected nowadays comes from Mailchimp, Sendgrid, etc., hacked email accounts (gmail, outlook, etc.).

I am unsure how the first ones are financially viable, maybe also hacked into?

Improperly setup mail servers I think are a thing of the past, since all the big providers have been blocking them for ages. Sure every now and then some come through, but at this point I believe these are basically all just old spam systems that are extremely easy to detect.

sneak 4 days ago |

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

fschuett 3 days ago |

I personally envision a future where I can just let a local LLM filter / categorize the E-Mail on-device where I can customize rules for me instead of having a certain racket do the "protection" for me.

gertrunde 3 days ago |

Surely working/aligned forward/reverse DNS has been mostly required for SMTP for years?

It's pretty much the only thing I usually bother with reverse DNS for.

xmddmx 4 days ago |

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?

raggi 4 days ago |

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?

azinman2 3 days ago |

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

nubinetwork 4 days ago |

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

undefined 3 days ago |

undefined

jiveturkey 3 days ago |

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

nikolay 3 days ago |

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

jwr 4 days ago |

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.

zurfer 3 days ago |

Every now and then I wonder how my mail inbox would feel when people would need to pay 1ct to send me an email, and how it would feel at 10ct and at 1usd.

Currently it seems to cost 0.001ct.

DmarcDkim about 1 hour ago |

[dead]

djgrillmaster 4 days ago |

[dead]

logicallee 3 days ago |

[flagged]