Cyrus-imapd status update

[Sven Mueller]

Henrique de Moraes Holschuh wrote:
> On Sat, 16 Jan 2010, Dan White wrote:
>> What can I do to help?
> 
> In the 2.3 side, we need a sane way to not utterly break any systems running
> 2.2 that get upgraded to 2.3.  There are threads about it in the archives
> for this ML...  note that it is not just Cyrus, berkeley DB upgrade of the
> databases might need to be handled (or not, it is an open question).

For the record:
I changed all the databases cyrus-imapd has in 2.2 to use BerkeleyDB,
ran the latest (4.7 it was at the time, I think) update-tool from
BerkeleyDB on them and compared them to the backup I had. Not a single
one of them changed in size or content (not even a single byte changed).
So I think we don't need to care for the BerkeleyDB upgrade at all.

Oh, and despite just having "upgraded" all its Berkeley Databases to a
newer version, my cyrus-imapd-2.2 installation was still happy with all
of them, working without flaw.

I also didn't see any mandatory (or even default) layout changes in the
directory structure or anything else which 2.3 would change
automatically on the mail store.

I even took the 2.3 packages we currently have in experimental, ran them
on my 2.2 setup (actually, I needed to "backport" our 2.3 version to
etch for this) and downgraded back to 2.2. No errors seen.

Mind you though that I have a pretty plain setup, especially I don't use
murder, just a plain local storage, squatter and lmtp via IP (not socket).

Regards,
Sven