DKIM, DMARC, SPF, rDNS/PTR, EHLO… all correct and verified in the email “original source,” BY GOOGLE. Still goes to SPAM folder because **** you, apparently. I hate Google.
DKIM, DMARC, SPF, rDNS/PTR, EHLO… all correct and verified in the email “original source,” BY GOOGLE. Still goes to SPAM folder because **** you, apparently. I hate Google.
Oh, there have been plenty. The issue though is the classic “make a better standard, and now you have N+1 standards”.
Everything is wrong with SMTP. It’s still in use because it’s supported everywhere. Anything that wants to replace it either needs to entirely replace it in one fell swoop, or it needs to be backwards compatible.
The result is that occasionally a new thing comes up, a handful of people try it but there isn’t critical mass to make other features really useful so it fades.
It’s fine if Legacy email Remains the thing that could spend whereas email 2 can be used for actual correspondence between people
Hence my references to DNS records in addition to MX to determine if an endpoint is SMTP only or better. For compatible interop.
But that’s the thing: now you haven’t made an email replacement, you’ve made email more complicated.
If you’re backwards compatible you need a very compelling feature to get people to switch, and using the feature is limited until people switch.
That’s how we added spf, dkim, dmarc and starttls.
The biggest difficulty is managing the layers of compatibility.