On 11 Dec 2018, at 16:37, Chris Pollock wrote: > On Mon, 2018-12-10 at 13:09 -0500, Bill Cole wrote: [...] >> Anyway, as of today I've capped those 2 subrules at levels which >> leave ample space to still match the target spam. Should show up in >> tomorrow's update.
I was wrong. The addition of a 'maxhits' parameter to the two subrules
apparently didn't get committed in time for the nightly rule promotion run. It
was in r1848602 and the current ruleset is still at r1848555. Assuming all goes
well tonight, the change will appear tomorrow.
Rule updates never work quite as fast as I hope...
> I see in today's update that the subrule was changed from this:
>
> if can(Mail::SpamAssassin::Conf::feature_bug6558_free)
> ifplugin Mail::SpamAssassin::Plugin::ReplaceTags
> meta T_MIXED_ES ( __LOWER_E > 20 ) && (
> __E_LIKE_LETTER > ( (__LOWER_E * 14 ) / 10) ) && ( ( __E_LIKE_LETTER /
> __LOWER_E ) < 10 )
> describe T_MIXED_ES Too many es are not es
That's the functional meta-rule.
> To this:
>
> if can(Mail::SpamAssassin::Conf::feature_bug6558_free)
> ifplugin Mail::SpamAssassin::Plugin::ReplaceTags
> body __E_LIKE_LETTER /<E>/
> tflags __E_LIKE_LETTER multiple
That's one subrule. Once my change filters through the update process, the
'tflags' lines for __E_LIKE_LETTER and __LOWER_E will be:
tflags __LOWER_E multiple maxhits=250
tflags __E_LIKE_LETTER multiple maxhits=400
--
Bill Cole
signature.asc
Description: OpenPGP digital signature
