From: "Logan Shaw" <[EMAIL PROTECTED]>
From: "Theo Van Dinter" <[EMAIL PROTECTED]>
On Sat, Aug 26, 2006 at 07:14:18PM -0700, jdow wrote:
Is there some magic to the .pre files that makes it important to have
the load_plugins there?
Yes, pre files are loaded before anything else, so the plugins loaded from
there can be used in all cf files.
On Sat, 26 Aug 2006, jdow wrote:
<<jdow>> That suggests a 00_ prefix for local plugins would be
sufficient to cause them to be loaded before other custom plugins.
It's Monday morning so maybe my brain is in a fog, but
doesn't SpamAssassin process everything in one directory in
lexicographical order, then move on to the next dir? If so,
the 00_ trick would only be enough to order things within one
directory and thus wouldn't be sufficient for foo.pre in dir2
to go before bar.cf in dir1.
As I understand it, SpamAssassin solves this problem by doing
one pass through all dirs for *.pre then another pass through
all dirs for *.cf. So unless SpamAssassin is updated to merge
the contents of all dirs, then do a lexicographical pass of
the merged set, the 00_ trick won't work.
/etc/mail/spamassassin is the first director considered to be
user customizable in the scan path. If SpamAssassin were to loop
for foo.pm support before that point it'd be doing a bad thing.
And indeed a name of ___foo.cf might be in order to make sure
it is REALLY the first thing. And any LATER directories, like
~/.spamassassin/user_prefs would be able to use items from
foo.pm.
{^_^}
