-Original Message-
From: Ben Wylie [mailto:[EMAIL PROTECTED]
Sent: 14 March 2005 13:28
To: users@spamassassin.apache.org
Subject: RE: save debug output and errors
>
> Having managed to capture the errors which pop up when my mailserver runs
> the spamassassin batch script, it is
> > where should I look for this to fix?
>
> Theo has the answer for that one - a bad meta rule somewhere.
>
> Given that --lint seemingly didn't catch it, and this pure perl error is
> less than descriptive of the problem, once you find the rule in question,
> I think it deserves a Bugzilla entry
> where should I look for this to fix?
Theo has the answer for that one - a bad meta rule somewhere.
Given that --lint seemingly didn't catch it, and this pure perl error is
less than descriptive of the problem, once you find the rule in question, I
think it deserves a Bugzilla entry for failure
On Mon, Mar 14, 2005 at 05:03:05AM -, Ben Wylie wrote:
> Scalar found where operator expected at (eval 57) line 724, near "} $self"
> (Missing operator before $self?)
> Failed to run meta SpamAssassin tests, skipping some: syntax error at (eval
> 57)
> line 724, near "} $self"
>
> whe
-Original Message-
> From: Loren Wilton [mailto:[EMAIL PROTECTED]
> Sent: 14 March 2005 02:36
> To: users@spamassassin.apache.org
> Subject: Re: save debug output and errors
>
> You probably have some broken rules or other lines in your local rules
> file, or poss
You probably have some broken rules or other lines in your local rules file,
or possibly elsewhere in the rules files. To catch thos you want to run
"spamassassin --lint" without the debug stuff. This will give you a
managable output.
Assuming you are on NT of some flavor, "spamassassin 2>&1
>o
