Keith Dunnett schrieb:
analyzer wrote:
server:~# spamassassin -V
SpamAssassin version 2.20
My provider have configured the system. Perhaps there is anything false.
Perhaps you have multiple copies of SpamAssassin on the system? Try
'whereis spamassassin'.
As Jonn said, these errors are likely to be the product of running SA
3.1.0 without loading the
necessary modules (by reason of using an old config file). That might
have been installed from
CPAN, rather than via Debian. The current Debian stable version is
3.0.3-2. You might try
'apt-cache showpkg spamassassin' to find out which version Debian
thinks it has installed.
If you don't mind managing the SpamAssassin installation yourself, you
can usually obtain a
newer version by installing via CPAN than using Debian packages. To
forcibly remove SA
and install the newest version, you could do the following (all as root):
1. apt-get remove spamassassin
2. whereis spamassassin
3. Delete anything still listed by 'whereis spamassassin', including
/etc/spamassassin
4. perl -MCPAN -e shell
5. Accept the defaults to set up the CPAN shell
6. In CPAN, type 'install Mail::SpamAssassin'.
7. Exit CPAN and cd /etc/spamassassin
8. Edit the configuration files local.cf and v310.pre according to
taste/need.
9. Test spamassassin as before.
10. When happy, google for RulesDuJour and decide whether you want it.
Many
of us find that it improves the effectiveness of SpamAssassin.
This is a fairly drastic solution, but ensures that you benefit from
the latest version. Do note
that this will no longer be upgraded for you by Debian's 'apt-get
upgrade', so you will have
to keep an eye out for new releases and update via CPAN. It's worth
the effort, though.
WARNING: Before doing this, make sure that you have perl 5.6.1 or
better, which is a
requirement of spamassassin 3.x. Also, please read the upgrade notes
available at
http://spamassassin.apache.org/full/3.1.x/dist/UPGRADE before
starting; you might
wish to take advantage of some of the new features.
And finally, as with any such advice, make sure that you understand
what I'm suggesting
and that it is what you want to do before you start typing commands.
If not, read the docs
or ask further questions.
HTH,
Keith
Here are the errors from starting sapd:
[13505] error: udp_timeout: no such method at
/usr/local/share/perl/5.6.1/Net/DN
S/Resolver.pm line 1136
[13505] error:
_Net::DNS::Resolver::AUTOLOAD('Net::DNS::Resolver=HASH(0x8a381c0)
', 3) called at
/usr/local/share/perl/5.6.1/Mail/SpamAssassin/DnsResolver.pm lin
e 97
[13505] error: _eval {...} called at
/usr/local/share/perl/5.6.1/Mail/SpamAssass
in/DnsResolver.pm line 85
[13505] error:
_Mail::SpamAssassin::DnsResolver::load_resolver('Mail::SpamAssass
in::DnsResolver=HASH(0x8a38034)') called at
/usr/local/share/perl/5.6.1/Mail/Spa
mAssassin/DnsResolver.pm line 65
[13505] error:
_Mail::SpamAssassin::DnsResolver::new('Mail::SpamAssassin::DnsRes
olver', 'Mail::SpamAssassin=HASH(0x80feeec)') called at
/usr/local/share/perl/5.
6.1/Mail/SpamAssassin.pm line 299
[13505] error: _Mail::SpamAssassin::new('Mail::SpamAssassin',
'Mail::SpamAssassi
n=HASH(0x80feeec)') called at /usr/local/bin/spamd line 686
[13505] warn: dns: Net::DNS version is 0.12, but need 0.34 at
/usr/local/share/p
erl/5.6.1/Mail/SpamAssassin/Dns.pm line 589.
[13505] info: spamd: server started on port 783/tcp (running version 3.1.0)
[13505] info: spamd: server pid: 13505
[13505] info: spamd: server successfully spawned child process, pid 13763
[13505] info: spamd: server successfully spawned child process, pid 13796
[13505] info: prefork: child states: IS
[13505] info: prefork: child states: II