On Fri, 2017-01-06 at 19:30 -0700, Eric O'Connor wrote:
I'm using the same username/password as I use successfully on my
iPhone, and I can run the --print-items and get a list of vcf items.
$ syncevolution --configure syncURL='https://contacts.zoho.com/carddav/
eric(a)oco.nnor.org/default/' backend=carddav username='eric(a)oco.nnor.org
' password='xxxxxxxx' sync=slow database='1483751134.3343.16@tara'
$ syncevolution --run eric-contacts9
[INFO] SoupTransport Failure: https://contacts.zoho.com/carddav/eric@oc
via libsoup: Unauthorized
[INFO] Transport giving up after 0 retries and 0:00min
It takes two commands to set up CardDAV syncing: once for the target
side (where CardDAV is used as storage) and once for the local side
(with EDS, Akonadi or plain files as local storage).
Perhaps one issue is that I don't really understand how
works. I think I want to sync between my webdav "backend", and my local
evolution "datastore", using the carddav "backend".
You need two datastores for that and thus two backends, not just one.
I guess when I do --print-databases, I refer to them using the thing
What is SyncML? I just want to sync Caldav/Carddav. Do I need to learn
Not really - how SyncML works is an implementation detail. It's just the
general concept (configure two sides, hook them up) which needs to be
Which documentation did you follow to get started?
The README.rst explains the general concept in the "Synchronization
beyond SyncML" section and "CalDAV and CardDAV" how to use that for
The same content is also on syncevolution.org
together with specific
HOWTO articles about other setups. Unfortunately the rendering there got
broken in several places when moving to a new Drupal version. I'm not
sure yet what to do about that - abandon Drupal, fix its setup (a bit
out of my league), or fix each broken page - all not very attractive :-/
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.