cyrus sync errors from 3.0.18 -> 3.4.8-patched

Michael Menge <[email protected]>
Newsgroups gmane.mail.imap.cyrus
Message-ID <20240701133401.Horde.SKsvUm6WBlMBWUteqpgKA_M@webmail.uni-tuebingen.de>
Hi,

at the moment i am migrating our servers from 3.0.18 to a patched version
of 3.4.8 to fix the murder problems


I have hit several different problems syncing form the old version to the new.
Most could be fixed with a reconstruct on the client side an a  
sync_reset on the server side.

But there is one kind of a problem that i am still unable to resolve.
As fare as i can tell, only folders unter "DELETED" have this problem.


Jul  1 13:10:35 mailserv04 be/sync_client[1978]: MAILBOX received NO  
response: IMAP_PROTOCOL_ERROR Protocol error
Jul  1 13:10:35 mailserv04 be/sync_client[1978]: do_folders(): update  
failed: DELETED.user.XXXX.Trash.Buch.663E43B3 'Bad protocol'
Jul  1 13:10:35 mailserv04 be/sync_client[1978]: Error in  
sync_do_mailboxes(): bailing out!


Jul  1 13:10:35 mailserv06 re/resyncserver[19487]: SYNCERROR: failed  
to parse uploaded record


the telemetry logs show the client did send a "APPLY MAILBOX " command,
and the sever did reply with NO IMAP_PROTOCOL_ERROR Protocol error

switching from csync to imap as sync protocol did not help.

Any ideas how to fix the folders?

Kind regards


    Michael Menge

--------------------------------------------------------------------------------
Michael Menge                          Tel.: (49) 7071 / 29-70316
Universität Tübingen                   Fax.: (49) 7071 / 29-5912
Zentrum für Datenverarbeitung          mail:  
[email protected]
Wächterstraße 76
72074 Tübingen


------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/T8556e55b2133ffdf-M14a53cba2a5af4cd506ea63b
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
smime.p7s (application/pkcs7-signature, 6.5 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.