Francis, thanks again for your quick response. My goal here is to allow all users of a domain the ability to read an address book, while giving a single user the ability to modify/add/etc the address book. Would I simply define another user source, specify that it is an address book, and define permissions?
To be honest, I don’t know much more than defining LDAP-based user sources (AD/OpenLDAP). So, I’m guessing they do not have the ability to do what I’m looking for. How about SQL user source, is it possible to allow one user permissions to modify this? Again, thank you for your insight. ~Laz On Mar 13, 2014, at 8:07 PM, Francis Lachapelle <flachape...@inverse.ca> wrote: > Hi Laz > > On Mar 13, 2014, at 10:44 PM, Laz C. Peterson <l...@paravis.net> wrote: > >> I have a question about the functionality of Apple’s iOS Contacts vs OS X >> Contacts. >> >> I know this is probably more of a question for Apple, but how come iOS >> Contacts works beautifully, yet OS X Contacts doesn’t work at all? Since OS >> X Contacts supports CardDAV, I would expect something more than just the >> ability to add a “group” contact. I can’t even see my actual contacts. >> Even with “one” subscribed contact list, as mentioned in previous bug >> requests or group messages. >> >> It really confuses me. I’m trying to put together a contacts server that >> supports Apple’s desktop application, yet it seems a little more impossible >> than I was hoping. >> >> Any suggestions or advice out there? Could there possibly be a >> configuration issue on my end? > > It’s true that iOS Contacts and OSX Contacts don’t seem to share the same > source code. > > However, both mostly work. All personal and shared address books appear under > iOS but only the personal address book appear under OSX. However, one can > access a public address book under OSX but not under iOS. > > > Francis-- > users@sogo.nu > https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
