Re: sync_client: IOERROR: fetching subscriptions

Jean Charles Delépine écrivait (wrote) : > 2020-10-06T10:51:45.070636+02:00 cyrus-3.0.8 cyrus/imap[2714758]: IOERROR: > fetching subscriptions for user1 user1.sub didn't have correct tab line termination. Certainly my fault sometime in the past. Jean Chales Delépine

sync_client: IOERROR: fetching subscriptions

. LSUB "*" "*" * LSUB (\HasChildren) "." INBOX [...] * LSUB () "." INBOX.archives.2000-2019.2018 I don't understand. Where can be

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~

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,

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.

Replication : IMAP_PROTOCOL_ERROR Protocol error

CENTTIME 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 m

Re: Upgrade to 3.2.2 and sieve

Stephan écrivait (wrote) : > sieve_rebuild: [path to script] parse failed: script errors:#015#012line > 5: header 'resent-from': not a valid header for an address test I had the same error with a 2.5 to 3.0 migration. Corrected with 'rfc3028_strict: 0' : rfc3028_strict: 1 If enabled, Sieve w

Debian's cyrus 2.5.10 ctl_mboxlist segfault

t_mode=S_IFREG|0600, st_size=37058416, ...}) = 0 fcntl(6, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x1c} --- +++ killed by SIGSEGV +++ I don't know anymore what to do... Sincerly, Jean Charles Delépine

setting acl on autocreate folders

the INBOX (that will be inherited by its subfolders on creation). defaultacl is only for non users mailboxes implicit_owner_rights is only for owner acl So, is there a way to automatically set acl anyone:p on newly created user mailboxes ? Sincerly, Jean Charles Delépine Cyrus Home

Re: Problems with murder upgrade from 2.2.13 to 2.5.8

emories. Thanks for your answer. Regards, On 06/06/2016 15:49, Jean Charles Delépine via Info-cyrus wrote: Hello, I'm on the way to make a big (late) upgrade. My murder config is composed of 16 1To backends. I can't upgrade all of them simultaneously. So I planed to : - upgrad

Problems with murder upgrade from 2.2.13 to 2.5.8

_disable_mailbox_referrals: 1 backends are in an internal non routable network. 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