Having a decent spam filter is nice (I've had loads of false positives in things I've tried elsewhere).
There is the idea that google/MS could just fall off the face of the earth, and then I look pretty stupid having loads of things connected to that account. That bothers me enough to where important things get thrown onto an email adress I'm pretty sure won't disappear for a while.
As to reading my mail... robots are reading my mail. This is a pretty valid "Chinese room" in my opinion. Nobody's actually understanding my mail, what do I care. The ads are usually pretty relevant to things I need though (I've clicked on more of the text ads than I would ilke to admit).
Pick a random (not broken) piece of hardware. Install debian stable on it with base install + postfix + roundcube. Configure: grey listing, black listing, and auto-update (relative easy, and there is a bunch of tutorials if needed). Leave it alone until once every 2-3 year where it will need a aptitude update, aptitude upgrade. It will run as long it has power and network connectivity. If you are a company and either the power or network is down, email is unlikely to be high on the priority list.
Spam: ~0. Might get one every full moon or so. After 5-10 years it might get a bit worse, but adding SpamAssassin tend to get rid of it.
As for Chinese rooms, do they leak information? Do they give out mail if asked by someone with money/power? Sure, one can say "I got nothing to hide so what do I care", but then that's what all email then must be. You can never again say: "This email is private and mine. I and only I have control over it". If you are a doctor, lawyer or any person dealing with private information, then it mean that any email given to you are defacto public.
That is true. However, Running an email server properly /is/ hard.
Security, maintenance, patching, journaling, litigation holds, bouncing, ssl/tls, dkim, etc.. It's not exactly as simple as apt-get install teh-emails
SSL/TLS require two additional step. You go to CAcert and add a very simple setting in postfix. If you uses webmail, you can just plug this in and use it there and forget about ssl/tls in postfix.
DKIM is neither required or useful in most use cases. If your a bank with online accounts, then you should use it, but then you really MUST not outsource your email. They should have a sysadmin that can maintain a secure email infrastructure, in the same way that they got a professional installing a lock and alarm on the door. Get a consultant, ie a professional doing the installation if you don't have a sysadmin.
As for journaling (default from the file system) and bouncing emails (defaulting to the user who sent the email), both are given free without any configuration.
Litigation holds, ie concerns about how to comply with being legally forced to retain and hand over emails to the government. That is a bit out of scope for most companies and users, but if you are concerned about this see above statement about DKIM.
So ye, for users and 99% of companies in the world it is indeed as simple as doing an apt-get install postfix and follow some simple tutorial in configuring grey listing, black listing subscription and adding a dns entry.
Hopefully the tutorial mentions how to make sure relay is off. And it explains how to configure those magic auto-updates. And it covers amavisd and/or other anti-spam features. Also, I hope it at least mentions some basic security for the system.
My point is and stands: it is not easy to properly run an email server. Simply running apt-get install postfix does not a properly configured email server make - no matter how easy it is. This fact makes hosted solutions, run by people dedicated to running that type of stuff, compelling. Especially for those "99%".
auto-update is as simple as apt-get install unattended-upgrades.
greylisting is: apt-get install postgrey
blacklisting is the only real "slightly" iffy area, because there aren't a obvious one guide to do it. It is however a very simple way of installing it once and not touching it again. (http://www.howtoforge.com/block_spam_at_mta_level_postfix) looks to be a old guide, through there might be more current methods out there.
As for system harderning... I have yet of hearing a single person having a stable debian installation getting hacked (if they update/autoupdate!). basic security for the system should be left to default, so long one do pick a decent password (or avoid installing ssh).
Its like being a online shop with only paypall. Its an easy method to go bankrupt fast.
It commonly received as a surprise when I talk about it, but once you give away your email to be handled by someone else, the emails are no longer private. If you give it to google, google then owns it. If you give it to Microsoft, its Microsoft that’s own it. Why are people acting so strange to the idea that if you give something away, its not longer in your control?
Running a email server is not hard. if its a company, running a email server + webbmail is as hard as installing two extra packages in debian and doing a single dns change. If you don't have a server, buy a old laptop/media station. Its email, its not going to demand processing power beyond simple spam filtering.
On that note, wonder if my phone can get postfix installed...