Re: Keeping plugin perl modules in /etc/spamassassin / /etc/mail/spamassassin

2011-08-11 Thread Benny Pedersen 

On Thu, 11 Aug 2011 18:12:06 -0400, dar...@chaosreigns.com wrote:

Anybody know why this page on the wiki says this works?  Does it 
actually

work anywhere?


in foo.pre:

loadplugin foo foo.pm

in foo.pm:

package foo

...



workds here just fine, but dont put loadplugin in cf files dammit :)

Re: Keeping plugin perl modules in /etc/spamassassin / /etc/mail/spamassassin

2011-08-11 Thread Axb 

On 2011-08-12 0:12, dar...@chaosreigns.com wrote:

http://wiki.apache.org/spamassassin/CustomPlugins says, twice, that the
perl modules for plugins can be kept in /etc/mail/spamassassin (aka
/etc/spamassassin, depending on your install).  Just finally tried it,
and it didn't work.  Perl complains that it can't find the file in its
module path, lists the directories in that pat, and doesn't contain
anything like /etc/spamassassin.

Anybody know why this page on the wiki says this works?  Does it actually
work anywhere?

I modified the wiki to reflect my experiences.


Plugins work fine

local.pre

loadplugin Mail::SpamAssassin::Plugin::DecodeShortURLs 
/etc/mail/spamassassin/DecodeShortURLs.pm



[20240] dbg: plugin: loading Mail::SpamAssassin::Plugin::DecodeShortURLs 
from /etc/mail/spamassassin/DecodeShortURLs.pm



I'd assume 3rd party modules for these plugins (if nor supplied by Perl 
should be installed in Perl paths.


Seems most plugins around do not require other that SA/Perl supplied 
modules so the issue never showed up.