On Tue, 2010-09-21 at 14:45 +0200, Cédric Jeanneret wrote:
> On Mon, 20 Sep 2010 10:42:22 -0400, Randy Ramsdell wrote:
> > Cédric Jeanneret wrote:
> >> Sep 20 12:25:06 hostname spamd[6157]: plugin: eval failed: bayes: (in
> >> learn) locker: safe_lock: cannot create tmp lockfile
> >> /home/USER/.spamassassin/bayes.lock.host.domain.ltd.6157 for
> >> /home/USER/.spamassassin/bayes.lock: Permission denied
> >>
> >> Is it possble to define the lockfile to, say, /tmp/ ?
This alone won't help much. If you cannot write the lock file, odds are
you cannot write the actual Bayes DBs either.
> >> As I don't have only one user, it can be nice to set the lockfile
> >> somewhere else on the system, where SA process can write. I didn't see
> >> anything about such a configuration variable....
> >>
> >> SA runs as "vmail" user, if it can help.
Please elaborate. How exactly do you run SA, and how do you pass it
mail? If that would be spamd running as user vmail, it would not even
attempt to use the recipient's $HOME, since it cannot suid.
> > SA can write to the users directories. You have something mis-configured
> > or you hosed the perms in the directory.
>
> well, rights are a bit "hard", like :
> drwx------ 24 tengu tengu 1528 Sep 20 10:16 tengu
>
> More over, some users are virtual.
Got to admit, I'm slightly confused. Some users. Does that include the
one in your originally reported error log message? If so, why does a
virtual user have a $HOME?
I guess the answer really depends on how you have SA integrated. Though
given you're running SA as a dedicated system user, site-wide Bayes
seems to be what you're looking for. Did you check the wiki and docs for
site-wide setup?
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
