On Mon, Feb 9, 2015 at 6:30 AM, Kevin A. McGrail <kmcgr...@pccc.com> wrote: > On 2/9/2015 4:12 AM, Reindl Harald wrote: >> >> what is that below introduced with tonights update and get triggered now >> for every single mail and why does such things not automatically get caught >> before push? > > It was part of a commit on Jan 30, > http://www.gossamer-threads.com/lists/spamassassin/commits/190790, that > likely needs a has_ function for a can() if encapsulation if you aren't > using the latest trunk to avoid warnings. > > Working on a patch now and a fix to the rules.
Hi KAM, Still seeing these, even after today's update, Feb 10 13:57:25 svr5 spamd[3922]: rules: failed to run T_SPF_HELO_PERMERROR test, skipping: Feb 10 13:57:25 svr5 spamd[3922]: (Can't locate object method "check_for_spf_helo_permerror" via package "Mail: [...]:SpamAssassin::PerMsgStatus" at (eval 1159) line 19, <GEN34> line 36. Feb 10 13:57:25 svr5 spamd[3922]: ) Feb 10 13:57:25 svr5 spamd[3922]: rules: failed to run T_SPF_TEMPERROR test, skipping: Feb 10 13:57:25 svr5 spamd[3922]: (Can't locate object method "check_for_spf_temperror" via package "Mail: [...]:SpamAssassin::PerMsgStatus" at (eval 1159) line 639, <GEN34> line 36. Feb 10 13:57:25 svr5 spamd[3922]: ) Feb 10 13:57:25 svr5 spamd[3922]: rules: failed to run T_SPF_PERMERROR test, skipping: Feb 10 13:57:25 svr5 spamd[3922]: (Can't locate object method "check_for_spf_permerror" via package "Mail: [...]:SpamAssassin::PerMsgStatus" at (eval 1159) line 809, <GEN34> line 36. Feb 10 13:57:25 svr5 spamd[3922]: ) Feb 10 13:57:25 svr5 spamd[3922]: rules: failed to run T_SPF_HELO_TEMPERROR test, skipping: Feb 10 13:57:25 svr5 spamd[3922]: (Can't locate object method "check_for_spf_helo_temperror" via package "Mail: [...]:SpamAssassin::PerMsgStatus" at (eval 1159) line 1154, <GEN34> line 36. Feb 10 13:57:25 svr5 spamd[3922]: ) Feb 10 13:57:25 svr5 spamd[3922]: spamd: clean message (-0.1/5.0) for test:106 in 0.2 seconds, 1642 bytes. What can we do to help fix this? -Jim P.
