Odd missing X-Spam-Status: Yes header

[Glenn Steen]

    [ The following text is in the "WINDOWS-1252" character set. ]
    [ Your display is set for the "US-ASCII" character set.  ]
    [ Some characters may be displayed incorrectly. ]

On 27/10/05, Jim Davis <jdavis at cs.arizona.edu> wrote:
> This slipped by my procmail filter; it looks like the spammer added a fake
> spamassassin block to the headers...
>
(snip)
> With
>
> High Scoring Spam Actions = header "X-Spam-Status: Yes" header
> "X-Spam-Flag: YES attachment deliver
>
> then there should have been a 'X-Spam-Status: Yes' header added (and the
> spam itself should have been wrapped in an attachment, but that's still
> not working).  Could the bogus 'X-Spam-Status: No' header somehow have
> interfered with that?
>
Why do you rely on procmail handling this? MailScanner can do either
of "delete", "Store", "forward" ... And you should be able to habdle
that in a ruleset too...
And why do you rely on a "publicly know" header.... for all you're
using it, you could as well invent your own... "X-Nyponsoppa: YES";-).

Just my ^À0.02
--
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se