This migration thing is a mess and will be problematic in the future. I however have no better idea. We'll have to be very careful in the future. And this makes managing Kolab4 installation (and updates), if you are not Apheleia IT, very difficult.

• Fix PHP5 compatibility, fix Kolab driver for addressbook

• Fix caching recurrent events' end date
• Small cleanup

CreateJob is already async, so I don't really see a reason to invoke another job. At least the point is to not create the mailbox/ldap record if the abuse check didn't finish yet.

• CS fixes

• Add an option to disable LDAP backend

• Remove Roundcube user record on user delete

• Merge branch 'master' into dev/direct-imap-backend

I still don't like it here, but I'll accept it if you add a test for this ;)

Please, add an explanatory comment .

This is upstream code, so we should be careful, and then create a PR for Roundcube to include the changes.

Is this still relevant?

This does not sound right. In your use-case we do release(60) which is not "failing silently" but waiting for domain to be set up and trying again.

• Cleanup