I am in the process of upgrading our cyrus aggregation from 2.2.12 to
2.3.16. I have installed cyrus 2.3.16 on a new back-end server, and it
appears fine. I can create accounts on the server, read email from
them, etc.
Now I am attempting to place the new back-end server into our
aggregation
Additional information. Recall that:
> I am in the process of upgrading our cyrus aggregation from 2.2.12 to
> 2.3.16. I have installed cyrus 2.3.16 on a new back-end server, and it
> appears fine. I can create accounts on the server, read email from
> them, etc.
>
> Now I am attempting to p
Maybe you need to upgrade the mupdate master to 2.3.16 first?
Andy
On Thu, 7 Oct 2010, Michael D. Sofka wrote:
> Additional information. Recall that:
>
>> I am in the process of upgrading our cyrus aggregation from 2.2.12 to
>> 2.3.16. I have installed cyrus 2.3.16 on a new back-end ser
I thought the procedue is to upgrade the back-end servers first.
Mike
"Andrew Morgan" wrote:
>Maybe you need to upgrade the mupdate master to 2.3.16 first?
>
> Andy
>
--
Michael D. Sofka
Sr. Systems Programmer
Communications & Middleware Technologies
Cyrus Home Page: http://www.cyrus
Michael D. Sofka wrote:
>
> Trying this on the 2.3.16 server, built from Simon Matter's source RPM
> on a RE5 server I get:
>
> Hacker[901]:mupdatetest -v -p 3905 -a g_murder imap-fe1.server.rpi.edu
> S: * AUTH "LOGIN" "PLAIN"
> S: * STARTTLS
> S: * PARTIAL-UPDATE
> S: * OK MUPDATE "imap-fe1.ser
