Differential accepted.

Thanks!

I meant to say resolved, because this part is indeed just that. I'm working on the SSH URIs right now.

This has escalated to our internal ticket tracking system as Ticket 1583 at priority high. I'm working on it.

Done.

What is the web server software that is installed (prior to setup-kolab)?

Can we make sure this commit lands in the -3.2 stable branch as well?

Please ensure the fix also lands in release-1.2.

rather than setting the timeout unconditionally, it should set the timeout only for if immediate:

Neither delegation nor password resets for a user should go through Roundcube. Roundcube, after all, is not an LDAP administration interface.

Line 444 should be claused similarly to line 431 (by line 430)

sync-mailhost-attr should use the (one) result attribute (cyrus-sasl, result attribute), not the mail attributes.

Again, the resources module is a different module from the invitation policy. I read this ticket as concerning the invitation policy. I'm not sure how the resources module got in to the mix.

The resources module is a different one from the invitation policy module. This ticket concerns the invitation policy module.

A failure of a load-balancer under the product name of F5 may in fact be creating long-lasting connections as well, as it tends to send a SYN, await the SYN, ACK, but never RST or ACK,FIN.

There's no technical provision that prevents us from allowing users to create multiple groups by the same name, provided that the data-to-presentation application logic uses keys that uniquely tie an entry to a (specific instance of a) group. Both SQL (primary index auto-increment) and Kolab (xml/uuid) provide these artifacts.

Some of the behavior that seems to be requested (albeit not explicitly) leans toward workflow management more so than it is squarly within the realm of simple task management.

Please note that, IIRC, the freebusy service renders Free/Busy information with a certain timeslot as well -- if any event overlaps either of the lower or upper boundaries the entire slot is considered busy.

I would suggest to consider sending out the notifications of the changes as user2, in that this is rendered quite dysfunctional practically, should no notifications be sent out at all.

Pushed

In T1244#20657, @vanmeeuwen wrote:

I agree with the suggested options by @machniak, since they combine in to the following combinations of bitflips for the underlying Syncroton:

1. Selected folders only (0),
2. All subscribed folders (1+4+16),
3. All folders (2+8+32)

Let's substitute the use of the word "delegate" here, for the "assignee" -- to avoid confusion with the actual delegation scenario involving a secretary, or indeed the delegation scenario in iTip.