On 04/01/2012 06:35 AM, joea wrote: > While exploring Bayes stuff, (wanting to populate appropriately for > my setup), found reference to removing headers that might confuse > Bayes. > > Specifically bayes_ignore_header. > > The example they show is an X header. Seems the ones spamassassin > puts in there will be ignored without intervention. > > Is one only concerned with X headers? What about things like > "Received From"? I have several upstream hosts. Must these be > specified?
The "X-" prefix is an old-fashioned convention that many argue should be phased out. There are two types of items you want to exclude, which may very well include non-x-prefixed headers: 1. Headers added after SpamAssassin runs. These can include anti-virus (though lots of people run A/V before SA), internal mail server (Exchange, procmail) headers, and those added by the mail client. 2. FP-prone filtering notes. If your ISP includes its own spam filters and you do not consider them reliable (if you do, why are you running your own?), they will poison your bayes db. The same thing goes for some of the third party ClamAV rules (like the phishing detection). Do *not* get aggressive here: if in doubt, let Bayes play with it. Proper Received header traversal is essential to getting SpamAssassin up and humming. Read the NETWORK TEST OPTIONS portion of the documentation and be sure to specify your internal_networks, trusted_networks, and msa_networks. ALL deployments need at least trusted_networks (unless you've disabled network tests, in which case I'd recommend something other than SA) and many will improve given the differences between these three.
signature.asc
Description: OpenPGP digital signature
