[EMAIL PROTECTED] wrote:
Quoting [EMAIL PROTECTED]:
It seems that the marked spam is never getting to this point, to have these rules applied to it. It is being marked and then being sent to the user, marked as spam, so that part is working.
If the headers are there, SA is doing its job. Ask the procmail mailing list for help debugging that problem.
I do all the deletion in /etc/procmailrc, like so:
# LOGFILE=/var/log/procmail.log DROPPRIVS=yes :0fw: spamassassin.lock * < 256000 | /usr/bin/spamc
# try a second time if Spamassassin failed
:0fw: spamassassin.lock2 * ! ^X-Spam-Level:.* * < 256000 | /usr/bin/spamc
:0
* ^X-Spam-Status: Yes
* ^X-Spam-Level: \*\*\*\*\*\*\*
{
:0
{ RULE="SPAM" }
:0:
/dev/null # toss it
# $HOME/mail/spam # send it to spam folder
}:0
* ^X-Spam-Status: Yes
{
:0
{ RULE="SPAM" }
:0:
$HOME/mail/spam
}
----------My server is small so I send it through spamc twice in case it failed the first time due to too many processes. Then I filter the result. If it is spam and the level is greater than 6.999 I send it to /dev/null. I actually started this level quite a bit higher (at like 10) and then ratcheted it down as I never found false positives up there. If it is spam but less that 7 (between 5 and 7) I send it to a spam folder in the user's box for checking for false positives. Otherwise it goes to the inbox.
-- Chris Marrin | Senior Software Architect | Sony Corporation phone: (408) 955-3049 | [EMAIL PROTECTED] | | What is this talk of software 'releases'? Klingons do not 'release' | | software; our software ESCAPES, leaving a bloody trail of designers | | and quality assurance people in its wake! (unknown author) |
