Bug 1180338 - Disable rule DNS_FROM_AHBL_RHSBL
Summary: Disable rule DNS_FROM_AHBL_RHSBL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: spamassassin
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-08 21:54 UTC by Adam Williamson
Modified: 2015-04-21 19:21 UTC (History)
5 users (show)

Fixed In Version: spamassassin-3.4.0-13.fc22
Clone Of:
Environment:
Last Closed: 2015-04-21 19:21:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2015-01-08 21:54:06 UTC
As per upstream:

https://svn.apache.org/viewvc/spamassassin/trunk/rules/50_scores.cf?r1=1570286&r2=1581922

the AHBL blacklist was shut down on January 1, and now returns a positive result for *any* query. This shouldn't affect many people as most folks will be using the updated rulesets, I guess, but just in case, we should drop this rule from our shipped rule set (for stable releases too).

Comment 1 Warren Togami 2015-01-09 04:16:35 UTC
http://www.spamtips.org/2011/01/disable-dnsfromahblrhsbl.html

Sigh.

Comment 2 Adam Williamson 2015-01-09 05:36:01 UTC
that's not really relevant, though. you recommended disabling it then because it was ineffective. different circumstance to the service being discontinued.

Comment 3 Kevin Fenzi 2015-01-09 23:30:24 UTC
Is this really worth pushing the update out for?

I mean, pretty much anyone who wants to have spamassassin work is going to be using the updated rules...

Comment 4 Warren Togami 2015-01-10 07:07:42 UTC
spamassassin upstream has been on life support for many years now.  Several of the 3.2.x and 3.3 releases happened only because I was pushing on it hard from Red Hat and for a year after I departed Red Hat.  After that 3.4 took several more years for them to release.  They are severely understaffed so things like this that should have been removed years ago have slipped through the cracks.

Comment 5 Jaroslav Reznik 2015-03-03 17:06:44 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 6 Fedora Update System 2015-04-03 17:20:26 UTC
spamassassin-3.4.0-13.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/spamassassin-3.4.0-13.fc22

Comment 7 Fedora Update System 2015-04-03 17:27:09 UTC
spamassassin-3.4.0-13.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/spamassassin-3.4.0-13.fc21

Comment 8 Fedora Update System 2015-04-04 16:31:30 UTC
Package spamassassin-3.4.0-13.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing spamassassin-3.4.0-13.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-5518/spamassassin-3.4.0-13.fc22
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2015-04-21 19:21:39 UTC
spamassassin-3.4.0-13.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.