On Sun, 16 Dec 2018 08:30:58 -0500
Kevin A. McGrail wrote:
>
> On Sat, Dec 15, 2018, 17:25 RW
> > On Sat, 15 Dec 2018 22:26:17 +0100
> > sebast...@debianfan.de wrote:
> >
> >
> > > I want to have a full report - i.g.: 5 Points for
> > > IMG_ONLY_FM_DOM, 5 Points for SURBL_BLOCKED .
> > >
> >
> >
> >
> > add_header all Report _REPORT_
> This can cause issues though. That feature is not header safe to my
> knowledge.
I had a look at the bug reports and I couldn't find anything to
substantiate this, the most relevant are:
Bug 7664 - This seems a bit anecdotal, so far. No-one has confirmed it,
I couldn't reproduce it on FreeBSD and the reporter couldn't reproduce
it on Windows. Also the sample email had broken MIME.
Bug 7253 - This is cosmetic. If non-ASCII characters are present, SA
3.x QP encodes the header incorrectly, but the basic header itself is
still valid and easily readable, apart from multi-byte characters being
displayed as hexadecimal. The serious problems mentioned in 7253 come
from unsuccessful attempts to reimplement QP header encoding with
third-party libraries.
In my experience email clients don't typically decode header MIME QP
unless the headers are being displayed with the message, which is
unlikely for X-Spam-Report. For those of us who read informational
headers without the QP being decoded, the fix in trunk may be worst than
doing nothing.
