[johnklos]

The true value of a company can be measured by our ability to communicate with them. If we can't communicate except after public outrage, then what does that say about the company?

Here's a genuine question: is Proton Mail the least shitty of companies that provide email services?

I self-host email and will continue until I die. But for others who need a company to do this for them, is Proton Mail the least shitty of options? Does this change the evaluation? I'm genuinely curious about the opinion of others here.

[crossroadsguy]

To answer your question, from my limited experience: no.

There are better or less shitty companies like Fastmail, Runbox (tried them), even Purelymail (but 1 or 2 people setup), Mailbox (shitty support, solid setup; I am a customer), Migadu (good name, I have never used them), there's Tuta (but somehow they seem off to me; like Proton they also do not allow IMAP/POP - Proton allows with some circus), MXRoute has good name at places like LET forum. There's even Zoho if you just a mail service (but then if you use Zoho then only reason to not use Google or MSFT will be cost or just the middle finger :D) … and many more.

So there are options.

PS. as per self hosting email - I can't self host my seedbox properly on a VPS, I don't think I should even try email :)

[cedws]

Not allowing IMAP/POP isn’t just for the lulz, it’s not compatible with the encryption architecture Proton uses, which is kind of the selling point of the product. You can either have your emails encrypted at rest with your key OR you can have plain IMAP/POP without a bridge client, you can’t have both.

[traceroute66]

> The true value of a company can be measured by our ability to communicate with them.

True, but sadly too many people don't care.

Look at how many people will happily throw $$$ per month at Claude when it is basically absolutely impossible to contact a human being at Antrhopic.

> is Proton Mail the least shitty of companies that provide email services?

Tutanota could be worth a look.

[gond]

I self hosted for 20 years, worked flawlessly, gave up because of security concerns. I would like to go back to it.

Question: How do you manage the security on such a box? Is there any simplification I missed?

I couldn’t keep up with it. So many patches, unrelated to mail, broke something in the stack, bringing the server into a critical state. Often, I had to lock down everything before going up again, consuming a day’s effort or two. These were two days without mail.

[jegp]

What's your stack? After reading this, self hosting suddenly appeals to me.

[_kidlike]

forget about self hosting email... I tried it for years, and even if you get it working (needs months), it will eventually stop working again. The problem is that in order to get the big boys to accept you as an email provider, you have to jump through infinite hoops, and be treated like a criminal and/or scammer in the meantime (or at best a business that is trying to send newsletters). You will never get a human to talk to, it's just an infinite loop of automated processes.

Anyway, the problem is "trust" which boils down to IP reputation. And since we are all still on ipv4, your IP was reused. Which means you need to spend months cleaning it. And you won't have a guarantee that you won't lose this IP in the future.

[BLKNSLVR]

Not who you asked, but I self-host some non-critical mail domains using Mailu[0], which is a set of docker containers. It's been fairly low maintenance. Ease of setup depends on your technical knowledge, but if I can do it, and you're on HN asking the question, you'll probably manage.

[0]: https://mailu.io/

[johnklos]

I'm still running Sendmail on NetBSD, the way I've been running it since the '90s.

You'll find plenty of people telling you to not do it, but they mostly seem to think that others shouldn't do things because they can't.

The biggest problem with self-hosting email is deliverability, and it's easily handled by smarthosting through a reputable service, so anyone who says it can't be done hasn't really thought things through very much.

[yogorenapan]

I've been self hosting my email for a couple years. Currently using mox https://github.com/mjl-/mox I'd avoid popular server providers like Hetzner or DO. Lots of abuse there so you might get dropped. https://www.eth-services.de sponsors mailcow and has been pretty reliable

[seszett]

OpenSMTPd + Dovecot is extremely easy to setup and maintain.

For my parents, I registered a domain on OVH and they use the free email accounts they come with. So that's an independent, ready to migrate, email account for about 8 euros per year.

[thr0w4w4y1337]

So, now you have to worry about your VPS/Internet provider deplatforming you. Or about your domain name being seized. And spam filtration, backups, redundancy...

I'm not saying email self hosting should not be done, I just say a bit of planning should be done.

DNS seems like the most annoying part, it is SPoF by design. The problem can be mitigated, but seems like cannot be solved. For example, owning multiple domain names in multiple jurisdictions. And round-robin them. You cannot eliminate SPoF for any one specific service you want to login using email. But you won't lose access to everything at once.

Edit: P.s. At the same time, owning your domain for mail seems to be one of the most impactful things to do to reduce digital serfdom. Banned at *mail? Just switch those MX records and go on.