Gary Mills wrote:
On Thu, Jan 04, 2007 at 07:47:54AM -0500, Ken Murchison wrote:
Gary Mills wrote:
On Wed, Jan 03, 2007 at 08:18:15AM -0500, Ken Murchison wrote:
Gary Mills wrote:
Can I use the old server as both a front end and one of the back ends
for a murder configuration, with the new server as the second back end?
Will that allow me to migrate mailboxes at my convenience? How do I
prevent a port conflict between the IMAP server and the proxy on the
old server?
You'll have to run the frontend + mupdate master on a separate machine.
so the frontend has to run there. Of course, the old IMAP server has
to run there too. Is there not a way to have the old IMAP server listen
on different ports, so that only the frontend connects to it? If not,
could it listen on a secondary IP address only?
It *might* make sense to upgrade the existing server to 2.3.x, since
imapd can both proxy and serve local mailboxes (a "unified" Murder).
Is there any documentation on how to configure and manage a unified
Murder? I couldn't find anything in the 2.3.7 source that described
Bascially build your config using both the backend and frontend
instructions and set mupdate_config:unified
it. In fact, the examples in the documentation still show the proxy
daemons, which no longer exist.
True, but we make hardlinks from proxyd -> imapd, etc so that older
cyrus.conf continue to work as expected.
--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University
----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
