experience report / upgrading to cyrus-imapd 2.3

[Andreas S. Kerber]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

JFYI, replying to my own mail:

I've just upgraded the below mentioned backend to 2.3.8. The acl compatibilty issues have been fixed just fine. The new 2.3 backend within the existing 2.1 murder works great now.

Since I have some uppercase mailboxes though, I had to set "username_tolower: 0" to make things working.



On Thu, Sep 14, 2006 at 05:45:53PM +0200, Andreas S. Kerber wrote:
> Hi,
> 
> currently we have a murder with 2 frontends, 3 backends and mupdate
> running on one of the backends (all running cyrus-imapd 2.1.x).
> 
> Today I've added a new backend which is running 2.3.7 and it went suprisingly
> well. Moving mailboxes between the old and the new backends, lmtp delivery, imap
> and pop3 access worked immediatly and without any problems.
> 
> The only problems I've found so far are these:
> 
> - "kick_mupdate: can't connect to target: No such file or directory" messages in the
> logfile whenever one enteres a mailbox with imap (not when using pop3).
> 
> - the transfered sieve script did not work reliable (sieve runtime error for .*: Not a bytecode file). uploading it again fixed this.
> 
> - deletion of messages via imap does not work through the old frontends, possibly due to the
> new ACL code in 2.3 which offers separate rights for message delete, mailbox delete, and expunge.
> The only way to fix this seems upgrading the frontends as well. Can anyone confirm this
> or has another idea how to fix this?
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFFyvHkP0gnkXA27R8RAl3SAJ9xFaFnVE5YNFOKbR8w/ilKzASVLwCgi5Bv
r3kRMA4HyTIFp88I5mbJIMM=
=qDRj
-----END PGP SIGNATURE-----