Michael Scheidell wrote: > On 2/23/10 9:28 AM, Bowie Bailey wrote: >> Michael Scheidell wrote: >> >>> On 2/23/10 9:03 AM, Jason Bertoch wrote: >>> >>>> Are there any internal checks that disable Bayes autolearn when these >>>> artificial whitelist rules match? I'd disabled these rules in >>>> versions prior to 3.3.0 but, with all the discussion on the matter, I >>>> thought I'd leave them in to see the "new and improved" version. >>>> Unfortunately, I'm still seeing false positives and am concerned that >>>> they are pushing the scores low enough to poison my Bayes database. >>>> >>>> >>> you can edit the tflags and add noautolearn >>> >>> example: >>> 72_active.cf:tflags __RCVD_IN_DNSWL nice net >>> >>> >>> becomes: >>> 72_active.cf:tflags __RCVD_IN_DNSWL nice net noautolearn >>> >> Are these settings cumulative? The man page doesn't specify. >> >> If I do this: >> >> tflags RULENAME nice net >> tflags RULENAME noautolearn >> >> what happens? Does everything get set or do I only get 'noautolearn'? >> >> > why not just do tflags RULENAME nice net noautolearn > > (oh.. and to find them, grep '^tflags.*RCVD_IN' *.cf
If I can just add 'noautolearn' in my local.cf, then I don't have to worry about what is currently set in the distributed rules. And if an update adds or removes a setting, it will happen automatically without me having to mess with it. -- Bowie
