On Wed, 18 Feb 2009 23:00:03 +0000 (UTC) Ray <rsk-gm...@misinformation.org> wrote:
> However, SA currently appears to be making spam > judgement and to be bayes autolearning. (A reasonable default setup > from the hosting provider.) > > * How do I determine what the current SA config is? The locations where spamassassin looks for configuration are listed in the main manpage. > Specifically, > can I see whether bayes is enabled, and whether it's auto-learning > (if that's distinct from merely enabled)? If it appears to autolearning, then bayes and autolearning are enabled. Note that autolearning uses its own, more conservative, rules, it's not based on the normal single threshold - you should use sa-learn to manually train too, if you can. By default Bayes scoring wont turn-on until you've learned 200 spam, and 200 ham (non-spam) messages. If you are going to make a judgement about moving the threshold then you should ignore the early mails that lack BAYES_* hits. > * Can I stop SA from judging spamminess (that is, making the binary > declaration of whether something is spam, X-Spam-Status, > X-Spam-Flag) and retain the scoring markup? I suppose this may not > be important, as sa-learn is said to ignore prior SA markup, it's > just that having the declaration sitting in the headers from there on > makes these mails look spammy whether they truly are, and other more > naive tools might be misled. Some third-party Baysian filters let you you ignore unwanted headers. Even if you use one that doesn't, a single spam/ham token isn't likely to have all that much effect compared to all the other SA tokens. There are two main ways to use SA with a separate Bayesian filter. One is to score it into SA (which you can't do) and the other is to let the Bayesian filter pick-up extra tokens from the SA headers. In the latter case you would probably want to leave in the result at the default threshold anyway. I think you could get rid of it by creating a custom header, but it's probably not worth the effort. > * If I can't stop SA from judging spamminess, can I at least > override the site-wide config to mark up subjects? I can't figure > this out. Currently I have 'rewrite_header subject ""', but that > fails. The docs say the string should be set to 'a null value', but > the config file's syntax for specifying nulls is not described. I believe it just means: rewrite_header subject
