Chris,
I loaded a stock QMT install, and in /var/qmail/supervise/smtp/run, it has the
line:
BLACKLIST=`cat /var/qmail/control/blacklists`
Which is used by SMTP before SPAMDYKE is called:
exec /usr/bin/softlimit -m 64000000 \
/usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
-u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
$RBLSMTPD $BLACKLIST \
$SPAMDYKE --config-file $SPAMDYKE_CONF \
$SMTPD $VCHKPW /bin/true 2>&1
I would think you could use either blacklists in /var/qmail/control/ or the
spamdyke config. Either should work... Using RBL to block it might be
faster/less load on the server than waiting for SpamDyke to startup, but either
way will work.
And for blacklist in /var/qmail/control/blacklists, mine is:
-r b.barracudacentral.org -r bl.spamcop.net -r zen.spamhaus.org -r
cbl.abuseat.org -r dul.dnsbl.sorbs.net
Note: to use barracudacentral, you must sign up with them and give them your IP
address to allow access. So don't Copy/Paste this unless you're signed up with
barracuda. It is free, and barracuda only blocks KNOWN/HARD spammers.
In either case, you would see the blocks in the /var/log/qmail/smtp/current [or
other files in that area].
Carl
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
