Trouble with Bayes

[Glenn Steen]

On 30/08/06, Martin <martin.lyberg at gmail.com> wrote:
> Glenn Steen wrote:
>
> > Might be that you have some further issue "above" what can be seen in
> > that listing (postfix lacking read privs on a dir further up). Do
> > su - postfix -s /bin/sh
> > cd /var/spool/MailScanner/spamassassin
> > ... does that work?
>
> Glenn,
>
> Both commands works with no error. Any other clue?
>
> Thank you
>
> / Martin
>
Right. And as the postfix user, doing a
spamassassin --lint -D 2>&1 | less -e
everything works as expected, right?
Is that lint snippet from MailWatch, perhaps? In that case, you need
do the same test for the apache user (whatever that is on your system.
It is "apache" on mine:).

The way to get everything to work with Postfix and MailWatch (if that
is the problem) is to make the necessary parts run as postfix:apache,
and adjust the group rights accordingly.
On a system near me I've got:
drwxrwsrwx  2 postfix apache     4096 aug 30 15:28 ./
drwxr-xr-x  7 root    root       4096 aug 30 04:12 ../
-rw-rw----  1 postfix apache    76440 aug 30 15:27 bayes_journal
-rw-rw----  1 postfix apache     1200 aug 30 15:27 bayes.mutex
-rw-rw----  1 postfix apache 20971520 aug 30 15:27 bayes_seen
-rw-rw----  1 postfix apache  5111808 aug 30 15:27 bayes_toks

... with
Run As User = postfix
Run As Group = postfix
Quarantine User = postfix
Quarantine Group = apache
Incoming Work Permissions = 0660
Quarantine Permissions = 0660
... in /etc/MailScanner.conf, and
bayes_path /etc/MailScanner/bayes/bayes
bayes_file_mode 0770
... in /etc/mail/spamassassin/mailscanner.cf (softlink to
spam.assassin.prefs.conf).

-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se