Spamassasin or clamd issue. Lot of spam

[oriongr]

Hi,

I just upgraded my Debian etch server to lenny. It has latest ISPconfig v2 on it.
Everything was ok except high cpu loads from clamav. I followed some instructions in the forum and I changed from ISPconfig's clamav to Debian's clamd.
Mails are scanned

X-Virus-Status: No
X-Virus-Checker-Version: clamassassin 1.2.4 with clamdscan / ClamAV 0.96.1/11334/Thu Jul  8 03:37:00 2010

but since I did that I receive a loooooot of spam. Like spamassasin stoped working.
Where should I check to see if ISPconfig's spamassasin is working ok?


Thanks

[oriongr]

If I try to run spamassasin I get this

zeus:/home/admispconfig/ispconfig/tools/spamassassin/usr/bin# ./spamassassin
Can't locate NetAddr/IP.pm in @INC (@INC contains: /home/admispconfig/ispconfig/tools/spamassassin/usr/share/perl/5.8.8 /etc/perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl) at /home/admispconfig/ispconfig/tools/spamassassin/usr/share/perl/5.8.8/Mail/SpamAssassin/NetSet.pm line 25.
BEGIN failed--compilation aborted at /home/admispconfig/ispconfig/tools/spamassassin/usr/share/perl/5.8.8/Mail/SpamAssassin/NetSet.pm line 25.
Compilation failed in require at /home/admispconfig/ispconfig/tools/spamassassin/usr/share/perl/5.8.8/Mail/SpamAssassin/Conf.pm line 86.
BEGIN failed--compilation aborted at /home/admispconfig/ispconfig/tools/spamassassin/usr/share/perl/5.8.8/Mail/SpamAssassin/Conf.pm line 86.
Compilation failed in require at /home/admispconfig/ispconfig/tools/spamassassin/usr/share/perl/5.8.8/Mail/SpamAssassin.pm line 71.
BEGIN failed--compilation aborted at /home/admispconfig/ispconfig/tools/spamassassin/usr/share/perl/5.8.8/Mail/SpamAssassin.pm line 71.
Compilation failed in require at ./spamassassin line 80.
BEGIN failed--compilation aborted at ./spamassassin line 80.

There is a differnce in perl version from ISPconfig and Debian Lenny?

Is that the case?

[oriongr]

I did some digging in the forum
http://www.howtoforge.com/forums/sho...25&postcount=4

This solved the errors. I think spamassasin should work now.

This forum is a treasure.
Thanks