zrepl VS Mailpile

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.

Have a look at mailpile if you are after a web interface; or, the ever-dependable Thunderbird if you are fine with a desktop application.

mailpile seems good, but I would encripted things and besides this it is well mantained? The dockerfile here is old https://github.com/mailpile/Mailpile. By the way I tested a container, this rroemhild/mailpile, and it seems easy and with a good interface.

Mailpile supports theming. https://github.com/mailpile/Mailpile/wiki/Themes

Take a look at Mailpile.

Mailpile.is comes to mind. Their Twitter account is inactive since 2018, but they did fix some things on Github in November of 2020: https://github.com/mailpile/Mailpile/

> Email is not decentralized. It relies on the central authority of domain registries.

By that definition, almost every chat app is centralized, especially if you include the step of downloading it over HTTPS. In any case, it would be possible to further enhance email using something like SMTorP so that .onion addresses are used instead.[0]

> And then if you do decide that whatever encryption scheme you've chosen is right for you, there's no guarantee any significant mass of people supports it.

The same is true of any system which is proposed as an alternative to email. Admittedly it will be difficult for a UI to convey the security properties of messages when you are interacting with users whose email clients don't support the recommended extensions, but there is always the risk that a recipient will copy-paste the plaintext of your securely sent message into an unsecured channel.

[0] https://github.com/mailpile/Mailpile/wiki/SMTorP

For PC : Thunderbird or Mailpile