Jeff,

> I have just started using Amavis and have a question regarding an
> discrepancy between the Spamassassin header in a spam message and the
> Spamassassin report included in the spam notification.
>
> Here is the report in the spam notification:
> Content analysis details:   (22.0 points, 5.0 required)

> And, here is the report in the header of the quarantined message:
>
> X-Spam-Status: Yes, score=21.973 tag=-9999 tag2=8 kill=10
>   tests=[AV:Sanesecurity.Junk.8084.UNOFFICIAL=0, AV_SS=7.5, BAYES_99=7,
>   FORGED_MUA_OUTLOOK=3.116, FORGED_OUTLOOK_HTML=0.001,
>   FORGED_OUTLOOK_TAGS=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457,
>   MSOE_MID_WRONG_CASE=0.82, SUBJ_ALL_CAPS=2.077] autolearn=spam

> How come the required value is only 5 in the spam notification while
> in the config files and the header it shows as 8?

As Daniel Luttermann explained, the '5.0 required' in the notification
comes from 'required_hits' in local.cf, the whole text section is
produced by SpamAssassin and not edited by amavisd - just inserted as-is.

The tag2 and kill levels are what really controls the amavisd behaviour,
the 'required_hits' in local.cf is never used, only spam score value
is taken from SA.

The discrepancy is purely a cosmetic issue. The '5.0 required' in text
should be ignored, it has no effect. If it bothers you, the best
approach is to set 'required_hits' to the same value as tag2_level.

  Mark


------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/amavis-user 
 AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 
 AMaViS-HowTos:http://www.amavis.org/howto/ 

Reply via email to