https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7972
Bug ID: 7972
Summary: Version compatibility flagging method
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Libraries
Assignee: dev@spamassassin.apache.org
Reporter: apa...@hege.li
Target Milestone: Undefined
(Copy from Bug 7826)
Assuming we want to go with the welcomelist route, I'd still like to figure out
a more generic solution for defining "version compatibility". So people can
turn on some flag when they have checked their local configs and removed old
incompatibilities, so old duplicate USER_IN_BLACKLIST rules stop beeing seen. A
bit like postfix "compatibility_level".
Previous solution was loading/unloading module and "ifplugin
Mail::SpamAssassin::Plugin::RaciallyCharged". A bit awkward and way too
hardcoded.
I'm visioning something like "enable_compat welcomelist_blocklist" that one can
insert into init.pre. It would create
"Mail::SpamAssassin::Conf::compat_welcomelist_blacklist" function dynamically,
so we can do this check to skip rules:
if can(Mail::SpamAssassin::Conf::compat_welcomelist_blacklist)
Of course the same could be checked from plugins etc if necessary.
--
You are receiving this mail because:
You are the assignee for the bug.
