Re: Replication : IMAP_PROTOCOL_ERROR Protocol error
Jean Charles Delépine écrivait (wrote) : > Jean Charles Delépine écrivait (wrote) : > > > Hello, > > > > I'm on the way to migrate one quite big murder config with Cyrus IMAP > > 3.0.8-Debian-3.0.8-6+deb10u4 > > to Cyrus IMAP 3.2.3-Debian-3.2.3-1~bpo10+1. > > > > My plan is to replicate 3.0.8's backends on 3.2.3 ones. This plan has work > > before for 2.5 > > to 3.0. migration. > > > > Il can replicate empty mailboxes. So the conf (attached) seems ok. > > But if the mailbox isn't empty here's the result (completes traces > > attached) : > > The conf might not be _that_ ok. > > If the option conversation is set to 1 and I create new mailboxes, ond > send mails to this mailboxes, no sync of these mailboxes is possible. > > If I remove the option 'conversation: 1', any new populated mailboxes can > be sync. > > So, the problem seems to be in this option. > > But even after removing "conversation: 1" and zeroed conversation indexes > (ctl_conversationsdb -z), the old "bad" mailboxes can't be synced. Even > removing their .conversations and .counters files doesn't help. > > Can I, and how can I, get rid of those conversation indexes in order to have > my mailboxes being "as if there never been conversation" ? After removing "conversations: 1" option AND restarted the serveur, ctl_conversationsdb -z did correctly remove conversations indexes and the replication finally works fine. I did have to revert xapian usage (which needs conversations) and switch back to squat indexes. Jean Charles Delépine Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Replication : IMAP_PROTOCOL_ERROR Protocol error
ellie timoney écrivait (wrote) : > On Thu, 24 Sep 2020, at 1:44 AM, Jean Charles Delépine wrote: > > Is this a known problem corrected after 3.0.9 ? > > Off the top of my head I no longer remember, but the current release in the > 3.0 series is 3.0.14. I'd suggest, if you haven't already, that you look in > the release notes from 3.0.8-3.0.14 and see if anything looks relevant. > They're here: > https://www.cyrusimap.org/imap/download/release-notes/3.0/index.html I didn't find anything relevant. > We don't generally recommend in-place upgrades between series (so, upgrading > in-place from 3.0.8 to 3.2.3 is not something we'd recommend). > Within-series, an in-place upgrade ought to be safe -- but please check the > release notes carefully for extra steps/considerations you may need to make, > depending on your deployment. I think you'll probably want to upgrade your > 3.0 systems in place as far forward as you can (while staying 3.0), and then > use the replication strategy to upgrade to 3.2 after that. I just do that. My test server is now using 3.0.14 (self build debian package) : >1601118406>APPLY MAILBOX %(UNIQUEID m8lfz12835tr5y3dfucebk95 MBOXNAME >user.testes2 SYNC_CRC 2393559122 SYNC_CRC_ANNOT 4164967045 LAST_UID 2 >HIGHESTMODSEQ 4 RECENTUID 0 RECENTTIME 0 LAST_APPENDDATE 1601117744 >POP3_LAST_LOGIN 0 POP3_SHOW_AFTER 0 XCONVMODSEQ 4 UIDVALIDITY 1601117689 >PARTITION default ACL "testes2lrswipkxtecdan " OPTIONS P RECORD >(%(UID 1 MODSEQ 4 LAST_UPDATED 1601118406 FLAGS (\Expunged) INTERNALDATE >1601117744 SIZE 2890 GUID 6f160d7026f4adbaebb2d0941c6398272a8692da ANNOTATIONS >(%(ENTRY /vendor/cmu/cyrus-imapd/thrid USERID NIL VALUE fee5d4912d9da6a8))) >%(UID 2 MODSEQ 3 LAST_UPDATED 1601118406 FLAGS () INTERNALDATE 1601117744 SIZE >2890 GUID 6f160d7026f4adbaebb2d0941c6398272a8692da ANNOTATIONS (%(ENTRY >/vendor/cmu/cyrus-imapd/thrid USERID NIL VALUE fee5d4912d9da6a8) <16011184061601118406>EXIT <1601118406http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Replication : IMAP_PROTOCOL_ERROR Protocol error
On Thu, 24 Sep 2020, at 1:44 AM, Jean Charles Delépine wrote: > Is this a known problem corrected after 3.0.9 ? Off the top of my head I no longer remember, but the current release in the 3.0 series is 3.0.14. I'd suggest, if you haven't already, that you look in the release notes from 3.0.8-3.0.14 and see if anything looks relevant. They're here: https://www.cyrusimap.org/imap/download/release-notes/3.0/index.html We don't generally recommend in-place upgrades between series (so, upgrading in-place from 3.0.8 to 3.2.3 is not something we'd recommend). Within-series, an in-place upgrade ought to be safe -- but please check the release notes carefully for extra steps/considerations you may need to make, depending on your deployment. I think you'll probably want to upgrade your 3.0 systems in place as far forward as you can (while staying 3.0), and then use the replication strategy to upgrade to 3.2 after that. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Replication : IMAP_PROTOCOL_ERROR Protocol error
Jean Charles Delépine écrivait (wrote) : > Hello, > > I'm on the way to migrate one quite big murder config with Cyrus IMAP > 3.0.8-Debian-3.0.8-6+deb10u4 > to Cyrus IMAP 3.2.3-Debian-3.2.3-1~bpo10+1. > > My plan is to replicate 3.0.8's backends on 3.2.3 ones. This plan has work > before for 2.5 > to 3.0. migration. > > Il can replicate empty mailboxes. So the conf (attached) seems ok. > But if the mailbox isn't empty here's the result (completes traces attached) : The conf might not be _that_ ok. If the option conversation is set to 1 and I create new mailboxes, ond send mails to this mailboxes, no sync of these mailboxes is possible. If I remove the option 'conversation: 1', any new populated mailboxes can be sync. So, the problem seems to be in this option. But even after removing "conversation: 1" and zeroed conversation indexes (ctl_conversationsdb -z), the old "bad" mailboxes can't be synced. Even removing their .conversations and .counters files doesn't help. Can I, and how can I, get rid of those conversation indexes in order to have my mailboxes being "as if there never been conversation" ? Sincerly, Jean charles Delépine Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Replication : IMAP_PROTOCOL_ERROR Protocol error
Hello,
I'm on the way to migrate one quite big murder config with Cyrus IMAP
3.0.8-Debian-3.0.8-6+deb10u4
to Cyrus IMAP 3.2.3-Debian-3.2.3-1~bpo10+1.
My plan is to replicate 3.0.8's backends on 3.2.3 ones. This plan has
work before for 2.5
to 3.0. migration.
Il can replicate empty mailboxes. So the conf (attached) seems ok.
But if the mailbox isn't empty here's the result (completes traces attached) :
cyrus/sync_client[3082351]: MAILBOX received NO response:
IMAP_PROTOCOL_ERROR Protocol error
cyrus/sync_client[3082351]: do_folders(): update failed: user.t 'Bad protocol'
cyrus/sync_client[3082351]: IOERROR: do_user_main: Bad protocol for t
to [no channel] (test-3.2.3)
Error from sync_do_user(t): bailing out!
cyrus/sync_client[3082351]: Error in sync_do_user(t): bailing out!
The destination server says :
SYNCERROR: failed to parse uploaded record
If I upgrade this test server to 3.2.3-Debian-3.2.3-1~bpo10+1 with
the same configuration, the same mailbox
can be sync whith the problem being corrected :
APPLY MAILBOX %(UNIQUEID 6kjf8ro4032wfjefcdewaqyl MBOXNAME user.t
SYNC_CRC 3435668400 SYNC_CRC_ANNOT 1359939586 LAST_UID 1 HIGHESTMODSEQ
3 RECENTUID 0 RECENTTIME 0 LAST_APPENDDATE 0 POP3_LAST_LOGIN 0
POP3_SHOW_AFTER 0 XCONVMODSEQ 3 UIDVALIDITY 1600855436 PARTITION
default ACL "" OPTIONS P FOLDERMODSEQ 3 SINCE_MODSEQ 3 SINCE_CRC 0
SINCE_CRC_ANNOT 12345678 RECORD ())
<1600872848cyrus/sync_client[3131948]: MAILBOX received NO response:
IMAP_SYNC_CHECKSUM Checksum Failure
cyrus/sync_client[3131948]: SYNC_NOTICE: CRC failure on sync user.t,
recalculating counts and trying again
Error but retry.
MAILBOX user.t
1600872848>APPLY MAILBOX %(UNIQUEID 6kjf8ro4032wfjefcdewaqyl
MBOXNAME user.t SYNC_CRC 3435668400 SYNC_CRC_ANNOT 1370712396
LAST_UID 1 HIGHESTMODSEQ 3 RECENTUID 0 RECENTTIME 0 LAST_APPENDDATE
0 POP3_LAST_LOGIN 0 POP3_SHOW_AFTER 0 XCONVMODSEQ 3 UIDVALIDITY
1600855436 PARTITION default ACL "" OPTIONS P FOLDERMODSEQ 3 RECORD
())
<1600872848cyrus/sync_client[3131948]: MAILBOX received NO response:
IMAP_SYNC_CHECKSUM Checksum Failure
cyrus/sync_client[3131948]: CRC failure on sync for user.t, trying full update
Error then full update
FULLMAILBOX user.t
1600872848>GET FULLMAILBOX user.t
<1600872848<* MAILBOX %(UNIQUEID 6kjf8ro4032wfjefcdewaqyl MBOXNAME
user.t SYNC_CRC 0 SYNC_CRC_ANNOT 12345678 LAST_UID 1 HIGHESTMODSEQ 3
RECENTUID 0 RECENTTIME 0 LAST_APPENDDATE 0 POP3_LAST_LOGIN 0
POP3_SHOW_AFTER 0 XCONVMODSEQ 3 UIDVALIDITY 1600855436 PARTITION
default ACL "" OPTIONS P FOLDERMODSEQ 3 RECORD ())
OK success
cyrus/sync_client[3131948]: user.t: same message appears twice 1 2
MAILBOX user.t
1600872849>APPLY MESSAGE (%{default
f0eeef2cc42f23884089760cf5de1961b358a498 2627}
)
<16008728491600872849>APPLY MAILBOX %(UNIQUEID 6kjf8ro4032wfjefcdewaqyl
MBOXNAME user.t SYNC_CRC 1009437458 SYNC_CRC_ANNOT 455745080
LAST_UID 2 HIGHESTMODSEQ 5 RECENTUID 0 RECENTTIME 0 LAST_APPENDDATE
0 POP3_LAST_LOGIN 0 POP3_SHOW_AFTER 0 XCONVMODSEQ 5 UIDVALIDITY
1600855436 PARTITION default ACL "" OPTIONS P FOLDERMODSEQ 3 RECORD
(%(UID 1 MODSEQ 5 LAST_UPDATED 1600872848 FLAGS (\Expunged)
INTERNALDATE 1600855652 SIZE 2627 GUID
f0eeef2cc42f23884089760cf5de1961b358a498 ANNOTATIONS (%(ENTRY
/vendor/cmu/cyrus-imapd/thrid USERID "" MODSEQ 0 VALUE
611d36cdcf46289a))) %(UID 2 MODSEQ 4 LAST_UPDATED 1600872848 FLAGS
() INTERNALDATE 1600855652 SIZE 2627 GUID
f0eeef2cc42f23884089760cf5de1961b358a498 ANNOTATIONS (%(ENTRY
/vendor/cmu/cyrus-imapd/thrid USERID "" MODSEQ 0 VALUE
611d36cdcf46289a)
<16008728491600872849>APPLY MAILBOX %(UNIQUEID nckzm4o710aom3c22o9ugy6a
MBOXNAME user.t.Drafts SYNC_CRC 0 SYNC_CRC_ANNOT 0 LAST_UID 0
HIGHESTMODSEQ 2 RECENTUID 0 RECENTTIME 0 LAST_APPENDDATE 0
POP3_LAST_LOGIN 0 POP3_SHOW_AFTER 0 XCONVMODSEQ 2 UIDVALIDITY
160087 PARTITION default ACL "" OPTIONS P FOLDERMODSEQ 2 RECORD
())
<1600872849
1600872849>EXIT
<1600872849Is there something I can do to successfully replicate my backends to
my new servers ?
Sincerly,
Jean Charles Delépine
configdirectory: /var/lib/cyrus
proc_path: /run/cyrus/proc
mboxname_lockpath: /run/cyrus/lock
defaultpartition: default
partition-default: /var/spool/cyrus/mail
partition-news: /var/spool/cyrus/news
newsspool: /var/spool/news
altnamespace: no
postuser: share-post
unixhierarchysep: no
lmtp_downcase_rcpt: yes
allowanonymouslogin: no
popminpoll: 1
autocreate_post: yes
autocreate_quota: 0
umask: 077
sieveusehomedir: false
sievedir: /var/spool/sieve
httpmodules: caldav carddav
hashimapspool: true
sasl_auto_transition: no
tls_client_ca_dir:
tls_session_timeout:
tls_versions:
lmtpsocket: /var/run/cyrus/socket/lmtp
idlesocket: /var/run/cyrus/socket/idle
notifysocket: /var/run/cyrus/socket/notify
syslog_prefix: cyrus
admins: mailadmin
metapartition_files: header index cache expunge squat annotations lock dav
archivecache
metapartition-default: /var/lib/cyrus/metas
search_engine: xapian
