Hello! I have a question to users of SyncEvolution. In 1.0 beta 1, we added a feature that gives you more control over error handling - but it is not enabled by default yet: $ syncevolution --sync-property preventSlowSync=? '--sync-property preventSlowSync=?' During a slow sync, the SyncML server must match all items of the client with its own items and detect which ones it already has based on properties of the items. This is slow (client must send all its data) and can lead to duplicates (when the server fails to match correctly). It is therefore sometimes desirable to wipe out data on one side with a refresh-from-client/server sync instead of doing a slow sync. When this option is enabled, slow syncs that could cause problems are not allowed to proceed. Instead, the affected sources are skipped, allowing the user to choose a suitable sync mode in the next run (slow sync selected explicitly, refresh sync). The following situations are handled: - running as client with no local data => unproblematic, slow sync is allowed to proceed automatically - running as client with local data => client has no information about server, so slow sync might be problematic and is prevented - client has data, server asks for slow sync because all its data was deleted (done by Memotoo and Mobical, because they treat this as 'user wants to start from scratch') => the sync would recreate all the client's data, even if the user really wanted to have it deleted, therefore slow sync is prevented Slow syncs are not yet detected when running as server and in the client when the server's anchor is wrong. This option is not enabled by default because it forces users to deal with slow syncs, which is a deviation from previous behavior. Is this something that you would find useful? -- Best Regards Patrick Ohly Senior Software Engineer Intel GmbH Open Source Technology Center Hermuelheimer Strasse 8a Phone: +49-2232-2090-30 50321 Bruehl Fax: +49-2232-2090-29 Germany