Config problem

Dwight Tovey dwight at
Sun Feb 1 21:01:43 EST 2004

Christopher Robin said:
> Hi everyone,
> I've been following the Cyrus IMAP Howto, as well as a few posts on this
> list, and have successfully made and installed Cyrus IMAP.  I have run
> into a problem.  According to the Howto, I was supposed to add a couple
> of lines to /etc/inetd.conf.  I'm using RH 9, and am not using INETD.
> So, I thought I could just add a couple of files to /etc/xinetd/.  The
> format of the files, however, is completely different, so I'm not sure,
> if it's working properly.  When I type chkconfig --list, the xinetd
> section shows that imap and pop3 are on, but I'm not sure if that really
> means anything.  When I su cyrus, I was able to complete the set up with
> tools/mkimap, as outlined in the Howto, but when I get to imtest -m
> login -p imap localhost, the connection is refused and the reason given
> is network initialization.  Nothing useful shows up in /var/log/messages
> or /var/adm/imapd.log or /var/adm/auth.log.  Obviously I've missed
> something, but I'm not sure what.  Any pointers in the right direction
> would be greatly appreciated.

I'm no expert on Cyrus (currently in the process of migrating to it), but
a lot of your questions aren't directly Cyrus issues.

First off, you don't need to worry about xinetd.  xinetd is a "super
daemon" that listens on multiple network ports and when a connection
request comes in on that port, it spawns the appropriate daemon to handle
the request.  Cyrus doesn't use it.  Instead it starts it's own daemon to
listen on the imap port and handle the connection requests directly.

Next, chkconfig.  This program helps you manage the daemons that get
started automatically when the system boots.  When you ran the 'chkconfig
--list' command, the xinetd section showed the ports that will be listened
to on the next system boot, not what it is currently listening to.  You
could get xinetd to start listening to those ports without rebooting by
using the command 'service xinetd restart', but as I mentioned above,
Cyrus doesn't want to use xinetd.

If you install using Simon Matter's source RPMs, you should end up with
the script /etc/init.d/cyrus-imapd.  This script can be used to start the
necessary processes at system boot.  You can also start them up without
rebooting by using the command 'service cyrus-imapd start'.  If you didn't
use the Simon's source, you can start the necessary processes with 'master
-d'.  Look at the man page for master(8) for more details.  You will
eventually need to write your own startup script to ensure that the master
process gets kicked off at system boot.  Look at the other scripts in
/etc/init.d for samples.


Dwight N. Tovey
email: dwight at
F u cn rd ths u cnt spl wrth a dm!

More information about the Info-cyrus mailing list