[Bug 4136] mass-check --reuse should disable reused rules during mass-check --net

[bu...@bugzilla.spamassassin.org]

http://bugzilla.spamassassin.org/show_bug.cgi?id=4136





------- Additional Comments From felicity@kluge.net  2005-02-14 09:21 -------
Subject: Re:   New: mass-check --reuse should disable reused rules during mass-check --net

On Mon, Feb 14, 2005 at 02:08:53AM -0800, bugzilla-daemon@bugzilla.spamassassin.org wrote:
> If --reuse is on, there's absolutely no point in actually running those rules,
> so some hackery should be added to mass-check to disable only those rules
> that are being skipped (see the %reuse object in tmp/rules.pl).  Perhaps
> add to user_prefs.cf in a machine-edited section?
> 
> Thoughts?

When I was trying to implement this several months ago:

- we're only going to need this when testing out Bayes, and the time consuming
  piece is the net checks, so only bother reusing net rules.

- we want to cause certain rules not to run, but we want the hit to show up
  and the score to be added as if it had been run.  the problem is that the
  score will only be added if the rule actually runs, and the rule will run if
  the score is non-zero.  at the time, it looked like a whole lot of hackery
  would be needed to get this working.

- the main problem, from my pov, with the reuse approach is that what
  you really want is to know what requests were made and what the answers
  were at a given point in time.  reuse attempts to deduce what that
  information is based on rule hit.  ie: it's good to know whether or
  not spamcop/surbl/etc hit on a given rule (means it ran and hit),
  but what's more important is to know that it didn't hit but was run.
  If it didn't run at all, we need to run it ala our current method.





------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.