If you use spamc/spamd:
A simple way to see this is to check the log file of spamassassin (spamd).
In my case, I have redirect the syslog channel to a separate file. Make a script with those line or run in manually... I have test it for SA 3.1.4 thru 3.1.7 but it will probably work whit all the 3.1.x and maybe 3.0.x
=================================
echo ****SpamAssassin Checkup****
echo ***Number of mail: `grep "second" /var/log/spamassassin -c`
echo ***Number of SPAM: `grep "identified" /var/log/spamassassin -c`
echo ***Max child reach: `grep "raising" /var/log/spamassassin -c`
=================================
If "Max child reach:" is greater then 0 , consider raising the number of possible child. (--max-children=num)
Sorry for my english too.
Francois Rousseau
2006/10/30, [EMAIL PROTECTED] <[EMAIL PROTECTED]
>:
Thanks.
I've found a possible answer.
Spamassassin works with only 1 child.
Now I have add another child, 2.
And now all my mails have the header.
Is possible that spamassassin couldn't process all mails because has
only one child... so I have some mails with no header and much spam???
sorry for my english
fraska
Il giorno 30/ott/06, alle ore 12:11, Loren Wilton ha scritto:
> SA always adds information the header I believe. Although what you
> get depends on the "report_safe" option value in local.cf.
>
> Many of the mail tools that use SA will process the message through
> SA and then discard the result if it isn't marked as spam. So you
> don't see SA's markup in these tools unless SA said it was spam.
> Sometimes there is an option to override this and always return the
> result SA generated.
>
> Here are some typical headers from a mail message that is NOT spam:
>
> X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on xxx.com
> X-Spam-Level: **
> X-Spam-Status: No, score=2.3 required=4.6
> tests=BAYES_50,DK_POLICY_SIGNSOME,
> FH_RELAY_NODNS,HELO_MISMATCH_COM,HTML_FONT_BIG,HTML_MESSAGE
> autolearn=disabled version=3.1.4
>
>
> Loren
>
