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
some interesting ones. not sure why they rate a net nice:
RCVD_IN_IADB_OPTOUTONLY net nice?
describe is: IADB: Scrapes addresses, pure opt-out only
or
describe RCVD_IN_IADB_NOCONTROL IADB: Has absolutely no mailing
controls in place
I would think a POSITIVE score for someone who we know violates federal
can-spam laws (scrapes addresses. violation of us federal can-spam laws)
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
