Thanks Bill...
tested...
>1. Add to local.cf, along with the other PYZOR_CHECK_2 lines you had:>>
>tflags PYZOR_CHECK_2 net>>Does that change whether the rule is hit?>>>2.
>Change the PYZOR_CHECK score line in 50_scores.cf to:>> score PYZOR_CHECK
>0.001 1.985 0.001 1.392>>Does that quiet the warning about the meta
>rule?>>>>If Test #1 makes PYZOR_CHECK_2 NOT match a message that matched
>without >it, then something is disabling 'net' rules and you need to find and
>>correct whatever is doing that if you want SA to work well.
PYZOR_CHECK_2 works well when tflag net is set...
>If Test #2 silences the warning, you've found what is PROBABLY a minor
>>cosmetic bug in SpamAssassin but MAY be a substantive one if it means >that
>meta rule is being skipped as a result of having detected the wrong >score in
>that line. Opening a bug report at >https://bz.apache.org/SpamAssassin/ would
>be helpful.
warning still present... :-(
This is a print Dumper of permsgstatus with a grep -i PYZOR:
'pyzor_available' => 1, }, 'Mail::SpamAssassin::Plugin::Pyzor' ),
'PYZOR_CHECK_2' => '2',
'PYZOR_CHECK' => '0',
'PYZOR_CHECK_2' => 'check_pyzor',
'PYZOR_CHECK' => 'check_pyzor',
'PYZOR_CHECK_2' => '/etc/mail/spamassassin/local.cf',
'PYZOR_CHECK' =>
'/var/lib/spamassassin/3.004001/updates_spamassassin_org/25_pyzor.cf',
'pyzor_timeout' => '3.5',
'Mail::SpamAssassin::Plugin::Pyzor' => 1,
'check_pyzor' => $VAR1->{'async'}{'main'}{'plugins'}{'plugins'}[6],
'updates_spamassassin_org/25_pyzor.cf' =>
'updates_spamassassin_org/25_pyzor.cf',
'PYZOR_CHECK' => 'Listed in Pyzor (http://pyzor.sf.net/)',
'PYZOR_CHECK_2' => 'Listed in Pyzor
(http://pyzor.sf.net/)' 'pyzor_path' => undef,
'DIGEST_MULTIPLE' => 'RAZOR2_CHECK +
DCC_CHECK + PYZOR_CHECKA > 1',
'setting' => 'use_pyzor'
'setting' => 'pyzor_max'
'setting' => 'pyzor_timeout'
'setting' => 'pyzor_options',
'setting' => 'pyzor_path',
'PYZOR_CHECK_2' => 13, 'PYZOR_CHECK'
=> 13, 'pyzor_options' => '',
'use_pyzor' => 1, 'PYZOR_CHECK_2' =>
'2', 'PYZOR_CHECK' => '0',
'PYZOR_CHECK_2' => '2',
'PYZOR_CHECK' => '0',
'PYZOR_CHECK_2' => '2', 'PYZOR_CHECK'
=> '0',
'pyzor_timeout' =>
$VAR1->{'async'}{'main'}{'plugins'}{'plugins'}[17]{'conf'}{'registered_commands'}[157],
'pyzor_path' =>
$VAR1->{'async'}{'main'}{'plugins'}{'plugins'}[17]{'conf'}{'registered_commands'}[159],
'pyzor_options' =>
$VAR1->{'async'}{'main'}{'plugins'}{'plugins'}[17]{'conf'}{'registered_commands'}[158],
'use_pyzor' =>
$VAR1->{'async'}{'main'}{'plugins'}{'plugins'}[17]{'conf'}{'registered_commands'}[155],
'pyzor_max' =>
$VAR1->{'async'}{'main'}{'plugins'}{'plugins'}[17]{'conf'}{'registered_commands'}[156],
'pyzor_max' => 5,
It seems PYZOR_CHECK is taken from file
/var/lib/spamassassin/3.004001/updates_spamassassin_org/25_pyzor.cf that looks
like:
ifplugin Mail::SpamAssassin::Plugin::Pyzor full PYZOR_CHECK
eval:check_pyzor() describe PYZOR_CHECK Listed in Pyzor
(http://pyzor.sf.net/) tflags PYZOR_CHECK net reuse PYZOR_CHECK
endif
and 50_scores.cf looks as suggested by Bill:
score PYZOR_CHECK 0.001 1.985 0.001 1.392 so still wondering about the
Dumper line: 'PYZOR_CHECK' => '0', i have even performed a ext4 fs deep
check to discard any drive corruption issue....
