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 2006/05/01 19:59:03 UTC

[Bug 4888] New: Some added "Report" variables

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4888

           Summary: Some added "Report" variables
           Product: Spamassassin
           Version: 3.1.0
          Platform: PC
        OS/Version: FreeBSD
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: spamassassin
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: tjg@meitech.com


I think it might be an improvement if we could include some more variables in 
SpamAssassin's reporting capability (when it re-writes a message body with a 
SPAM report).  Specifically, I think it would be nice to add:

_FROM_        - The "Return-Path" or "From" address of the e-mail.
_MESSAGEID_   - The SendMail (or other MTA) Message ID.

These would both be particularly useful for including a link in the SPAM report 
that users could click to report an incorrectly tagged message, instead of them 
having to forward me the whole message.  For example, I might add the following 
to my local.cf:

report If this e-mail has been incorrectly tagged as SPAM, please click the
report link below so that we may update our filters accordingly:
report http://blah.com/report.php?From=_FROM_&ID=_ID_

Then, I could make report.php skim through my Sendmail logs and pick out the 
message in question, and then make updates to my local.cf file to prevent the 
sender in question from being tagged as SPAM anymore.

Just a suggestion.  :)



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

[Bug 4888] Some added "Report" variables

Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4888





------- Additional Comments From tjg@meitech.com  2006-05-03 17:45 -------
Making it more generic works for me.



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

[Bug 4888] Some added "Report" variables

Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4888


felicity@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From felicity@apache.org  2006-05-03 17:59 -------
it ended up being really simple, so I just committed it in for 3.2:

Sending        SpamAssassin/Conf.pm
Sending        SpamAssassin/PerMsgStatus.pm
Transmitting file data ..
Committed revision 399368.

:)



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

[Bug 4888] Some added "Report" variables

Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4888


felicity@apache.org changed:

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




------- Additional Comments From felicity@apache.org  2006-05-03 17:32 -------
Hrm, interesting idea.

My only comment would be that an implementation should be more generic,
something like:

_HEADER(From)_
_HEADER(Message-ID)_

Where the value is equal to the same as those for header rules.  ie: for the
above From addition, you'd really probably want:

_HEADER(From:addr)_

or

_HEADER(EnvelopeFrom)_

etc.  This should be pretty trivial to code up I think.  Thoughts anyone?



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