On 26.06.08 10:06, Skip Morrow wrote:
> I see, and got it working. Next question: How would I set it up so that
> I could have a separate whitelist for each user (I only have four users)?
it's the default
> Again, I call spamassassin from procmail, and each user has its own
> procmailrc,
then
> That option wasn't removed from SA.. it was removed from the main conf
> docs, as all of the AWL is now a plugin. That option is documented in the
> docs for the AWL plugin, which is where it really belongs. (if the option
> isn't valid without the plugin, then it in theory shouldn't be in the ma
On Thu, June 26, 2008 05:56, Matt Kettler wrote:
> the docs for the AWL plugin, which is where it really belongs. (if the
> option isn't valid without the plugin, then it in theory shouldn't be in
> the main Conf manpage..)
there is still docs for bayes in conf, even bayes is a plugin now
needs
On Thu, June 26, 2008 05:16, Skip wrote:
> option with my own configuration file, and I should be able to pass it
> the -C or --siteconfigpath options to set admin settings. Any help?
AWL and BAYES will when procmail is in use be in $HOME./spamassassin/
but can be overwrited in user_prefs with
Skip wrote:
How does one set the file location for the auto-whitelist file on a
3.2.x system? I am on a shared hosting system, but call spamassassin
manually from procmail. Here's the debug output that deals with
auto-whitelist:
[25947] dbg: locker: safe_lock: created
/ramdisk/etc/spamassa
How does one set the file location for the auto-whitelist file on a
3.2.x system? I am on a shared hosting system, but call spamassassin
manually from procmail. Here's the debug output that deals with
auto-whitelist:
[25947] dbg: locker: safe_lock: created
/ramdisk/etc/spamassassin/data/aut
