I have completely deactivated the local folders and only work directly on my Memotoo account.
Okay, I just made some more specific tests (also with 5.0.17944.0). Here is what I’ve found out:
If i create an event IN eM client and then copy and sync, everything is fine and both events are there with a different UID (in eM Client-Format). But: It seems, that Memotoo changes both UIDs into its own format (like “memotooEvent23524062”), but increased on the second event. So this works correctly.
If I take an event which is formerly created BY Memotoo (or synced from there, which means with UID in Memotoo-format) and copy it, the second event has the exactly same (Memotoo-)UID like the first one. So during next sync, the first event gets deleted.
So I think in this case, eM client doesn’t recognize the Memotoo-UID as a valid UID and so it doesn’t increase or change it, just copies it, which leads to deleting because of double UID.
In addition, I’ve found out, that Memotoo changes the UID of every event to its own format during sync. Is this compliant to CalDAV standards?
So, who can fix this now?
Could you teach em Client to recognize the Memotoo-UIDs as valid UIDs or should the Memotoo-Webmaster switch the UID-format for his whole system to a more common format? Perhaps you could contact him directly? He is very friendly and cooperative to solve bugs in the Memotoo-system.
If I can help in any way to solve this problem, just tell me how!!!
Furthermore, I’d really like to participiate in making eM client even better! Is there any beta-testing programme?
I already have some ideas to improve usability of eM client, I will contact you, as soon as I write them down.