zrepl VS docker-mailserver

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.

I can recommend Docker mailserver (it also works with Podman). It is already pretty lightweight but you can even make it lighter and it has an active community as well as regular updates.

https://github.com/docker-mailserver/docker-mailserver https://docker-mailserver.github.io/docker-mailserver/latest/ https://www.programonaut.com/how-to-host-a-mail-server-with-docker-for-free-step-by-step/

Use https://github.com/docker-mailserver/docker-mailserver or mailcow . They both provide reasonable default setup for spam detection and even UI for adjusting settings.

" this docker based mail server looks pretty legit https://github.com/docker-mailserver/docker-mailserver "

Check https://github.com/docker-mailserver/docker-mailserver It has almost everything in a single docker image. Email is not the easiest to implement with container(s), but that project has managed it.

I set up docker-mailserver[0] Monday in ~6 hours, most of which were me trying to be fancy using podman instead of docker and dealing with SELinux. But then again I did choose it over mail-in-a-box for just that level of customization. Obviously I can't tell how reliable it will be in the long run yet, but since it's using the classic Postfix/Dovecot stack I expect it'll be pretty stable

[0] https://github.com/docker-mailserver/docker-mailserver