On Wed, 2005-04-13 at 09:14 -0700, Carl Parrish wrote: > When using the toaster should something called couriertcpd be running?
Not if you want to use the qmail-pop3d service it shouldnt. > when I run vpopmailctl stat I get > > /service/qmail-pop3d: up (pid 21698) 0 seconds > /service/qmail-pop3d/log: up (pid 10372) 20751 seconds > /service/qmail-pop3ds: up (pid 21769) 0 seconds > /service/qmail-pop3ds/log: up (pid 10469) 20751 seconds > > so I ran vpopmailctl starttl start > Starting qmail-pop3d > Starting qmail-pop3ds > > > then check out my log > tail -f /var/log/qmail/pop3d/current > @40000000425d449d2442ad3c tcpserver: fatal: unable to bind: address > already used > @40000000425d449e2636dc1c tcpserver: fatal: unable to bind: address > already used > @40000000425d449f2af8c544 tcpserver: fatal: unable to bind: address > already used > @40000000425d44a02a46e234 tcpserver: fatal: unable to bind: address > already used > > So I'm thinking I must still have something running that's preventing > vpopmail from doing its thing. > > netstat -a -p --tcp | fgrep php gives me > tcp 0 0 *:pop3s *:* > LISTEN 6468/couriertcpd > tcp 0 0 *:pop3 *:* > LISTEN 5600/couriertcpd > > So now I'm not sure if couriertcpd *should* be running or if that should > say vpopmail. If you stop the courier pop daemon, then tcpserver will be able to grab the port and it should start answering immediately. I stuck with the qmail-pop3d as i found it to be less resource intensive then couriers, though not much. I also prefer having it running under supervise. Shane
