> I hope you dont also own some google router or even better, "home security" device. This would make it a real pain. I am explaining this to people since the birth of gmail, but no one listens.
> Let me think for a moment, what would happen if google does this to me...
> {lots of stuff that is impossible for the average person}
If you're making the same comments to those who "don't listen" then I can see why. Honestly this comes off more as a gloat post than pragmatic suggestions. And this is coming from someone who used to run all of the above.
The problem is, hosting your own email is actually really hard. Not only much harder to set up than it should be Particularly so considering how old the technology is -- you'd think there would be a GitLab-like solution that is a single package for all the components but no, the end user is left working out what MTA to select, then there is choices between the DB backend, user authentication, POP3 vs IMAP, and possible a web server and web site code itself (if you want web mail as well as POP / IMAP). And that's before you get as far as SSL, login attacks (eg fail2ban), spam protection, setting up your DNS records in the exact combination to protect yourself from being identified as spam and then finally creating your user accounts. And even after all of that, you're still likely to find that Google and Microsoft just assume you to be spam because you're not running on a known trusted service. It's ridiculously hard to get right and that's before you've concerned yourself with the weekly upkeep (security updates, application updates, back ups, etc). There's a reason a great many skilled sysadmins -- including myself -- have given up bothering to run their own mail server. It's easier to trust $COMPANY and make regular backups in case of emergency than it is to run the process in reverse.
...and that's just email. Running your own cloud is also problematic -- not as difficult as email but it is still a considerable hassle and still out of the question for the average Joe.
About the first part of your post, actually there is a single package for all the components: mailu does that in the form of a set of docker images. I've also heard about iRedMail but I don't know it. For the rest of your comment you're right, after launching mailu you still have to configure the DNS and deal with some providers still thinking you're a spammer. But at least you can avoid the painful traditional setup which requires to install multiple pieces of software and configure them to make them talk each other, and mailu also helps you with DNS by telling you which value you should put to have dkim working (and maybe also something else that I'm not recalling right now). Personally the problem that stopped me from having my own mail server was the difficulty to have a reverse PTR record configured for your vps. I was trying to get it with an Oracle Cloud server, but after a rather time consuming process of trying to gather information about this, I found out that Oracle didn't offer the option to have a reverse PTR record.
"The problem is, hosting your own email is actually really hard. Not only much harder to set up than it should be... "
This is the very crux of the problem. We need newer protocols so this is dead easy for anyone to do but I don't see it happening anytime soon. As Google and other Big Tech are on internet standards bodies they'd almost certainty oppose it as a more distributed internet would be bad if not ultimately devastating for their businesses.
Unfortunately, we naively let the Trojan horse into the internet years ago now we're paying a terrible penalty for our foolhardiness.
> Let me think for a moment, what would happen if google does this to me...
> {lots of stuff that is impossible for the average person}
If you're making the same comments to those who "don't listen" then I can see why. Honestly this comes off more as a gloat post than pragmatic suggestions. And this is coming from someone who used to run all of the above.
The problem is, hosting your own email is actually really hard. Not only much harder to set up than it should be Particularly so considering how old the technology is -- you'd think there would be a GitLab-like solution that is a single package for all the components but no, the end user is left working out what MTA to select, then there is choices between the DB backend, user authentication, POP3 vs IMAP, and possible a web server and web site code itself (if you want web mail as well as POP / IMAP). And that's before you get as far as SSL, login attacks (eg fail2ban), spam protection, setting up your DNS records in the exact combination to protect yourself from being identified as spam and then finally creating your user accounts. And even after all of that, you're still likely to find that Google and Microsoft just assume you to be spam because you're not running on a known trusted service. It's ridiculously hard to get right and that's before you've concerned yourself with the weekly upkeep (security updates, application updates, back ups, etc). There's a reason a great many skilled sysadmins -- including myself -- have given up bothering to run their own mail server. It's easier to trust $COMPANY and make regular backups in case of emergency than it is to run the process in reverse.
...and that's just email. Running your own cloud is also problematic -- not as difficult as email but it is still a considerable hassle and still out of the question for the average Joe.