At 03:09 16-08-2007, =?iso-8859-2?Q?Pawe=B3_T=EAcza?= wrote:
Here are the Spamassassin headers for one of a spam mail we received:
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on
anubis3.poczta.uw.edu.pl
X-Spam-Level: xxxxxxxxxxxxxxxxxxx
X-Spam-Status: Yes, score=19.3 required=5.0
tests=FH_HELO_EQ_D_D_D_D,FRT_PRICE,
FRT_STRONG1,FRT_SYMBOL,HTML_MESSAGE,MIME_QP_LONG_LINE,RCVD_IN_BL_SPAMCOP_NET
,
RCVD_IN_PBL,TVD_FUZZY_SYMBOL,TVD_STOCK1 autolearn=disabled
version=3.2.1
The message is detected as spam.
Thanks for the hint! I'll try a look at them.
You don't need those rules then.
Now I use MyISAM strorage backend, because I just created Bayesian
database using Spamassassin sql/bayes_mysql.sql file :)
The recommendations in the sql/bayes_mysql.sql file are for the
average setup. It doesn't cover MySQL optimization techniques as
that a MySQL specific issue.
You can change the engine from MyISAM to InnoDB (see ALTER
TABLE). That should improve performance for INSERTs. With the
amount of mail your server handles, you either have to improve MySQL
performance, switch to more powerful hardware or disable Bayes. If
you disable Bayes, the punctuation spam would still be caught in your
setup as it scored over 19 points.
Regards,
-sm
