- cross-posted to:
- privacy
- cross-posted to:
- privacy
Unnecessary and deeply concerning bow to the new “king”
Update: position got backed up by an official Proton post on Mastodon, it’s an official Proton statement now. https://mastodon.social/@protonprivacy/113833073219145503
Update 2, plot-twist: they removed this response from Mastodon - seems they realize it exploded into their face!
I see a lot of good discussion here. I’ve been on proton for years now, using my own domain. While true that Andy is one of 5 board members, and it’s a nonprofit etc, these statements are raising hairs on my neck, personally.
Does anyone have a good guide on problems associated with self-hosting email?
Setting up is a piece of cake but getting your emails through spam filters can be a pain.
Have you considered Tuta?
I don’t know any guide, but deliverability is the biggest concern and it may also not be fully under control. Sometimes IP blocks get blacklisted or deranked and your emails end in spam, and you might not even know that.
I think the main difficulty is getting companies like Gmail to recognize your domain as legitimate, as they don’t by default
By default it should be OK. The problem is if your IP was previously used by someone bad before it recycled to you.
But it you have a server for a decade and have held the IP the whole time, you should be OK if you setup your email server correctly (which you probably won’t)
I don’t think I do this like you’re suggesting, but I have my email hosted at opalstack. I’ve been really happy with them. I don’t have a server-side spam solution yet, though. I just set up spam rules on Thunderbird on my local machine.
You’re gonna need a few books and a full time engineer
If you self host it, do it on a VPS so if you’re out of town and it goes down, you don’t lose a month’s worth of emails