On Tue, 23 May 2006, Sydney Bogaert wrote:
> Are the options to spamassassin not enough ?
>
> -C path, --configpath=path, --config-file=path
> Use the specified path for locating the distributed configuration
> files. Ignore the default directories (usually "/usr/share/spamas-
> sassin" or similar).
>
> --siteconfigpath=path
> Use the specified path for locating site-specific configuration
> files. Ignore the default directories (usually "/etc/mail/spamas-
> sassin" or similar).
>
> -p prefs, --prefspath=prefs, --prefs-file=prefs
> Read user score preferences from prefs (usually "$HOME/.spamassas-
> sin/user_prefs").
>
> Copy only the interesting tests in the path for the -C option and
> override default settings with --siteconfigpath. Optionnaly set your
> scores with -p.
This would work if I was running spamassassin directly, but if I
run spamd with those options, it wouldn't be running the sitewide config
for the anti-spam role. I'd definitely have to run two instances this way,
so I'll keep it in mind in case I need to. (Still have to research the
spamc options, but won't have time until at least tomorrow.)
