On Fr, 2010-01-29 at 14:19 +0000, Jim Rorie wrote: The way to be sure of this is to keep logs around long enough so that when you notice a problem, you (or us, if you share the relevant logs) can look at what was sent to the server and what came back. The "logdir" and "maxlogdirs" properties are relevant for this. Try out "syncevolution --print-sessions" - you might still have some relevant logs. If you do that in the "full name" text field instead of the "full name" dialog, then Evolution will split this into first name "ACME", middle name "Water", last name "company" automatically. Not a big deal, but it is something to watch out for in the data exchanged with the server. Sounds plausible, however, for this will typically only become a problem when the server does item matching, for example during a slow sync. I tried to reproduce the problem by sending the "ACME Water company" example and forcing a slow sync, but it didn't duplicate. Some additional properties might be relevant. You could give it a try yourself: - make sure client and server are in sync - force a slow sync: syncevolution --sync slow funambol - watch the "synccompare" output to find unwanted changes - restore previous content: syncevolution --restore ... + syncevolution --refresh-from-client If you are concerned about your data, do it with a test account on the server and a second local address book. The SyncML server itself preserves the prefix. Perhaps the web UI or some other client breaks your data. -- 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.