Michael Parker wrote on Wed, 28 Jan 2004 17:53:12 -0600:
2.6x doesn't support that config option. You still need to use -a on
the command line. use_auto_whitelist is only supported in the
development version of SA.
I can't quite believe that, although I want. It's in the official
On Thu, Jan 29, 2004 at 05:31:36PM +0100, Kai Schaetzl wrote:
Michael Parker wrote on Wed, 28 Jan 2004 17:53:12 -0600:
2.6x doesn't support that config option. You still need to use -a on
the command line. use_auto_whitelist is only supported in the
development version of SA.
I
Michael Parker wrote on Fri, 30 Jan 2004 10:43:34 -0600:
perldoc Mail::SpamAssasisn::Conf and search for use_auto_whitelist.
If you find it, then I stand corrected. I'm guessing it's not there.
Ah, well, yes, you are right. It's not there. I was using
On Fri, Jan 30, 2004 at 08:31:39PM +0100, Kai Schaetzl wrote:
Michael Parker wrote on Fri, 30 Jan 2004 10:43:34 -0600:
perldoc Mail::SpamAssasisn::Conf and search for use_auto_whitelist.
If you find it, then I stand corrected. I'm guessing it's not there.
Ah, well, yes, you are right.
I'm getting
Failed to parse line in SpamAssassin configuration, skipping:
use_auto_whitelist 1
on a spamassassin --lint with sa 2.63. I think that has started with 2.60,
but I didn't really notice or care until now. Checking the documentation
at spamassassin.org this parameter is still there
On Wed, Jan 28, 2004 at 11:31:44PM +0100, Kai Schaetzl wrote:
I'm getting
Failed to parse line in SpamAssassin configuration, skipping:
use_auto_whitelist 1
on a spamassassin --lint with sa 2.63. I think that has started with 2.60,
but I didn't really notice or care until now. Checking
line in Spamassassin configuration, skipping: report_header 1
Failed to parse line in Spamassassin configuration, skipping: defang_mime 0
Errors when i run spamassassin --lint
And if I run It resources go outa site and mail stops
but it has been working for a couple of months through upgrades.
At 09:55 AM 1/16/2004, Michael H. Collins wrote:
line in Spamassassin configuration, skipping: report_header 1
Failed to parse line in Spamassassin configuration, skipping: defang_mime 0
snip
but it has been working for a couple of months through upgrades. And
those lines look good in the
On Wed, 15 Oct 2003 15:20:37 -0500 in
[EMAIL PROTECTED] Arlo Gilbert
[EMAIL PROTECTED] wrote:
debug: Failed to parse line in SpamAssassin configuration, skipping:
report_header 1
debug: Failed to parse line in SpamAssassin configuration, skipping:
defang_mime 0
man Mail::SpamAssassin::Conf
Spamassassin 2.6, perl 5.8 on a redhat 9 machine
called from perl i get the following debug messages even though it
appears to read those two settings as sa does abide by them.
debug: Failed to parse line in SpamAssassin configuration, skipping:
report_header 1
debug: Failed to parse line in
On Wed, Oct 15, 2003 at 03:20:37PM -0500, Arlo Gilbert wrote:
called from perl i get the following debug messages even though it
appears to read those two settings as sa does abide by them.
debug: Failed to parse line in SpamAssassin configuration, skipping:
report_header 1
debug: Failed
Arlo Gilbert wrote:
Spamassassin 2.6, perl 5.8 on a redhat 9 machine
called from perl i get the following debug messages even though it
appears to read those two settings as sa does abide by them.
debug: Failed to parse line in SpamAssassin configuration, skipping:
report_header 1
debug:
Hi,
I've got in my SA user_prefs file 'dcc_path /usr/local/bin', which is where
dccproc lives, but I'm getting:
'Failed to parse line in spamassassin configuration: skipping dcc_path
/usr/local/bin'
In my maillog (with the -D option to spamd)
dcc seems to be working because dccproc is later
At 05:00 PM 6/20/2003 +0100, Jim Ford wrote:
I've got in my SA user_prefs file 'dcc_path /usr/local/bin', which is where
dccproc lives, but I'm getting:
'Failed to parse line in spamassassin configuration: skipping dcc_path
/usr/local/bin'
What version of SA are you using? Works fine on my copy
At 08:44 PM 6/20/2003 +0100, you wrote:
On Fri, Jun 20, 2003 at 03:04:26PM -0400, Matt Kettler wrote:
What version of SA are you using? Works fine on my copy of 2.54..
2.55
Here's the start of my ~.spamassassin/user_prefs - looks alright to me!
# SpamAssassin user preferences file. See
I believe you need to specify the fully quallified path name to
the dcc binaryie dcc_path /usr/local/bin/dccproc
russ...
- Original Message -
From: Jim Ford [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, June 20, 2003 3:44 PM
Subject: Re: [SAtalk] Failed to parse line in SA
On Fri, Jun 20, 2003 at 01:38:44PM -0700, Patrick Morris wrote:
If there are no weird characters in that line that didn't translate into
the e-mail, you're not running the version you think you are. You may
want to check and make sure you don't have an older copy of SpamAssassin
installed
On Fri, Jun 20, 2003 at 05:03:18PM -0400, Matt Kettler wrote:
What happens if you add a # to the dcc_path line to comment it out and run
spamassassin --lint again?
spamassassin --lint doen't report any errors with the dcc_path line in or
commented out. BTW, I use spamd+spamc and there's no
On Fri, Jun 20, 2003 at 05:16:48PM -0400, Russ wrote:
I believe you need to specify the fully quallified path name to
the dcc binaryie dcc_path /usr/local/bin/dccproc
Nope - no difference. I'm pissed off with it for tonight and going to bed.
I'll get my teeth into its arse again in the
19 matches
Mail list logo
