Re: cyrus sync errors from 3.0.18 -> 3.4.8-patched

Albert Shih <[email protected]>
Newsgroups gmane.mail.imap.cyrus
Message-ID <[email protected]>
Le 01/07/2024 à 20:41:21+0200, Jean Charles Delépine via Info a écrit
Hi everyone, 

I end up with almost exact same problem. I try to sync from 3.0.18
(freebsd) to 3.6.x.  (Debian). 
> > 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!
> 
> The same problem occurs between Debian versions 3.2.6 and 3.6, and now with
> debian's 3.8.1 (not yet tested with the latest patches).
> 
> First sync with a brand new backend does not trigger the error.
> 
> But once the error is here, even after removing the mailbox from the
> destination backend, the error still occurs, whith a segfault on the 3.2
> backend.
> 
> It seems the error occurs when some big folders on big malboxes are moved
> arround.
> 
> I have not found any way to fix the mailbox, but once it is transferred to
> another 3.2 backend server, the sync on the new 3.6 completes successfully
> and the initial backend can finish o sync his other malboxes.

I'm not totally sure to understand what you did...

Did you start from 3.0 -> 3.2 then 3.2 -> 3.6 ? Because I didn't see how
you transfert from xxx -> 3.2, in some email in 2020 I see you strugle to
sync from 3.0 -> 3.2 ? Did you use a classic imapsync ? 

Regards.

JAS
-- 
Albert SHIH 🦫 🐸
Observatoire de Paris
France
Heure locale/Local time:
ven. 06 sept. 2024 22:05:18 CEST

------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/T66d706d238d631f2-M59d6b7db42fc37b05bbe3ce8
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
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.