I wonder if anyone already has thought about trying the following as a rule for PerlScanner..
Yes.* Virus-X-Spam-Status: ANTI-SPAM: Spamassassin told us
Too bad it doesn't work for me :-) so maybe it by design that PerlScanner
cannot match the body against the qmail-scanner spamassassin "X-Spam" tag..
Or is there another way to achieve this?
In my experience SA does a great job (almost no false positives for me with threshold 5.0)
identifying spam - so why not quarantining the freshly tagged spam, preventing it
from reaching the users' mailbox?
Some may criticize this approach as a too strong intervention in the
mail flow - or the users right to have the last say what is spam and what
is not..
Cheers, Kai.
------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
