Proper fix https://github.com/roundcube/roundcubemail/commit/df02322d6a38e6691ec066d83ee7e6ca34a1054d

I tried taking into account how states override each other

Avoid pushing resync jobs for deleted users

This warning message is not that useful without a wallet ID, I suppose.

Regarding syncrotons needs:

• I think we need to get away from the timestamp comparisons and instead store whatever we need to as part of the synchronization state (tied to the synckey)
• Ideally we find something better to store than all entries in a folder that are part of the tag, or at least a more efficient representation than huge urls.

just as an fyi, purging users became less of a priority, so I'm parking this diff for now.

Rely on onlyTrashed

Do not disable a pending mandate

Really only test the IMAP_READY status

Rewrote resync to use separate queries for created/deleted

Do not retry the payment, we will on the next charge cycle, but make sure email notifications are not interrupted by topup failing.

Check updated_at/created_at

I was thinking about removing the try/catch. If we make a top-up attempt on every WalletCheck job run there's really no need for dispatching a separate job. The only danger will be that if topUpWallet() always throws the rest of the code will never execute, but how big of a danger is that I'm not sure.

Fixed some typos, now the query exeutes in reasonable time

Questions:

• Is this good enough to detect inactivity?
• Is the degraded state good enough or do we need to check the wallet balance?

This uses the same mechanisms as the horizon dashboard, and allows us to largely ignore the dashboard and implement monitoring (to e.g. notice if a queue gets stuck or so).