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.

Call IMAP::verifyAccount from the create job

Addressed 2 out of 3 comments

Deployment configs as a filesystem overlay

Optional IMAP backend, pass tests with imap backend disabled, fixed IMAP::verifyAccount.

• Fix PHP5 compatibility, fix Kolab driver for addressbook

• Fix caching recurrent events' end date
• Small cleanup

@mollekopf, will updates residing in Kolab:16:Testing be pushed to Kolab:16 automatically or is manual intervention needed? In other words, should I file an inclusion request?

@sicherha
roundcubemail-1.5.3-0~kolab2 is still not in stable repo... why?

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.

I suppose Handler::created could be used to spawn a job, not sure if it is a good solution or not.

The abuse check now lives externally. As a generic mechanism vanmeeuwen suggested that we may be able to install an app/Handler/Abuse.php just like we do for app/Handler/Mailbox.php, and that this might provide a suitable generic hook to run an abuse-check background job.

Cleanup

Removed production seeder

Fixed production seeder

• CS fixes

The fix is accepted into git.
But as I ran into another Error, you should also use the latest Diff 11060.

I ran into an integer error on other tests,
so I corrected this with this patch.

The fix works when applied by hand but does not yet show up in update package.