Dan,

It sure sounds to me like cyradm is favoring the alias ip for some odd reason that probably has to do with your machine more than cyradm. When you shut down Citadel and change cyrus.conf to simply 'listen="imap", then cyrus is listening on all available addresses and that solves the problem but not the way you want. May I suggest you user the --server <server> argument when you invoke cyradm. That way you control exactly what server address it's going to.

-- Rob

On 03/01/2006 05:46 PM, Dan O'Brien wrote:
I've got 2 different IMAP servers running on the same hardware (Cyrus IMAPd 2.2.10 and Citadel 6.72). Citadel is bound to one IP address (an alias on a single physical adapter). I've got entries in my cyrus.conf file

        SERVICES {
imap cmd="imapd" listen="192.168.224.105:imap" prefork=2 imaps cmd="imapd -s" listen="192.168.224.105:imaps" prefork=1
        ...
        }

When I try to use cyradm, I get the message:
cyradm: cannot connect to server If I shut down Citadel, and change cyrus.conf to listen="imap", I can use cyradm with no problem.

I tried to update the cyrus.conf file with the loopback address, but cyradm still doesn't work. I can telnet to port 143 on the loopback, 105 and 101 (Citadel) with appropriate responses.

        SERVICES {
imap cmd="imapd" listen="192.168.224.105:imap" prefork=2
        imapx   cmd="imapd"             listen="127.0.0.1:imap" prefork=2
imaps cmd="imapd -s" listen="192.168.224.105:imaps" prefork=1
        imapsx  cmd="imapd -s"          listen="127.0.0.1:imaps" prefork=1
        ...
        }

I'm guessing this is something simple I'm missing, but I'm stumped.

Thanks in advance,
Dan O'Brien

----
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

----
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Reply via email to