On Sun, 2014-07-13 at 21:18 +0800, Emfox Zhou wrote:
Hello, I've try to sync google contacts to my debian box.
The syncevolution version is 1.4-1.1, I did according to the manual:
emfox@XXXX:~$ syncevolution --configure --template WebDAV
username=XXXXX(a)gmail.com password=XXXX
database=https://google.com:443/carddav/v1/principals/XXXX%
40gmail.com/lists/default/ target-config@webdav
[INFO] addressbook: looking for databases...
[INFO] addressbook: okay
[INFO] calendar: looking for databases...
[INFO] calendar: no database to synchronize
[INFO] memo: looking for databases...
[INFO] memo: no database to synchronize
[INFO] todo: looking for databases...
[INFO] todo: no database to synchronize
emfox@XXXX:~$ syncevolution --configure --template
SyncEvolution_Client syncURL=local://@webdav sslverifyserver=0
username= password= webdav addressbook
[INFO] addressbook: looking for databases...
[INFO] addressbook: backend failed: error code from SyncEvolution
authorization failed (remote, status 401): PROPFIND: Neon error code 3
= NE_AUTH, HTTP status 401: Could not authenticate to server: ignored
GoogleLogin challenge
[ERROR] addressbook: backend failed: error code from SyncEvolution
authorization failed (remote, status 401): PROPFIND: Neon error code 3
= NE_AUTH, HTTP status 401: Could not authenticate to server: ignored
GoogleLogin challenge
It's still working for me.
Do you perhaps have two-factor login enabled for your Google account? In
that case the main password that you use to log into the account via the
Google web pages does not work for CardDAV. You have to create a
password for the SyncEvolution client - see
https://support.google.com/mail/answer/1173270?hl=en
Another pitfall might be the username. Google web interface recognizes
email address added to the account, CardDAV doesn't. If in doubt, try
the one created by Google (@gmail.com).
--
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.