offlineimap VS dendrite

There are also isync and OfflineIMAP which sync email locally.

I'd consider using the Bridge + offlineimap (or a similar tool). That can connect via IMAP to both the Bridge IMAP and your destination IMAP service and copy all mails automatically that way.

As u/alex_herrero says, Proton Mail Bridge is very much useful. I'm using this myself together with offlineimap to have a local backup. I also use the Bridge with Thunderbird too, which also works quite well (especially the v3 beta).

For the sync / import functionality the MSP uses offlineimap, which is another counterpart to IMAPSYNC. Changing the import tool will not bring up the solution to the main problem, that I am not able to reset the imported stuff back to zero in order to test the different scenarios of the main use case.

Don't risk relying on someone else's hardware or service, use something like Offlineimap or Mbsync to sync your emails to your computer then automate multiple backups.

Many people use OfflineIMAP.

I've used offlineimap in the past: http://www.offlineimap.org/

I'm looking into replacing Thunderbird with mu4e (for the first time, despite being an Emacs guy for 15 years) and I got unexpectedly stuck at step 1, dowloading my email. offlineimap is broken on newer Pythons, getmail doesn't support Python 3 at all, and fetchmail is infamously inscrutable. It all seems a bit ridiculous, but I guess it speaks to how webmail has come to dominate proper email clients. Any recommendations?

Neither a mutt, nor an offlineimap user, but I believe those two are often used in combination: http://www.offlineimap.org/

Matrix already has key-based identity in the works at https://github.com/matrix-org/matrix-spec-proposals/blob/keg... (and implemented in Dendrite at https://github.com/matrix-org/dendrite/pulls?q=is%3Apr+is%3A...). Matrix is set up to let folks go wild and change fundamentals like this; basically every Matrix Spec Change (MSC) is a small fork, which then gets merged into the main spec if it can be proven to work well in the wild.

I really hope that Dendrite is getting more traction and maybe there's an OIDC solution for Matrix one day.

Yes there is an official helm chart. https://github.com/matrix-org/dendrite/releases/tag/helm-dendrite-0.11.2

This is what the Matrix team is developing Dendrite for. To have a feature-complete yet small server software. But it's still in beta.

Pinecone, which is an experimental overlay routing protocol used by P2P Matrix. It and Dendrite are extremely important to P2P Matrix.

So I want to setup an instance of Dendrite, a matrix home server. I have a docker-compose set, the yaml file in the correct directory, but I do not understand how to generate the key files. the dockerhub states that I should use this:

Dendrite, meanwhile, can be found here. They say it's in beta. I think it's a late Alpha. Dendrite's primary mode is "Monolith"; this will have many of the same scalability/balancing options that Synapse does. However the true benefit to Dendrite as I see it is the "polylith" mode where workers can swap around which worker is the master without any interruption of service. I do not think that Dendrite polylith works yet, but I might be wrong. I'll be looking at running it on a test server in January to see if it's time to upgrade from Synapse (and time to invest in 4-6 SBCs to keep three here and send 3 to 3 of my buddies to make my Matrix even more reliable).