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