When we initially discussed MAXWEIGHT (and MINWEIGHT) functionality, you indicated that when the MAXWEIGHT was reached, the processing of that filter would be stopped. I've noted that a filter capable of producing multiple matches, each at the MAXWEIGHT limit, it will show in the warning that the last possible hit in the file will be noted in the WARN action. This means that the filter will continue to do searches all the way to the end of the file. The score though is properly capped. Could you please take a look at this.
Are you running the latest interim release? Could it be that the last hit in the file is the one causing it to reach the maximum weight? When the MAXWEIGHT is hit, the processing should stop. I'm looking at the code for the latest interim, and if the weight gets capped, there shouldn't be any way for the processing to continue.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask about our free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
--- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
