Re: sync_client Sieve from 2.4.20 to 3.2.2 issue

For Sieve the new path "C" is reported by mbpath, but sync_client replicates the sieve scripts elsewhere. Sorry, I would mean "For Sieve the new path with "H" is reported by mbpath, but sync_client replicates the scripts elsewhere (in the path with "S"). Many many thanks for every help Che

sync_client Sieve from 2.4.20 to 3.2.2 issue

Hello, I have a replication issue from Cyrus IMAP 2.4.20 to 3.2.2 about sieve path. Let suppose there is a user in Cyrus IMAP 2.4.20 with # mbpath user/gianni.ferromagne...@example.com /maildata/example.com/maildata1/domain/C/example.com/S/user/gianni^ferromagnetic and the Sieve is in: /va

backupd and sync_client Syntax error

Hello, I would ask an help with a new replication error in backup channel. I have this never-ending loop error: 2020-07-22T11:35:16.212126+02:00 tst-msg03 cyrus/sync_client[22465]: MAILBOXES received NO response: IMAP_PROTOCOL_BAD_PARAMETERS Bad parameters 2020-07-22T11:35:16.212185+02:00 tst-