http://bugzilla.spamassassin.org/show_bug.cgi?id=3902
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|critical |minor
Component|spamc/spamd |spamassassin
OS/Version|Linux |All
Target Milestone|Undefined |3.1.0
Version|3.0.0 |SVN Trunk (Latest Devel
| |Version)
------- Additional Comments From [EMAIL PROTECTED] 2005-04-06 22:52 -------
http://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_Conf.html
clearly states that
a) headers added by the
> add_header { spam | ham | all } header_name string
parameter will all begin with X-Spam-
b) headers removed by the
> remove_header { spam | ham | all } header_name
parameter will be headers that begin with X-Spam-
c) "clear_headers" clears the list of headers to be added to messages, excepting
X-Spam-Checker-Version
Confirmed: in SpamAssassin 3.1.0-r158541 (2005-03-21) on Cygwin under WXP,
running SpamAssassin with NONE of the above parameters removes all previous
X-Spam-anything headers before any new SA headers are inserted into the email.
This seems overly egotistical -- X-Spam-anything headers which are placed/found
in the email, and which are NOT in conflict with SpamAssassin's own headers, and
not in conflict with the above commands, should probably be left in the email.
They might be useful to the recipient or email admin.
Alternately, if SA behavior is to always remove such headers, it should be
documented. (If it is documented somewhere, I could not find it.)
Suggestion: treat as a documentation bug for 3.1.0, and supply that
documentation. Then if the headers should not be removed, open new bug for 3.1.1
which will modify the code and avoid removing non-conflicting headers.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
