Hello Mike We recently change to dbmail 2.1.1 because we were having connection time out and %cpu up to 99%
With this new installation %cpu was reduced between 50%-80% but we still having connections time, dbmail-imapd drop connection, or queries time out to mysql. This should be a dbmail-imapd bug, dbmail.conf configuration parameters, mysql problems or postfix problems. If you have any idea please let me know Thanks, Humberto " I notice that we have a lot of messages queued and we now need to flush postfix to everything can start working perfectly" CentOS 4.0 kernel 2.6.x CPU Intel Pentium 4 1.6 GHZ MySQL 4.1.10 with InnoDB support We have like about 80 - 90 users running outlook or squirrelmail most of the time Configuration [POP] EFFECTIVE_USER=dbmail # the user that dbmail-pop3d will run as (need to be root to bind to a port<1024) EFFECTIVE_GROUP=dbmail # the group that dbmail-pop3d will run as BINDIP=* # the ipaddress the dbmail-pop3d server has to bind to, * for all addresses PORT=110 # the port number the dbmail-pop3d server has to bind to. NCHILDREN=10 # default number of POP3 handlers (each is a process) MAXCHILDREN=100 # mac. number of POP3 handlers MINSPARECHILDREN=2 MAXSPARECHILDREN=4 MAXCONNECTS=10000 # the maximum number of connections a default childs makes TIMEOUT=4000 # the time (s) before the dbmail-pop3d should shutdown a connection which is being idle. RESOLVE_IP=no # if yes, the pop daemon resolves IP numbers to DNS names in the log POP_BEFORE_SMTP=yes TRACE_LEVEL=1 [IMAP] EFFECTIVE_USER=dbmail EFFECTIVE_GROUP=dbmail BINDIP=* PORT=143 NCHILDREN=25 MAXCHILDREN=100 # mac. number of IMAPD handlers MINSPARECHILDREN=2 MAXSPARECHILDREN=4 MAXCONNECTS=10000 # the maximum number of connections a default childs makes TIMEOUT=4000 # the time (s) before the dbmail-imapd should shutdown a connection which is being idle. RESOLVE_IP=no # if yes, the imap daemon resolves IP numbers to DNS names in the log IMAP_BEFORE_SMTP=yes TRACE_LEVEL=1
