Hi there,

i'm running a little courier pop3 server for 7 users. My problem is that every time they connect to the server, a new courierpop3login process is opened that gets never closed!

Of course $maxprocs is very soon reached and they cannot connect.

I set $maxprocs temporary very high so they can login. My process list gathers hundreds of lines like this (ps axu): USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 16101 0.0 0.0 1616 412 ? S 16:40 0:00 /usr/lib/courier/courier/courierpop3login /usr/lib/courier/courier/courierpop3d Maildir

Logfile looks like this: Dec 4 16:22:23 www courierpop3login: Connection, ip=[::ffff:x.x.x.x] Dec 4 16:22:23 www courierpop3login: Connection, ip=[::ffff:x.x.x.x] Dec 4 16:22:23 www courierpop3login: LOGIN, user=web2p2, ip=[::ffff:x.x.x.x] Dec 4 16:22:23 www courierpop3login: LOGOUT, user=web2p2, ip=[::ffff:x.x.x.x], top=0, retr=0, rcvd=12, sent=39, time=0

There is a LOGOUT but the process does not get killed.

Server is Debian 4.0 with the following courier packages: ii courier-authda 0.58-4 Courier authentication daemon ii courier-authli 0.58-4 Courier authentication library ii courier-authli 0.58-4 userdb support for the Courier authenticatio ii courier-base 0.53.3-5 Courier Mail Server - Base system ii courier-imap 4.1.1.20060828 Courier Mail Server - IMAP server ii courier-pop 0.53.3-5 Courier Mail Server - POP3 server

Client: Outlook 2003 :-(

My config files:

/etc/courier/pop3d PIDFILE=/var/run/courier/pop3d.pid # Workaround :-( MAXDAEMONS=300 MAXPERIP=300 POP3AUTH="" POP3AUTH_ORIG="PLAIN LOGIN CRAM-MD5 CRAM-SHA1 CRAM-SHA256" POP3AUTH_TLS="" POP3AUTH_TLS_ORIG="LOGIN PLAIN" POP3_PROXY=0 PORT=110 ADDRESS=0 TCPDOPTS="-nodnslookup -noidentlookup" LOGGEROPTS="-name=pop3d" POP3DSTART=YES MAILDIRPATH=Maildir

/etc/courier/authdaemonrc authmodulelist="authpam" authmodulelistorig="authuserdb authpam authpgsql authldap authmysql authcustom authpipe" daemons=10 authdaemonvar=/var/run/courier/authdaemon DEBUG_LOGIN=1 DEFAULTOPTIONS="" LOGGEROPTS=""