On Wed, 2014-07-16 at 04:26 +0200, Karsten Bräckelmann wrote: > On Tue, 2014-07-15 at 00:11 -0500, Chris wrote: > > dbg: plugin: loading Mail::SpamAssassin::Plugin::DCC > > from /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Plugin/DCC.pm > > Debug states loading a plugin from "an explicitly given absolute > referenced file name", rather than resolving from @INC (in which case > there literally would be reported "from @INC"). > > > warn: plugin: failed to parse plugin > > /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Plugin/DCC.pm: > > Can't locate /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Plugin/DCC.pm > > in @INC (you may need to install ...) (@INC contains: ...) at ... > > Lint states the same. The explicitly given absolute referenced Perl > module cannot be parsed. Because it cannot be located. > > The module unable to be located being prefixed with a full, absolute > path is another hint. Stock SA loadplugin lines are not absolute, but > relative. > > > The SA stock site configuration regarding DCC is in v310.pre, commented > out by default. > > #loadplugin Mail::SpamAssassin::Plugin::DCC > > To enable DCC, un-comment, or add that option to a local .pre file. > > > What you have in your .pre (or .cf) site configuration is a custom > loadplugin option, with the perl module's path hardcoded. > > loadplugin Mail::SpamAssassin::Plugin::DCC > /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Plugin/DCC.pm > > The path is optional, and should only be given if absolutely necessary. > It certainly is not necessary with stock SA plugins. It isn't necessary > either with any plugin included in Perl @INC. > > To find and correct this issue, grep in your site config dir: > > grep DCC *.pre *.cf > > To find this and more similar issues: > > grep /usr/lib *.pre *.cf > > > > warn: plugin: failed to parse plugin /etc/spamassassin/clamav.pm: > > Can't locate File/Scan/ClamAV.pm in @INC ... > > This is a relative path. You didn't install F::S::ClamAV after setting > up the new system. > > > > Any advice/assistance would be appreciated. > > Glad to help. > > Though grepping through your site config might have helped. Or carefully > revisiting the config inherited from an other (and older) system. > You were right (as I knew you would be) I had a path pointing to an old path changed to the correct path and it worked fine. As far as File::Scan::ClamAV I've tried to install it several times and always get the same out put - http://pastebin.com/yDydeFwF
Thanks for the reply Chris
