https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6074
Summary: parse-rules-for-masses shouldn't use a separate rules
parser
Product: Spamassassin
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
Component: Masses
AssignedTo: [email protected]
ReportedBy: [email protected]
Depends on: 6012
parse-rules-for-masses parses SpamAssassin rules for use in the scoring
process, but it does so in a manner that is completely different than
Mail::SpamAssassin::Conf. For example, parse-rules-for-masses is unable to
handle conditional rule definitions, and it makes it more difficult to add new
rule types.
It should be easy to replace parse-rules-for-masses with a script that builds a
Mail::SpamAssassin::Conf object, parses the rules and dumps the results in the
same format as p-r-f-m.
The only tricky part is that p-r-f-m currently is able to read "#reuse" and
"#<gen:mutable>" instructions directly from the config. The "#reuse" issue will
be solved with bug 6012. To handle mutable scores, we might need to make a
"notmutable" tflag (and assume everything else is mutable) to replace the
"<gen:mutable>" instruction.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
