[sorry for the late reply - I was busy and only came back to this when going through pending items in my inbox] On Tue, 2013-05-14 at 14:45 +0200, Dustin Demuth wrote: So you can already do things like syncevolution --print-items @default addressbook and access your CardDAV contacts? The relevant part is under "Finally, here is how the @webdav context needs to be configured so that SyncML clients or servers can be added to it": one must set databaseUsername/Password and database properties. This ensures that the source works on its own, without additional information from the "target-config". The documentation uses "@webdav" as context for the WebDAV sources. It's okay to use "@default", as you indicated above. The documentation adds a SyncML server to that context. The same works with a mobile phone via Bluetooth. Just use the same command that you would normally use to set that up. From https://syncevolution.org/wiki/sync-your-phone-bluetooth syncevolution --configure --template ${template} --sync-property syncURL=obex-bt://${deviceAddress} MyPhone -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.

Am 13.06.2013 14:02, schrieb Dustin Demuth: Hey, As promised I'll report back: at the moment I'm having problems with NEON (the webdav library), as it can't authenticate with the owncloud instance. If I remember correctly, OC uses digest-authentication. [ERROR] error code from SyncEvolution authorization failed (remote, status 401): REPORT 'meta data': Neon error code 3 = NE_AUTH, HTTP status 401: Could not authenticate to server: rejected Basic challenge So I did not manage to bring the whole thing to life. Version : 1.2.2-1 BR Dustin