Re: Syncing shared folders
Ralph Sikau <[email protected]> Sat, 16 Sep 2017 15:58:08 +0200
| Newsgroups | gmane.comp.horde.sync |
|---|---|
| Organization | Parabol Pictures |
| Message-ID | <[email protected]> |
Michael J Rubinsky schrieb: > > Quoting Ralph Sikau <[email protected]>: > >> Michael J Rubinsky schrieb: >>> >>> Quoting Ralph Sikau <[email protected]>: >>> >>>> Michael J Rubinsky schrieb: >>>> >>>>> Quoting Ralph Sikau <[email protected]>[1]: >>>>> >>>>>> A calendar or an addressbook which is shared with another >>>>>> user, >>>>>> cannot be synced by this user with Activesync. Is that >>>>>> normal >>>>>> or are we doing anything wrong? >>>>> >>>>> Synchronization requires that the user synchronizing have edit >>>>> permissions on the source. This is due to the fact that ActiveSync >>>>> does not provide any permissions checking, it assumes the user >>>>> owns the resources being synchronized. >>>> >>>> Even with read and write permissions ActiveSync does not synchronise >>>> the shared folders to Android on the client side. After many >>>> tests that >>>> is obvious. The alternative is to sync these folders with >>>> caldav/carddav. >>> >>> You must enable "support separate address books" in the sync >>> preferences for Turba, and the Android sync client must support it >>> (most current clients do). >> Nope. That does not help either. Shared folders are not shown in the >> selection for being synchronized, only your own folders - both in >> turba and kronolith. Wether or not "support separate address books" >> is enabled does not change anything. Our Android sync client is the >> app Nine which is capable to handle separate folders. > > > This is exactly the same setup I use, and it is working fine. > > Just checked the code, and it actually requires DELETE permissions, > not EDIT. Well, we did not try that. Because we would not want that a client is able to delete events in the owner's calendar. It is only shared for information. -- sync mailing list Frequently Asked Questions: http://wiki.horde.org/FAQ To unsubscribe, mail: [email protected]