Hi Nicola,
Sorry if I was not clear. As far as I can tell, the problem only occurs
if you run reconstruct as part of your upgrade process (which is not
necessary, and based on this, very much not recommended) Just upgrade
and the index format is upgraded automatically when you access the
mai
Hi Nicola,
Sorry if I was not clear. As far as I can tell, the problem only occurs
if you run reconstruct as part of your upgrade process (which is not
necessary, and based on this, very much not recommended) Just upgrade
and the index format is upgraded automatically when you access the
mai
> Not sure if both servers have the same cyrus version, but we have seen
issues
> where reconstruct did not deal properly with the old format of the cyrus
files
> in the mailboxes when we ran it after converting from 2.0.16 to 2.2.3.
( I
> know others have hit this as well.) I have not researched
Not sure if both servers have the same cyrus version, but we have seen issues
where reconstruct did not deal properly with the old format of the cyrus files
in the mailboxes when we ran it after converting from 2.0.16 to 2.2.3. ( I
know others have hit this as well.) I have not researched the
I'm trasferring mailbox files from one server to another.
When all is done if i do a reconstruct i lose UIDVALIDITY...
If i login in the server user mailbox and *after* i reconstruct UIDVALIDITY
is keeped.
This is a not good behaviour for me, in case i would give e reconstruct -p
from backup.
Ca
