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

Your VPS / ISP better have a good reason to "deplatform". If you're really worried, use two different ones.

Also, people have more problems with being "deplatformed" by Google, often with no reason given, and with no way to communicate with a human about the issue. Look it up. I'd be more worried about that.

DNS isn't a single point of failure. Nor is email when it comes to reception (that's what backup MXs are for). If you need redundancy when it comes to being able to fetch email, you can easily have the primary MX also forward to mailboxes on another host so you have two (or more) copies of everything. None of this is all that hard, and people have been doing it for ages. Give it a try :)

1) To quote myself: "I'm not saying email self hosting should not be done, I just say a bit of planning should be done". I self host my email. I just meant it is not "just rent a VPS and slap some docker containers on it"

2) I never said receiving email is a SPoF

3) Please explain in detail what do I do in order to keep receiving emails using "me@johndoe.com" after johndoe.com gets undelegated. I do not know of a way and would very much like to know. If there is no way.. It is a SPoF.

edit: formatting