Bug 3718

Summary: Mail::SpamAssassin::Conf - report_safe, remove_header all Report
Product: Spamassassin Reporter: Jesus Climent <climent>
Component: DocumentationAssignee: SpamAssassin Developer Mailing List <dev>
Status: NEW ---    
Severity: normal    
Priority: P5    
Version: SVN Trunk (Latest Devel Version)   
Target Milestone: Future   
Hardware: Other   
OS: other   
Whiteboard:

Description Jesus Climent 2004-08-23 02:05:53 UTC
in Manual Mail::SpamAssassin::Conf it is not entirely clear that simply
adding this line will now work:

       always_add_report { 0 | 1 }   (default: 0)
           ...
           option instead:

           add_header all Report _REPORT_

Please clarify this by stating that it is mandatory to set
report_safe before touching "Report" setting. Like this:

        report_safe             0
        remove_header all Report

This will not work:

        remove_header all Report
        report_safe             0
Comment 1 Theo Van Dinter 2004-08-23 09:09:57 UTC
Subject: Re:  New: Mail::SpamAssassin::Conf - report_safe, remove_header all Report

On Mon, Aug 23, 2004 at 02:05:54AM -0700, bugzilla-daemon@bugzilla.spamassassin.org wrote:
> in Manual Mail::SpamAssassin::Conf it is not entirely clear that simply
> adding this line will now work:
> 
>        always_add_report { 0 | 1 }   (default: 0)
>            ...
>            option instead:
> 
>            add_header all Report _REPORT_

??  always_add_report doesn't exist in 3.0.  it's not in the Conf POD at all.

> Please clarify this by stating that it is mandatory to set
> report_safe before touching "Report" setting. Like this:
>         report_safe             0
>         remove_header all Report
> This will not work:
>         remove_header all Report
>         report_safe             0

So the current documentation isn't clear?:

If [report_safe] is set to 0, incoming spam is only modified by adding
some C<X-Spam-> headers and no changes will be made to the body.  In
addition, a header named B<X-Spam-Report> will be added to spam.  You
can use the B<remove_header> option to remove that header after setting
B<report_safe> to 0.


Comment 2 Daniel Quinlan 2005-03-30 01:08:27 UTC
move bug to Future milestone (previously set to Future -- I hope)