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.
<<jdow>> That suggests a 00_ prefix for local plugins would be
sufficient to cause them to be loaded before other custom plugins.
If "foo.pm" is a local plugin there is no reason to presume that
any native rules would address it. (And for that matter rather
few other rule sets would likely address it. But 00_ should take
care of that issue.) Once something is distributed WITH SpamAssassin
then it ought to go into a .pre file. Until then SpamAssassin default
rule sets should not address it nor presume it is there.
I do NOT like including local modules in the perl5 path SpamAssassin
directory tree. That gets updated and the modules would potentially
get lost or overwritten, which is worse. That's why I suggested the
local_plugin directory.
{^_^}
