You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2018/09/19 19:09:50 UTC

[Bug 7627] warn: config: Strange rule token: 0.001

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7627

John Hardin <jh...@impsec.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jhardin@impsec.org

--- Comment #1 from John Hardin <jh...@impsec.org> ---
(In reply to Reindl Harald from comment #0)
> Sep 19 12:36:22.977 [1193328] warn: config: Strange rule token: 0.001
> *that* is not helpful without mention file and line

Agreed.

Not sure whether we *have* a file/line available at that point in the parser
code.

The parser includes the rule name in the lint_warn() parameters but that
apparently gets discarded. This may be a symptom of a wider bug in lint
logging...


This is the cause:
> meta T_OBFU_ATTACH_MISSP 0.001

That appears nowhere in the base rules.

The number there is not a score, it's whether the rule hits. Something like

  meta T_OBFU_ATTACH_MISSP 0

is done to satisfy dependencies with a rule that never hits.

Set that to either 0 if you want to pretend the rule never hits, or 1 if you
want to pretend the rule always hits.

-- 
You are receiving this mail because:
You are the assignee for the bug.