You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by BrianSebby <se...@anl.gov> on 2007/05/03 23:51:47 UTC
SpamAssassin removing X-Spam-Flag header
We recently put an Ironport anti-spam appliance in front of our SpamAssassin
installation for evaluation, and I have noticed a problem. I configured the
Ironport to add the "X-Spam-Flag: YES" header to messages that it determines
to be spam, as we have already trained our user population to look for that
header to redirect their spam messages to a separate folder.
After doing some tests, however, I discovered a problem. It looks like
SpamAssassin removes that header if it does not determine that the message
is spam. Is there a way to configure SpamAssassin to leave that header
alone if it already exists?
We are using SpamAssassin 3.1.8, which is launched via spampd, the spam
proxy daemon, which gets the messages delivered to it from postfix.
Thanks,
Brian Sebby
--
View this message in context: http://www.nabble.com/SpamAssassin-removing-X-Spam-Flag-header-tf3689152.html#a10313831
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: SpamAssassin removing X-Spam-Flag header
Posted by Loren Wilton <lw...@earthlink.net>.
>> We recently put an Ironport anti-spam appliance in front of our
>> SpamAssassin
>> installation for evaluation, and I have noticed a problem. I
The Ironport machine is SA in disguise. So you effectively have two copies
of SA in series. You porbably understand this, but I'm just mentioning it
to be sure.
SA begins scanning a message by first removing any previous markup it may
have inserted. In this case, the second SA will remove all of the markup
beginning with X-Spam that the Ironport SA installed.
You can't keep SA from doing this. But you may be able to use procmail or
some other integration tool to change the Ironport X-Spam-xxx headers to
X-Ironport-Spam-xxx headers or the like. These won't be "X-Spam" headers,
so they won't get stripped in the second SA instance.
Loren
----- Original Message -----
From: "Robert Nicholson" <ro...@gmail.com>
To: "BrianSebby" <se...@anl.gov>
Cc: <us...@spamassassin.apache.org>
Sent: Thursday, May 10, 2007 9:21 PM
Subject: Re: SpamAssassin removing X-Spam-Flag header
> SpamAssassin is configured to add the header when it's spam and not when
> it's ham.
>
> you can change that
>
> add this
>
> add_header all Flag _YESNOCAPS_
>
> and it will keep the header in both cases.
>
>
> On May 4, 2007, at 4:51 AM, BrianSebby wrote:
>
>>
>> We recently put an Ironport anti-spam appliance in front of our
>> SpamAssassin
>> installation for evaluation, and I have noticed a problem. I configured
>> the
>> Ironport to add the "X-Spam-Flag: YES" header to messages that it
>> determines
>> to be spam, as we have already trained our user population to look for
>> that
>> header to redirect their spam messages to a separate folder.
>>
>> After doing some tests, however, I discovered a problem. It looks like
>> SpamAssassin removes that header if it does not determine that the
>> message
>> is spam. Is there a way to configure SpamAssassin to leave that header
>> alone if it already exists?
>>
>> We are using SpamAssassin 3.1.8, which is launched via spampd, the spam
>> proxy daemon, which gets the messages delivered to it from postfix.
>>
>>
>> Thanks,
>>
>> Brian Sebby
>> --
>> View this message in context: http://www.nabble.com/SpamAssassin-
>> removing-X-Spam-Flag-header-tf3689152.html#a10313831
>> Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
>>
Re: SpamAssassin removing X-Spam-Flag header
Posted by Robert Nicholson <ro...@gmail.com>.
SpamAssassin is configured to add the header when it's spam and not
when it's ham.
you can change that
add this
add_header all Flag _YESNOCAPS_
and it will keep the header in both cases.
On May 4, 2007, at 4:51 AM, BrianSebby wrote:
>
> We recently put an Ironport anti-spam appliance in front of our
> SpamAssassin
> installation for evaluation, and I have noticed a problem. I
> configured the
> Ironport to add the "X-Spam-Flag: YES" header to messages that it
> determines
> to be spam, as we have already trained our user population to look
> for that
> header to redirect their spam messages to a separate folder.
>
> After doing some tests, however, I discovered a problem. It looks
> like
> SpamAssassin removes that header if it does not determine that the
> message
> is spam. Is there a way to configure SpamAssassin to leave that
> header
> alone if it already exists?
>
> We are using SpamAssassin 3.1.8, which is launched via spampd, the
> spam
> proxy daemon, which gets the messages delivered to it from postfix.
>
>
> Thanks,
>
> Brian Sebby
> --
> View this message in context: http://www.nabble.com/SpamAssassin-
> removing-X-Spam-Flag-header-tf3689152.html#a10313831
> Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
>