spamassassin marks spam, and that spam is forwarded to a spambox, which we simply delete all the mails in this box every week.
now, we are starting to get quite a bit of porn spam slipping thorugh with a low score. I would like to enable the bayesian filtering of spamassassin,
yet doing so will cause a lot of false positives. We don't have the staff to go through the spambox looking for false positives.
a) is there something I can do that I am not doing already doing, to increase the number of positive spam detections, without increasing false positives...
b) anyone thought of modifiying qmail-scanner/spamassassin to have 2 different headers/detection routines...
one for really/really spam,
the other for possible spam.
then I could filter the really, really spam (as we are now) to a local spambox,
yet, have the possible spam go through, where the user is responsible for filtering it?
here is our spamassassin local.cf file: required_hits 5 use_terse_report 1 rewrite_subject 1 use_razor2 1 use_dcc 1 use_pyzor 1 #score RCVD_IN_RBL 10 score RCVD_IN_RSS 4 score RCVD_IN_DUL 4 subject_tag *****SPAM*****
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
