[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vps-mail] VPS2, Bayes problem



I keep getting this set of messages:

>
> 2974-Mar 31 12:22:14 ddai spamd[67632]: got connection
> over /var/run/spamd.sock

> 2975-Mar 31 12:22:14 ddai spamd[19137]: info: setuid to
> root succeeded

> 2976-Mar 31 12:22:14 ddai spamd[19137]: Still running as
> root: user not specified with -u, not found, or set to
> root. Fall back to nobody.

> 2977-Mar 31 12:22:14 ddai spamd[19137]: processing message
> <406B283A.36A19246@xxxxxxxxxxxxxxxxxxxx> for root:65534.

> 2978:Mar 31 12:22:14 ddai spamd[19137]: cannot write to
> /root/.spamassassin/bayes_journal, Bayes db update ignored

I am using one Bayes database server wide. Currently I have
removed the DROPPRIVS=yes line from the procmailrc
configuration, because I thought it was inappropriate to
this context. That is, I thought that I should maintain
the user as root. (However, I also had Bayes problems when
DROPPRIVS was set - I had removed it partly to try to
rectify those)

bayes_journal was set to 600 - I have changed it to 700

bayes_toks and bayes_seen are currently set to 777, as is
the .root/spamassassin directory.  I think these settings
are overbroad, but I'm having a lot of problems with getting
permissions set properly to run programs on the VPS2. It was
quite a struggle to get the program to even use Bayes; now
I've got it reading Bayes but not writing to it.

Help???

-Abigail

======================================================================
This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
Before posting a question, please search the archives (see above URL).


Main Index | Thread Index
Match: Format: Sort by:
Search: