On Tue, 2014-07-15 at 23:37 +0800, Emfox Zhou wrote: > It output many lines such as: > > > > <d:href>/carddav/v1/principals/[email protected]/lists/default/xxxxxxx</d:href> > <d:propstat> > <d:status>HTTP/1.1 200 OK</d:status> > <d:prop> > <d:getetag>"2011-07-29T01:34:21.127-07:00"</d:getetag> > <d:resourcetype/> > </d:prop> > </d:propstat> > </d:response>
That means it is talking to the server and credentials were okay. Now try SYNCEVOLUTION_DEBUG=1 syncevolution --daemon=no --export /dev/null loglevel=4 c102 addressbook Does that work repeatedly without authentication errors? I'm starting to suspect that you run into temporary requests by Google to log into their web form. SyncEvolution should work around that by resending requests with plain authentication. In your second sync output from two emails ago, the sync did proceed to the "download data" phase and the only unusual output were INFO messages, not ERRORs: [INFO] sync: /org/syncevolution/Session/15756214181405429789: operation temporarily (?) failed, going to retry in 4.8s before giving up in 299.8s: GET: Neon error code 3 = NE_AUTH, HTTP status 401: Could not authenticate to server: ignored GoogleLogin challenge How did that sync end? Successfully or with a failure? Google stopped supporting plain text authentication. At some point you'll have to get OAuth-based authentication working; unfortunately that is not easy on a headless server. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
