You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by David Borton <da...@santafe.edu> on 2004/05/19 18:18:18 UTC

not filtering [was help: bayes database error}

It's me back again... still looking for a bit of guidance.

SA is still letting all the spam (even GTUBE) slip by.  Using 
spamassassin -D --lint I may have found more clues about why  Please 
let me know if this is relevant and if so how to change it:

debug: using  "/usr/share/spamassasin" for default rules dir
debug: using  "/etc/spamassassin" for site rules dir

Neither one of these directories exist.  Are they required?

A less interesting clue is this message:

debug:  is Net::DNS::Resolver available? no
debug:  is DNS available? 0

I'm sure DNS is working properly here at this site.

Thanks,

	David Borton
	Computer Systems Manager
	Santa Fe Institute

On May 18, 2004, at 10:49 AM, David Borton wrote:

> Thanks to Steve Yuroff and someone else who replied (sorry I deleted 
> your message).  This is a great community.
>
> One suggestion was to do a 'sa-learn --rebuild'.   This didn't work 
> (same errors) but it got me thinking... Since every sa-learn option 
> gave the errors, I just deleted the bayes_* files, and started over.
>
> The sa-learn --ham and --spam did their thing, now no errors!
>
> But... SA is still not catching anything, even the GTUBE 
> sample-spam.txt.
>
> The SA headers (X-Spam-Flag, X-Spam-Level, X-Spam-Status) are NOT 
> being added to the message.   Only the "X-Spam-Checker-Version: 
> SpamAssassin 3.0.0-r9809" is getting inserted.
>
> I need to figure out what role Bayes is playing in this if any.    I 
> would be happy for the moment to disable Bayes, get my users up and 
> running.   Can SA run without Bayes?  And if so how do you do that?
>
> I suspect some other factor is at play, because even with the contents 
> of .spamassassin folder reset to default, SA isn't adding any headers. 
>  FYI, that folder looks like this:
> ls -l .spamassassin
> total 52
>   24 -rw-------    1 david    sfistaff    24576 May 18 10:44 bayes_seen
>   24 -rw-------    1 david    sfistaff    24576 May 18 10:44 bayes_toks
>    4 -rw-r-----    1 david    sfistaff     1550 May 18 10:43 user_prefs
>
> Thank you all,
>
>     David Borton
>     Computer Systems Manager
>     Santa Fe Institute
>     www.santafe.edu
>
> On May 17, 2004, at 5:34 PM, David Borton wrote:
>
>> Hi everybody,
>>
>> I have seen lots of references to this error, but can someone steer 
>> me in the right direction for FIXING it?
>>
>> The error is the very popular:
>>    Cannot open bayes databases /home/david/.spamassassin/bayes_* R/W: 
>> tie failed:
>>
>> Here's what the procmail log says when handling the GTUBE message.  
>> Of course it should say "Match on "^X-Spam-Level: 
>> \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*":
>>
>> procmail: Locking "spamassassin.lock"
>> procmail: Executing "/opt/perl5.8.3/bin/spamassassin"
>> Cannot open bayes databases /home/david/.spamassassin/bayes_* R/O: 
>> tie failed:
>> Cannot open bayes databases /home/david/.spamassassin/bayes_* R/O: 
>> tie failed:
>> Cannot open bayes databases /home/david/.spamassassin/bayes_* R/W: 
>> tie failed:
>> [snip, snip]
  


Re: not filtering [was help: bayes database error}

Posted by Clive Eisen <cl...@serendipita.com>.
David Borton wrote:

>
> A less interesting clue is this message:
>
> debug:  is Net::DNS::Resolver available? no
> debug:  is DNS available? 0
>
install Net::DNS from CPAN