https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6752
Bug #: 6752
Summary: URIBL_BLOCKED rule causes lookup, doesn't just check
for previous lookup results
Product: Spamassassin
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Rules
AssignedTo: [email protected]
ReportedBy: [email protected]
Classification: Unclassified
The recent addition of URIBL_BLOCKED (which I unfortunately didn't notice)
caused spamassassin to start to query multi.uribl.com even though I had
disabled it via:
score URIBL_BLACK 0
score URIBL_GREY 0
score URIBL_RED 0
I would suggest that the addition of this rule should have had a method to
check and see if its even necessary to see if it was "blocked".
In my case, it caused my servers to start to query that list, thus getting them
blocked.
I could imagine others may have had this problem if they had disabled the URIBL
rules the way I had as well.
My suggestion would be a syntax in the configuration to say disable everything
for multi.uribl.com, something similar to:
disable_urlbl_source multi.uribl.com
This would ensure that any future rules added for a specific list would not
cause SpamAssassin to start querying a previously disabled list.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
