John Hardin wrote: > If you want to override the default behavior of SA to that degree, it's > easier to change the config directory that SpamAssassin and spamd use > with the -c option,
You mean -C (note capital). -c (lower-case) is to autocreate userprefs files. <g> > so that none of the base rule files are read in the > first place. You'll need to provide some minimal set of config files in > whatever custom config directory you specify in order to get SA to run, > but that will avoid all the extra default stuff you don't seem to want. > > I've never customized SA to that degree so there may be some pitfalls in > this that I'm not aware of - somebody else will probably say something > if there's other stuff you need to be aware of. I've done this here; we run a stripped-down SA instance with a bunch of DNSBL rules (local and Spamhaus datafeed) and a handful of miscellaneous high-scoring stock rules (hand-picked based on local mail flow and stock scores). Key arguments for spamd are -C (to specify the "default" rules path (overrides and combines DEF_RULES_DIR and LOCAL_STATE_DIR) and --siteconfig for your "site" config (could probably be pointed somewhere empty but we found it simpler to put a minimal local.cf and local.pre there). I can't speak to running "spamassassin" but IIRC it takes much the same arguments for this as spamd. If you build a local rules channel for this custom ruleset, use --updatedir with sa-update with the same path as you specified for spamd with -C. -kgd
