> 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.
If you have a static IP address and they're allowing outbound port 25 then my first thought is that you might have some sort of premium residential or business account that permits hosting in the ToS, in which case I would then infer they might allow you to specify a PTR record in their zone or maybe even support delegation to you.
Lots of inferences there, but presuming Spamhaus isn't already blacklisting your IP address then that's additional evidence you don't have a vanilla residential IP address.
I'm guessing good practice is renting a VPS and hoping it's not on blacklists already, or (more commonly) letting third parties read your mail by using a relay service. Or should we be applying for an ASN and buying IP blocks just to send mail?
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.
Even before AI, was DKIM and DMARC hard to setup? It's been a streamlined process for at least four years now (as long as I've had to professionally enter records in a registrar), and even longer before that in my homelab setups.
In my experience, it's really only the homegrown email servers failing DKIM/DMARC in the current year, which must be simple ignorance. I've had mailcow for years and it handles DKIM/DMARC perfectly, and I assume Stalwart is exactly the same.
In the office, Google or Microsoft, it's been copy and pasting a couple records into your registrar for like four years. Not sure how admins are still messing this up even with AI now, haha.
When you say "through Google, Amazon, and Microsoft", is what you mean "through a server on GCP, AWS, or Azure" (or through their equivalent email-sending services)?
I assume you don't mean you're receiving a large volume of spam from @amazon.com or @microsoft.com email addresses?
I think we can assume that most people responding here are running their own mailserver that receives. I am. And I run a catch-all for my domain that doesn't check any spf/dkim/dmarc or any of that. And I can tell you, yes, the megacorps still send the most spam.
Almost all my spam, similarly, is "legal spam". Any time you interact with any service you end up "agreeing" to be added to potentially hundreds of different mailing lists, and the "unsubscribe" link cheerfully tells you that you've been removed from Marketing Emails on Weekdays Odd Months Just For Accessories, but not the other ones. I have never in my life wanted to subscribe to anything.
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.
Ah. So DMARC can actually makes things less secure? Can't say I'm surprised. I've had spf and dkim signing set up since ~2017. I only set up dmarc in 2024.
> 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.
Lots of inferences there, but presuming Spamhaus isn't already blacklisting your IP address then that's additional evidence you don't have a vanilla residential IP address.
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.
I expect someone attempting to make money by sending mass emails does not have the ability to create DNS records or figure it out alone
It's gotten even easier with newer tooling. Stalwart will manage most of it for you if you want for example.
No AI required.
In the office, Google or Microsoft, it's been copy and pasting a couple records into your registrar for like four years. Not sure how admins are still messing this up even with AI now, haha.
We've allowed them to grow this way by preferring convenience.
I assume you don't mean you're receiving a large volume of spam from @amazon.com or @microsoft.com email addresses?
Survivorship bias
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/
can i get recruiter list spam punished?
I've published a DMARC record that basically says to ignore DMARC and do nothing. I wonder if this will be enough.
I have no plans to ever change from none.