Looks like none of libkolabxml and plugins: libkolab and calendar support BYSETPOS. As a quick fix we should probably allow two simple and most common cases of "first weekday" and "last weekday" by converting them to correct BYDAY property.

This is RFC 3744 which has to be implemented. We have a ticket for this (T756), but that one is about WebDAV. Let's keep a separate ticket for CalDAV.

I'm not able to reproduce the issue anymore.

This is a duplicate of T1847.

I can confirm this. There are at least two issues here:

1. allday flag for exceptions is forced to be the same as main event. This can be fixed with this:

-- a/plugins/libkolab/lib/kolab_format_event.php
+++ b/plugins/libkolab/lib/kolab_format_event.php
@@ -291,7 +291,9 @@ class kolab_format_event extends kolab_format_xcal
         }

Roundcube core and kolab_addressbook plugin does not support photo URLs. It is not clear to me if it is at all possible to store URL and mediatype in Kolab XML format (probably only URL without type is supported).

I just did an update on some old Kolab:Winterfell installation:

33 | update                   | 2016-12-29 09:31 | E, I, O, U     |  481 EE
32 | update                   | 2016-08-31 12:05 | E, I, U        |  194 EE

I see no issues. Anyway this looks more like a mysql issue.

This was fixed in 66310b2fc46138.

clamav-update package is required dependency of kolab-16.0.1-3 according to https://obs.kolabsys.com/package/rdiff/Kolab:16/kolab?linkrev=base&rev=9 So, this probably is fixed already. @vanmeeuwen ?

The same as in syncroton (T1751) it is caused by authentication cache.

I'm afraid Chwala does not log successful logins either. Failed logins log comes from kolab_auth plugin.

It is because syncroton uses authentication cache. So, when the username is in the cache kolab_auth plugin (which logs userlogins errors) is bypassed. We need some additional code in kolab_sync::authenticate(), probably should depend on Roundcube's log_logins setting.

Done. It does create folder names similar to these known from ActiveSync settings in Roundcube. Also iRony uses similar technique. So, the unification is good, but likely there's still a place for improvement. If we could agree on some precise unified format (with all corner cases described) we could then implement it for all of these three systems.

1. Rooms:
   • id - unique room identifier
   • creator - user that created the room (and is an admin for it)
   • is_public - is the room for everyone or requires an invitation
   • alias - human readable room name (especially for public rooms) - should be unique
   • created_timestamp

@vanmeeuwen, So we have a case with no delegation, but with a shared folder where user (with write rights) deletes an event. Considering my comment here https://git.kolab.org/T1357#27566 and the next one, what would you propose? Note that we first have to solve this independently from what wallace does, i.e. define what iTip messages are sent and when, should we use SENT-BY field, etc. Then how wallace would handle that is another story.

Anything interesting in mariadb logs?

Implemented in D351

• Text chat (using public room)

Did you try to use mysql from command line? Does Roundcube work? What exactly did you upgrade?

• Install bootstrap js/fonts and jquery

• User status (presence)

This is already implemented.

The upstream issue has been fixed.

I'm working on websockets and tokens (yes, Phoenix.Token). So, this diff only stores users in database to have user ID. Status is for user status in future (but I suppose we'll change that to some another database table). I didn't think about Phoenix.Presence yet.

Are we going to write LDAP authentication (which is not so simple considering multi-domain and username canonification) or we should use e.g. chwala API connection to authenticate the user?

What distro are you using? I guess it would be better to update PEAR package. It should not throw warnings with pear-1.10.x.

This works for me. So, it may be some timing issue. Note that these notifications are not "instant", they are "pulled" in one minute intervals (timer starts when the page is loaded).