860 words
November 18, 2023
5 minutes read
Privacy and security implications of selfhosting your emails
Introduction
Security implication of selfhosting your email
The first point is that it is not easy to do, even with the new all in packages like mailinabox you still need some understanding of what you are doing. Then, even if this works, if you forget some basic configuration of your domain or to update your server you risk being the source of some spam emails and having to restart everything from nothing having to get a new ip and domain.
The second is that if you are using said packages and not installing everything by yourself it is hard to maintain. You need to check your domain reputation, your ip reputation, that everything is up to date and well configured…
There is also no E2E encryption by default, so if you want to encrypt your emails you also need to use PGP with everyone. While it is pretty much the same with “privacy respecting” email services there is still E2E encryption protocols between their users and as more and more peoples are using proton in the community it is easier. These services also have encryption at rest using your PGP key which I haven’t seen offered in any email selfhosting solution.
Privacy implication of selfhosting your email
Maybe you are telling yourself “yes but I can encrypt my disks”. Without even talking about cold boot attacks (because it’s not like you will keep your email server offline) the problem is that every email going in and out of your server is directly connected to your server. It mean that you are unique on the network and can be easelly wiretaped. More than your mail being wiretaped in mean that every connection made to your server would be too, including yourself fetching your mails.
Privacy implication of using a “privacy respecting” email provider
The second one is metadata, on the internet every packet needs some informations to go from point a to point b. This is the case for you emails with the header not being hidden when using PGP but also for your IP adress being sent to the server on your access. While proton always had (as far as I can remember) a Transparency page stating that they would give out everything they could (pretty much only IP adresses and recovery informations) to a Swiss Court legal request it maybe was not as clear as people would have liked which make a lot of people loose trust in Proton.
The thing is, every point I made here is also true for selfhosting your own email server if not even more true. Getting your IP adress is easier because you are unique on the network. Getting your email metadata is even easier it just needs an access to your physical server or router.
Conclusion
As always, I am more than happy to discuss my thoughts with anyone. If you have any arguments that I may have missed (which I’m sure there are plenty, as I wrote this in under 15 minutes after reading another Reddit post), I would appreciate hearing them. Thanks for reading:)