On 11/21/2014 12:32 PM, Bowie Bailey wrote:
> bayes_path is considered to be an administrator setting and is not
> allowed to be specified in user_prefs.
Ah, that's what I get for grepping through the man page instead of paging
through in order. Thanks very much.
On 11/21/2014 2:51 PM, Starchy Grant wrote:
Hello,
I'm working on a limited test of a global bayes databases on Debian
Wheezy with spamassassin 3.3.2, and trying to set bayes_path in my
user_prefs file. When I add the line
bayes_path /var/spamassassin/bayes_db/bayes
I see the following in the
On 12/6/2011 12:55 PM, Christian Gregoire wrote:
What happens if you put those lines into a local.cf or similar configuration
file rather than a user preference?
Doesn't look like it's taken into account. The rule is not triggered
Then you are putting it in the wrong place or the rule isn't hi
>What happens if you put those lines into a local.cf or similar configuration
>file rather than a user preference?
Doesn't look like it's taken into account. The rule is not triggered
>What are your command line parameters for spamd and spamc?
/usr/bin/spamd --socketpath=/tmp/spamassassin.sock
On 12/6/2011 10:28 AM, Christian Gregoire wrote:
Hi,
With the following prefs file (taken from
http://wiki.apache.org/spamassassin/WritingRules) :
header LOCAL_DEMONSTRATION_SUBJECT Subject =~ /\btest\b/i
score LOCAL_DEMONSTRATION_SUBJECT 0.1
I get the below error :
Dec 6 14:39:
Jeffrey,
> I'm running SpamAssassin version 3.3.1, running on Perl version 5.10.0.
> I'm seeing a lot of errors similar to:
>
> config: failed to parse line, skipping, in
> "/tmp/.spamassassin13924v0B7j5tmp/60_adsp_override_dkim.cf":
> adsp_override ebay.com
>
> during the daily cron run. (the
Drew Burchett wrote:
> I made this same mistake yesterday.
Turned out that I hadn’t enabled razor in v310.pre.
Thanks very much for the reply Drew!
I found that the line loading the Razor plug-in in v310.pre
was commented out:
# Razor2 - perform Razor2 message checks.
#
# Ra