Re: Problem with rules not being parsed I think

2014-08-01 Thread Kevin A. McGrail
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

2014-07-31 Thread Karsten Bräckelmann
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! H

Re: Problem with rules not being parsed I think

2014-07-31 Thread Kevin A. McGrail
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

Re: Problem with rules not being parsed I think

2014-07-31 Thread Karsten Bräckelmann
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. -- char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x

Re: Problem with rules not being parsed I think

2014-07-31 Thread Karsten Bräckelmann
On Thu, 2014-07-31 at 19:59 +, Chris Brandstetter wrote: > body NWU_YOLASITE /yolasite\.com/i This (and the other similar ones) really should better be a uri rule. And this particular one be merged with the almost duplicating uri rule just 20 lines below. > # Yolasite URI rule > uri NWU_

Re: Problem with rules not being parsed I think

2014-07-31 Thread Kevin A. McGrail
On 7/31/2014 5:08 PM, Chris Brandstetter wrote: If showed it being loaded "Jul 31 15:43:07.794 [20903] dbg: config: read file /etc/mail/spamassassin/local.cf” Is there any way to list what rules are being loaded? Like a list all available rules type of thing? Not that I'm aware of, no. Put i

Re: Problem with rules not being parsed I think

2014-07-31 Thread Karsten Bräckelmann
On Thu, 2014-07-31 at 21:08 +, Chris Brandstetter wrote: > If showed it being loaded "Jul 31 15:43:07.794 [20903] dbg: config: > read file /etc/mail/spamassassin/local.cf” Is there any way to list > what rules are being loaded? Like a list all available rules type of > thing? No, but you can

Re: Problem with rules not being parsed I think

2014-07-31 Thread Chris Brandstetter
If showed it being loaded "Jul 31 15:43:07.794 [20903] dbg: config: read file /etc/mail/spamassassin/local.cf” Is there any way to list what rules are being loaded? Like a list all available rules type of thing? Chris Brandstetter System Administrator Nebraska Wesleyan University Office Phon

Re: Problem with rules not being parsed I think

2014-07-31 Thread Kevin A. McGrail
On 7/31/2014 3:59 PM, Chris Brandstetter wrote: We are running spam assassin 3.3.1 with Postfix. So I have added some rules to mark as spam yolasite, wix, etc…. as we have been getting besieged by them. My thing is these rules seem not to be loading. When I do a spamassassin —lint I don’t g