On Wed, Oct 16, 2002 at 11:23:10AM -0500, [EMAIL PROTECTED] wrote: > This leads me to a question. Is there a way to tell SA to ignore (and > possibly overwrite) all conflicting header lines like X-Spam-Status? That
It does already. SA removed the X-Spam-* headers before scanning. This actually causes problems for some folks (as discussed on the list) where a mail gets scanned (say on a sitewide basis) and marked as spam including subject and/or body rewriting. Then it's scanned again (receiving server, or a user's procmailrc, etc) but this time isn't marked as spam due to a whitelist. The headers will be correct, but the first rewrite's markup will be left in place as well. Very confusing. Personally, if a mail comes in and it's already "X-Spam-Status: yes" I file it in my spam folder. If that specific string doesn't exist, the message is scanned again. So there's no hole for a spammer. :) -- Randomly Generated Tagline: "I wouldnt trust NT to feed my cat." - Unknown poster on Slashdot
msg08937/pgp00000.pgp
Description: PGP signature
