Check maillog and see if spamdyke it's working.
Here's an example, i hope it helps you.
May 4 14:44:16 v1ps spamdyke[19462]: INFO: querying
212.84.112.59.in-addr.arpa with DNS server 206.212.246.2:53 (attempt 1)
May 4 14:44:16 vps spamdyke[19463]: INFO: querying
212.84.112.59.in-addr.arpa with
Eric Shubert wrote:
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
On Sun, May 04, 2008 at 10:01:45AM -0700, Eric Shubert wrote:
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.
It does work.
rblsmtpd isn't any more (or less) efficient at checking DNS RBLs than
spamdyke but there are several reasons not to use both. First, in terms
of efficiency, spamdyke will check other (faster) filters before it
performs the DNS RBL checks. If the connection is going to be rejected
for some
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)
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
