Quote:
Originally Posted by ezu  Please let me know if you require any additional details. I might have much more in the other day-to-day logs also. What I had attached was zdesktop.log for a given day. Hopefully, it should have enough material to isolate and resolve the issue. |
As per latest comments available in Bug 31450, this issue was caused by duplicate key issue if mail was moved from non-synchronized local Zimbra desktop folder to trash folder and is now resolved and will be available in upcoming RC2.
This will definitely apply if I move a mail from non-synchronized folder to trash in the upcoming RC2.
But what would happen to messages moved already long back in the local folders using previous releases of Zimbra desktop (around July 2008 time frame) and still available in local Zimbra desktop folders. How will the duplicate key issue be taken care of ? Will they get sync'ed back to the yahoo web server. At the end of the whole process, all local mails available and all yahoo web server mails available should be in perfect sync without missing or altering any original mails.
I am also still wondering as to how this can STOP each and every mail available in local Zimbra desktop folder and not available in Yahoo web mail server to be pushed back to Yahoo web mail server. From what I know, if a mail cannot be pushed back for three times, it will be skipped and the process for next mail should continue. Does this mean that each and every mail in local Zimbra desktop folder not available on Yahoo web mail server has a duplicate key.