Hi,
On Wed, Aug 27, 2014 at 6:18 PM, Karsten Bräckelmann <guent...@rudersport.de>
wrote:
>
> On Wed, 2014-08-27 at 17:07 -0400, Alex wrote:
> > I've set up a local URI DNSBL and I believe there are some FPs that
> > I'd like to identify. I've currently set up amavisd to set
> > $sa_tag_level_deflt at a value low enough that it always produces the
> > X-Spam-Status header on every email.
> >
> > It will show "LOC_URIBL=1" in the status, but is it possible to have
> > it somehow report/show the domain that caused the rule to fire, in the
> > same way that it can be done with spamassassin directly on the
> > command-line using -t?
>
> The URIs [1] are automatically added to the uridnsbl rule's description
> for _REPORT_ and _SUMMARY_ template tags. The latter is identical to the
> additional summary at the end with the -t option, the first one is
> suitable for headers.
>
> add_header spam Report _REPORT_
>
> That Report header is set by default with report_safe 0 (stock SA, not
> Amavis).
I now recall having added a few custom headers in the past, and it was
indeed necessary to instruct amavis to display them. I did a little more
digging around, and learned how I was doing it previously was replaced with
the following, in amavisd.conf:
$allowed_added_header_fields{lc('X-Spam-Report')} = 1;
So I've modified my local.cf with the following:
report_safe 0
clear_report_template
add_header all Report _REPORT_
Despite specifying "all", it's only displayed in quarantined messages. I
need it to be displayed on non-spam messages, and "all" messages would be
most desirable.
There's also this in the SA conf docs:
report ...some text for a report...
Set the report template which is attached to spam mail messages.
See the 10_misc.cf configuration file in
/usr/share/spamassassin for an example.
If you change this, try to keep it under 78 columns. Each report
line appends to the existing template,
so use clear_report_template to restart.
Is this still valid? 10_misc.cf apparently no longer exists, so I wasn't
able to follow through there.
Thanks,
Alex
