Nick Leverton wrote:
I'm running it on pperl with tcpserver, and I wouldn't recommend pperl.
That's odd, since I am running the same way, yet I don't have problems (usually). Can you tell if the service is restarting? Are you being very generous with RAM through softlimit?
Here's my modified run script (based closely on what qmail-conf uses):
#!/bin/sh
exec 2>&1 \
envdir ./env \
sh -c '
case "$REMOTENAME" in h) H=;; p) H=p;; *) H=H;; esac
case "$REMOTEINFO" in r) R=;; [0-9]*) R="t$REMOTEINFO";; *) R=R;; esac
exec \
envuidgid qmaild \
softlimit ${DATALIMIT+"-d$DATALIMIT"} \
/usr/local/bin/tcpserver \
-vDU"$H$R" \
${LOCALNAME+"-l$LOCALNAME"} \
${BACKLOG+"-b$BACKLOG"} \
${CONCURRENCY+"-c$CONCURRENCY"} \
-xtcp.cdb \
-- "${IP-0}" "${PORT-25}" \
pperl -Tw -- --prefork=$MAXCLIENTS --maxclients=$MAXCLIENTS \
--no-cleanup ./qpsmtpd 2>&1
'And I have the following env/* files defined
env/DATALIMIT:25000000 env/IP:12.38.22.1 env/LOCALNAME:a.mx.rlpgbooks.com env/MAXCLIENTS:10 env/MAXFILESIZE:1000000 env/PORT:25
It does cope well with over three thousand actual messages per hour though (plus an extra 5500 connections rejected somewhere between HELO and RCPT), and I'm very happy with qpsmtpd itself.
Me too!
John
