On Wed, Oct 09, 2002 at 08:07:30PM +0200, Malte S. Stretz wrote: > No, it doesn't. At least not always ;-) SA first checks for the existence of > a X-Spam-Status header. If this one exists, it will remove all X-Spam-* > headers. As this mail contains only a X-Spam-Level, it won't be removed. > I've got currently no time to fix this, somebody has to do it or should > open a bug.
Well, I've just looked at the code: At the top of PerMsgStatus::check()
there's a call for "$self->clean_spamassassin_headers();". No checks
around it for anything, just a call. That routine is very simple
and strips out the X-Spam-{Status, Level, etc.} headers, and replaces
Content-Transfer-Encoding, Content-Type, and Return-Receipt-To if there's
a X-Spam-Prev header for it. The check then commences.
I also just did a quick check by taking the message I'm responding to,
added a "X-Spam-Level" header with 15 stars or so, then ran through
spamc -- header was removed. spamassassin -- header was removed.
So unless I'm missing something obvious in the discussion, the behavior
described doesn't happen in 2.42 at least. I don't think the code has
changed since 2.40, so 2.4x and later should be fine. I haven't looked
at anything earlier, so 2.2 and 2.3 may have a bug, but well -- that's
what the new versions are for. ;)
--
Randomly Generated Tagline:
"By golly, I'm beginning to think Linux really *is* the best thing since
sliced bread."
(By Vance Petree, Virginia Power)
msg08624/pgp00000.pgp
Description: PGP signature
