Noticed this occurring recently since we bumped up the SPF_FAIL score. What's odd to me is that the mail server still records the Received-SPF header as a pass, yet Spamassassin apparently ignores this for its scoring. This is odd because `ignore_received_spf_header` is 0 and `use_newest_received_spf_header` is 0 by default. This would imply that it should be using the existing header, and yet it's not.