I've been seeing this problem too. We really need to come up with a
permanent fix for this.

>From what I've observed, it appears that spamassassin -D --lint can create
these files, perhaps if/when it syncs the journal, perhaps during
autoexpire. I'm not sure the exact conditions, but I've seen it happen.

Do you have a cron job running spammassassin or sa-learn? If you're running
sa-learn, you'll need to use the '-u vpopmail' and that should work.

I've been trying to find a way to run spamassassin -D --lint as vpopmail
though, and haven't been successful. Does anyone know of a way to do this?
If not, I'd say that the basic toaster is broken (jmho) and needs a fix.

Quinn Comendant wrote:
> How do you guys keep reins on your /home/vpopmail/.spamassassin/* files? I 
> find that after running sa-learn --sync, etc the bayes_toks file becomes 
> root:root 600, and I get these errors in the spamd log:
> 
> 
> 2006-11-06 18:15:15.237817500 [23333] info: spamd: connection from localhost 
> [127.0.0.1] at port 47865
> 2006-11-06 18:15:15.244756500 [23333] warn: bayes: cannot open bayes 
> databases /home/vpopmail/.spamassassin/bayes_* R/O: tie failed: Permission 
> denied
> 2006-11-06 18:15:15.258772500 [23333] info: spamd: processing message <[EMAIL 
> PROTECTED]> for [EMAIL PROTECTED]:89
> 2006-11-06 18:15:15.260484500 [23333] warn: bayes: cannot open bayes 
> databases /home/vpopmail/.spamassassin/bayes_* R/O: tie failed: Permission 
> denied
> 2006-11-06 18:15:15.671482500 [23333] warn: bayes: cannot open bayes 
> databases /home/vpopmail/.spamassassin/bayes_* R/O: tie failed: Permission 
> denied
> 
> 
> I tried setting chown vpopmail:vchkpw and setting chmod 666, but something 
> keep setting it back to root:root.
> 
> Huh?
> 
> Q
> 


-- 
-Eric 'shubes'

---------------------------------------------------------------------
     QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to