You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Thomas Schlosser <ts...@googlemail.com> on 2006/06/10 15:38:53 UTC

Problems after upgrade to SA 3.1.3: PerMsgStatus.pm can't locate object methods "check_for_spf_neutral"....

Hi,

I have updated my SA installation yesterday. Most but not all seems to run
well.
In my mail.log I constantly find these errors all referring on some methods
called from PerMsgStatus.pm:

----snip----
Jun 10 12:21:54 homesrv spamd[6367]: Failed to run __ENV_AND_HDR_FROM_MATCH
SpamAssassin test, skipping:__(Can't locate object method
"check_for_matching_env_and_hdr_from" via package
"Mail::SpamAssassin::PerMsgStatus" at
/usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line
2340, <GEN105> line 522._)
Jun 10 12:21:54 homesrv spamd[6367]: Failed to run USER_IN_DEF_SPF_WL
SpamAssassin test, skipping:__(Can't locate object method
"check_for_def_spf_whitelist_from" via package
"Mail::SpamAssassin::PerMsgStatus" at
/usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line
2340, <GEN105> line 522._)
Jun 10 12:21:54 homesrv spamd[6367]: Failed to run RATWARE_EFROM
SpamAssassin test, skipping:__(Can't locate object method
"check_ratware_envelope_from" via package "Mail::SpamAssassin::PerMsgStatus"
at /usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line
2340, <GEN105> line 522._)
Jun 10 12:21:54 homesrv spamd[6367]: Failed to run __RATWARE_NAME_ID
SpamAssassin test, skipping:__(Can't locate object method
"check_ratware_name_id" via package "Mail::SpamAssassin::PerMsgStatus" at
/usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line
2340, <GEN105> line 522._)
Jun 10 12:21:54 homesrv spamd[6367]: Failed to run SPF_NEUTRAL SpamAssassin
test, skipping:__(Can't locate object method "check_for_spf_neutral" via
package "Mail::SpamAssassin::PerMsgStatus" at
/usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line
2340, <GEN105> line 522._)
Jun 10 12:21:54 homesrv spamd[6367]: Failed to run USER_IN_SPF_WHITELIST
SpamAssassin test, skipping:__(Can't locate object method
"check_for_spf_whitelist_from" via package
"Mail::SpamAssassin::PerMsgStatus" at
/usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line
2340, <GEN105> line 522._)
----snap---
Some mails e received in the meanwhile where correctly identified as spam,
so genereally it seems to work. Most of them qualified by
"URIBL_xx_SURBL"-tests.

I am running SA as spamd/spamc under a postfix on SUSE 9.3
homesrv:/etc/mail/spamassassin # spamassassin -V
SpamAssassin version 3.1.3
  running on Perl version 5.8.6

I updated it via perl -MCPAN - e shell -> force install Mail::SpamAssassin
The output was too long to have a chance to see if any problems have been
reportet.
THe install without force reported 99,xx% ok.

Interestingly spamassassin -V report 3.1.3, but spam mails contain a
"version=3.0.4" which was the previously run version.
Is this ahint (on a now mixed installation)?

Any hints how I can debug the situation?
I tried to use "spamassassin -V <mail.txt" to check for more information.
Without success.

Thanks for any feedback
Thomas

Re: Problems after upgrade to SA 3.1.3: PerMsgStatus.pm can't locate object methods "check_for_spf_neutral"....

Posted by Thomas Schlosser <ts...@googlemail.com>.
Thanks for the immediate answer!
It seems that the old SA was under
/usr/lib/perl5/vendor_perl/5.8.6/Mail/SpamAssassin/
while the new one under /usr/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/

rpm reported two packages spamassassin and perl-spamassassin.
I have deinstalled these using YAST (rpm reported dependencies, YAST too,
but I am used to YAST more)

Currently I am reinstalling via perl -MCPAN and hope, that the situation
will change to the better ;-)

Thx for the moment
Thomas


2006/6/10, Radoslaw Zielinski <ra...@gmail.com>:
>
> Thomas Schlosser <ts...@googlemail.com> [10-06-2006 15:38]:
> [...]
> > I updated it via perl -MCPAN - e shell -> force install
> Mail::SpamAssassin
> > The output was too long to have a chance to see if any problems have
> been
> > reportet.
>
> New SA should have been installed somewhere around /usr/local (if your
> perl is build with -Dvendorlib; probably is).  Locate and uninstall old
> version of SA:
>
>   find `perl -le 'map print,grep/\//,@INC'` | grep SpamAssassin
>
> I guess the right way in your case would be 'rpm -qa|grep -i spamas' and
> rpm -e the output.  You might have to reinstall using CPAN.pm afterwards.
>
> --
> Radosław Zieliński <ra...@pld-linux.org>
>
>
>

Re: Problems after upgrade to SA 3.1.3: PerMsgStatus.pm can't locate object methods "check_for_spf_neutral"....

Posted by Radoslaw Zielinski <ra...@gmail.com>.
Thomas Schlosser <ts...@googlemail.com> [10-06-2006 15:38]:
[...]
> I updated it via perl -MCPAN - e shell -> force install Mail::SpamAssassin
> The output was too long to have a chance to see if any problems have been
> reportet.

New SA should have been installed somewhere around /usr/local (if your
perl is build with -Dvendorlib; probably is).  Locate and uninstall old
version of SA:

  find `perl -le 'map print,grep/\//,@INC'` | grep SpamAssassin

I guess the right way in your case would be 'rpm -qa|grep -i spamas' and
rpm -e the output.  You might have to reinstall using CPAN.pm afterwards.

-- 
Radosław Zieliński <ra...@pld-linux.org>