Loren Wilton [EMAIL PROTECTED] writes:
Is there a way that [user rules] could be saved in a more-compiled
state when used with spamd and similar? Maybe name the rules with the
username as part of the procedure name, and just add them to the
namespace the first time encountered?
Beyond the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Quinlan writes:
Loren Wilton [EMAIL PROTECTED] writes:
Is there a way that [user rules] could be saved in a more-compiled
state when used with spamd and similar? Maybe name the rules with the
username as part of the procedure name,
Justin Mason [EMAIL PROTECTED] writes:
I don't get it -- how does that help?
Basically, user rule would always run last. Something like:
for (@priorities) {
standard prorities loop
}
if ($allow_user_rules $defined_rules{$user}) {
do_xxx_tests($user, ...); # $user is the priority
http://bugzilla.spamassassin.org/show_bug.cgi?id=4497
Summary: reorganise PerMsgStatus code
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
I know user rules aren't real popular with the sa dev community, however
that attitude isn't universally shared by sa users. Therefore may I
suggest:
Would it be possible when reorganizing things to come up with some
semi-persistant storage for compiled user rules, so that they don't have to
be
