Sounds like a question for the sa-exim list, but from some quick testing
that I did it appears that Marc's local_scan.c routine will strip out
any pre-existing X-Spam* headers prior to sending the message to spamc
(or spamassassin).
- Mark
-----Original Message-----
From: Chad Leigh -- Shire.Net LLC [
mailto:chad@shire.net]
Sent: Thursday, March 13, 2003 1:17 AM
To: exim-users@???
Subject: [Exim] exim and local_scan SpamAssassin and receiving mails
that have been SA scanned somewhere else
Hi
I am scratching my head on this problem. I have Spam Assassin running
in local_scan.c using the Marc Merlin stuff, and it works quite well.
However, I get mail that has already been scanned somewhere else by
Spam Assassin and has the "X-Spam-Flag" flag set to YES, using
different criteria than are set in our Spam Assassin. So after our
Spam Assassin runs on it, the various X-Spam-* headers that Spam
Assassin adds get replaced by new ones, but since our SA might think it
not to be spam, the previous "X-Spam-Flag" flag with YES is still
there, even though the "X-Spam-Status: No, ..." header from our SA says
no. This confuses our users' filters in their clients (we only add
headers with our SA, we never delete stuff ourself).
I have looked through the Spam Assassin docs and config files to see if
there is a setting to purge existing SA headers prior to running, and
in the local_scan SA stuff for exim, and in the exim mail flow, to see
if there was a way of purging these headers myself and I have not come
up with any solutions or found anything.
Does someone have a suggestion or see a solution to this?
Thanks
Chad
