On Tuesday, March 25, 2003, at 01:34 PM, Jason 'XenoPhage' Frisvold wrote:

I'm a little confused concerning my "toaster" setup...  I have the
following in my /var/qmail/supervise/qmail-smtpd/run file :

#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
exec /usr/local/bin/softlimit -m 6000000 \
    /usr/local/bin/tcpserver -v -H -R -l 0 \
    -x /etc/tcp.smtp.cdb -c "$MAXSMTPD" \
    -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
    /usr/local/bin/rblsmtpd -rlist.dsbl.org -rmultihop.dsbl.org \
    /var/qmail/bin/qmail-smtpd domain.com \
    /usr2/vpopmail/bin/vchkpw /bin/true 2>&1


I don't understand the items after the qmail-smtpd command... Can anyone explain what that is intended to do?

From the patched qmail-smtpd man page:


       qmail-smtpd can accept LOGIN,  PLAIN,  and  CRAM-MD5  AUTH
       types.   It  invokes  checkprogram,  which  reads  on file
       descriptor 3 the username, a 0 byte, the password or chal¡Z
       lenge  derived  from  hostname, another 0 byte, a CRAM-MD5
       response (if applicable to the AUTH type), and a  final  0
       byte.   checkprogram  invokes  subprogram  upon successful
       authentication, which should in turn return  0  to  qmail-
       smtpd,   effectively  setting  the  environment  variables
       RELAYCLIENT and TCPREMOTEINFO (any supplied value replaced
       with the authenticated username).  qmail-smtpd will reject
       the authentication attempt if it receives a nonzero return
       value from checkprogram or subprogram.

Bill Shupp



Reply via email to