On 7/31/2014 5:41 PM, Karsten Bräckelmann wrote:
On Thu, 2014-07-31 at 17:34 -0400, Kevin A. McGrail wrote:
Put it in a different CF and comment out a description and look for an
error that a description is missing.
A missing description is not an error, not even a lint warning.
Yes, it is a warning (though in my defense I was using "error"
generically. I think this explains why some of your rules are missing
descriptions ;-)
spamassassin -D --lint 2>&1 | grep -i description | grep KB
Jul 31 19:01:36.329 [31451] dbg: config: warning: no description set for
KB_RATWARE_MSGID
Jul 31 19:01:36.362 [31451] dbg: config: warning: no description set for
KB_RATWARE_OUTLOOK_08
Jul 31 19:01:36.369 [31451] dbg: config: warning: no description set for
KB_RATWARE_OUTLOOK_MID
Jul 31 19:01:36.379 [31451] dbg: config: warning: no description set for
KB_FAKED_THE_BAT
Jul 31 19:01:36.410 [31451] dbg: config: warning: no description set for
KB_RATWARE_OUTLOOK_16
Jul 31 19:01:36.418 [31451] dbg: config: warning: no description set for
KB_DATE_CONTAINS_TAB
Jul 31 19:01:36.421 [31451] dbg: config: warning: no description set for
KB_RATWARE_OUTLOOK_12
Jul 31 19:01:36.424 [31451] dbg: config: warning: no description set for
KB_RATWARE_BOUNDARY
regards,
KAM
