On Wed, Aug 10, 2016 at 12:30:03PM +1000, ellie timoney wrote:
> On Tue, Aug 2, 2016, at 02:14 PM, Kenneth Marshall via Info-cyrus wrote:
> > On Tue, Aug 02, 2016 at 12:34:13PM +1000, Bron Gondwana wrote:
> > > 2.3.2 wasn't version 10, it was version 7! It would have upgra
On Fri, Aug 05, 2016 at 11:11:33AM -0400, Eric W. Bates via Info-cyrus wrote:
> We are migrating our cyrus from a venerable computer to a new one.
>
> We've been gradually moving individuals over to the new machine and are
> quite surprised at the poor performance characteristics we're seeing on
>
On Tue, Aug 02, 2016 at 12:34:13PM +1000, Bron Gondwana wrote:
> 2.3.2 wasn't version 10, it was version 7! It would have upgraded through 8,
> 9, 10 - and maybe you needed to reconstruct to get GUIDs for those versions -
> that sounds familiar.
>
> Bron.
>
Hi Bron,
Is there a way to identif
ges. You need to upgrade
> > > the mailboxes before you can use them for replication. The GUID is used
> > > for replication - if we allowed zero GUIDs, then every message would
> > > deduplicate to the same message!
> > >
> > > On Tue, Aug 2, 2016, at 0
Hi Cyrus Developers,
Thank you for your patch to address the folder move problem between
un-reconstructed mailboxes after the 2.3.16 -> 2.5.9 upgrade. I am
not sure, but it looks like there may be another overly aggressive
check. I keep getting these fatal errors from sync_client:
Aug 1 16:24:16
On Mon, Jul 25, 2016 at 03:53:43PM +1000, ellie timoney wrote:
> I don't have a 2.3.x environment handy to try to reproduce this from the
> outside in, so I'm starting at the error code and working outwards...
>
> > > <1469384361 > > >1469384362>a0080 NO Mailbox format corruption detected
>
> "Ma
On Mon, Jul 25, 2016 at 03:53:43PM +1000, ellie timoney wrote:
> I don't have a 2.3.x environment handy to try to reproduce this from the
> outside in, so I'm starting at the error code and working outwards...
>
> > > <1469384361 > > >1469384362>a0080 NO Mailbox format corruption detected
>
> "Ma
Hi,
I accidentally hijacked another thread. So here is a new message. I am
testing a Cyrus IMAP 2.3.16 to 2.5.9 upgrade and I am having problems
moving messages between folders before the 'reconstruct -V max' has been
run on the mailboxes. Here is the error from the IMAP client:
imap_copy_message
On Sat, Jul 16, 2016 at 12:04:26AM +1000, Bron Gondwana via Info-cyrus wrote:
> On Fri, Jul 15, 2016, at 23:52, Bron Gondwana via Info-cyrus wrote:
> > On Fri, Jul 15, 2016, at 23:46, Andy Dorman via Info-cyrus wrote:
> > > So if the issue apparently lies with twoskip, can we keep our dbs using
>
On Fri, Jul 15, 2016 at 10:34:53PM +1000, Bron Gondwana via Info-cyrus wrote:
> Squatter indexes will be broken without the latest patches on the 2.5 branch.
> The data gets indexed differently, and I had to patch the squatter code to
> search both styles.
>
> Bron.
>
Hi,
Does this problem al
10 matches
Mail list logo
