Is there some specific reason for using qmail own pop3 daemon for plain
pop3 (and courier implementation for pop3-ssl, imap, imap-ssl)?
The courier version is way more verbose about users who's logging in and
also return bandwith usage and time spent. I just converted the pop3 to
use courier binaries [/usr/sbin/pop3login, /usr/bin/pop3d] to do the job
instead of [/var/qmail/bin/qmail-popup, /var/qmail/bin/qmail-pop3d].
This will also give consistent logformat across all 4 services.
The new run script would be:
#!/bin/sh
HOSTNAME=`hostname --fqdn`
rm -rf ./env/*;
cat /etc/courier/pop3d | /usr/bin/envconv
exec /usr/bin/envdir ./env/ \
/usr/bin/softlimit -m 24000000 \
/usr/bin/tcpserver -v -R -H -l $HOSTNAME 0 110 \
/usr/sbin/pop3login \
/usr/bin/pop3d Maildir 2>&1
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
