http://bugzilla.spamassassin.org/show_bug.cgi?id=1948
------- Additional Comments From [EMAIL PROTECTED] 2004-04-27 00:23 -------
Subject: Re: spamd configuration from config file
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>I think we can leave the hashed user dirs alone for now - it's not
>relevant for us if we go to SQL bayes dbs anyway, which looks like the
>way for large high volume sites to go. It may be useful for some smaller
>installtions that are looking for some performance enhancements or the
>ability to spread user db's across multiple mount points and/or not store
>the dbs in a user's homedir.
Yeah, agreed I think. don't worry about that then ;)
>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 ;)
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.
- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFAjgpyQTcbUG5Y7woRAthsAKDWMk8RN7WM3iDbObsw7gUfowTOhwCgm7H/
pdisanQH4CzAkHlF56UzAKI=
=2iLB
-----END PGP SIGNATURE-----
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
