-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
true. Colin, any chance of a bug report with attachments that demo it? - --j. Loren Wilton writes: > This sounds like a bug in 3.0 that someone shoudl file. Whitespace is > whitespace. > > Loren > > ----- Original Message ----- > From: "Colin A. Bartlett" <[EMAIL PROTECTED]> > To: "'Matt Kettler'" <[EMAIL PROTECTED]>; > <[EMAIL PROTECTED]> > Sent: Wednesday, May 19, 2004 5:23 AM > Subject: RE: disabling tests > > > Matt Kettler Sent: Tuesday, May 18, 2004 9:48 AM > > > > > At 07:33 AM 5/18/04 -0400, Colin A. Bartlett wrote: > > > > > > >I just upgraded to 3.0.0-r10591 from 2.55. > > > > > > > >I have several global rules that are set to score 0 so that they are > > > >disabled. Individual users can then turn them on by setting a score in > > > >SQL prefs. It seems that with the new version even with the score set > > > >to 0 they're still being run. Did this change with the new version or > > > >am I overlooking something?. I have a test that is /.*/ and even with > > > >the score set to 0 it hits on every single message. Never used to do > > that... > > > > > > Hmm, strange.. Since 3.0 is still in development I wonder if it's a bug > > > or if they intentionally disabled the "don't run > rules with zero > score" > > > feature for testing purposes and will turn it back on when 3.0 is > > released. > > > > > > The "zero score" feature works properly in 2.63. > > > > I fixed this. Turns out 3.0 is pickier about tabs/spaces. > > I had: score [tab] rulename [space] 0 > > Instead of: score [space] rulename [tab] 0 > > > > Same config worked fine in previous version. Thanks for the help. On the > > other hand a "don't run rules > 0 - yes/no" option might actually be handy > > for some. > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Exmh CVS iD8DBQFAq3BVQTcbUG5Y7woRAqSuAJ0UmsBK2RR8IdrbbxnwOwBGQRSJzACgz94b sNxro8FRxOeUx3n2RZ3snpY= =eTC3 -----END PGP SIGNATURE-----
