[Richard Sonnen]
> It might be useful to set up spamc and spamd so that you could
> specify alternate config files more easily. i.e.
>
> spamc --cf /path/to/system/conf/dir --rf /path/to/user/rules
[Craig Hughes]
> Which entirely defeats the purpose of spamd -- to pre-compile the
> rules.
That only invalidates the second option (/path/to/user/rules). It would
still, IMHO, be useful to specify an arbitrary user config file, so
that scores, use_terse_report, etc. can come from somewhere
other than ~user/.spamassassin/user_prefs, for some user listed
in /etc/passwd.
The reason I'd like to see this: I'm about to setup SA on a system with
~100 mailing lists, but only a handful of "real" email addresses
(ie. where the localpart == a username from /etc/passwd). It would be
nice to be able to tweak SA's parameters -- particularly scores -- on a
per-list basis. The cleanest and most flexible way I can think of for
this is for me to create a directory full of per-list config files, say
/etc/spamassassin/lists. Then the code that I write to hook my MTA to
SA (which might be a snippet of Exim configuration stuff, or might be a
little Python script that launches spamc) will figure out which config
file to use, and tell spamc. Presumably, spamc will then tell spamc to
use that config file instead of ~user/.spamassassin/user_prefs, which
will be irrelevant most of the time.
Greg
--
Greg Ward - software developer [EMAIL PROTECTED]
MEMS Exchange http://www.mems-exchange.org
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
