This Microsoft outage being the last drop in the bucket, I'm looking to get my email/calendar/contacts somewhere under my control.

As I already self-host a number of things (e.g. my Linux ISO collection), and have services exposed to the internet, it would make sense to run it at home.

After all, it's not heavy lifting. It's not hosting 500+ mailboxes for 100+ people. It's just little old me, with a handful of domains, catch-all receiving and a few dedicated sending addresses.

However email is a bit more mission critical than my smarthome control or self hosted LLMs. Downtime could be critically bad, and I still don't trust my home setup to be truly 99.999999% available.

I don't mind paying for a service but if I do I'd prefer something European, given I'm based in the UK (and otherwise am an EU citizen).

I'm really curious how y'all solve it. I guess I'm interested in some kind of hybrid solution where there's my own server and a hosted service, latter which acts as a backup solution, but still fully synced, so if my internet or power goes out (or my server goes down), I can still get mail sent and delivered.

So I'm not only just interested in the stack you run for email but the entire infrastructure, especially if you've solved this sort of off-site fallback service.

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 15 hours ago (1 child)

I solved it with mailcow dockerized and an LT2P service for a non residential static IP. Works great, regular updates & patches and super reliable.

You can set up a fallback using their supplied script to make a cold backup in the cloud if you need to, but I've never had to bother. I also use another of their scripts to properly dump the db and files to my NAS and then I use borg to copy all the things to Hetzner.

  • source
  • hideshow 1 child comment
  • [–] [S] 1 point 15 hours ago

    I've been debating between Mailcow and Stalwart (or Maddy), as well as Modoboa.

    The fallback isn't a cold backup though - it would be the same server with the same data (ideally) being made primary in case my own server is down.

  • source
  • parent