Re: sync_client problems

2017-05-11 Thread Bron Gondwana
It looked like the '148.' file was corrupted in some way. I assume you've deleted all the evidence now, so we can't see how! Oh well :( Bron. On Fri, 12 May 2017, at 04:55, Eric Cunningham wrote: > Just to close the loop on this, once the corrupted cdm-lit account on my > copy server

Re: sync_client problems

2017-05-11 Thread Eric Cunningham
Just to close the loop on this, once the corrupted cdm-lit account on my copy server successfully reconstructed, the backlog of replication has completed successfully and is now caught up. -Eric On 05/11/2017 02:20 PM, Eric Cunningham wrote: -G didn't seem to help, but I tried a "reconstruct

Re: sync_client problems

2017-05-11 Thread Eric Cunningham
-G didn't seem to help, but I tried a "reconstruct -f -r" command without having previously deleted all occurrences of the cyrus.* files and it was then successful. On 05/11/2017 01:44 PM, Patrick Boutilier wrote: Try a -G with reconstruct? -G Force re-parsing of the underlying

Re: sync_client problems

2017-05-11 Thread Patrick Boutilier
Try a -G with reconstruct? -G Force re-parsing of the underlying message (checks GUID correctness). Reconstruct with -G should fix all possible individual message issues, including corrupted data files. On 05/11/2017 02:37 PM, Eric Cunningham wrote: I have to walk this back. In

Re: sync_client problems

2017-05-11 Thread Eric Cunningham
I have to walk this back. In looking slightly further back in my logfiles, before every instance of a failure to sync some folder, I see a common error reported prior to every "bailing out! Bad protocol" error - "IOERROR: GUID mismatch /var/spool/cyrus/mail/c/user/cdm-lit/Sent/148." May 11

Re: sync_client problems

2017-05-11 Thread Eric Cunningham
Thanks Bron, but that doesn't seem to work for me, unless I'm missing something. I ran reconstructs for this account on both my master and copy hosts: [cyrus@imap1 ~]$ reconstruct -f -r user.scramer user.scramer user.scramer.Archive user.scramer.Archives user.scramer.Archives.2004 ...

Re: Cyrus imapd and automaticaly purge 3 months old emails only for some user

2017-05-11 Thread Anton Shilov via Info-cyrus
Hi Josef Yes it's possible. You have to use "ipurge -f -d 90 " and any kind of schedooler system Example: crontab 0 2 * * * /usr/lib/cyrus-imapd/ipurge -f -d 90 user.test1 Every day at 2am remove messages older then 90 days for user test1 > > >Hi there, >   is there able to set automatically

Cyrus imapd and automaticaly purge 3 months old emails only for some user

2017-05-11 Thread Josef Karliak
Hi there, is there able to set automatically delete old emails only for some users ? Is an user able to set it or only administrator ? Is there some Imap webclient that can set it ? Thanks and best regards J.Karliak Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info:

Re: sync_client problems

2017-05-11 Thread Bron Gondwana
Looks like you have a corrupted mailboxes database - if you run a reconstruct at each end then it should be fine. Replication won't bail for an actually-doesn't-exist mailbox, but it can't fix broken mailboxes, that's what reconstruct is for. Bron. On Thu, 11 May 2017, at 01:01, Eric