Lorin G. Tremblay wrote: > You are right sorry about that. Well, I can't help you diagnose your hit-problems based on a config file. As said before, at absolute minimum I'd need to see a list of hits, if not a sample mail.
That said, there's some things you should consider about your config file: > Mac OS X -- Communigate - SA3.04 - AWL - AUTOLEARN > # Use terse version of the spam report > use_terse_report 1 Error: Ancient option, not supported by modern versions of SA, delete this line. > # Bayes database path > bayes_path /etc/mail/spamassassin/Bayes/spamassassin Error: You need bayes_file_mode 0777 when you set a bayes path. Otherwise you must guarantee that only one user will ever execute any SA tools on your system. Warning: that path seems a little off. They pretty much always should end in "bayes". Right now SA will attempt to use the following files: /etc/mail/spamassassin/Bayes/spamassassin_toks /etc/mail/spamassassin/Bayes/spamassassin_seen But I suspect you wanted it to use the ending "spamassassin" as a directory name, not a filename. The weirdness of "bayes_path" is it's not a path. It's a path plus partial filename. As long as you realize that your system uses "spamassassin_toks" instead of "bayes_toks" you should be fine, but you should be aware of it. > # Learning minimum value > bayes_min_spam_num 140 Suggestion: I'd question the wisdom of lowering this below the default of 200, but by now you should have enough training this is irrelevant. I'd kill the line. > > # Mail which scores outside this range will be fed back into SpamAssassin's > # learning system automatically, to train the Bayesian scanner. > bayes_auto_learn_threshold_nonspam 1.0 > bayes_auto_learn_threshold_spam 5.0 Warning: your learning threshold of 5.0 is rather low. It's so low SA won't even honor it, as other hard-coded criteria add up to an absolute minimum of 6.0. That setting really is asking for the bayes database to go awry unless you've got manual training to fix mis-learning. > # default: per-user whitelist: > auto_whitelist_path ~/.spamassassin/auto-whitelist > auto_whitelist_file_mode 0600 Error: the mode should be 0700 not 0600. SA requires the X bit on all the "file_mode" options as they are sometimes used in directory creation. Fortunately these circumstances are rare, but it's worth fixing. > # use this for a system-wide whitelist: > auto_whitelist_path /etc/mail/spamassassin/Autowhitelist/auto-whitelist > auto_whitelist_file_mode 0666 Error: the mode should be 0777 not 0666. Suggestion: comment out One or the other of these pairs of AWL declarations. You can't be both site-wide and per-user. Currently you'll end up using the site-wide settings, so you probably ought comment out the first set. > score HTML_WEB_BUGS 12.0 Warning: This could cause considerable FP problems. Compare that score to the default this rule gets: score HTML_WEB_BUGS 0.166 0.013 0.311 0.035 And look at STATISTICS.txt, which says this rule has a S/O of 0.895. (ie: 10.5% of all mail hitting this rule is nonspam) which is why it's scored so low. Are you sure that rule should have such a high score?
