Your message dated Sat, 2 Sep 2017 21:16:26 -0700 with message-id <[email protected]> and subject line resolving ancient bug has caused the Debian Bug report #265905, regarding spamassassin: Mail::SpamAssassin::Conf - report_safe, remove_header all Report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 265905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=265905 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: spamassassin Version: 2.64-1 Severity: minor 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 -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.26.20040601 Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set to en_US) Versions of packages spamassassin depends on: ii debconf 1.4.30 Debian configuration management sy ii libhtml-parser-perl 3.36-1 A collection of modules that parse ii perl 5.8.4-2 Larry Wall's Practical Extraction ii spamc 2.64-1 Client for perl-based spam filteri -- debconf information: spamassassin/upgrade/2.40: spamassassin/upgrade/2.40w: spamassassin/upgrade/cancel: Continue spamassassin/upgrade/2.42m: No spamassassin/upgrade/2.42u: No
--- End Message ---
--- Begin Message ---This was fixed so long ago that the forwarded link no longer works...
--- End Message ---
