Bug 6932 - SA is using an RBL, which is closing down
Summary: SA is using an RBL, which is closing down
Status: RESOLVED DUPLICATE of bug 6913
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL: http://dnsbl.njabl.org/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-29 10:26 UTC by wyrm.white
Modified: 2013-05-07 17:35 UTC (History)
3 users (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description wyrm.white 2013-04-29 10:26:07 UTC 
Spamassassin uses dnsbl.njabl.org, but dnsbl.njabl.org is empty and is going to close down for good very soon (visit their site for proofs).
All notices of this RBL should be erased from SA rules.
Comment 1 AXB 2013-04-29 10:37:08 UTC 
See bug 6913
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6913

Run sa-update

*** This bug has been marked as a duplicate of bug 6913 ***
Comment 2 wyrm.white 2013-05-07 08:36:56 UTC 
No, SA still tries to use njabl

/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:header __RCVD_IN_NJABL                eval:check_rbl('njabl', 'combined.njabl.org.')
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:describe __RCVD_IN_NJABL      Received via a relay in combined.njabl.org
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:tflags __RCVD_IN_NJABL                net
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:header RCVD_IN_NJABL_RELAY    eval:check_rbl_sub('njabl', '127.0.0.2')
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:describe RCVD_IN_NJABL_RELAY  NJABL: sender is confirmed open relay
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:tflags RCVD_IN_NJABL_RELAY    net
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:header RCVD_IN_NJABL_SPAM     eval:check_rbl_sub('njabl', '127.0.0.4')
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:describe RCVD_IN_NJABL_SPAM   NJABL: sender is confirmed spam source
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:tflags RCVD_IN_NJABL_SPAM     net
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:header RCVD_IN_NJABL_MULTI    eval:check_rbl_sub('njabl', '127.0.0.5')
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:describe RCVD_IN_NJABL_MULTI  NJABL: sent through multi-stage open relay
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:tflags RCVD_IN_NJABL_MULTI    net
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:header RCVD_IN_NJABL_CGI      eval:check_rbl_sub('njabl', '127.0.0.8')
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:describe RCVD_IN_NJABL_CGI    NJABL: sender is an open formmail
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:tflags RCVD_IN_NJABL_CGI      net
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:header RCVD_IN_NJABL_PROXY    eval:check_rbl_sub('njabl', '127.0.0.9')
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:describe RCVD_IN_NJABL_PROXY  NJABL: sender is an open proxy
/var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:tflags RCVD_IN_NJABL_PROXY    net


I had to manually add string
score __RCVD_IN_NJABL 0
into local.cf file, this resolved the case.
Comment 3 AXB 2013-05-07 08:43:22 UTC 
(In reply to comment #2)
> No, SA still tries to use njabl

> /var/lib/spamassassin/3.002005/updates_spamassassin_org/20_dnsbl_tests.cf:
> tflags RCVD_IN_NJABL_PROXY    net
> 
> 
> I had to manually add string
> score __RCVD_IN_NJABL 0
> into local.cf file, this resolved the case.

Please confirm you're using SA 3.2.5 which is obsolete and unsupported.

Please run :

spamassassin -V

and post results
Comment 4 wyrm.white 2013-05-07 09:19:55 UTC 
~$ spamassassin --version
SpamAssassin version 3.2.5
  running on Perl version 5.10.0
~$ dpkg -l|grep spamass
ii  libmail-spamassassin-perl                3.002005-1                        Spam detector and markup engine
Comment 5 AXB 2013-05-07 09:23:53 UTC 
(In reply to comment #4)
> ~$ spamassassin --version
> SpamAssassin version 3.2.5
>   running on Perl version 5.10.0
> ~$ dpkg -l|grep spamass
> ii  libmail-spamassassin-perl                3.002005-1                     
> Spam detector and markup engine

(In reply to comment #4)
> ~$ spamassassin --version
> SpamAssassin version 3.2.5
>   running on Perl version 5.10.0
> ~$ dpkg -l|grep spamass
> ii  libmail-spamassassin-perl                3.002005-1                     
> Spam detector and markup engine

SA 3.2.5 is 6 years old and unsupported.
Comment 6 Darxus 2013-05-07 13:41:51 UTC 
(In reply to comment #5)
> SA 3.2.5 is 6 years old and unsupported.

Yet still listed on https://spamassassin.apache.org/downloads.cgi as if it were reasonable to use.  And I think no indication anywhere on the website that it's not a good idea?
Comment 7 Kevin A. McGrail 2013-05-07 13:48:36 UTC 
(In reply to comment #6)
> (In reply to comment #5)
> > SA 3.2.5 is 6 years old and unsupported.
> 
> Yet still listed on https://spamassassin.apache.org/downloads.cgi as if it
> were reasonable to use.  And I think no indication anywhere on the website
> that it's not a good idea?

Agreed.  It's a problem that we need someone to work on but too many fish to fry.  Anyone want to help change the website to svnpubsub and make some updates?

http://wiki.apache.org/spamassassin/ReleaseGoals is the only place that I believe reflects the outdatedness of 3.2.5.
Comment 8 Darxus 2013-05-07 17:35:29 UTC 
Replied on dev mailing list:  http://mail-archives.apache.org/mod_mbox/spamassassin-dev/201305.mbox/%3C20130507161039.GE22137%40chaosreigns.com%3E

(That archive takes annoyingly long to update.)