Matt,
On 5/10/07, Matt Kettler <[EMAIL PROTECTED]> wrote:
BQ wrote:
> Hi,
>
> Recently I had some false positives that also had BAYES_99 triggered.
>
> As I saved the original e-mail(s), I'd like to see what tokens
> actually caused this. Is it possible to do th
Hi,
Recently I had some false positives that also had BAYES_99 triggered.
As I saved the original e-mail(s), I'd like to see what tokens
actually caused this. Is it possible to do this with Spam Assassin
3.1.8?
I vaguely remember that previously I ran spamassassin in debug mode
and that it show
sa-learn --force-expire to expire the Bayes database.
On our busy servers I set this up so it's run from cron every night at
4AM. Gives pretty good results.
Cheers,
BQ
$sa_kill_level_deflt = $sa_tag2_level_deflt; # triggers spam evasive actions
> # The $sa_tag_level_deflt, $sa_tag2_level_deflt and $sa_kill_level_deflt
> mailgate jnichols #
What do you have set for $final_spam_destiny? It should be D_DISCARD
if you want amavisd-new to discard the message which has higher score
then the kill level.
BQ.
0 non-token data: last expiry atime
0.000 0 43200 0 non-token data: last expire atime delta
0.000 0 370471 0 non-token data: last expire
reduction count
Cheers,
BQ
