Re: Migration murder from 3.2 to 3.10 (Debian 11 to 13) – frontend to backend auth error
Frank Richter <[email protected]> Mon, 16 Mar 2026 15:24:12 +0100
| Newsgroups | gmane.mail.imap.cyrus |
|---|---|
| Message-ID | <[email protected]> |
Am 09.03.26 um 07:29 schrieb Frank Richter: > thanks for you help. Some minutes ago I changed the setting to > improved_mboxlist_sort:1 for our 3.2.11 murder: No complaints from users so far :-) But we’re still in 3.2.11 (for 99,9% of users) … Now I started to XFER some mailboxes from backend with 3.2.11 to a new one with 3.10.2 with an often-used script using Cyrus::IMAP::Admin with: $cyrus->xfer($folder, $new_backend, $new_part); die "Error in xfer $folder to $new_backend:$new_part: " . $cyrus->error . "\n" if $cyrus->error; It always ends with: Error in xfer user.xxx to yyy:2: Bad protocol But it seems to have xferred all the e-mails and the sieve scripts. These are the last log line on backend server (3.2.11) from which the mailboxes moved away: Mar 16 15:01:13 porto cyrus/imap[2650095]: mbentry user.xxx has no uniqueid, needs reconstruct Mar 16 15:01:13 porto cyrus/imap[2650095]: Deleted mailbox user.xxx Any idea what this is related to? I tested transferring of shared folders. As seen in past updates some years ago, these shared folders are not xferred recursively. Also transferring sieve filters of shared folders doesn't work. I’ll have to do it with some extra steps. Or do I miss something? Thanks, Frank -- Frank Richter, Chemnitz University of Technology, Germany ------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/Tc654c39c5afc4bc1-Meab8249b560e10aea7d2780a Delivery options: https://cyrus.topicbox.com/groups/info/subscription