Bazooka Joe wrote:

X-Spam-Status: No, score=1.0 required=3.0 tests=BAYES_60 autolearn=ham
     version=3.0.4
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on agwebinc.com

I have required of 3 which you can see and i have the milter rejecting email w/ score more than 7


On 5/10/06, Matt Kettler <[EMAIL PROTECTED]> wrote:
Bazooka Joe wrote:
> more and more i am seeing spam marked as autolearn=ham
>
> I was wondering the best way to correct this?

Depends.. Really you first need to figure out why it this happened before you
take any action at all.

Can you post a X-Spam-Status header for one of the messages?

Have you modified the required_score, or any of the learning thresholds in your
config?

In general there are only a few rules that can cause a message to be tagged as
spam, but do not count toward the computation of score for learning purposes.
*_IN_BLACKLIST, AWL, BAYES_*, and GTUBE are the most noteworthy ones.

You can set bayes_auto_learn_threshold_nonspam in local.cf to be 0 or a negative number, then autolearn=ham won't kick in unless it's below a certain score (not sure if this counts bayes or not).  But yes, the real question is why are no rules triggering...  Is DNS working?  Are you using the blacklist rules, etc?  What does the spam look like?

Jay

Reply via email to