I have abandoned D3190 and submitted the individual commits in D3223, D3226, D3229, D3232, D3235, D3241 and D3244.

Submitted D3190, which has ended up being sort of... bulky. There are several commits in this differential; does Phabricator offer no option to review these commits individually like Git{Hu,La}b do, without the author having to create a separate differential per commit?

Could you create differential(s)? It should be possible to do this having patches via https://git.kolab.org/differential/diff/create/. Or just by using arc diff on your git clone.

Note that all changes I have made so far should™ be backward-compatible with Python >= 2.6, so they wouldn't necessitate any changes to our existing packaging.

This is not a level of integration nor support to which the reporter is entitled, or what their version of PHP were to support.

it could be useful too to allow to add Kolab Distribution Group in another group

automatic_addressbook is not working if we are hiding the global address book. The saved ids are not comming in compose window in autocompletion.

I'm running Nextcloud 17 and connected Kolab 16 (both on Debian 10) via webdav.
In my Folder tree I have:

This is especially useful for fully automated setup runs like

setup-kolab \
[...]
--mysqlserver=existing \
--mysqlrootpw=unix_socket
[...]

Kolab support for KDE PIM is discontinued. Create a ticket on https://bugs.kde.org

Case 1 is already implemented.

Please, be more clear. I don't have owncloud installation. Are you saying that it returns full folders hierarchy event if we ask for "1,noroot"? My understanding of owncloud and other dav servers was that they do (may) not support "infinity", but "1,noroot" should be supported. And this is what the rest of the code expects.

Hi Aleksandar,
i was on vacation so sorry for the delayed repsonse.
You're using a very old sabre dav library version (2.x) however nextcloud uses a much newer version (3.x).
There's no reference on the pref you're refering to.
Since my patch works but will be ignored by nextcloud (always sending recursive output), how do you treat the option in you code ? (Sabre dav doesn't support the extension at all )

I'm the person behind kolabops, and also @vanmeeuwen, but if you have issues/questions/comments with regards to Kolab Now, would you mind submitting an email to support@kolabnow.com?

Excuse poor assumptive assigningetiquette but could I ask @vanmeeuwen how this should be assigned?

Excuse poor etiquette but could I ask @vanmeeuwen where this should be assigned? I follow you (kolabops) on Twitter so presume you have most to do with Kolab Now

But you say it's a fix. So, what exactly are you trying to fix? I don't see a problem when I use chwala with Kolab storage connected using webdav driver.

Hi Aleksander,
first of all, the limit pref has been mentioned in the rfc 8144 not before 2017 and is a Microsoft extension.
Secondly, the Sabre lib, eg. (3.2.3 (2018-10-19)) doesn't support the pref at all.
I scanned the source as well as the Changelog of the Sabre Lib !
You really should treat this pref optional not mandatory though.
You use version 2.1.11 (2016-10-06), so the extension was invented afterwards !
Rgds.
Franz

The whole point is to never use infinity. Now the procedure is recursive and we never fetch more than one level of the folder tree. Or are you saying that your webdav server does not support "1,noroot"?

Correcting the priority from 60/40 to Normal

Correcting the priority from 60/40 to Normal

Correcting the priority from 60/40 to Normal