|
Use of this dnsbl is currently free. It may eventually become a commercial service. We haven't figured out yet where the money will come from to support operating the list, but at some point we will either charge a small fee for access to the list or perhaps charge those listed for expedited removal. For now, if you want to use our list, all we require is that you subscribe to list@njabl.org so that you can be kept up to date on any important changes. This moderated list is intended to be a low (nearly zero) traffic mailing list to keep the people using our dnsbl up to date on any important changes or developments. You can subscribe to list@njabl.org by sending an email to list-subscribe@njabl.org. If you would like to discuss anti-spam issues with other interested users of dnsbl.njabl.org, there's antispam@njabl.org. This list was setup to handle traffic tangentially related to njabl.org, but not appropriate for list@njabl.org. You can subscribe by sending an email to antispam-subscribe@njabl.org. Note: Before using any DNSBL, you really ought to be sure you know how to override a listing (locally whitelist an IP) as you may eventually need to receive email from a listed IP. For sendmail users, this can be done in the access db or via this dnswl feature based on sendmail's dnsbl feature. Note: a typo was noticed and fixed (4-29-2004) in this m4 that may have caused m4 to fail with strange errors when building your sendmail.cf. The NJABL.ORG dnsbl zones are currently available in query mode as a dnsbl format DNS zone and can be copied via rsync. Currently, all entries resolve to one of the following:
Currently, the following zones exist:
Starting in 2010, the data from bhnc.njabl.org will be included in combined.njabl.org. If you're using sendmail, edit your sendmail.mc file, and add a line such as: FEATURE(dnsbl,`dnsbl.njabl.org',`Message from $&{client_addr} rejected - see http://njabl.org/lookup?$&{client_addr}')
and/or
FEATURE(dnsbl,`dynablock.njabl.org',`Message from $&{client_addr} rejected - see http://njabl.org/lookup?$&{client_addr}')
or just
FEATURE(dnsbl,`combined.njabl.org',`Message from $&{client_addr} rejected - see http://njabl.org/lookup?$&{client_addr}')
Then rebuild your sendmail.cf and restart sendmail. Note: This syntax is
not available in sendmail versions prior to 8.10.x. For older versions, check to see
if you have the old rbl syntax, or upgrade. Very recent versions of
sendmail support a new feature called enhdnsbl that allows you to specify
which 127.0.0.x result codes you want to take action on and ignore the rest.
If you're using qmail, the following links should be useful: rblsmptd documentation You'll need to get one of the rss patches for either ucspi or rblsmtpd from mail-abuse.org since most of our dial-up entries do not have TXT records. Our dnsbl can also be used to tag potential spam messages (letting individual users decide what action to take) using Spamassassin. After you have Spamassassin properly installed, add the following to your local.cf, probably /etc/mail/spamassassin/local.cf: (note: according to the Spamassassin developers, these rules will only work with Spamassassin up to version 2.5x and will not work properly with Spamassassin >= 2.6x). Also note, NJABL is included in later versions of Spamassassin in its default config. You really shouldn't be running a version of Spamassassin old enough that it lacks NJABL rules...so there's no need to muck about with custom NJABL rules unless you want to change the default scoring or use NJABL zones not in the the default config.
header IN_NJABL_ORG rbleval:check_rbl('njabl','dnsbl.njabl.org.')
describe IN_NJABL_ORG Received via a relay in dnsbl.njabl.org
tflags IN_NJABL_ORG net
header NJABL_OPEN_RELAY rbleval:check_rbl_results_for('njabl', '127.0.0.2')
describe NJABL_OPEN_RELAY DNSBL: sender is Confirmed Open Relay
tflags NJABL_OPEN_RELAY net
header NJABL_DUL rbleval:check_rbl_results_for('njabl', '127.0.0.3')
describe NJABL_DUL DNSBL: sender ip address in in a dialup block
tflags NJABL_DUL net
header NJABL_SPAM_SRC rbleval:check_rbl_results_for('njabl', '127.0.0.4')
describe NJABL_SPAM_SRC DNSBL: sender is Confirmed Spam Source
tflags NJABL_SPAM_SRC net
header NJABL_MULTI_STAGE rbleval:check_rbl_results_for('njabl', '127.0.0.5')
describe NJABL_MULTI_STAGE DNSBL: sent through multi-stage open relay
tflags NJABL_MULTI_STAGE net
header NJABL_CGI rbleval:check_rbl_results_for('njabl', '127.0.0.8')
describe NJABL_CGI DNSBL: sender is an open formmail
tflags NJABL_CGI net
header NJABL_PROXY rbleval:check_rbl_results_for('njabl', '127.0.0.9')
describe NJABL_PROXY DNSBL: sender is an open proxy
tflags NJABL_PROXY net
score IN_NJABL_ORG 0.38
score NJABL_DUL 0.62
score NJABL_MULTI_STAGE 0.75
score NJABL_PROXY 3.00
score NJABL_OPEN_RELAY 3.00
score NJABL_CGI 1.50
score NJABL_SPAM_SRC 3.00
For information on how to use dnsbl format lists with other mail server software, see your documentation, ask your vendor, or search the net. Important notes for "SMTP after POP" or SMTP-Auth setups: |