On onsdag, nov 6, 2002, at 10:20 Europe/Stockholm, Jeremy Shaffner wrote:
Did that, but:On Wed, Nov 06, 2002 at 09:19:09AM +0100, Carl-Johan Kihlbom wrote:No. If you installed via Ports then you should have two startup scriptsHello!I've installed Courier-IMAP from ports on my FreeBSD system. But when I try to connect all I get is this: $ telnet localhost 143 Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused telnet: Unable to connect to remote host I'm guessing this is a problem with inetd. That should I put in inetd.conf?
in /usr/local/etc/rc.d. They are installed witih a .sample suffix.
Remove the suffix and run '/usr/local/etc/rc.d/courier-imap-imapd.sh
start' and '/usr/local/etc/rc.d/courier-imap-pop3d.sh start'. They'll
also be run at boot automatically.
/usr/local/etc/rc.d]$ sudo ./courier-imap-imapd.sh start
.: Can't open /usr/local/etc/courier-imap/imapd-ssl: No such file or directory
What's that about? I don't want to use ssl. Not yet anyway
These scripts setup the environment and start the auth daemons and the imapd and pop3d daemons using couriertcpd, which is part of Courier..
So the imap and pop should be commented out in inetd.conf?
Hehe, I did install via Ports.If you didn't install via Ports, then whasamattayou?
/ CJ
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
