https://bugs.exim.org/show_bug.cgi?id=1876
Bug ID: 1876
Summary: Write more detailed spam report to spool file
Product: Exim
Version: N/A
Hardware: x86
OS: Windows
Status: NEW
Severity: bug
Priority: medium
Component: Content Scanning
Assignee: tom@???
Reporter: rq@???
CC: exim-dev@???
With bug #1647, $spam_score and $spam_bar now actually persist* until delivery.
It would be nice to have access to a more detailed spam report in transports
however. One way to get this would be to persist $spam_report as well. Even
though this "header" is quite big, I'm not sure how that could cause a problem:
I assume all linebreaks in that huge report could be replaced with \n's, and it
would still fit into a single line, albeit much longer than usual.
But there's another thing that I would actually want to see even more: a
$spam_status variable (if possible). According to SpamAssassin
documentation[1], when it scans a message, it adds an X-Spam-Status headers to
it, which looks like this:
X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,
HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,SPF_SOFTFAIL,T_DKIM_INVALID
autolearn=no autolearn_force=no version=3.4.0
I've been using SA-Exim for years, and always saw this header being added. It
seems to me like it is a much more compact equivalent of X-Spam-Report, so I'd
love it if Exim allowed me to actually have a $spam_status variable and add an
X-Spam-Status header instead of (or along with) $spam_report and X-Spam-Report.
* I haven't actually tested, still using an older version packaged by Debian
[1]
https://wiki.apache.org/spamassassin/X_Spam_Status
--
You are receiving this mail because:
You are on the CC list for the bug.
