Enabling IMAP/POP3 daemons

[AQ]

Hi All....

I'd like to ask a few question about IMAP/POP3 daemon. I've installed imap-4.7 on mandrake using RPM and i've uncomment the line on /etc/inetd.conf to open the port 110/143 respectively and restart the inetd. According to man pages, this should be enough to start the daemon, however, I was able to connect to port 143 but can't connect to 110. I've rechecked the /etc/inetd.conf files couple of times, yet couldn't figure out what's wrong with it.
I really appreciated the help or anything that you guys can come up with to solve this problem :)

[BigBlockMopar]

Since you've restarted inetd to no avail, make doubly sure of the path and name that you put into inetd.conf, because if there's a typing error, it won't work, though you should see the messages by tail -f /var/log/messages.

Similarily, if your firewall is closed on POP and/or IMAP ports, the corresponding remote mail client (ie. Eudora, M$ Outcast, etc.) won't be able to connect to the service.

Configuration options okay for the daemon? Command line switches in inetd.conf?

To see whether it's inetd not working right for some reason (ie. not launching it properly), try launching your POP/IMAP server as a daemon from the command line. If you can now connect and get your mail, figure out where you went wrong with inetd.conf.

It's probably best to have the daemon started by inetd, unless you're running a very large traffic mail server, simply for the memory load savings of not having your POP/IMAP hiding in the background at all times. And probably safer, too.

POP/IMAP servers will also need to be setuid to root, since they read and modify different users' mail spools, so it's worthwhile to check that.

:) But try the first thing first.

[ 18 April 2001: Message edited by: BigBlockMopar ]