Hi Christian On 2013-01-15, at 4:44 AM, Christian Rößner <[email protected]> wrote:
>> uick follow-up: this bug has been fixed in the upcoming 2.0.4 release. >> Notice that with OS X, SOGo only returns the personal addressbook along with >> the first shared source. However, you can control which of your shared >> sources is returned since the list is now sorted first. >> >> Ticket: http://www.sogo.nu/bugs/view.php?id=2099 > > > First of all, thanks for fixing this. Just a short question: Is your > described limitation based on Contacts.app or the current state with SOGo? (I > guess, for most users this is no real problem; just a general question) Instead of using collections, Contacts.app defines special vCards to group contacts. This format looks similar to our own so-called "vList". SOGo has the advantage to offer both: you define vLists inside DAV collections (the addressbooks). Contacts.app creates groups inside a single collection. An Apple group is defined like this: BEGIN:VCARD VERSION:3.0 PRODID:-//Apple Inc.//AddressBook 7.1//EN N:group from Contacts.app FN:group from Contacts.app X-ADDRESSBOOKSERVER-KIND:group X-ADDRESSBOOKSERVER-MEMBER:urn:uuid:c4eff15c-f26f-4759-a89e-43ac79c92cd7 REV:2013-01-15T15:25:20Z UID:6cbbeb5c-b339-48f1-87a6-4edee17822b5 END:VCARD A vList is defined like this: BEGIN:VLIST UID:26F2-50F57600-1-FE99460.vlf VERSION:1.0 FN:group from SOGo CARD;FN=john doe:c4eff15c-f26f-4759-a89e-43ac79c92cd7.vcf END:VLIST SOGo should eventually convert on-the-fly collections (and vList?) to Apple groups for OS X clients. Notice that Contacts on iOS has proper collections support. We can suspect Apple to eventually have an identical code base for Contacts on iOS and OS X, but I wonder which format they'll use! Francis -- [email protected] :: +1.514.755.3640 :: http://www.inverse.ca Inverse :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- [email protected] https://inverse.ca/sogo/lists
