xfer problems between 2.3.15 and 2.4.17

[Andrew Morgan]

On Thu, 5 Jun 2014, gavin.gray at ed.ac.uk wrote:

> As you may be aware we are attempting this and have run into various
> problems.
>
> Currently we have a mixed murder of 2.3.15 backends and 2.4.17 backends.
> We are now fairly confident that we can xfer accounts succesfully between
> these backends. The problems we had appear to have been with a very small
> number of accounts on our older backends that had corrupt cyrus.index
> files.
>
> However we are now having trouble configuring frontends that will work
> with this mixed murder environment while we xfer our users accross.
>
> If we use our existing 2.3.15 frontends then users have who have been
> migrated lose the ability to see other accounts in the "Other Users" name
> space.
>
> On the other hand if we introduce 2.4.17 frontends then we see strange
> behaviour around folder creation. Clients can create the folders but
> autosubscription fails with the client being told the new folder doesn't
> exist. If one waits a minute or two one can manually subscribe to the
> folder.

This is tickling my memory, but I can't recall exactly what it was.  I 
remember running into a problem like this as well.  Something about the 
frontend's mailbox database not being updated in a timely fashion...

> So far we have not upgraded the mupdate master. Is this a mistake?
>
> In terms of the frontend config we have added
>
> suppress_capabilities: ESEARCH QRESYNC WITHIN XLIST LIST-EXTENDED
>
> to the 2.4.17 frontends, otherwise the config is identical to our 2.3.15
> frontends. Is there any other config changes we should be aware of?

I used the following when I upgraded from 2.3 to 2.4:

   suppress_capabilities: ESEARCH LIST-EXTENDED QRESYNC WITHIN XLIST ENABLE SORT=DISPLAY

There was a thread I started back in October 2011 with the subject "2.3 to 
2.4 Murder upgrade" where I ran through the upgrade and the workarounds I 
had to make.

 	Andy