> My solution was to set up the Proton Bridge in a VM on my NAS, then used rinetd to forward incoming connections on the IMAP and SMTP ports to the bridge (which only listens on 127.0.0.1). I then set up tailscale on that box and on my phone; with that, I could connect any Android email client (I like FairEmail) to my Proton account. I was also accessing it from Linux using Claws.
That sounds like a big fraction of the complexity of a self-hosted setup.
Every time email is discussed here, people familiar with self-hosting point out that it’s nearly impossible to get Gmail to not flag your mail as spam. (I have no idea, but it’s a recurring theme.)
Google and Microsoft both were easy to deal with for me, and I even have a domain with a newer TLD (bar). DKIM+SPF is all it seems to take.
My host was also on Spamhaus' blacklist, but no one else's. I'm not sure it mattered, but they were nice enough to remove it and reply with a snippy email about how reluctant they were to do so. No surprise there, folks at Spamhaus would block their own mother.
Self-hosting email is just not that hard. It does take a bit of work, but that's why it's called DIY.
It was easy for you because you were lucky. My server has SPF and DKIM and DMARC, à grade of 100% on mail-tester, and was on zero blacklist.
I NEVER could send an email to a Microsoft email address and have it end up in the inbox. It was systematically flagged as spam. Microsoft's answer was to subscribe to some shitty, shady third party service to maybe, MAYBE change my reputation.
They're probably talking about True Scotsman's Self-Hosting whereby your MTA is not configured to go through someone else's SMTP forwarding host, but is slugging it out on its own, sending mails directly to target mail domains, and is sitting on an IP address that doesn't have reputation for sending mail. Self-hosting like it's 1992.
The wise man accepts that using a reputable forwarding host for sending is still valid self-hosting.
I use Mailgun, but all the big name providers should be pretty much the same for low volume sending. Unfortunately my 9 year old VPS IP was already on a spam list when I got it, not sure if it falls off eventually.
Nope! I use my local Big ISP, and have for 13 years.
To quell your worries about a prospective service, you can try them without rushing to relying on it. Just point a mail client at their SMTP host and test for a while.
I imagine if you have your DNS records set up strongly enough it would warm up to your MTA's IP address rather quickly, but I have not tested this for a few years now.
Yes and the same with Microsoft's consumer domains like live.com, outlook.com and hotmail.com . It's a total pain, they don't trust you unless you send a lot of email. Even if you never send any spam.
The plural of "anecdote" is not "data", but I'll throw my hat into the ring as not having deliverability issues with Gmail. I can't attest to how easy or not it might be for someone who hasn't been running a mail server for nearly 20 years, though.
That sounds like a big fraction of the complexity of a self-hosted setup.