Re: cannot write and parse errors

2004-12-17 Thread David Newman
On Thu, 16 Dec 2004, Richard Ozer wrote: It looks like your port had a 2.x local.cf file Thanks very much to all who responded. The port in question is 3.0.1 on FreeBSD 5.2.1. I had CVSUP'd the system before installing SA, so I'm reasonably sure what I got was current. Note for the FBSD ports ma

Re: cannot write and parse errors

2004-12-16 Thread Jim Maul
Stuart Johnston wrote: Matt Kettler wrote: auto_learn has NEVER been valid. It's bayes_auto_learn. It also should only contain a 1 or a 0 after it. No $ I've seen a lot of people with auto_learn in their configs. Where'd you get that? did you use some config auto generator? http://www.yrex.com/

Re: cannot write and parse errors

2004-12-16 Thread Matt Kettler
At 03:18 PM 12/16/2004, Stuart Johnston wrote: Matt Kettler wrote: > auto_learn has NEVER been valid. It's bayes_auto_learn. It also should only contain a 1 or a 0 after it. No $ > I've seen a lot of people with auto_learn in their configs. Where'd you get that? did you use some config auto gener

Re: cannot write and parse errors

2004-12-16 Thread Stuart Johnston
Matt Kettler wrote: auto_learn has NEVER been valid. It's bayes_auto_learn. It also should only contain a 1 or a 0 after it. No $ I've seen a lot of people with auto_learn in their configs. Where'd you get that? did you use some config auto generator? http://www.yrex.com/spam/spamconfig.php - ge

Re: cannot write and parse errors

2004-12-16 Thread Richard Ozer
It looks like your port had a 2.x local.cf file. To fix this, comment out rewrite_subject, comment out subject_tag, comment out use_terse_report, and change auto_learn to bayes_auto_learn Also be sure you have something like the following section... (replace amavis with whatever you prefer or

Re: cannot write and parse errors

2004-12-16 Thread Matt Kettler
At 06:17 AM 12/16/2004 -0800, David Newman wrote: The docs cover some of these but not all. Neither the USAGE nor the UPGRADE files describe what to use in place of use_terse_report in 3.0. Yes, it's not in there because it's been dead for a long time. It wasn't something that was dropped in 3.0,

Re: cannot write and parse errors

2004-12-16 Thread Matt Kettler
At 08:50 PM 12/15/2004 -0800, David Newman wrote: Dec 15 00:42:53 mailman spamd[2224]: Cannot write to /nonexistent/.spamassassin/user_ prefs: No such file or directory There's no such user as "nonexistent" on this system. Where do you get the idea there might be a user "nonexistent"? That's the

Re: cannot write and parse errors

2004-12-16 Thread David Newman
On Thu, 16 Dec 2004, Loren Wilton wrote: interested in particular in four parse errors: debug: config: SpamAssassin failed to parse line, skipping: rewrite_subject 1 debug: config: SpamAssassin failed to parse line, skipping: subject_tag $ *SPAM* debug: config: SpamAssassin failed to parse

Re: cannot write and parse errors

2004-12-16 Thread Loren Wilton
> interested in particular in four parse errors: > > debug: config: SpamAssassin failed to parse line, skipping: > rewrite_subject 1 > debug: config: SpamAssassin failed to parse line, skipping: subject_tag $ > *SPAM* > debug: config: SpamAssassin failed to parse line, skipping: > use_terse

cannot write and parse errors

2004-12-16 Thread David Newman
Greetings. I'm seeing two problems with SA 3.0.1_2 on a FreeBSD 5.2.1 system running Postfix 2.1.5,1 and procmail 3.22_5. All are installed via ports. Problem 1: The mail log has lots of entries like this: Dec 15 00:42:53 mailman spamd[2224]: Cannot write to /nonexistent/.spamassassin/user_ pre