On Thu, June 25, 2009 10:35, rich...@buzzhost.co.uk wrote:
> A routine look in the logs shows me a steady warn in the logs.
> It's probably harmless - but I would like to solve it for tidiness:
>
>
> Thu Jun 18 16:45:21 2009 [12663] warn: config: created user preferences
> file: /var/lib/spamassassin/.spamassassin/user_prefs
> Tue Jun 23 16:58:42 2009 [13778] warn: config: cannot write
> to /root/.spamassassin/user_prefs: Permission denied
> Tue Jun 23 16:58:43 2009 [13778] warn: auto-whitelist: open of
> auto-whitelist file failed: locker: safe_lock: cannot create tmp
> lockfile /root/.spamassassin/auto-whitelist.lock.stinger.13778
> for /root/.spamassassin/auto-whitelist.lock: Permission denied
> Wed Jun 24 11:46:16 2009 [4734] warn: config: cannot write
> to /root/.spamassassin/user_prefs: Permission denied
> Wed Jun 24 11:46:17 2009 [4734] warn: auto-whitelist: open of
> auto-whitelist file failed: locker: safe_lock: cannot create tmp
> lockfile /root/.spamassassin/auto-whitelist.lock.stinger.4734
> for /root/.spamassassin/auto-whitelist.lock: Permission denied
> Wed Jun 24 12:08:10 2009 [4734] warn: config: cannot write
> to /root/.spamassassin/user_prefs: Permission denied
> Wed Jun 24 12:08:11 2009 [4734] warn: auto-whitelist: open of
> auto-whitelist file failed: locker: safe_lock: cannot create tmp
> lockfile /root/.spamassassin/auto-whitelist.lock.stinger.4734
> for /root/.spamassassin/auto-whitelist.lock: Permission denied
>
> I'm slightly confused as I see this;
> /var/lib/spamassassin/.spamassassin/user_prefs created,
> but then SA seems to be trying to write to /root/.spamassasin/...
>
> Probably my configuration - any pointers ?

check configs for awl path, and unset them, when its not set in user_prefs
you get permissions errors when not run as root, and not have it local to
the user trying

perldoc Mail::SpamAssassin::Conf
perldoc Mail::SpamAssassin::Plugin::AWL

tell more about what os, user you try test with

awl path must be local to each user not global for all users when sql is
not used


-- 
xpoint

Reply via email to