Re:Email Authentication: A Developer's Guide
by Avamander on Friday August 25, 2023 @06:27PM
(#37267794)
> Microsoft, particularly, uses UCEPROTECT as a blacklist source, and that particular company will blacklist and entire ASN if they receive too much spam from a particular IP address block (that doesn't get resolved in time)
They absolutely do not use that crap.
Re:Email Authentication: A Developer's Guide
by charamis on Friday August 25, 2023 @08:00PM
(#37268539)
Glad you're pointing it out. I still have problems, indeed, having my emails flagged as spam when sent to outlook.com. On gmail.com they go straight to the inbox.
If I understand correctly though, I should have to set a reverse PTR record in the case of setting up my own mail server, right? And I should configure it on the mailserver's side, correct? That's not my case though, I'm just using a custom domain with the MX records pointing to the mail service that I'm using.
I'll just wait a few days cause the domain is new and I guess that's the reason outlook.com flags it.
Re:Email Authentication: A Developer's Guide
by nicolast on Saturday August 26, 2023 @03:53AM
(#37270697)
Exactly: a non-blacklisted IP with good reputation, correct mailname and valid PTR record is the foundation, ideally augmented with SPF. I've been running an e-mail service without DKIM and DMARC for many years without any delivery issues, only adding those very recently.
Re:Email Authentication: A Developer's Guide
by Avamander on Saturday August 26, 2023 @04:47AM
(#37270884)
Ideally? No. SPF (or DKIM) is pretty much mandatory for delivering mail.
Furthermore, you need to pick a host that takes action when their IP addresses appear on blacklists. Microsoft, particularly, uses UCEPROTECT as a blacklist source, and that particular company will blacklist and entire ASN if they receive too much spam from a particular IP address block (that doesn't get resolved in time).