> Hi, > These are the lines in my local.cf: > > bayes_path /home/sharedspam/.spamassassin/bayes > auto_whitelist_path /home/sharedspam/.spamassassin/auto-whitelist > bayes_file_mode 777 > auto_whitelist_file_mode 777 > lock_method flock
777 is rather insecure... What's the output of ls -al on your .spamassassin directory? > Except for the last line, the others were also present for my > 2.63 config and I believed they worked fine. > > Lint and sync seem to work fine. I've also tried the following: > > ./check_whitelist /home/sharedspam/.spamassassin/auto-whitelist > -2.3 (-43.1/19) -- [EMAIL PROTECTED]|ip=217.15 > -2.0 (-6.1/3) -- [EMAIL PROTECTED]|ip=217.15 > -2.8 (-5.5/2) -- [EMAIL PROTECTED]|ip=none > -2.8 (-2.8/1) -- [EMAIL PROTECTED]|ip=217.15 > -2.6 (-2.6/1) -- [EMAIL PROTECTED]|ip=217.15 > -2.6 (-5.3/2) -- [EMAIL PROTECTED]|ip=217.15 > I'm assuming that's fine. Don't see a problem > Finally, I also tried: > spamassassin -D < > /root/.cpan/build/Mail-SpamAssassin-3.0.4/sample-spam.txt > > This gave me the following: > > From: Sender <[EMAIL PROTECTED]> > To: Recipient <[EMAIL PROTECTED]> > Subject: *****SPAM***** Test spam mail (GTUBE) > Date: Wed, 23 Jul 2003 23:30:00 +0200 > Message-Id: <[EMAIL PROTECTED]> > X-Spam-Flag: YES > X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on > mailhost.datastream.com.mt > X-Spam-Level: ************************************************** > X-Spam-Status: Yes, score=997.2 required=5.0 tests=ALL_TRUSTED, > DNS_FROM_AHBL_RHSBL,GTUBE autolearn=unavailable version=3.0.4 > > Wierdly this reports unavailable as opposed to failed. I think that for certain messages, such as ALL_TRUSTED, bayes learning is unavailable. At least, that is what I'm seeing here. > > -----Original Message----- > From: crisppy fernandes [mailto:[EMAIL PROTECTED] > Sent: 06 July 2005 12:28 > To: Joe Borg; users@spamassassin.apache.org > Subject: Re: Autolearn problem > > On 7/6/05, Joe Borg <[EMAIL PROTECTED]> wrote: > > Hi, > > I've tried moving the file. What happens is that a new one > is created; > > usually belonging to a different user on the system and > then, that get > > This is something strange. > > > stuck. In other words the problem keeps on reoccurring. > Which user? And as which user is spamassassin installed? As which user is spamd running, and as which users are spamd's children running?
