sanoid VS Mailpile

I’m on the other end of the spectrum. I like knowing the flags and settings I use to create the pools.

For snapshots and replication take a look at sanoid (https://github.com/jimsalterjrs/sanoid).

I use a combo of PBS and ZFS with Sanoid. The ZFS snapshots are nice because you define it all in a config file with frequent, hourly, daily, weekly, monthly snaps retained however you want. Importantly I use that on the root pool as well as my data pools. With PBS I have a custom retention config and have it backing up VMs and LXCs every couple hours. The PBS dedupe functionality makes it possible to keep full backups going back ages with minimal storage consumption, just the changed blocks. PBS is running inside a VM yes, but it’s storage is on another pool.

[3] https://github.com/jimsalterjrs/sanoid/

No, it's written by the developer of Sanoid and Syncoid. The foremost open source ZFS snapshotting tool. He contributes on this sub all the time.

Hi there! Not so much to answer your questions, but are you aware of Sanoid and syncoid? It does backup and remote Sync in the most seamless way. Perhaps this would solve some of your concerns...

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