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.
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.
Are you suggesting that hosts along the path besides the sender and receiver mailserver are interpreting it and filtering? I'm not being glib, I just can't think of how what others do changes what my mailserver sees.
I mean, I get the whole "herd immunity" angle so that if everyone requires spf pass then spammers will start using spf. But this doesn't change anything about the ratio of megacorp spam versus independent spam.
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?
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.
> 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.
> Residential IPs seem to be the most trusted these days
Oh, I see we've got a stand-up comedian in our ranks. ;)
Most trusted ? You mean aside from all those residential IPs we see in our logs on a daily basis with the inevitably infected machines behind them taking part in DDoS attacks and other shenanigans.
Spamhaus and others maintain databases of residential IPs and whilst it doesn't get used for auto-blocking, most sensible organisations will reduce the trust score by a large chunk if its a residential IP.
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?
There are SMTP relay services that are cheaper than a reliable VPS, that will manage monitoring the sending addresses for appearance in blocklists and do the work to fix that so you don't have to. I still send direct (my home account is in an almost-commercial plan with an ISP that takes things seriously including IP reputation), but if that starts to fail I'll move over to one of those services rather than using a cheap VPS for sending. Maybe more than one for resilience.
A reputable and conscientious VPS provider will rigorously block outbound port 25. Some of those allow you to request outbound port 25 on a discretionary basis. If they're quick to respond to complaints then their address blocks should be pretty clean. You can always lookup your assigned address in various blacklists and roll the dice again on a new instance if you get a bad one. Ditto if you find Google or Microsoft doesn't like it, either.
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.
If the ISP is not permitting you to configure the PTR of "your" addresses, then are they really your addresses?
Spamhaus specifically recommends a "branded" name. Deferring to the (recognizable as such) ISPs defaults, and thus raising the suspicion of attempting to wash all customers together is not terribly useful with other antispam systems either.
On residential, they're never "your" IP address. The one assigned to me is 'mostly static', but they did notify me that the IP address they'd assigned to my connection was going to change, which it now has.
Given my ISP has been kind enough to allow 'bridge mode' for my router, and outgoing traffic on port 25, then maybe I could ask them to change the reverse DNS lookup as well - feels like it may be a bridge too far, all I can do is ask though.
Separate, but related, I host email for multiple domains on this connection, so the reverse lookup would only be relevant for one of those domains. I'm not sure if there are additional ways around that, but haven't thought in too much detail about it yet.
No, your ISP’s IPs are not “really your addresses”, and precisely no one claimed they were. This is a workaround so that someone can send emails out. Most people don’t have their own PI IP space, especially these days.
Yeah, it does have a reverse DNS that resolves to the ISP, and whilst looking at the article I had the same thought. Might see if I can implement that sooner rather than later.
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.
This is not why these techniques are useful, though. They reduce plausible deniability and laundering-by-mixing. Because once you connected your unique (domain) name to your stuff, there is no "oh, it must have been that other customer that used that address before me" excuse any more. If everyone plays nicely and identifies their systems unambiguously, the question of who is responsible is clear. And thus, the reaction after detected misbehavior can be immediate and decisive.
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.
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.
You can also reach out to sender support through the same, and they are ~reasonably responsive (though very clearly outsourced / limited power). If it's a lingering MS block they should be able to override it. I've had luck in the past (though this was on behalf of a notable tech company, I don't know that the support people cared at all about that fact).
> 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...
Check the headers of messages received via Microsoft; they don't even care what your policy says and check the alignment and validity of your SPF/DKIM configuration just the same.
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.
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?
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.
> Most of my spam is through Google, Amazon and Microsoft
Survivorship bias
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.
Nothing you said negates my point
You do not exist in a vacuum.
Are you suggesting that hosts along the path besides the sender and receiver mailserver are interpreting it and filtering? I'm not being glib, I just can't think of how what others do changes what my mailserver sees.
I mean, I get the whole "herd immunity" angle so that if everyone requires spf pass then spammers will start using spf. But this doesn't change anything about the ratio of megacorp spam versus independent spam.
Can you be more explicit?
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 get plenty of spam from @gmail.com addresses, yes
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.
> 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.
I’m surprised your emails have ever gotten through if they’re coming from a residential IP. That’s definitely not considered good practice.
Residential IPs seem to be the most trusted these days, other than those, ironically, owned by the handful of big tech companies.
Email should be able to be run from anywhere.
> Residential IPs seem to be the most trusted these days
Oh, I see we've got a stand-up comedian in our ranks. ;)
Most trusted ? You mean aside from all those residential IPs we see in our logs on a daily basis with the inevitably infected machines behind them taking part in DDoS attacks and other shenanigans.
Spamhaus and others maintain databases of residential IPs and whilst it doesn't get used for auto-blocking, most sensible organisations will reduce the trust score by a large chunk if its a residential IP.
Not being able to send mail at all from a residential IP is bullshit, though. Increase its spam score, but let it through.
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?
There are SMTP relay services that are cheaper than a reliable VPS, that will manage monitoring the sending addresses for appearance in blocklists and do the work to fix that so you don't have to. I still send direct (my home account is in an almost-commercial plan with an ISP that takes things seriously including IP reputation), but if that starts to fail I'll move over to one of those services rather than using a cheap VPS for sending. Maybe more than one for resilience.
A reputable and conscientious VPS provider will rigorously block outbound port 25. Some of those allow you to request outbound port 25 on a discretionary basis. If they're quick to respond to complaints then their address blocks should be pretty clean. You can always lookup your assigned address in various blacklists and roll the dice again on a new instance if you get a bad one. Ditto if you find Google or Microsoft doesn't like it, either.
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.
My ISP does block outbound port 25 by default, I specifically asked for it to be unblocked for me, and they obliged.
My residential connection has working reverse DNS, although I fail to see how this has anything to do with spam.
Most ISPs have a PTR that also resolves to the IP; try using the one they chose for you (cust-462728.atl1.ispname.com) in your HELO.
If the ISP is not permitting you to configure the PTR of "your" addresses, then are they really your addresses? Spamhaus specifically recommends a "branded" name. Deferring to the (recognizable as such) ISPs defaults, and thus raising the suspicion of attempting to wash all customers together is not terribly useful with other antispam systems either.
On residential, they're never "your" IP address. The one assigned to me is 'mostly static', but they did notify me that the IP address they'd assigned to my connection was going to change, which it now has.
Given my ISP has been kind enough to allow 'bridge mode' for my router, and outgoing traffic on port 25, then maybe I could ask them to change the reverse DNS lookup as well - feels like it may be a bridge too far, all I can do is ask though.
Separate, but related, I host email for multiple domains on this connection, so the reverse lookup would only be relevant for one of those domains. I'm not sure if there are additional ways around that, but haven't thought in too much detail about it yet.
No, your ISP’s IPs are not “really your addresses”, and precisely no one claimed they were. This is a workaround so that someone can send emails out. Most people don’t have their own PI IP space, especially these days.
Yeah, it does have a reverse DNS that resolves to the ISP, and whilst looking at the article I had the same thought. Might see if I can implement that sooner rather than later.
Yeah, well, you can’t always get what you want.
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.
This is not why these techniques are useful, though. They reduce plausible deniability and laundering-by-mixing. Because once you connected your unique (domain) name to your stuff, there is no "oh, it must have been that other customer that used that address before me" excuse any more. If everyone plays nicely and identifies their systems unambiguously, the question of who is responsible is clear. And thus, the reaction after detected misbehavior can be immediate and decisive.
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.
It is pretty straightforward. If you can learn regex or cron expressions, you can learn their meaning and format.
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 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.
HELO hostname / banner is a little tricker
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
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/
Make sure to register on their SNDS and you might be able to find the issue? https://substrate.office.com/ip-domain-management-snds/snds
You can also reach out to sender support through the same, and they are ~reasonably responsive (though very clearly outsourced / limited power). If it's a lingering MS block they should be able to override it. I've had luck in the past (though this was on behalf of a notable tech company, I don't know that the support people cared at all about that fact).
> 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...
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?
Being picky about what is sent in HELO/EHLO seems like useless nitpicking toil that will not prevent any spam.
Not by itself. But it solves the "that was not me" dance: It was you. Your zone points there = your responsibility!
>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.
I have no plans to ever change from none.If you have SPF/DKIM active this setting will void them.
Check the headers of messages received via Microsoft; they don't even care what your policy says and check the alignment and validity of your SPF/DKIM configuration just the same.
This is just not correct.
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.