Mailing List Archive

spamd not accessing site rules WAS: spamd not accessing user rules
----- Original Message -----
From: "Gorm Jensen" <gjensen@magma.ca>
To: "spamassassin" <spamassassin-users@incubator.apache.org>
Sent: Monday, February 16, 2004 4:28 PM
Subject: spamd not accessing user rules


> I am using SA2.63 on a RH7.2 system. spamd, running as "mail" is called
> from procmail as $USER, which is set by fetchmail as the user whose mail
is
> being downloaded. My setup is a common bayes database in
> /etc/mail/spamassassin for two users.
>
> The SA report inserted in each message shows that only the default rules
are
> applied, but none of the user rules, which are in /etc/mail/spamassassin.
> If spamassassin is run directly from the command line as "root" and as
> "mail", all rules are applied.
>
> Here is the maillog with procmail set to verbose and spamd set to debug.
>
> procmail: Executing "/usr/bin/spamc,-u,Gorm"
> Feb 16 12:54:04 myserver spamd[25419]: logmsg: connection from localhost
> [127.0.0.1] at port 49161
> Feb 16 12:54:04 myserver spamd[25419]: connection from localhost
[127.0.0.1]
> at port 49161
> Feb 16 12:54:04 myserver spamd[25436]: debug: read_scoreonly_config:
cannot
> open
> "/home/Gorm/.spamassassin/user_prefs": Permission denied
> Feb 16 12:54:04 myserver spamd[25436]: debug: user has changed
> Feb 16 12:54:04 myserver spamd[25436]: debug: bayes: 25436 untie-ing
> Feb 16 12:54:04 myserver spamd[25436]: debug: mkdir
/home/Gorm/.spamassassin
> failed: mkdir /home/Gorm/.spamassassin: Permission denied at
> /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin.pm line 1279
> Feb 16 12:54:04 myserver spamd[25436]: debug: bayes: no dbs present,
cannot
> scan: /home/Gorm/.spamassassin/bayes_toks
>
> During troubleshooting, I changed permissions on /home/Gorm to allow user
> "mail" to create a directory, but as can be seen above, that was denied
too
> by file permissions.
>
> Background: The system worked normally until I re-organised one large
> local rules file into five files. I tried removing one file at a time to
> test for a bad file, but nothing changed. (Of course, I tried --lint
too).
> I also deleted the bayes database files, but that did not help either.
>
> I'm a semi-newbie, so the logs give me a tease, but not something that I
can
> figure out. All help appreciated.

I used poor terminology in my original post (blush). I should have said
that spamd was not accessing "site rules", not "user rules". I have only
two users, so "user preferences" isn't needed on my system.

I tried adding DROPPRIVS=yes to /etc/procmailrc - no change
I tried changing ownership of all files in the site directory to "mail" -
no change.
Originally, the *.cf files were owned by root and group "mail" had r--
privilege. The bayes* files were owned by root and group "mail" had rw-
privilege. This setup worked on another machine; however, is setting all
files to mail.mail rwx------ a recommended practice?

Still groping for a solution...