spamass-milt-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Subject rewriting


From: Ted Hatfield
Subject: Re: Subject rewriting
Date: Thu, 13 May 2010 17:08:30 -0500 (CDT)
User-agent: Alpine 2.00 (BSF 1167 2008-08-23)

On Thu, 13 May 2010, Paul Macdonald wrote:


Hi,

I have a scenario where mail is being flagged as spam on one box, but gets a lower score and is non spam due to a slightly different config on the final relay.

The X-Spam-Level and X-Spam-Checker-Version headers are successfully modified but the subject maintains the *****SPAM***** prefix.

May 13 14:23:59 server sm-mta[54409]: o4DDNvM8054409: Milter delete: header X-Spam-Flag: YES May 13 14:23:59 server sm-mta[54409]: o4DDNvM8054409: Milter change: header X-Spam-Status: from Yes, score=6.6 required=6.0 tests=BAYES_50,RCVD_IN_BRBL_LASTEXT,\n\tRCVD_IN_PBL,RDNS_NONE shortcircuit=no autolearn=no version=3.3.1 to No, score=-11.6............ May 13 14:23:59 server sm-mta[54409]: o4DDNvM8054409: Milter delete: header X-Spam-Level: ****** May 13 14:23:59 server sm-mta[54409]: o4DDNvM8054409: Milter change: header X-Spam-Checker-Version: from SpamAssassin 3.3.1
(2010-03-16) on server1 to SpamAssassin 3.3.1 (2010-03-16) on <server>

Thanks in advance.

Paul.

--


The subject line is rewritten by the spamd daemon and not the spamass-milter program.

This is done using the "rewrite_header Subject" option found in the user_prefs file.

You will need to remove this option on the configuration for the upstream server or if the servers are sharing the same user configuration you will need to overwrite individual options on the upstream server by adding a "rewrite_header Subject" option to the global local.cf file.


Ted Hatfield




reply via email to

[Prev in Thread] Current Thread [Next in Thread]