http://bugzilla.spamassassin.org/show_bug.cgi?id=1948
------- Additional Comments From [EMAIL PROTECTED] 2004-04-27 00:32 -------
Subject: Re: spamd configuration from config file
> >I was thinking of a config file formatted along the lines of
> >
> >ListenAddress 0.0.0.0
> >#Port 783
> >DefaultConfigPath {insert at install}
> >SiteConfigPath {insert at install}
> >#EnableAutoWhiteList
> >CreateUserPrefs
> >#Paranoia
> >StartProcessors
> >MinProcessors
> >MaxProcessors
> >...
>
> well, I'd suggest just using the *existing* format, e.g.
>
> --nouser-config
> --auth-ident
> --username=scanner
> ....
>
> That avoids each possible configuration item having 1 representation on
> the command line and a different one in the config file, which (in my
> experience) causes pain and repeated RTFMing ;)
I had originally thought that most of the cmdline options could be removed,
just leaving the stuff that people need to play with - like debug, and of
course, an optional path to the config file itself.
I'm not sure if forcing everyone to use a config file is a good idea, but
on the other hand, I don't think there is any other server process that I
run that takes all of it's options on the command line.
> either way, the "standard" format is "lowercase-lowercase-lowercase"
> rather than "BouncyCaps" for the SpamAssassin config settings; it'd
> be better to keep that consistent.
Okay. I was thinking of Apache and other common servers that most admins
are comfortable with.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
