773
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.
this post was submitted on 16 Aug 2026
773 points (97.9% liked)
memes
22364 readers
2662 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Frankly, I'm rather shocked it hasn't happened by now.
We've tried to bandaid over it with various weird things, but fundamentally SMTP is just weird.
I could easily imagine a domain having some SRV record to advertise "hey, I support NeoSMTP", and peers switching to that instead, possibly pinning on successful NeoSMTP negotiation.
Get rid of a lot of the relaying which has not been useful in modern times and only a liability, and perhaps offer an https option to be less likely to be blocked (a TXT record to indicate url, and a node could declare their NeoSMTP entry point as https://mail.server/NeoSMTP/ or whatever works for them).
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.
Jmap is also an emerging standard. https://jmap.io/
Looks like replacing IMAP rather than SMTP, which is significantly less thorny.