Re: upgrading with murder/aggregator
Ken Murchison <[email protected]>
| Newsgroups | gmane.mail.imap.cyrus |
|---|---|
| Organization | Carnegie Mellon University |
| Message-ID | <[email protected]> |
On 03/15/2017 02:02 PM, Patrick Hennessy wrote: > We are looking to migrate from a 2.3.7 server to a 2.4.18 server. I was > hoping to set up the cyrus murder/aggregator and move the existing > server behind that. While doing some reading and research, I came > across the following mailing list thread. I was wondering if it's still > the case that the frontend needs to be the same version as the older > backend? > > https://lists.andrew.cmu.edu/pipermail/info-cyrus/2010-May/033061.html Yes, it is still the case that a newer frontend may try to proxy commands to an older backend that it does not understand/support. As a result, backends are usually upgraded before the frontends. > Aside from the compatibility between frontend and backend, there was > also a comment about having to recompile the sieve filters per the other > post below. Is that still the case moving from 2.3.7 to 2.4.18? Are > there any other gotchas to look out for? > > https://lists.andrew.cmu.edu/pipermail/info-cyrus/2010-May/033056.html Sieve scripts compiled with 2.3 *should* be compatible with 2.4. There is no mention of recompiling in the upgrade notes. > Thanks in advance, > > Pat > ---- > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus -- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus