Comment FIX details: (Score 4, Informative) 115
this is also happening on Ubuntu server, running Spamassassin 3.2.5
The linked article references a workaround:
add this line to the "local.cf" spamassassin config file, on this system is was
score FH_DATE_PAST_20XX 0.0
If you're running spamassassin as a daemon, you *may* also want to restart spamd
with something like:
sudo
This solution simply removes the rule by setting the score for that rule to 0.
You'll want to undo this once a solution is deployed.