Jeffrey Duncan wrote: > Okay, so I see that I have two versions of PerMsgStatus.pm (below) > > How do I remove one of them to get rid of the issues? > > Jeffrey Duncan wrote: > >> Thanks, >> >> What do you mean resolve? Here is the output ... >> >> >> [EMAIL PROTECTED] log]# locate PerMsgStatus.pm >> /usr/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm >> /usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm >> /usr/src/redhat/BUILD/Mail-SpamAssassin-3.1.0/lib/Mail/SpamAssassin/PerMsgStatus.pm >> /usr/src/redhat/BUILD/Mail-SpamAssassin-3.1.0/blib/lib/Mail/SpamAssassin/PerMsgStatus.pm >> /downloads/qmailrocks/perlmods/rpms/newmods/Mail-SpamAssassin-3.1.0/lib/Mail/SpamAssassin/PerMsgStatus.pm >> /downloads/qmailrocks/perlmods/rpms/newmods/Mail-SpamAssassin-3.1.0/blib/lib/Mail/SpamAssassin/PerMsgStatus.pm
I'd assume you installed an older version of SA while you were using perl 5.8.5. Later you upgraded to 5.8.6 and then installed 3.1.0 sometime afterward. The 3.1.0 installation did not see the outdated site_perl directory, thus never removed it. I'd suggest blowing away the old copy entirely with rm -rf: rm -rf /usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/ then try your SA. If that doesn't fix things, rm -rf both of them and re-install SA 3.1.0. While you're at it double-check for duplicate spamd and spamc scripts. That's less likely but it is possible that one is in /usr/bin and another is in /usr/local/bin..
