zrepl VS maddy

Lastly there is zrepl. This is an automatic snapshot creation, pruning and replication daemon. It lets you automate the creation of ZFS snapshots at specific intervals, apply a retention policy to them, and replicate them out to a remote system with ZFS, like a NAS with TrueNAS on it.

I run it in a FreeBSD jail and take frequent ZFS snapshots using zrepl. I’ve had to restore after failed updates and it worked flawlessly.

As others have noted, I use syncoid but zrepl is an alternative that could be considered.

I’m going to throw out Zrepl again because it’s amazing: https://zrepl.github.io/

Current idea: We offer some form of container each other, where we have that zvol mounted somewhere for the replication use. This would mean that I could create an "inside zfs" where I create a filebased zpool. How is performance on a filebased zpool? (Although it is technically not so important that it performs critically, just trying to find the - or one of - "best" ways). Then we would offer each an ssh endpoint into that container (It doesn't have to be ssh, but it is so far convenient to setup and resilient to be open to the public). And my current plan is to use zrepl (https://zrepl.github.io/) to organise replication from my home server to this "inside" zpool.

It's interesting how there is now

* Maddy: https://github.com/foxcpp/maddy

* Mox: https://github.com/mjl-/mox

* and Stalwart

which all see to aim for more or less the same niche. I wonder if we'll see two of those merge eventually.

Does anybody run maddy (https://github.com/foxcpp/maddy) in production or for personal matters?

Yeah, that's a bummer. If you need the docs, then its here.

I've been using maddy mail server as it's quick and easy to setup for over a year now

Both my home server and VPS have unattended upgrades with email notifications about faliures that override do not disturb on my phone. acme.sh has automatic TLS renewal configured with systemd. Maddy mail server itself runs on Docker that is also set up with systemd to automatically restart and start at reboots. When it comes to updating Maddy i just keep an eye on the release Atom feed and change the docker compose file and restart the container.

I wonder how does it compare to Maddy mail server: https://github.com/foxcpp/maddy

If you want to self hosted, I strongly recomend https://github.com/foxcpp/maddy since it's just a single binary to run.

If you still want to do it on your own, there is Go simple mail server - maddy where you can borrow some code or simply use it for the purpose as a IMAP server (I mentioned above, but dovecot as IMAP probably would be the best)

https://github.com/emersion has great libraries related to emails, for example go-imap. https://github.com/foxcpp/maddy is an email server written in Go that you could look into.

Check ready-to-go maddy-SMTP/IMAP server