• Don't consider existing domains in the same account as non-existing

Merged indirectly.

• Save ACTIVE status before createing an LDAP record where it may be relevant, simplify some code

I hacked something in utils.py to try and live with the workaround again.... it looks okay, but we will see where else we might have issues...

I finally managed to upgrade my debian and went to deb11 with kolab16

The way we use folder_id() in kolab4 driver is different. Also I think we could probably get rid of object_prettyname(). Anyway, see my untested version in https://git.kolab.org/D5457

• Use saveQuietly()

• Remove redundant code

• Throw an exception if mailbox already exists (added a way to disable this)

This means we can only execute this command from where we also have imap admin access, but that's ok I suppose.

is_broken would be better because we already have is_deleted in some tables, but fine.

I guess the version number for packaging needs to be bumped somewhere now.

I am a seeing the same thing on Debian. It crashes roughly once a month, also without anything in the log.

Use boxwarning

Boolean broken state with the rest in extraData

In D5436#70779, @machniak wrote:

We should make this new code consistent with kolab_sync_storage_kolab4::folders_list(). You can find there how we handle special folders type. kolab_storage::folders_typedata() should not be used.

In D5445#70752, @machniak wrote:

I don't see how you unset the "broken" state. You said that when you reset Outlook according to your manual it will use the same device identifier. How it will unlock itself then? A test would be nice.

We should make this new code consistent with kolab_sync_storage_kolab4::folders_list(). You can find there how we handle special folders type. kolab_storage::folders_typedata() should not be used.

This is how outlook looks once we block the device (as you can see it enters "Disconnected/Getrennt" state).

Separate kolab4 implementation

I don't see how you unset the "broken" state. You said that when you reset Outlook according to your manual it will use the same device identifier. How it will unlock itself then? A test would be nice.

Makes sense.

Handle blocking of devices via config option

Clearly with room for improvement, but this gets the job done.
I'm open to some easy to implement suggestions, as I'm not very familiar with registering new forms (which is why I'm hijacking the subscriptions list).

My plan is to deploy this, review which devices get marked as broken, and only then start failing requests early.

mysql.initial version

Basically the same as we do for FolderSync, but useful for loops that don't report changes on FolderSync (and thus get no counting), or for loops that don't include FolderSync at all.

Seems to work for the delegation case.