Re: lint failure with 3.1.2

2006-05-28 Thread Loren Wilton
> Thanks Loren, so I guess the best rule would be to upgrade each time a new > version is released whether its minor or major that way something like this > shouldn't happen again. Well I don't know about that. You would have hit this complaint in lint one release sooner, and might have had more

Re: lint failure with 3.1.2

2006-05-28 Thread Chris
On Saturday 27 May 2006 11:02 pm, Loren Wilton wrote: > > Thanks, I believe I see what you're saying. I have no idea either why > > it worked fine in 3.1.0. I've commented out the internal_networks > > entry for now and everything lints fine now. > > 'worked fine' and 'linted clean' may be two dif

Re: lint failure with 3.1.2

2006-05-27 Thread Loren Wilton
> Thanks, I believe I see what you're saying. I have no idea either why it > worked fine in 3.1.0. I've commented out the internal_networks entry for > now and everything lints fine now. 'worked fine' and 'linted clean' may be two different things. It linted clean in 3.1.0 because the checks wer

Re: lint failure with 3.1.2

2006-05-27 Thread Daryl C. W. O'Shea
On 5/27/2006 11:44 PM, Loren Wilton wrote: From: "Daryl C. W. O'Shea" <[EMAIL PROTECTED]> [9324] warn: config: SpamAssassin failed to parse line, "MY_LRGROD .85" is not valid for "score", skipping: score MY_LRGROD .85 I thought this was required in 3.1.0 (but not 3.0.x) too, but anyway,

Re: lint failure with 3.1.2

2006-05-27 Thread Loren Wilton
> From: "Daryl C. W. O'Shea" <[EMAIL PROTECTED]> > > [9324] warn: config: SpamAssassin failed to parse line, "MY_LRGROD .85" is > > not valid for "score", skipping: score MY_LRGROD .85 > > I thought this was required in 3.1.0 (but not 3.0.x) too, but anyway, > all of these scores require a leading

Re: lint failure with 3.1.2

2006-05-27 Thread Chris
On Saturday 27 May 2006 5:50 pm, jdow wrote: > > Yeah, you'll need those hosts' IPs along with any intermediate relays > > such as the IP(s) of any POP3 servers your mail might go through. > > trusted_networks 127/8 192.168/16 207.217.121/24 209.86.93/24 > > That works here on earlier versions nic

Re: lint failure with 3.1.2

2006-05-27 Thread jdow
From: "Daryl C. W. O'Shea" <[EMAIL PROTECTED]> Chris wrote: On Saturday 27 May 2006 4:33 pm, you wrote: Any why did --lint work fine every time in 3.1.0? Commenting out the internal_networks entry and restarting SA, --lint shows no errorrs now, why? We're continuously improving the config

Re: lint failure with 3.1.2

2006-05-27 Thread Daryl C. W. O'Shea
Chris wrote: On Saturday 27 May 2006 4:33 pm, you wrote: Any why did --lint work fine every time in 3.1.0? Commenting out the internal_networks entry and restarting SA, --lint shows no errorrs now, why? We're continuously improving the config parser's ability to detect configuration *logic*

Re: lint failure with 3.1.2

2006-05-27 Thread Daryl C. W. O'Shea
Chris wrote: On Saturday 27 May 2006 12:21 pm, Daryl C. W. O'Shea wrote: [9324] warn: trusted_networks doesn't contain internal_networks entry '192.168/16' [9324] warn: lint: 7 issues detected, please rerun with debug enabled for more information Here is my local.cf entry for trusted_networks:

Re: lint failure with 3.1.2

2006-05-27 Thread Chris
On Saturday 27 May 2006 4:01 pm, Sanford Whiteman wrote: > >> > internal_networks 192.168/16 > > > > > > Isn't this the internal_networks entry? > > Yes, and the warning is telling you that the value '192.168/16' (not > thethename 'internal_networks')

Re[2]: lint failure with 3.1.2

2006-05-27 Thread Sanford Whiteman
>> > internal_networks 192.168/16 > > Isn't this the internal_networks entry? Yes, and the warning is telling you that the value '192.168/16' (not thethename 'internal_networks') is not duplicated in trusted_networks, as would normally be expect

Re: lint failure with 3.1.2

2006-05-27 Thread Chris
On Saturday 27 May 2006 12:21 pm, Daryl C. W. O'Shea wrote: > > [9324] warn: trusted_networks doesn't contain internal_networks entry > > '192.168/16' > > [9324] warn: lint: 7 issues detected, please rerun with debug enabled > > for more information > > > > Here is my local.cf entry for trusted_ne

Re: lint failure with 3.1.2

2006-05-27 Thread Daryl C. W. O'Shea
Chris wrote: During the CPAN upgrade from 3.1.0 to 3.1.2 last night I could have swore I saw --lint being ran as a test. However, when I got up this morning I found this in my RDJ output email folder: [9324] warn: config: SpamAssassin failed to parse line, "MAKEPENIBIG .33" is not valid for

Re: lint failure with 3.1.2

2006-05-27 Thread Chris
On Saturday 27 May 2006 10:31 am, Kai Schaetzl wrote: > Chris wrote on Sat, 27 May 2006 09:12:36 -0500: > > The others above appear to be from the 'adult.cf' rule file, which has > > been running fine with 3.1.0. Any suggestions? > > Contact the maintainer of that ruleset. I suspect 3.1.2 doesn't

Re: lint failure with 3.1.2

2006-05-27 Thread Chris
On Saturday 27 May 2006 10:31 am, Kai Schaetzl wrote: > Chris wrote on Sat, 27 May 2006 09:12:36 -0500: > > The others above appear to be from the 'adult.cf' rule file, which has > > been running fine with 3.1.0. Any suggestions? > > Contact the maintainer of that ruleset. I suspect 3.1.2 doesn't

Re: lint failure with 3.1.2

2006-05-27 Thread Kai Schaetzl
Chris wrote on Sat, 27 May 2006 09:12:36 -0500: > The others above appear to be from the 'adult.cf' rule file, which has been > running fine with 3.1.0. Any suggestions? Contact the maintainer of that ruleset. I suspect 3.1.2 doesn't like scores that start with "." My --lint is still fine whic

lint failure with 3.1.2

2006-05-27 Thread Chris
During the CPAN upgrade from 3.1.0 to 3.1.2 last night I could have swore I saw --lint being ran as a test. However, when I got up this morning I found this in my RDJ output email folder: [9324] warn: config: SpamAssassin failed to parse line, "MAKEPENIBIG .33" is not valid for "score", skippi