Hi Chris,
Nothing looks horribly wrong to me with your setup. See if you can
reproduce the no-rewrite state with an email you have received which did
not
get the subject rewritten. Remove the spamassassin markup and re-send
the
message through spamassassin (pipe a marked-up email through
"spamassassin
-d"). Then, run it through spamc once, twice, three times. Does it
fail to
rewrite the header here each time? If it doesn't fail, the problem may
be
outside SA. If it does fail to rewrite the header each time, then try
passing it through spamassassin (not spamc). Does it fail? Also,
enable -D
when passing it to spamassassin and look for any problems in the debug
output.
I tired this, same results. The eamil is flagged as spam, but the subject
is not re-written. Something of interest though. I did not have the:
"rewrite_header Subject *****SPAM*****" option in my local.cf. I added
this option, and now all the subjects that are associated with spam are
getting flagged with *****SPAM*****. However, some are now coming through
as "*****SPAM***** [SPAM] original-subject". Alsmost seems as if SA or
some associated option in SA is parsing the mail twice? Any idea what
defaults to [SPAM] in the subjects? Razor, DCC, etc?
Nothing in the message header stands out. This is an example of what I am
getting now:
Received: from localhost by stuttgart.feger.net
with SpamAssassin (version 3.1.0);
Thu, 01 Dec 2005 16:01:43 -0600
From: "Dennis H. NORAD" <[EMAIL PROTECTED]>
To: Jade <[EMAIL PROTECTED]>
Subject: *****SPAM***** [SPAM] Software
Date: Fri, 02 Dec 2005 05:03:39 -0600
Message-Id: <[EMAIL PROTECTED]>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on
stuttgart.feger.net
X-Spam-Level: ****************
X-Spam-Status: Yes, score=16.2 required=7.0 tests=DATE_IN_FUTURE_12_24,
RAZOR2_CF_RANGE_51_100,RAZOR2_CF_RANGE_E8_51_100,RAZOR2_CHECK,
SPF_HELO_PASS,UNPARSEABLE_RELAY,URIBL_AB_SURBL,URIBL_JP_SURBL,
URIBL_SBL,URIBL_SC_SURBL autolearn=spam version=3.1.0
MIME-Version: 1.0
I guess I just need to track down what defaults as [SPAM]. :) Maybe this
is a Debian thing. :)
Thanks,
James
