[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kolab-users
Subject:    Re: Unable to access CalDAV/CardDAV
From:       <bruederli () kolabsys ! com>
Date:       2014-10-02 7:18:51
Message-ID: 542CFC5B.4050305 () kolabsys ! com
[Download RAW message or body]

Henning wrote:
> Hello,
> 
> I think this is indeed a cyrus problem. Is ./shared/vendor/kolab/
> supposed to be located within IMAP or maybe within the iRony public_html
> directory? Anyway, I do not find anything like that on my server.

Hello Henning

I think there's a misunderstanding from my previous response.
/{shared,private}/vendor/kolab/uniqueid refers to IMAP folder metadata
and not filesystem paths. Therefore you won't find them anywhere on your
disk.

When using Cyrus Imap 2.5, a uniqueid is automatically created for each
folder and iRony will use this metadata:
/shared/vendor/cmu/cyrus-imapd/uniqueid. For older versions, iRony
attempts to create the uniqueid and save it into the
/shared/vendor/kolab/uniqueid metadata entry.

Therfore your IMAP backend needs to allow setting this metadata which is
controlled by the definitions in /etc/imapd.annotations.conf. See the
related issue at https://issues.kolab.org/show_bug.cgi?id=3586#c4

You can check folder metadata using the following shell command on your
Kolab server:

  kolab list-mailbox-metadata user/john.doe/Calendar@example.org

(replace john.doe/Calendar with the username/foldername of yours)

I admit that writing of the uniqueid is assumed to work and iRony
doesn't handle failures. The following commit fixes this by returning a
uniqueid derived from the IMAP folder name:

  http://git.kolab.org/iRony/commit/?h=iRony-0.2&id=47610844

However, you should seek to fix your IMAP configuration rather than
relying on this fix. Because renaming the folder would lead to
synchronization failures as the uniqueid changes.

Kind regards,
Thomas


> Am 25.09.2014 um 09:45 schrieb Thomas Brüderli:
>> If that's not available, iRony
>> will generate a UUID for the folder itself and write it to
>> /shared/vendor/kolab/uniqueid or /private/vendor/kolab/uniqueid. If that
>> fails, the folder can't be found in subsequent requests.
> _______________________________________________
> users mailing list
> users@lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users
_______________________________________________
users mailing list
users@lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
[prev in list] [next in list] [prev in thread] [next in thread]