Maddy: Composable all-in-one mail server
maddy.email
Maddy: Composable all-in-one mail server
1–10 of 122 posts
Re: Maddy: Composable all-in-one mail server
#2Re: Maddy: Composable all-in-one mail server
#3Maddy (sqlite) + https://litestream.io/ might be simple enough to get right.
Re: Maddy: Composable all-in-one mail server
#4I used to run my own mail, but gave up due to the risk of me screwing up backups/restoration. Maddy (sqlite) + https://litestream.io/ might be simple enough to get right.
Re: Maddy: Composable all-in-one mail server
#5I used to run my own mail, but gave up due to the risk of me screwing up backups/restoration. Maddy (sqlite) + https://litestream.io/ might be simple enough to get right.
Mail is one of the easier things to backup IMO. It's just a directory if you use Maildir. Just tar it up with other important stuff on your filesystem you probably also want to save. No need for fancy "streaming SQLite replication."
What replication lag could tar-on-a-cronjob reasonably achieve for a moderate 5GB mail store?
Even tar'ing isn't trivial: I've seen casing of people having missed preserving file permissions, making restoration difficult.
Re: Maddy: Composable all-in-one mail server
#6[edit] I found the FAQ:
> It was intended to be one but developers quickly acknowledged the fact email cannot be easily abstracted behind some magic.
So it can't be as simple as caddy, but they're doing their best. :)
Re: Maddy: Composable all-in-one mail server
#7I've got to write a longer article about this, but self-hosting email is incredibly liberating. I now own my entire digital identity. I can work on open source projects with developers around the world completely while relying only on my own capabilities.
Re: Maddy: Composable all-in-one mail server
#8Earlier quoted context omitted.
Mail is one of the easier things to backup IMO. It's just a directory if you use Maildir. Just tar it up with other important stuff on your filesystem you probably also want to save. No need for fancy "streaming SQLite replication."
I recall Litestream citing a ~3s streaming replication lag. What replication lag could tar-on-a-cronjob reasonably achieve for a moderate 5GB mail store? Even tar'ing isn't trivial: I've seen casing of people having missed preserving file permissions, making restoration difficult.