777
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
777 points (97.8% liked)
memes
22390 readers
1931 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
I might be out of the loop on how email works, but doesn’t it hop between several other email servers on its way from Alice to Bob (and at least some of it must still be unencrypted)? If so and given google’s scale you could probably just assume that even if they’re not your inbox they’re going to be at least handling many if not most emails along the way.
Depends. Usually not. It hops from your computer to your email provider which then looks up the server of the recipient and sends it there. The recipient's server might send it on internally and in big installations probably does so.
It is theoretically possible that one of the involved parties has a third party authorised to accept mails on their behalf in case of outages. I don't believe that is very common nowadays. It's much more likely that your provider will keep the mail for a few hours to days when it can't reach the recipient.
But ideally only your provider and the recipient's provider can read the mail with all connections in between being encrypted. There's just no guarantee that all paths are encrypted. But I think nowadays that is much more likely than it used to be, thanks to Let's Encrypt.
Now, if you don't want any of the servers to be able to read the mail you have to encrypt it with something like GPG. But for that to work you need the recipient's key. But hardly anyone uses that. And it only encrypts the content of the mail. Not the metadata.
If you control the DNS and the mail server, you get to decide where it goes. However, if any senders or recipients are on gmail, Google basically has all of those emails' content.
That was the theory, nowadays moest email goes from google or microsoft to google or microsoft. At least 99% of the rest goes directly from the senders provider to the recipients provider. Afaik none of the larger providers still accept non-TLS connections.
Yeah that’s what I’m saying. Even if you’re not using one of the big providers there’s a good chance they’re going to be at least handing it on its way to your self-hosted inbox, and its contents are unencrypted while they’re handling it (unless you encrypt the contents yourself). So there’s not much benefit to self hosting email if your goal is to keep your data out of big tech’s hands (and if that is your goal, don’t send anything important with email)
If neither the sender nor the recipient is hosted by google the email is never going to reach googles servers. It will go directly from the sender provider to the recipients provider.