I was just thinking : Couldn't it be that ctl_mboxlist -u already
created the new mailboxes.db as skiplist ?
I mean, as far as I have understood it, ctl_mboxlist -u creates the
mailboxes.db using the backend defined in /etc/imapd.conf, that is
skiplist if you did not state anything, berkeley if
> I was trying the same procedure here : upgrade problem 2.0.16 Berkeley
> DB 3 to 2.2.12 Berkeley DB 4
>
> I have used the ctl_mboxlist -d to dump the old db3 mailboxes.db file ,
> on the old machine . After a copy to the new
> machine with 2.2.12 Berkeley DB 4, I did a ctl_mboxlist -u., and a ne
I was trying the same procedure here : upgrade problem 2.0.16 Berkeley
DB 3 to 2.2.12 Berkeley DB 4
I have used the ctl_mboxlist -d to dump the old db3 mailboxes.db file ,
on the old machine . After a copy to the new
machine with 2.2.12 Berkeley DB 4, I did a ctl_mboxlist -u., and a new
mailb
Pascal Mouret wrote:
Has anybody got an idea ? Where did I go wrong ? Could it be a result of
running version 2.2.12 cvt_cyrusdb while 2.0.16 is still up ?
Running two different versions (or even having them present on the
system) of BDB libraries is always somewhat a problem. Save yourself
a l
