I suppose you could continue to use rblsmtpd/blacklists, and simply not specify any check-dnsrbl parameters in spamdyke. I haven't tried it, but in theory it should work. The end result would be the same either way.
However, assuming that rblsmtpd and spamdyke are equally efficient at processing RBLs (which is not necessarily a good assumption), letting spamdyke do the rbl processing would be (slightly) more efficient, as there would be one less process and pipe to pass the data through. slamp slamp wrote: > no i didnt qtp. i wanted to make the manual changes so i know what > files are getting changed instead of qtp doing it. thanks for shedding > the light this. now is there a downside to using the old rblsmtpd > compare to spamdyke? wouldn't it lessen the work for spamdyke since > the soul purpose of rblsmtpd is to do just that, check for dns rbls. > > On Sat, May 3, 2008 at 10:49 AM, Eric Shubert <[EMAIL PROTECTED]> wrote: >> The old RBLSMTPD is doing the lookup before passing it on to spamdyke, so >> spamdyke is never receiving it. You need to remove "$RBLSMTPD $BLACLISTS" to >> disable the toaster's stock blacklist processing. >> >> You didn't use qtp-install-spamdyke, did you? It would have modified your >> run file to look like this: >> >> #!/bin/sh >> QMAILDUID=`id -u vpopmail` >> NOFILESGID=`id -g vpopmail` >> MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` >> SPAMDYKE="/usr/local/bin/spamdyke" >> SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf" >> SMTPD="/var/qmail/bin/qmail-smtpd" >> >> TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb" >> >> HOSTNAME=`hostname` >> VCHKPW="/home/vpopmail/bin/vchkpw" >> REQUIRE_AUTH=0 >> >> exec /usr/bin/softlimit -m 20000000 \ >> /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \ >> -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \ >> $SPAMDYKE --config-file $SPAMDYKE_CONF \ >> >> $SMTPD $VCHKPW /bin/true 2>&1 >> >> I think that's a little cleaner than burying spamdyke in $SMTPD as you have >> done. If you use the above run script, be sure to change /etc/spamdyke to >> /etc/mail, or move your spamdyke.conf file appropriately. >> >> >> >> >> slamp slamp wrote: >> > I have a question. I have the line below in my config. >> > >> > check-dnsrbl=zen.spamhaus.org >> > >> > So spamdyke should check if the sender is listed correct? and it >> > should never need to pass the traffic to qmail? >> > >> > My observation so far seems that spamdyke is not doing this and my >> > qmail install (qmailtoaster) is still doing the dns rbl checking. >> > >> > My qmail smtp log says this: >> > >> > 2008-05-03 10:27:50.146011500 rblsmtpd: 201.12.53.18 pid 27047: 451 >> > http://www.spamhaus.org/query/bl?ip=201.12.53.18 >> > >> > And nothing in the corresponding spamdyke maillog. >> > >> > log-level=2 >> > >> > >> > smtp run file. >> > >> > #!/bin/sh >> > QMAILDUID=`id -u vpopmail` >> > NOFILESGID=`id -g vpopmail` >> > MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` >> > BLACKLIST=`cat /var/qmail/control/blacklists` >> > SMTPD="/usr/bin/spamdyke -f /etc/mail/spamdyke.conf >> /var/qmail/bin/qmail-smtpd" >> > TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb" >> > RBLSMTPD="/usr/bin/rblsmtpd" >> > HOSTNAME=`hostname` >> > VCHKPW="/home/vpopmail/bin/vchkpw" >> > REQUIRE_AUTH=0 >> > >> > exec /usr/bin/softlimit -m 20000000 \ >> > /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \ >> > -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \ >> > $RBLSMTPD $BLACKLIST $SMTPD $VCHKPW /bin/true 2>&1 >> > _______________________________________________ >> > spamdyke-users mailing list >> > [email protected] >> > http://www.spamdyke.org/mailman/listinfo/spamdyke-users >> >> >> -- >> -Eric 'shubes' >> _______________________________________________ >> spamdyke-users mailing list >> [email protected] >> http://www.spamdyke.org/mailman/listinfo/spamdyke-users >> > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users -- -Eric 'shubes' _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
