Re: [vps-mail] VPS2, Bayes problem

[Scott Wiersdorf <scottw@xxxxxxxxxxxx>]

On Fri, Apr 02, 2004 at 10:33:33AM -0800, Abigail Marshall wrote:
> Scott, based on your suggestions here is the configuration
> that seems to work:
> 
> Local CF settings:
> 
> use_bayes            1
> bayes_path      /etc/mail/spamassassin/bayes/bayes
> bayes_file_mode 0770
> bayes_auto_expire       1
> bayes_auto_learn        1
> 
> Directory & File settings:
> drwxrwx---  2 root  nobody /etc/mail/spamassassin/bayes
> -rw-rw----  1 nobody  nobody    19299 Apr  2 10:22 bayes_journal
> -rw-rw----  1 root    nobody  2535424 Apr  2 10:22 bayes_seen
> -rw-rw----  1 root    nobody  5373952 Apr  2 10:22 bayes_toks

These look much better.

> You were right that SA needs group privileges as "nobody". I
> think an alternative might be to run spamc as -u spam
> ("spam" being the user that owns the mailbox called "spam"),
> and either set group privileges for the
> /etc/mail/spamassassin/bayes to include "spam", or else put
> the bayes database in the .spamassassin directory under the
> user /home/spam.

That sounds like a great idea, imo. Who can tell that the default
'nobody' won't change in the future. By explicitly setting -u to some
spam user you've created, you guarantee future compatibility.

> Also, one other note in case anyone has similar problems -
> I have found that when I make path changes in the local.cf
> file, restart_sendmail is not enough to make the changes
> fully effective; I also need to reboot.

It may be that you really just need to restart spamd instead. sendmail
doesn't read local.cf, so it shouldn't need to be restarted (unless
you're also making sendmail.cf changes at the same time). A reboot
seems a bit drastic (do you use Windows, by any chance? ;o). Restarting
the affected daemon is enough.

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