At 02:44 PM 1/5/2004, Mitch \(WebCob\) wrote:
Do you know where that is doc'd? I can remember a conversation a while ago
about that not being the case - that the rule was still executed, but
effectively disabled... but maybe I'm mixing things up - sorry.
it's in the Mail::SpamAssassin::Conf manpage
ED] Behalf Of Matt
Kettler
Sent: Monday, January 05, 2004 11:36 AM
To: Mitch (WebCob); Upwood, Jim; [EMAIL PROTECTED]
Subject: RE: [SAtalk] Auto disable rules...
At 01:52 PM 1/5/2004, Mitch \(WebCob\) wrote:
>Hmmm- unless I missed something (and I MAY have) setting a score of 0
>doesn't
At 01:52 PM 1/5/2004, Mitch \(WebCob\) wrote:
Hmmm- unless I missed something (and I MAY have) setting a score of 0
doesn't disable. The rule is still run - it just doesn't effect the score,
the only think that removes a rule is removing the rule -
Setting a score of 0 DOES disable the rule. It is
very difficult though.
m/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Upwood, Jim
Sent: Monday, January 05, 2004 10:23 AM
To: [EMAIL PROTECTED]
Subject: [SAtalk] Auto disable rules...
This would be a neat feature add-on for SA:
- Mail gets scanned by SA, lo
This would be a neat feature add-on for SA:
- Mail gets scanned by SA, log written to syslog
- Hit freqs get parsed in real-time and written to a mySQL table
- All rules are in another mySQL table, including custom rules
- Once a week a cron job kicks off and compares hit frequencies with
rules ba
