Re: more spamassassin questions.
Yes, I misunderstood your message. Have you tried the spamassassin.org
website for documentation? I too thought that
either /etc/spamassassin.prefs or /etc/spamassassin/local.cf was a
sitewide configuration file.
Tony
On Wed, Mar 13, 2002 at 07:36:48PM -0600, Corey Halpin wrote:
> 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.
>
> > I just enabled the daemon by enabling the it in the
> > /etc/default/spamassassin file. The "default" setting does not include
> > the -x setting.
> >
> > On Sun, Mar 10, 2002 at 02:28:14PM -0600, Corey Halpin wrote:
> > > when one runs spamd -x, is there a way to specify what default configuration
> > > should be used by spamd?
> > > or does it just use the "factory default" settings?
>
> thanks,
> crh
> --
> Corey R. Halpin (http://www.cae.wisc.edu/~halpin/ )
> Student of Electrical Engineering and Computer Sciences
> University of Wisconsin - Madison
>
>
Reply to: