offlineimap VS docs

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/

I will recommend you review the documentation for the official Postgresql docker images which you can read here.

This is the full documentation for these images. Please note, this page has links to Docker official documents on volumes, etc., which are necessary to run images such as this.

We've just followed the official documentation to add a PostgreSQL database server. This will act as an application container, as our app will soon be depended on it. And in order to make sure that the database container is always started whenever we start our application container, we've added a new depends_on key to the app service and let it know which other service(s) it, well, depends on. This will make sure that the database server is up and running before the app. You may also have noticed that we've mounted volume to our database server's datapath a bit differently. This is known as "named volume". We'll discuss it a bit more in another part, it's not relevant to what we're learning here.

Nextcloud isn't hard to setup, follow the official doc https://github.com/docker-library/docs/blob/master/nextcloud/README.md

Looking at the setup for this (link here: https://github.com/docker-library/docs/blob/master/nextcloud/README.md), I am starting to understand a lot of the recent posts that we've seen & how much of a mess it still is :(

Coming back to nextcloud, the official readme of the nextcloud image has a few notes on how to set up both nextcloud versions.

Use the native command envstubst to replace the Auth Tokens in your Config File before starting NGINX. Example: https://github.com/docker-library/docs/tree/master/nginx#using-environment-variables-in-nginx-configuration-new-in-119

It's not clear why you want to split the web server (nginx) and the app (nextcloud). However, if you do have a good reason, you're in luck, they have a compose file that does just that: https://github.com/docker-library/docs/blob/master/nextcloud/README.md#base-version---fpm (version 2, but it'll work)