Re: more spamassassin questions.
* Corey Halpin <crhalpin@students.wisc.edu> [020314 09:36]:
> You seem to be confused about what I mean by "default configuration".
> I most expressly _do_not_ mean the contents of /etc/default/spamassassin.
> I _do_ mean what is the default behavior of spamd.
> See "man spamd":
> -x Turn off per-user config files. All users will just
> get the default configuration.
>
> You see, the debian install of spamd, when enabled, runs spamd as root. I
> _really_ am not comfortable with the idea of running a perl srcipt that
> listens on a network port as root.
> So I used the '-u mail' option, which runs it as the unpriveleged user
> "mail", but (by definition of unpriveleged) the user "mail" cannot see or
> modify the contents of user's home directories (ie, it can't touch
> ~/.spamassassin anymore). This is fine, I'll just use a system wide
> configuration and users can tune it with procmail if they like.
> Now, how do I use a system wide configuration?
> you'd think that it would read /etc/spamassassin.conf but it doesn't. This
> is just a template that it copies if the user running spamassassin doesn't
> have a configuration of their own.
Maybe a .spamassasin file in the user 'mail's homedir?
Greets,
Karsten
--
Karsten Heymann <karsten.heymann@gmx.de> <karsten@ecology.uni-kiel.de>
CAU-University Kiel, Germany
Registered Linux User #221014 (http://counter.li.org)
Reply to: