Re: Migration issue with seen/subscription/sieve databases

2020-01-02 Thread Gionatan Danti
Il 02-01-2020 00:01 ellie timoney ha scritto: I think, in that case, you should be fine! It wasn't clear if your installation had only ever been 2.3, or had previously been upgraded to 2.3 from some earlier version in the past, so I thought I'd better point it out just in case :) Cheers,

Re: Migration issue with seen/subscription/sieve databases

2020-01-01 Thread ellie timoney
On Mon, Dec 30, 2019, at 8:59 PM, Gionatan Danti wrote: > Are you referring to the problem described here [1]? If so, from the > linked page I read: > "Versions of 3.0 prior to 3.0.11 contained a bug (Issue #2839) that > could lead to loss of seen state/flags during reconstruct for some >

Re: Migration issue with seen/subscription/sieve databases

2019-12-30 Thread Gionatan Danti
Il 30-12-2019 01:51 ellie timoney ha scritto: You're both right. Since 2.4ish (?? MAILBOX_MINOR_VERSION=12, anyway), a user's seen status on their own mailboxes is stored in the mailbox index. But the separate userid.seen database is still used for storing their seen state on mailboxes that

Re: Migration issue with seen/subscription/sieve databases

2019-12-29 Thread ellie timoney
On Fri, Dec 27, 2019, at 11:40 PM, Gionatan Danti wrote: > Il 27-12-2019 04:07 Scott Lambert ha scritto: > > Didn't the seen status database get moved from it's own file to the > > message index database for 3.x?  I'm not running 3.x yet but think I > > remember seeing something about that. > >

Re: Migration issue with seen/subscription/sieve databases

2019-12-27 Thread Gionatan Danti
Il 27-12-2019 04:07 Scott Lambert ha scritto: Didn't the seen status database get moved from it's own file to the message index database for 3.x?  I'm not running 3.x yet but think I remember seeing something about that. Hi, from what I read here [1], and from my experience when testing the

Re: Migration issue with seen/subscription/sieve databases

2019-12-26 Thread Scott Lambert
On 12/24/19 1:52 AM, Gionatan Danti wrote: On 23/12/19 18:28, Patrick Boutilier wrote: Only thing I can think of is that a different config file is actually being used? Hi Patrick, I double-checked my config and it seems the same (within the limits imposed by the Cyrus version change). If

Re: Migration issue with seen/subscription/sieve databases

2019-12-24 Thread Gionatan Danti
On 23/12/19 18:28, Patrick Boutilier wrote: Only thing I can think of is that a different config file is actually being used? Hi Patrick, I double-checked my config and it seems the same (within the limits imposed by the Cyrus version change). If seems to me that when default for

Re: Migration issue with seen/subscription/sieve databases

2019-12-23 Thread Patrick Boutilier
On 12/23/19 7:04 AM, Gionatan Danti wrote: On 20/12/19 09:51, Gionatan Danti wrote: Hi all, I am tasked to migrate an old cyrus 2.3.x CentOS6 installation to a new CentOS8 server with cyrus 3.0.7. I'm following the instructions at https://cyrusimap.org/imap/download/upgrade.html

Re: Migration issue with seen/subscription/sieve databases

2019-12-23 Thread Gionatan Danti
On 20/12/19 09:51, Gionatan Danti wrote: Hi all, I am tasked to migrate an old cyrus 2.3.x CentOS6 installation to a new CentOS8 server with cyrus 3.0.7. I'm following the instructions at https://cyrusimap.org/imap/download/upgrade.html (compresive of berkeley db format change to skiplist)

Migration issue with seen/subscription/sieve databases

2019-12-20 Thread Gionatan Danti
Hi all, I am tasked to migrate an old cyrus 2.3.x CentOS6 installation to a new CentOS8 server with cyrus 3.0.7. I'm following the instructions at https://cyrusimap.org/imap/download/upgrade.html (compresive of berkeley db format change to skiplist) and all is mostly working, except for some