It's a limitation in the filtering capabilities.  I certainly don't want to do that, but there is no way around it.  You just have to keep that in mind when scanning the headers after seeing this test tripped.

The way you had it written, it would be tripped just as often, but it would have credited 7 points to spam that spoofed the Mozilla header and didn't spoof your domain.  That would of course not be a good idea.

Matt



John Tolmachoff (Lists) wrote:
Actually, you want to apply the weight in the Global.cfg, 7 in this
case, and then all of your positives should be listed as 0 in the filter
file and the Mozilla exception should be scored as a -7.  The way it is
now, it will credit 7 points to any message claiming to be Mozilla
generated, and that of course includes a lot of spam.  Doing it the way
I suggested only defeats the scoring of the test when Mozilla is found,
but that also means that this test will show up to Declude as failed
despite the lack of scoring
    

But why would you want it to show up as a failed test when the overall
weight given is zero?

John Tolmachoff MCSE CSSA
Engineer/Consultant
eServices For You
www.eservicesforyou.com
  

Reply via email to