Dear List, I was running SA 3.0.4 with amavisd-new 2.2.1 without any problems. To use SA 3.1.0 I've updated my amavis to 2.3.3 and now (with 3.0.4) I see therse lines in my logs:
Sep 27 11:14:38 sns amavis[14103]: (14103-01-11) SPAM, <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>, Yes, score=28.285 tag=2.5 tag2=5.5 kill=5.5 test s=[BAYES_99=5.1, FORGED_MUA_OUTLOOK=1, FORGED_OUTLOOK_HTML=0.629, FORGED_OUTLOOK_TAGS=0.074, FROM_ENDS_IN_NUMS=0.2, FROM_ILLEGAL_CHARS=0.008, HEAD_ILLEGAL_CH ARS=2.125, HTML_FONT_BIG=0.142, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.137, MIME_BOUND_DD_DIGITS=4.139, MIME_HTML_ONLY=0.177, MIME_HTML_ONLY_MULTI=2.443 , MIME_QP_LONG_LINE=0.039, MISSING_MIMEOLE=0.012, MPART_ALT_DIFF=0.066, MSGID_SPAM_CAPS=3.791, MSGID_YAHOO_CAPS=3.8, RCVD_NUMERIC_HELO=1.248, SUBJ_ILLEGAL_CH ARS=2.854, X_PRIORITY_HIGH=0.3], autolearn=no, quarantine lIryibYzE0NF (spam-quarantine) I've set in local.cf bayes_auto_learn_threshold_spam 10.0 and now I'm wondering why it says autolearn=no?! With 2.2.1 this value wasn't displayed, so don't know if this behaviour is default. And there's a second point keeps me away from updating to 3.1.0: I've set in local.cf bayes_expiry_max_db_size 200000, which should be a size about 10MB. But look at my files: 168148992 Sep 27 11:25 auto-whitelist 14136 Sep 27 11:25 bayes_journal 167034880 Sep 27 11:25 bayes_seen 5324800 Sep 27 11:25 bayes_toks A force-expire doesn't help. (I'm using DB_File 1.75) Any ideas? Thx Michael
