http://bugzilla.spamassassin.org/show_bug.cgi?id=3113
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
------- Additional Comments From [EMAIL PROTECTED] 2004-03-01 11:16 -------
Some more remarks on this (thought this would not be contentions,
but here we go):
- 2.63 did remove pre-existing X-Spam headers
- I don't find in Changes where this (serious) change of
behaviour is mentioned
- There is a call to $self->{msg}->delete_header('X-Spam-.*') in
PerMsgstatus. What does this achieve if the intended purpose is
not what a superficial reading implies (and earlier SA versions
actually did at the same place)?
- If old X-Spam headers are not deleted, you lose the ability to do
simple and clean RE matches on headers for the very condition SA is there
to decide: "this is spam, as seems by the local SA". Up to 2.63,
a "^X-Spam-Status: Yes" was sufficient for this. This no longer works
since it also matches SA headers of the incoming message, i.e.
some I cannot rely on.
- Surely it won't take long until Spammers find this out and add
X-Spam-Status: No
themselves.
- If old X-Spam headers are not deleted, you have no way to distinguish
between X-Spam headers coming from the original message while spamc
was not able to contact spamd, and X-Spam headers added locally.
- If old headers shouldn't be deleted, renaming them to something like
X-Old-Spam-* sounds like an easy solution.
I would kindly urge you to rethink this design decision since it created
huge problems.
Robert
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
