Re: Problem with rules not being parsed I think

["Kevin A. McGrail" <KM...@PCCC.com>]

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

Re: Problem with rules not being parsed I think

["Kevin A. McGrail" <KM...@PCCC.com>]

On 7/31/2014 7:29 PM, Karsten Bräckelmann wrote:
> Moreover, it is important to note that this debug warning was 
> introduced in 3.4. In particular, since the OP is running 3.3.x. ;) 
And you didn't beat him up for running an outdated version?  For shame!

Regards,
KAM

Re: Problem with rules not being parsed I think

[Karsten Bräckelmann <gu...@rudersport.de>]

On Thu, 2014-07-31 at 19:02 -0400, Kevin A. McGrail wrote:
> On 7/31/2014 5:41 PM, Karsten Bräckelmann wrote:

> > 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.

Hah, that's actually news to me!

However, that is merely a debug message, phrased to look like a warning.
It is not an actual lint warning or generic error. Without the -D
switch, the command below returns nothing. A plain lint check also exits
clean. (In contrast, a describe option for an undefined rule does
trigger a lint warning.)

Moreover, it is important to note that this debug warning was introduced
in 3.4. In particular, since the OP is running 3.3.x. ;)


> I think this explains why some of your rules are missing 
> descriptions ;-)

Doh!

> 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


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}