The problem is that the point behind the Habeas test is its protection against abuse -- if spammers do try to abuse it, they will be hunted down and money (spare change, most likely, given the average spammer) pulled from their pockets.> The habeas test type should only be used if you have a specific reason to > do so (such as to automatically forward violations of the Habeas headers).Thank you, Scott. This is exactly what I had in mind -- to lower Habeas weights sufficiently to reduce false positives while also catching Habeas abuse. Do I have this right?
If the Habeas headers *were* widely abused, it would become almost useless as a spam test.
Remove default "WHITELIST HABEAS" Add "HABEAS habeas x x -20 0" to reduce false positives Add "HABEAS WARN" to catch Habeas abusers (when weight is still high) In mail client, filter on X-RBL-WARNING contains HABEAS and X-RBL-WARNING contains WEIGHT10
This would work fine.
-Scott
---
[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.
