On 03/05/2013 02:01 PM, Matus UHLAR - fantomas wrote:
On 3/1/2013 6:14 PM, Kevin A. McGrail wrote:
score RCVD_IN_NJABL_CGI 0
score RCVD_IN_NJABL_MULTI 0
score RCVD_IN_NJABL_PROXY 0
score RCVD_IN_NJABL_RELAY 0
score RCVD_IN_NJABL_SPAM 0
On Fri, 1 Mar 2013, Kevin A. McGrail wrote:
And score __RCVD_IN_NJABL 0 just in case...
On 04.03.13 10:38, John Hardin wrote:
Should this be happening:
72_scores.cf:score RCVD_IN_NJABL_CGI 0.001 0.001
0.001 0.001
72_scores.cf:score RCVD_IN_NJABL_MULTI 0.001 0.001
0.001 0.001
72_scores.cf:score RCVD_IN_NJABL_PROXY 0.001 0.001
0.001 0.001
72_scores.cf:score RCVD_IN_NJABL_RELAY 0.001 0.001
0.001 0.001
72_scores.cf:score RCVD_IN_NJABL_SPAM 0.001 0.001
0.001 0.001
hmmm, we don't want to minimalize the impact of these rules but completely
disable them...
hmpf!
I still see some orphan scores due to
/var/lib/spamassassin/3.004000/updates_spamassassin_org/20_dnsbl_tests.cf:reuse
RCVD_IN_PBL RCVD_IN_PBL T_RCVD_IN_PBL_WITH_NJABL_DUL
RCVD_IN_NJABL_DUL
I removed all NJABL rule references yesterday - we'll need to wait for
sa-update to catch up with the changes.
(probably after the weekly masscheck on Sat)
