Re: Continuing - Re: How do I actually add these descriptions then...

2016-03-08 Thread Robert Chalmers
Ok, thanks. Everything is working now. and yes, spamassassin —lint returns nothing. I had probably just got outputs confused somewhere along the line. The —lint -D log now also shows no warnings. thanks Robert > On 8 Mar 2016, at 13:27, RW wrote: > > On Tue, 8 Mar 2016 07:05:11 + > rob..

Re: Continuing - Re: How do I actually add these descriptions then...

2016-03-08 Thread RW
On Tue, 8 Mar 2016 07:05:11 + rob...@chalmers.com.au wrote: > In the original email I posted, I'm asking two questions. > 1. I'm getting two warnings about nonexistent rules. Is this fixable? That's because you created descriptions for rules that don't exist. Either you did something wrong o

Re: Continuing - Re: How do I actually add these descriptions then...

2016-03-07 Thread rob...@chalmers.com.au
In the original email I posted, I'm asking two questions. 1. I'm getting two warnings about nonexistent rules. Is this fixable? And 2. why is lint reporting a random set of 13 missing descriptions when I have actually put those descriptions into local.cf? As to the descriptions themselves, it's

Re: Continuing - Re: How do I actually add these descriptions then...

2016-03-07 Thread RW
On Mon, 7 Mar 2016 19:11:12 +0100 Reindl Harald wrote: > Am 07.03.2016 um 19:05 schrieb RW: > > If someone gets around to creating descriptions for these rules you > > wont see them > > maybe *you* won't see them, others do > > they are part of the report-headers instead something like I kn

Re: Continuing - Re: How do I actually add these descriptions then...

2016-03-07 Thread Joe Quinn
On 3/7/2016 1:05 PM, RW wrote: On Mon, 7 Mar 2016 15:12:25 + Robert Chalmers wrote: I?ve added descriptions, grabbing the actual RULE name with awk, and creating the list that way. { a=$12; print "describe " a " Spam check applied."; } The result is like this. describe L

Re: Continuing - Re: How do I actually add these descriptions then...

2016-03-07 Thread Reindl Harald
Am 07.03.2016 um 19:05 schrieb RW: On Mon, 7 Mar 2016 15:12:25 + Robert Chalmers wrote: The result is like this. describe LONG_TERM_PRICE Spam check applied. describe MULTIPART_ALT_NON_TEXT Spam check applied. describe TVD_IP_OCT Spam check applied. describe HK_NAME_DR Spam check applied.

Re: Continuing - Re: How do I actually add these descriptions then...

2016-03-07 Thread RW
On Mon, 7 Mar 2016 15:12:25 + Robert Chalmers wrote: > I?ve added descriptions, grabbing the actual RULE name with awk, and > creating the list that way. > > { > a=$12; > print "describe " a " Spam check applied."; > } > > > The result is like this. > describe LONG_TERM_PRICE

Continuing - Re: How do I actually add these descriptions then...

2016-03-07 Thread Robert Chalmers
I’ve added descriptions, grabbing the actual RULE name with awk, and creating the list that way. { a=$12; print "describe " a " Spam check applied."; } The result is like this. describe LONG_TERM_PRICE Spam check applied. describe MULTIPART_ALT_NON_TEXT Spam check applied. descr

Re: How do I actually add these descriptions then...

2016-02-12 Thread Robert Chalmers
Yes well, back again. sa-update is running, and supposedly updating rules. spam assassin -D —lint still shows a long list… however, no longer shows that first one from a while back… Feb 12 09:09:30.977 [73122] dbg: config: warning: no description set for HK_SCAM_N2 Feb 12 09:09:30.977 [73122]

Re: How do I actually add these descriptions then...

2016-02-10 Thread Reindl Harald
Am 08.02.2016 um 19:18 schrieb John Hardin: On Mon, 8 Feb 2016, Reindl Harald wrote: Am 08.02.2016 um 18:58 schrieb Robert Chalmers: I have quite a list of these in the output from spam assassin -D —lint they should be part of the rules itself and i don't understand why rule writes don't

Re: How do I actually add these descriptions then...

2016-02-08 Thread Chalmers
Thanks folks. As they are cosmetic, I'll worry about them later... I now know how to fix it up though, so it wont take long. I'll also check rule update is going on. thanks - From my iPhone. > On 8 Feb 2016, at 6:18 pm, John Hardin wrote: > >> On Mon, 8 Feb 2016, Reindl Harald wrote: >>

Re: How do I actually add these descriptions then...

2016-02-08 Thread John Hardin
On Mon, 8 Feb 2016, Reindl Harald wrote: Am 08.02.2016 um 18:58 schrieb Robert Chalmers: I have quite a list of these in the output from spam assassin -D —lint they should be part of the rules itself and i don't understand why rule writes don't run "-D --lint" regulary *before* publish I

Re: How do I actually add these descriptions then...

2016-02-08 Thread John Hardin
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_PR

Re: How do I actually add these descriptions then...

2016-02-08 Thread Reindl Harald
Am 08.02.2016 um 19:06 schrieb Bill Cole: You *COULD* add descriptions for rules with missing descriptions in local.cf, but why bother? well, because looking for warnings because local modifications is much easier when the stock install don't produce them at all signature.asc Description

Re: How do I actually add these descriptions then...

2016-02-08 Thread Reindl Harald
Am 08.02.2016 um 18:58 schrieb Robert Chalmers: I have quite a list of these in the output from spam assassin -D —lint they should be part of the rules itself and i don't understand why rule writes don't run "-D --lint" regulary *before* publish "describe RULNE_NAME description" in local.c

Re: How do I actually add these descriptions then...

2016-02-08 Thread Bill Cole
On 8 Feb 2016, at 12:58, 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