Updating front-end and master server

[Lucas Zinato Carraro]

Another issue is:

-  Frontend with  2.3.16
-  Backend with 2.4
-  And a account in this backend accesing a shared mailbox
in another backemd with cyrus 2.3.16


The shared  imap mailbox  appears with  a \Noselect flag.
And normally this means the folder can contain child folders, but not messages.


With:

-  Frontend with  2.4
-  Backend with 2.4
-  And a account in this backend accesing a shared mailbox
in another backemd with cyrus 2.3.16

no problem.


My sugestion is  upgrade  MUPDATE first , Frontends after  and
Backends at the end.

Zinato






On Wed, Nov 24, 2010 at 9:03 PM, Bron Gondwana <brong at fastmail.fm> wrote:
> On Wed, Nov 24, 2010 at 11:20:46AM -0500, Michael D. Sofka wrote:
>> Is there a preferred order for updating the Cyrus master and front-end
>> servers?  The back-end servers are all upgraded from 2.2.12 to 2.2.16.
>> Should the master be upgraded before or after the front-end servers?
>>
>> Also, is it possible to run with a mixture of 2.2.12 and 2.3.16
>> front-end servers?
>
> Oh so ancient!  It should be OK, but you might hit issues with more
> recent frontends than backends if the frontends advertise capabilities
> that the backends don't support.  We saw this just the other day with
> a site with 2.4.4 frontends and 2.3.16 backends, where the frontends
> advertised the ESEARCH capability and iPhones got sad when their
> perfectly reasonable searches were rejected!
>
> Bron.
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
>