Re: [SAtalk] Failed to parse line in SA config.

2003-06-20 Thread Jim Ford
Looks like the problem is with spamd. Killing the spamd daemon and substituting spamassassin for spamc in my procmailrc eliminated the error. Maybe I've found a bug in spamd! Regards: Jim Ford -- Spam poison - don't use! ---> [EMAIL PROTECTED] <--- -

Re: [SAtalk] Failed to parse line in SA config.

2003-06-20 Thread Jim Ford
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 mor

Re: [SAtalk] Failed to parse line in SA config.

2003-06-20 Thread Jim Ford
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 l

Re: [SAtalk] Failed to parse line in SA config.

2003-06-20 Thread Jim Ford
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 > install

Re: [SAtalk] Failed to parse line in SA config.

2003-06-20 Thread Russ
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] F

Re: [SAtalk] Failed to parse line in SA config.

2003-06-20 Thread Matt Kettler
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 'perl

Re: [SAtalk] Failed to parse line in SA config.

2003-06-20 Thread Patrick Morris
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 in a different place from 2.55. Jim Ford wrote: On Fri, Jun 20, 200

Re: [SAtalk] Failed to parse line in SA config.

2003-06-20 Thread Jim Ford
On Fri, Jun 20, 2003 at 03:04:26PM -0400, Matt Kettler wrote: > >'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 of 2.54.. 2.55 > Are you sure there's not a typo in a previous line? (ie: a missin

Re: [SAtalk] Failed to parse line in SA config.

2003-06-20 Thread Matt Kettler
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

[SAtalk] Failed to parse line in SA config.

2003-06-20 Thread Jim Ford
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 fou