The symptoms you describe sound a lot like a completely broken rule
someplace that should probably (but not absolutely guaranteed) show up as a
lint error. Unfortunately the error will probably be on some completely
innocent rule, quite possibly in another file.
Look in local.cf or any other place you have put local rules for a possibly
unterminated regex that is missing the final slash, or perhaps has a
mismatched number of parends. Both of those can cause this sort of thing.
If necessary, divide the problem by whacking out a big hunk of rules until
the lint problem goes away, then start putting things back until it shows
up.
Loren
----- Original Message -----
From: "Hamish Marson" <[EMAIL PROTECTED]>
To: <users@spamassassin.apache.org>
Sent: Tuesday, February 28, 2006 9:55 AM
Subject: False hits on rules... But Debugging doesn't show them. (SA3.1.0)
> I have a problem... Got aload of complaints about emails not coming
> through. On investigating, I have discovered that we're getting rules
> such as MISSING_SUBJECT hit, where an email clearly has a subject: line
> in the headers. Also missing recieved header, no from_or_to etc..
>
> So I can spamassassin -D to see why... And although those rules get
> listed & counted in the summary, they DON'T show up as being hit in the
> actual debug output.
>
> But what I do get is a suspicious looking line about header tests...
>
> [3317762] dbg: rules: running header regexp tests; score so far=0
> [3317762] warn: rules: failed to run header tests, skipping some:
> Illegal declaration of anonymous subroutine
> at /usr/local/perl-5.8.6/etc/mail/spamassassin/70_sare_genlsubj1.cf,
> rule SARE_SUB_GROW_BUSINESS, line 9.
>
>
> Now it started with a different sare ruleset first... Which I checked
> and can't see any anonymous subroutine sbeing declared... SO renamed it
> to see what would happen. And the problem moved to this file. Again
> nothing there. Especially at line 9, which just happens to be
> constant...
>
> So it looks like a problem with an actual module somewhere being
> reported falsely as in a ruleset...
>
> Anyone have any ideas which? And why? The environment is perl-5.8.6 on
> AIX 5.1. perl was compiled using xlc. Checking the same message on a
> Linux box also using SA310 and that doesn't have the problems (And does
> use SARE rulesets).
>
> TIA
>
> Hamish.
>
