From: "Daryl C. W. O'Shea" <[EMAIL PROTECTED]>
Steven Stern wrote:
These occur with spamassassin -D --lint. RDJ is up to date, as is
sa-update.
[6837] info: rules: meta test DIGEST_MULTIPLE has undefined dependency
'DCC_CHECK'
[6837] info: rules: meta test SARE_SPEC_PROLEO_M2a has dependency
'MIME_QP_LONG_LINE' with a zero score
[6837] info: rules: meta test SARE_HEAD_SUBJ_RAND has undefined
dependency 'SARE_XMAIL_SUSP2'
[6837] info: rules: meta test SARE_HEAD_SUBJ_RAND has undefined
dependency 'SARE_HEAD_XAUTH_WARN'
[6837] info: rules: meta test SARE_RD_SAFE has undefined dependency
'SARE_RD_SAFE_MKSHRT'
[6837] info: rules: meta test SARE_RD_SAFE has undefined dependency
'SARE_RD_SAFE_GT'
[6837] info: rules: meta test SARE_RD_SAFE has undefined dependency
'SARE_RD_SAFE_TINY'
[6837] info: rules: meta test SARE_OBFU_CIALIS has undefined dependency
'SARE_OBFU_CIALIS2'
[6837] info: rules: meta test FP_MIXED_PORN3 has undefined dependency
'FP_PENETRATION'
It's just info. Some of your rules have undefined dependencies or are
disabled via a zero score.
If the rule is part of a meta a zero score on the rule should not
matter. It should still be evaluated because ultimately it has an
indirect score via the meta rule.
I like to see the sub-rules of a meta rule hitting for tracking. So
I always issue a 0.001 score or something like that which will not
affect results materially.
{^_^}
