Nice - and important. As communication is not the only part of collaboration, we should link this doc together with a bigger docs work that can explain the thoughts behind our product.

This seems to be too workaroundish. I vote against it.

Upgrades are not generally supported, in that the guides we do provide are a courtesy to community consumers.

Perhaps this should be "Documentation for KE14 on Jessie" with two subtasks: "Install guide" and "Upgrade guide"..

I am about to upload the differentials with arc.

I would like for these patches to be turned in to differentials, so we have the opportunity to not only comment on the semantics of the ticket (like we do here), but refer to items on a line-by-line basis as well.

for a preview of the changes, have a look at:

• https://github.com/TBits/KolabScripts/blob/Kolab16/kolab/patches/canonification_via_uid_pykolab.patch
• https://github.com/TBits/KolabScripts/blob/Kolab16/kolab/patches/canonification_via_uid_wap.patch

Cyrus IMAP version 2.5.7 +8 revisions ahead of the upstream tag has been made available in updates-testing.

By resolving T1062, this has just become a lot more reasonable.

In T1086#16217, @pafei wrote:

In T1086#15868, @vanmeeuwen wrote:

Client applications that do not allow multiple sessions against a single (base) URI, such as a regular browser, can only be made to authenticate with different credentials using the HTTP Basic Authentication realm. However, the CalDAV and CardDAV clients I know of do allow this second connection.

There is at least one Client which does this: Mozilla Thunderbird which is a CalDAV / CardDAV Client together with AddOns like Inverse SOGo Connector.

In T1086#15868, @vanmeeuwen wrote:

This more specifically involves a multi-domain deployment for which the services such as are addressed over the same URI, such as is often the case for a Hosted Kolab deployment.

The original problem space seems to be one single human being opening up two connections to WebDAV with the intent to use a different set of credentials between the first and the second, with both sets of credentials in a different domain name space aka. "authorization realm" in IMAP terminology.

This more specifically involves a multi-domain deployment for which the services such as are addressed over the same URI, such as is often the case for a Hosted Kolab deployment.

Noting that our current service health percentage is 99.71%, I would note that some services ("Kernel update installed, running an older kernel") may need to be excluded -- this could be achieved with recognizing the service type.

A feature with high marketing value. Something that has been requested a lot.