You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2015/06/02 22:42:36 UTC

[Bug 7204] New: Added headers ("X-Spam-*") should be customizable to enable user to be able to keep different versions of them

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7204

            Bug ID: 7204
           Summary: Added headers ("X-Spam-*") should be customizable to
                    enable user to be able to keep different versions of
                    them
           Product: Spamassassin
           Version: 3.4.0
          Hardware: PC
                OS: FreeBSD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: spamassassin
          Assignee: dev@spamassassin.apache.org
          Reporter: yuri@tsoft.com

I have my mail checked by spam assassin twice. One time my provider runs it
without some CPU intense checks enabled (as they explained), because they just
can't afford to run CPU intense checks for everybody. I run it the second time
on the same messages with all CPU intense checks.

My spam assassin overwrites the original X-Spam-* headers on the messages. As a
result, the first checker's status gets lost.

I think, the string "X-Spam" should be customizable in the user config file.
Currently it is hard-coded (ex. in SpamAssassin/PerMsgStatus.pm).

Most people probably don't run this way, or don't care to lose such info, so
this isn't the major feature. But this is offset by it being very easy to
implement (new config option).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7204] Added headers ("X-Spam-*") should be customizable to enable user to be able to keep different versions of them

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7204

Yuri <yu...@tsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7204] Added headers ("X-Spam-*") should be customizable to enable user to be able to keep different versions of them

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7204

Kevin A. McGrail <km...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|Undefined                   |Future

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7204] Added headers ("X-Spam-*") should be customizable to enable user to be able to keep different versions of them

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7204

Kevin A. McGrail <km...@pccc.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kmcgrail@pccc.com

--- Comment #1 from Kevin A. McGrail <km...@pccc.com> ---
Feature requests are one of the harder things to make time to address.  Can you
take a pass at coding what you want for consideration?

Regards,
KAM

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7204] Added headers ("X-Spam-*") should be customizable to enable user to be able to keep different versions of them

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7204

Yuri <yu...@tsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yuri@tsoft.com

--- Comment #3 from Yuri <yu...@tsoft.com> ---
One easy alternative solution is to add the "Rewrite with regexp" feature, that
will be run on all old headers before modification.
So the older X-Spam headers can be put out of the way of the new ones.

I am still deliberating which of these three solutions is the best.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7204] Added headers ("X-Spam-*") should be customizable to enable user to be able to keep different versions of them

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7204

Yuri <yu...@tsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Hardware|PC                          |All
            Version|3.4.0                       |SVN Trunk (Latest Devel
                   |                            |Version)
                 OS|FreeBSD                     |All

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7204] Added headers ("X-Spam-*") should be customizable to enable user to be able to keep different versions of them

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7204

--- Comment #2 from Mark Martinec <Ma...@ijs.si> ---
> My spam assassin overwrites the original X-Spam-* headers on the messages.
> As a result, the first checker's status gets lost. 
> I think, the string "X-Spam" should be customizable in the user config file.
> Currently it is hard-coded (ex. in SpamAssassin/PerMsgStatus.pm).

Alternatively, make removal of existing markup configurable
(and making sure that new X-Spam-* header fields are always
added at the top of a header section).

-- 
You are receiving this mail because:
You are the assignee for the bug.