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.