Re: Ignore third-party SA headers

2017-01-23 Thread Chris 
On Mon, 2017-01-23 at 17:43 -0500, Ruga wrote:
> spam that already includes SA headers is getting through without
> local SA filtering. Is it posible to tell the local SA to always add
> its own headers, possibly taking note of the existence of former
> SA headers while rewriting them out of the way?
> 

I think this is what you mean:

bayes_ignore_header Old-X-Spam-Status
bayes_ignore_header Old-X-Spam-Score
bayes_ignore_header Old-X-Spam-Bar
bayes_ignore_header Old-X-Spam-Report

Put the above in your local.cf. From the SA Wiki:

If you or any upstream service has added any additional headers to the
emails which may mislead Bayes, those should probably be removed before
feeding the email to sa-learn. Alternatively, use the
bayes_ignore_header setting in your local.cf (as detailed in the man
page for Mail::SpamAssassin::Conf)

If this is not what you're referring to I apologize.

Chris

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
19:19:09 up 6 days, 2:09, 2 users, load average: 0.42, 0.38, 0.28
Ubuntu 16.04.1 LTS, kernel 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6
17:47:47 UTC 2017

signature.asc
Description: This is a digitally signed message part

Re: Ignore third-party SA headers

2017-01-23 Thread Joe Quinn 

On 1/23/2017 5:43 PM, Ruga wrote:
spam that already includes SA headers is getting through without local 
SA filtering. Is it posible to tell the local SA to always add its own 
headers, possibly taking note of the existence of former SA headers 
while rewriting them out of the way?


SA never short-circuits from pre-existing headers. Look at where your 
mailflow calls SA (postfix, amavis, mimedefang, etc).

Ignore third-party SA headers

2017-01-23 Thread Ruga 
spam that already includes SA headers is getting through without local SA 
filtering. Is it posible to tell the local SA to always add its own headers, 
possibly taking note of the existence of former SA headers while rewriting them 
out of the way?