Control: tags -1 + upstream fixed-upstream Control: forwarded -1 https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7730
> file /usr/share/spamassassin/20_head_tests.cf contains: > > -------------------------------------------------------------------------- > header __FROM_NEEDS_MIME From:name:raw =~ > /[\x00-\x08\x0b\x0c\x0e-\x1f\x7f-\xff]/ > header __FROM_ENCODED_QP From:raw =~ /=\?\S+\?Q\?/i > header __FROM_ENCODED_B64 From:raw =~ /=\?\S+\?B\?/i > > > meta FROM_EXCESS_BASE64 __FROM_ENCODED_B64 && !__FROM_NEEDS_MIME > describe FROM_EXCESS_BASE64 From: base64 encoded unnecessarily > -------------------------------------------------------------------------- > > It results in false positive for every properly encoded From header. > All the incoming mails in my box are marked with FROM_EXCESS_BASE64. It looks like this has been fixed upstream already. Please see https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7730 While you wait for updated packages to be available, you may wish to enable spamassassin's periodic rules update feature. This will retrieve updated rules published by the upstream project. I documented this process for Debian in /usr/share/doc/spamassassin/README.Debian.gz and at https://noah.meyerhans.us/blog/2015/01/15/spamassassin-updates/ If you don't wish to run the update process regularly, you can run it once with the following, as root: start-stop-daemon --chuid debian-spamd:debian-spamd --start \ --exec /usr/bin/sa-update -- \ --gpghomedir /var/lib/spamassassin/sa-update-keys noah
