How about file permissions on the directories and the .pm files? Maybe perl can't read the files, even though it knows what path it should be looking in?
C Chris Cosentino wrote: CC> I edited "spamassassin" and added the following lines (probably CC> overkill...) near the other "use lib" entries: CC> CC> use lib '/home/user/SpamAssassin/lib'; CC> use lib '/home/user/SpamAssassin/lib/Mail'; CC> use lib '/home/user/SpamAssassin/lib/Mail/SpamAssassin'; CC> CC> Now my procmail log file is clean (woot), but I still get the "Failed to CC> run A_FROM_IN_AUTO_WLIST SpamAssassin test" when testing from the command line. CC> CC> So, something is funky somewhere, but according to the log there are no CC> more errors. Thanks! CC> CC> At Wednesday 03:12 PM 5/1/2002, Craig R Hughes wrote: CC> >Yeah, that's probably it then. Sounds like perl isn't using the path where CC> >you've got SA installed in its lib path. Try something like CC> > CC> >perl -I$HOME/path/to/where/sa/installed spamassassin -t < message CC> > CC> >That should force it to be able to find the perl libs it needs. CC> > CC> >C CC> > CC> >Chris Cosentino wrote: CC> > CC> >CC> Problem is that it's a "clean" install. I downloaded the latest "2.20" CC> >code CC> >CC> and installed it for "Personal" use (it's not site wide). CC> >CC> CC> >CC> When I run the test from the command line I get only the following error: CC> >CC> CC> >CC> === CC> >CC> CC> >CC> HOST$ spamassassin -t < sample-spam.txt > spam.out CC> >CC> CC> >CC> Failed to run A_FROM_IN_AUTO_WLIST SpamAssassin test, skipping: CC> >CC> (Can't locate object method "check_for_auto_whitelist" via CC> >package CC> >CC> "Mail::SpamAssassin::PerMsgStatus" (perhaps you forgot to load CC> >CC> "Mail::SpamAssassin::PerMsgStatus"?) at CC> >CC> lib/Mail/SpamAssassin/PerMsgStatus.pm line 1529. CC> >CC> ) CC> >CC> CC> >CC> === CC> >CC> CC> >CC> Like I said, it's a clean install, no earlier version had been installed. CC> >CC> Perhaps it's a PERL thing where it can't find the proper modules? When run CC> >CC> from the command line it's not generating the same errors as it does when CC> >CC> it's run by procmail. CC> >CC> CC> >CC> -Chris CC> >CC> CC> CC> -- CC> Chris Cosentino CC> Cisco Systems, Inc. CC> [EMAIL PROTECTED] CC> <mailto:[EMAIL PROTECTED]> CC> CC> CC> _______________________________________________________________ CC> CC> Have big pipes? SourceForge.net is looking for download mirrors. We supply CC> the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] CC> _______________________________________________ CC> Spamassassin-talk mailing list CC> [EMAIL PROTECTED] CC> https://lists.sourceforge.net/lists/listinfo/spamassassin-talk CC> CC> CC> _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
