Hi all,
So, I just upgraded to Mail::SPF v2.008 (via the
perl-Mail-SPF package from rpmforge-extras), and the error is still
occurring. It would appear that v2.008 does NOT fix this issue.
I also upgraded to SpamAssassin 3.3.2 (again via
rpmforge-extras), but this didn't resolve the issue, either. (I
didn't expect it to, since I am fairly certain the error is within
Mail::SPF, but I figured I'd mention it.)
The error doesn't occur on every call to spamd, but it's
definitely quite often. I have not been able to figure out why some
calls to spamd don't trigger this error (maybe they're using v2 of
Record.pm instead of v1, don't know).
Does anyone have ideas on how to resolve this? I'm not so
much worried about it filling up my maillog (disk space is cheap),
more so that I'm worrying SA isn't working as optimally as it could,
i.e. that some tests which should hit end up failing due to this
error and some spam therefore gets missed (FNs).
Any ideas are most welcome.
Thanks.
--- Amir
At 12:01 AM -0600 06/13/2013, Amir 'CG' Caspi wrote:
Hi all,
I am getting the follow error peppering my maillogs:
Jun 13 01:26:42 kismet spamd[24575]: spf: lookup failed: Can't locate
object method "new_from_string" via package "Mail::SPF::v1::Record"
at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SPF/Server.pm line 524.
This occurs very often, seemingly with every call to spamd.
I've googled for this error and have found only a couple of previous
reports, one from 2008 and one from 2011. This error appears to be
very long-lived, going back at least 5 years, but neither of the two
reports I did find could offer any resolution. Hence, I figured I'd
try asking again.
For reference, I am on CentOS 5.8, running SpamAssassin 3.3.1 and
Mail::SPF v2.007. My spamd is running with the following flags:
--max-conn-per-child=1 -d -c -m5 -H
Is this an error with SpamAssassin, or with Mail::SPF? Any ideas on
how to fix it? Mail::SPF is up to v2.008, but I don't believe it has
yet been packaged for CentOS/RHEL 5.x (and may never be), and I have
no idea if it fixes the error, anyway.
Any help would be appreciated.
Thanks!
--- Amir
