On Fri, Mar 21, 2014 at 2:59 PM, Patrick Ohly <[email protected]>wrote:
> On Fri, 2014-03-21 at 14:32 +0100, Emiliano Heyns wrote: > > I'm looking to setup server-to-server sync between Exchange and a > > Caldav/Carddav server (Google probably, but memotoo for now). > > You really do like to try new things, don't you? ;-) > > Guilty as charged. But I have a real use-case for this: my employer uses Exchange, so I have all my work appointments there. I want my family to be able to see both my personal and my work calendar. I can't give them access to my Exchange account, but a sync between exchange and google would allow them to see when I'm busy. One-way and two way sync would both work. I could of course do this with an outlook plugin, but that requires me to have outlook open almost always. My current setup, I kid you not, is a VBox instance on my headless server running Win7 running ICal4OL doing the syncing. But this setup fails regularly for reasons entirely mystical, and even though I get some mild amusement from proving Marc Andreessen right, it's not a setup I want to keep. > > I'm looking at > > https://syncevolution.org/wiki/ms-exchange-and-kde-synchronization, > > but in the setup of the exchange link, I don't know which parts of > > "target-config@Work contacts" are meaningful literals for > > syncevolution, and which I can give names that are meaningful to me. > > "target-config" is a special config which combines several properties > (like username and password) for sources created in the same context > (the part after @) and used on the target side of a local sync (the ones > with "syncURL=local://...."). > > "target-config" is a fixed string. The context name can be chosen > freely, for example "@google" for sources related to the same Google > account. > > > As all the howto's use 'target-config' so that might be a meaningful > > literal, but the howto at the url also uses 'work@KDE' > > "work@KDE" is a sync configuration, the local side of the local sync in > this case. "@KDE" was used to make it explicit that the sources in that > context use KDE as local storage. The implicit "@default" context could > also have been used. > > "work" is again a name that was chosen freely. > > See the man page for a section on the terminology. > > OK, so if I get this correctly, I would have (in server to server sync) two targets, one named (for example) target-config@exchange, and another target-config@memotoo, and no local sync config (as I don't have KDE running). I see that the last parameter of the config command ("contacts" in the howto) is supposed to be a 'source', but I can't tell between the howto and the manpage what source it is supposed to refer to. The howto implies it's connected to whether or not you use a template... but I haven't used a template (so far). If I set up memotoo, I'll have to use the webdav template, but https://syncevolution.org/documentation/syncevolution-usage#caldav-and-carddavomits the source parameter. Also, when I set up two targets and no local source, how will syncevolution --sync slow webdav know that it's peer is exchange? Thanks, Emile
_______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
