Redundancy redundancy redundancy. See e.g. Unison, rsync, sanoid or https://syncthing.net https://syncthing.net - runs on anything, does a good job. > You stil

Redundancy redundancy redundancy. See e.g. Unison, rsync, sanoid or https://syncthing.net https://syncthing.net - runs on anything, does a good job. > You still give access to your data to a company, which controls software updates and the EC2 proxy (in this case). Because you read all code changes every time you `pkg upgrade` or `dpkg dist-update`. > Many home ISPs have shitty upload connectivity, so your email won't work that well on the go. Is that really an issue? I probably use <100kB personnal email per day anyway. Even in the US, 100kB/day upload is not unheard of. Also, the "on-the-go" issue is DL speed: from your device to your server. How long your server takes to send the mail is mostly irrelevant - instantaneous transmission should be done by phone. > Internet and power outages mean you won't send or receive any email. More comments around here about sending servers that MUST retry, and fail only after a few days. > You lose the knowledge email providers get from scale, including ever-evolving spam filters, and a guaranteed clean outgoing IP. That could be a real issue, but the ever-evolving filters at my ISP clearly can't spot (nor stop) the spam I receive anyway. The outgoing IP shouldn't be a problem if you've registered it in your DNS, and it matches the SMTP or whatever subdomain.