• Performance: Use lighter rcube_message_header instead of rcube_message

Adding methods to backend interface implementation requires some more code. Phpstan says:

Line   lib/ext/Syncroton/Command/FolderSync.php                          
------ ------------------------------------------------------------------ 
 295    Call to an undefined method Syncroton_Backend_IFolder::exists().

• Fixes regarding syncroton API for tags

• Small doc fix

• CS fixes
• ANNOTATE driver
• Improvements
• SQL driver fixes

BTW, none of the other registered passport clients are added via the migration. Maybe they should too. However, as all of them depend on existing-in-config client secrets and Ids, I'm still not sure migration is the correct place. Maybe we should have something like a "global seeder".

We call the seeder after migration, so the seeder will fail because the record already exists.

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

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

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.

Take a look at App\Jobs\User\DeleteJob, it will add STATUS_DELETED after all code before passes (does not throw an exception). So, checking for missing STATUS_DELETED should be included, and probably should be enough to check just this one.

Also, whereNot('status', '&', User::STATUS_DELETED) would probably do the same. This status is set after user deletion from LDAP/IMAP was successful.

Maybe where deleted_at < "5 seconds ago" would be better to give some slack to users deleted "right now".

• Add QR code

• CS fixes