SA does not allow running it as 'root' user. It is considered a security
risk. SA files also should not be in 'root' user folder. Should be in
something like /var/filter/.spamassassin  (filter being the name of the
user)

You need to have a user such as 'filter' run it.

Here is a fairly good write-up.

http://advosys.ca/papers/postfix-filtering.html





> Why is this?  And how can I fix it?
>
>>and B: that it cannot write to /root/.spamassassin/bayes_journal.
>>
>>The file had disappeared!
>
>>I went back thru the shell history to
>> make sure I hadn't done anything stupid, but the only thing between
>> the time it worked, and the files disappearance was my looking at
>> it with the 'less' file viewer.
>>
>>So I touched a new one and set the perms to 0666 so it would be
>>writable.
>
> Is this some sort of a berkeleyDB file?  If so, how can I regenerate
> it properly?
>
>>That didn't make any difference.  The other files in that directory
>>are being updated if I run a session of sa-learn, but that file
>>isn't being touched, and although the dates are being updated for
>>the other 2 main files, no content is actually being added to them
>> by the sa-learn session as evidence by their unchanging size of
>> several megs each.
>>
>>However, it does seem to be filtering the spam as well as before
>> after I updated the rules for the 2nd filter in kmail as the marker
>> strings had been changed some from the 2.64 version.  Its also not
>> marking the subject line [SPAM] like it did before. I'd like it to
>> if possible.
>>
>>>>From this amount of data, can it be determined whats wrong?
>>
>>Any help accepted with glee & thanks.
>
> --
> Cheers, Gene
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> 99.34% setiathome rank, not too shabby for a WV hillbilly
> Yahoo.com and AOL/TW attorneys please note, additions to the above
> message by Gene Heskett are:
> Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
>

Reply via email to