https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5842
------- Additional Comments From [EMAIL PROTECTED] 2008-03-04 11:09 ------- (In reply to comment #5) > well, we had no form of reuse for SPF, so the scores were based on whatever > SPF records were in place at the time of mass-check. in my opinion, basing > scores on this is better than on no data at all. Actually we did have #reuse for the SPF tests. I was actually questioning where the set0/2 scores for the SPF rules came from, but of course, they were generated based on the results of single set3 mass-check (just like any other set0/2 rules). So that's fine (assuming all/most of the corpus submitters have SPF checks enabled). > We could modify the code so that it knows that #reuse implies "tflags net", > sure. basically I didn't want the effects of #reuse to be too widespread > in the main Mail::SpamAssassin classes, since it's only supposed to affect > mass-checks. I can't think of any reason why #reuse must or should only apply to net rules. If you wanted to #reuse bayes rules (which I've been considering for a while) I think you should be able to. Same goes for any other rule if it makes sense for that rule. > I see your point -- they are pretty messy. other suggestions? I don't see what the harm would be of *not* having "tflags net" for the SPF rules and just having mass-check #reuse whatever we tell it to. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
