https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5839
Summary: A missing or failed eval rule function can mistakenly
count as a rule hit
Product: Spamassassin
Version: 3.2.4
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: Libraries
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
A rule specifying an eval function which does not exist (or dies)
does not clear a $result variable, so the rule would count
as a hit if a previous eval rule fired.
The error does get reported as a 'warn:', although few would
notice, but the result is still wrong. E.g.:
[76898] dbg: rules: ran eval rule XXX ======> got hit (1)
[76898] warn: rules: failed to run XXX test, skipping:
[76898] warn: (Can't locate object method "check_xxx"
via package "Mail::SpamAssassin::PerMsgStatus ... )
This can happen if for example a rule from a new version is used
with SpamAssassin code from an earlier version, or if there is a
typo in eval function name in the rule specification, or if
the function dies for some reason.
Problem was reported by Michael Scheidell.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
