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.
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.
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.
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.