We've allowed them to grow this way by preferring convenience.
Survivorship bias
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?
I assume you don't mean you're receiving a large volume of spam from @amazon.com or @microsoft.com email addresses?
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.
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.
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
> 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.
Email should be able to be run from anywhere.
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.
At best residential IPs are in the same category of IPs of the so-called "bulletproof hosts" and similar.
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.
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.
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.
For that you'll need to pick a domain that you don't mind the others being associated with, and having all MX entries be pointing to the sending hostnames for that. Or you'll need multiple addresses and some way to route outgoing mail through the right one.
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?
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).
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...
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.
v=DMARC1;p=none;adkim=r;aspf=r;pct=0
I have no plans to ever change from none.