4 ms·
I understand this guy's frustration but this: > And this is happening after SPF, DKIM and DMARC provided a solution to the spam problem. is just wrong. Tons o
by Analemma_ 4y ago
I understand this guy's frustration but this:
> And this is happening after SPF, DKIM and DMARC provided a solution to the spam problem.
is just wrong. Tons of spam comes from servers with SPF, DKIM and DMARC
now. It stopped being a trustworthy signal of not-spam many years ago.
- ed_mercer 4y agoThat explains why I'm starting to receive spam in Outlook again... Guess it's a cat and mouse game.
- cge 4y agoHaving SPF and DKIM implemented says little about the email coming from a server. But it should allow filtering of spam from domains based on the history of emails received from them, and how users have interacted with them. They should allow the keeping of trust scores at a domain, rather than server or IP, level, and that should be feasible with even relatively few emails involved. Yet Google and Microsoft don't do that. I can send replies on a personal domain and server to people I've talked with often in the past, and quite often they'll go to spam with Gmail. I can send emails to universities running Office365 from the domain of a prominent university, and sometimes they'll go to spam. I've seen Google and Microsoft email at universities have emails from mts-nature.nature.com, Nature's manuscript tracking system, something no academic would want sent to spam, get sent to spam. SPF and DKIM should allow these things to be rather simply avoidable. But they don't.
- billpg 4y agoSPF et al are not anti-spam but anti-impersonation.