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.9% liked)
memes
22375 readers
2673 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 run my own mailserver in docker and it's not so hard! There was some difficulty at the start with mail going to spam, but after a little while "warming up" the IP with usage, it works fine. It's hardest to build an IP's reputation in the beginning because if your mail goes to spam, it doesn't typically lead to healthy conversations that can support it's history.
My trick was to forward all my incoming gmail messages from the account I was replacing into the new server - that way I could receive and reply from the new mailserver if people sent mail to the old one. Once it built up a bit of a history it started working fine, and that took maybe a few conversations over a couple of days.
The thing I have noticed is that you very quickly get destroyed by incoming spam - a more advanced filter is definitely on the list.
One of the problems with self hosting is that a lot of IP addresses have historically been used for spam and still have a bad reputation. If you get assigned one of those IP addresses there's very little you can do about your mails going to spam.
You can request to be removed from the list by SpamHaus. Worked for me. But for still need to make sure everything is set up currently (which is true is tedious) or you go right back onto the list.
I had a small problem with this, but Linode (others do that, too) allowed me to allocate myself a /56 and that solved it. Since IPv6 is preferred if set up - it's the protocol that gets used. And so my reputation problems went away.
Another is most ISPs will put your IP in the PBL so unless you use a relay your outbound email is going nowhere. Google fiber was slow on updating their PBL when they rolled out service in my area so I got to send direct for several months before having to use an external relay.
You can use MXToolbox to check for blacklists on your IP. If you find any, you can submit to each party to get removed. I've done this for a previous company and it was super easy.