On Tue, 2014-04-08 at 20:01 +0200, Dustin Demuth wrote: Not being able to specify it directly for the source is one of the known limitations of the current property mechanism. It was discussed before (for example here: https://lists.syncevolution.org/pipermail/syncevolution/2014-January/0045...). Currently "SSLVerifyHost" and "SSLVerifyServer" need to be set indirectly for a source in the sync or target config; the setting then applies to all sources used in the sync. Both need to be set to 0 for WebDAV, because libneon (in contrast to libsoup for SyncML over HTTP) only has a coarser check. Does SyncEvolution run on the phone or are you setting up a SyncML<->WebDAV bridge used by the phone? If SyncEvolution runs on the phone and thus uses local sync, then set "SSLVerifyHost" and "SSLVerifyServer" in the "target-config" of the target context. In the bridge case (same as in the mail thread pointed to above), the settings need to go into the sync config created for the phone. Thanks. I'm glad myself that more people chime in again recently, ask questions and offer suggestions. Thanks Graham, Emile, Jane! And let's not forget Ove for supporting SyncEvolution on phones, that's invaluable. -- 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.