Further question,
Since the *combined.njabl.org*: dnsbl.njabl.org and dynablock.njabl.org
in a single zone is what you get....
and :
With the advent of Spamhaus's PBL (http://spamhaus.org/pbl/),
dynablock.njabl.org has become obsolete. Rather than maintain separate
similar DNSBL zones, NJABL will be working with Spamhaus on the PBL.
Effective immediately, dynablock.njabl.org exists as a copy of the
Spamhaus PBL. After dynablock users have had ample time to update their
configurations, the dynablock.njabl.org zone will be emptied.
Would it be wise to tell SA not to check combined.njabl.org? And just
look at dydns.njabl.org only?
THANKS!
Vasiliy Boulytchev
[EMAIL PROTECTED]
Vasiliy Boulytchev wrote:
Excellent,
Now we are in the right direction.
Now. I use the NJABL-provided rsync syntax to sync...
$ cat /usr/local/bin/njablrsync
#!/bin/sh
rsync -vaL rsync.njabl.org::njabl/rbldnsd/ /var/dnsbl/njabl/
which provides me with:
ls /var/lib/rbldns/work/
bhnc.gz dnsbl.njabl.org.data
rbldns.dynablock.easynet.nl
dnsbl.njabl.org.auto dnsbl.njabl.org.generic README
How come am I not getting the combined? And so how do I set SA to use
my current dnsbl.njabl.org,
THANKS!
Vasiliy Boulytchev
[EMAIL PROTECTED]
Theo Van Dinter wrote:
On Wed, Jan 24, 2007 at 11:46:28AM -0500, Vasiliy Boulytchev wrote:
be tested via dig @dnscacheserver 2.0.0.127.dnsbl.njabl.org... i see
[...]
Can someone please help me setup NJABL properly? I am invoking SA
via MS... as you can see below, SA does seem to check NJABL...
[...]
[15101] dbg: dns: checking RBL combined.njabl.org., set
njabl-lastexternal
[15101] dbg: dns: checking RBL combined.njabl.org., set njabl
SpamAssassin is looking for combined.dnsbl.org. You've setup your
servers to
deal with dnsbl.njabl.org, which is different, and so won't be used.
