On Mon, 8 Feb 2016, Robert Chalmers wrote:
I have quite a list of these in the output from spam assassin -D —lint
Feb 8 17:44:07.199 [15545] dbg: config: warning: score set for non-existent
rule DUP_SUSP_HDR
Feb 8 17:44:07.205 [15545] dbg: config: warning: no description set for
STOX_AND_PRICE
Feb 8 17:44:07.206 [15545] dbg: config: warning: no description set for
FSL_INTERIA_ABUSE
Feb 8 17:44:07.206 [15545] dbg: config: warning: no description set for
MID_DEGREES
Feb 8 17:44:07.206 [15545] dbg: config: warning: no description set for
HK_SCAM_N13
Feb 8 17:44:07.206 [15545] dbg: config: warning: no description set for
HTML_TITLE_SUBJ_DIFF
Feb 8 17:44:07.206 [15545] dbg: config: warning: no description set for
STOCK_PRICES
Feb 8 17:44:07.207 [15545] dbg: config: warning: no description set for
LOTTERY_PH_004470
Feb 8 17:44:07.207 [15545] dbg: config: warning: no description set for
REPLYTO_WITHOUT_TO_CC
Feb 8 17:44:07.207 [15545] dbg: config: warning: no description set for
FSL_HELO_SETUP
Feb 8 17:44:07.207 [15545] dbg: config: warning: no description set for
KB_RATWARE_OUTLOOK_MID
Fixing those is on the rule maintainers, not you (unless any of those are
referring to custom rules you added locally). They're also not fatal, just
cosmetic.
I find the first one (score set for non-existent rule DUP_SUSP_HDR)
surprising, though. DUP_SUSP_HDR is in the current published base rules,
so it shouldn't be complaining about setting a score for it...
Are you sure you're getting rules updates?
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhar...@impsec.org FALaholic #11174 pgpk -a jhar...@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
The ["assault weapons"] ban is the moral equivalent of banning red
cars because they look too fast. -- Steve Chapman, Chicago Tribune
-----------------------------------------------------------------------
4 days until Abraham Lincoln's and Charles Darwin's 207th Birthdays
