Re: [qmailtoaster] Errors in SA

2005-12-14 Thread Jake Vickers
Riezal Ross wrote: First I tried changing local mirrors, it gave the same errors. I tried using mirrors from other countries and it still gave the errors. I suspect that it must've cached the .gz file as I already have it on my machine. So I gave up on that. You may try removing the .gz file

RE: [qmailtoaster] Errors in SA

2005-12-14 Thread Riezal Ross
] Errors in SA Riezal Ross wrote: First I tried changing local mirrors, it gave the same errors. I tried using mirrors from other countries and it still gave the errors. I suspect that it must've cached the .gz file as I already have it on my machine. So I gave up on that. You may try removing

Re: [qmailtoaster] Errors in SA

2005-12-13 Thread Jake Vickers
Riezal Ross wrote: I actually checked the directory and found that those files do exist in root/.spamassassin/y/sources/authors/id/A/AN/ANDK/CPAN-1.80.tar.gz and I am running CPAN from /root/.spamassassin You might try installing Bundle::CPAN from this location also; they package the perl

RE: [qmailtoaster] Errors in SA

2005-12-12 Thread Riezal Ross
Title: Message Anybody has any idea what'swrong with my bayes setup? Regards, Riezal Ross -Original Message-From: Riezal Ross [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 07, 2005 4:49 PMTo: qmailtoaster-list@qmailtoaster.comSubject: [qmailtoaster] Errors in SA I'm

Re: [qmailtoaster] Errors in SA

2005-12-12 Thread Jake Vickers
Riezal Ross wrote: /[3738] dbg: bayes: DB_File module not installed, cannot use bayes/ /[3738] warn: dns: Net::DNS version is 0.31, but need 0.34 at /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 589./ Cannot use bayes? Also, when I do sa-learn --spam against a

RE: [qmailtoaster] Errors in SA

2005-12-12 Thread Riezal Ross
, Riezal Ross -Original Message- From: Jake Vickers [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 13, 2005 9:29 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Errors in SA Riezal Ross wrote: /[3738] dbg: bayes: DB_File module not installed, cannot use

Re: [qmailtoaster] Errors in SA

2005-12-12 Thread Jake Vickers
Riezal Ross wrote: I get this error when using CPAN: [EMAIL PROTECTED] .spamassassin]# perl -MCPAN -e shell Can't locate CPAN.pm in @INC That file doesn't seem to exist anywhere on my system. Is there any other way to do the upgrade? Or can you point my in the right direction to get my CPAN

RE: [qmailtoaster] Errors in SA

2005-12-12 Thread Riezal Ross
: Jake Vickers [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 13, 2005 10:10 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Errors in SA Riezal Ross wrote: I get this error when using CPAN: [EMAIL PROTECTED] .spamassassin]# perl -MCPAN -e shell Can't locate CPAN.pm

Re: [qmailtoaster] Errors in SA

2005-12-12 Thread Jake Vickers
Riezal Ross wrote: Silly me, I didn't have CPAN install. I did a yum install perl-CPAN and it went of. I installed the modules recommended by Nick: Mail::SpamAssassin::Plugin::Pyzor IP::Country::Fast IO::Socket::SSL Archive::Tar IO::Zlib Some of them worked, some returned errors. Lastly, I

RE: [qmailtoaster] Errors in SA

2005-12-12 Thread Riezal Ross
- From: Jake Vickers [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 13, 2005 10:22 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Errors in SA Riezal Ross wrote: Silly me, I didn't have CPAN install. I did a yum install perl-CPAN and it went of. I installed the modules

[qmailtoaster] Errors in SA

2005-12-07 Thread Riezal Ross
Title: Errors in SA I'm still trying to get a grip on things here. I've just re-installed the new spamassassin-toaster and it looks to be booting up fine with no issues. When I run spamassassin -D --lint, it spews a whole lot of messages. There is one part that I'm concerned about: [3738]

Re: [qmailtoaster] Errors in SA

2005-12-07 Thread Jake Vickers
Riezal Ross wrote: I'm still trying to get a grip on things here. I've just re-installed the new spamassassin-toaster and it looks to be booting up fine with no issues. When I run spamassassin -D --lint, it spews a whole lot of messages. There is one part that I'm concerned about: /[3738]