pykolab version is irrelevant. This is roundcubemail-plugins-kolab issue.

See T224.

BTW, RFC2177 is talking about re-connecting in 29 minutes, so I suppose guam should set the timeout to 30 minutes.

I updated the list in my previous comment with Outlook 2013 behavior. Now, we need to think what we can do to make the behavior better.

So, I tested some clients with my blacklist implementation and enabled folders hierarchies for all.

I agree some solution for cleaning old events could be useful. It could be also a command line utility for admins as they would likely want to keep the database size as small as possible.

We have a separate ticket for this issue now - T1607.

@seigo I wasn't able to implement this. For now I configured a proxy which looks working, so not a prio for now.

D238 fixes this.

Make the number of slots in an hour here should depend on Preferences > Calendar > Time slots per hour (T1381)

No, it does not require changes! Putting the files from master into KE14 can't just work.

Well, there's code that is executed async when opening the dialog, so -finish/-end is not exactly true when you trigger the event. That's why I prefer a name without such a suffix.

BTW, the libcalendaring package is not the same as libcalendaring plugin.

In T1523#25018, @greve wrote:

Hasn't the choice which calendar to store something into upon acceptance been a feature request recently? So then the user could always choose where to store a new event, and that would default to their private calendar.

Privileges to shared folders are managed by admins. Users have no way to make sure delegatee has access to a shared folder. User probably should not care much about this.

The headers are indeed added by smtp access policy and come from:

[kolab_smtp_access_policy]
delegate_sender_header = True
alias_sender_header = True
sender_header = True
xsender_header = True

Problem is that Roundcube already set X-Sender and Sender headers.