4 ms·
I suspect it has something to do with Gmail's policy change on nov 2022 when they started requiring spf, dkim, and dmarc. There are probably a ton of misconfig
by frogperson 4y ago
I suspect it has something to do with Gmail's policy change on nov 2022 when they started requiring spf, dkim, and dmarc.
There are probably a ton of misconfigured domains and non-google email servers that interpret the new configurations slightly differently.
- paulgb 4y agoMaybe that's part of it, but to add some datapoints, I've had a bunch of legit email from GMail addresses flagged as spam, and had people tell me that my emails (from a GMail account I've had for ~18 years) landed in spam. (This HN post caused me to check and I found another important GMail-originated message in spam)
- kccqzy 4y agoThat's just because spammers have wised up and started using Gmail itself to send spam, including old established accounts via weak passwords. Those spam would pass SPF, DKIM, DMARC. It would be both inappropriate and probably illegal for Gmail to automatically mark emails sent by Gmail as non-spam.