[prev in list] [next in list] [prev in thread] [next in thread]
List: spamassassin-devel
Subject: [Bug 7905] New: Meta tests that use networking should not be ignored in maybe_header_only and maybe_
From: bugzilla-daemon () spamassassin ! apache ! org
Date: 2021-05-10 18:29:31
Message-ID: bug-7905-26 () https ! bz ! apache ! org/SpamAssassin/
[Download RAW message or body]
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7905
Bug ID: 7905
Summary: Meta tests that use networking should not be ignored
in maybe_header_only and maybe_body_only
Product: Spamassassin
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Learner
Assignee: dev@spamassassin.apache.org
Reporter: bert@bhack.net
Target Milestone: Undefined
Currently when tests are evaluated for the header and body scores for Bayes
autolearning, meta tests that define that they are network tests (tflags = net)
are fully ignored. I would argue that this should not be the case.
Specifically, the code within Conf.pm for maybe_header_only and maybe_body_only
both contain code that when meta tests are passed to it, they are either not
considered when the network tflag is set (which this bug is about) or always
scored (which has other problems I will file another bug about).
I don't understand why requiring network functionality automatically
disqualifies a meta test, but then does not disqualify a non-meta test.
Considering that a meta test combines for example two URI tests that use
external databases available through some sort of DNS or HTTP API, then both
tests should set the network flag, as well as the meta test that derives from
it (if I understand things correctly). I don't see why that inherently makes
that test more or less relevant for defining whether or not it's relevant for
autolearning.
--
You are receiving this mail because:
You are the assignee for the bug.=
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic