Problems after upgrading from 3.0.1 to 3.0.2 via CPAN

[Greg Earle <ea...@isolar.DynDNS.ORG>]

I just upgraded my Testbed SA installation (on a Solaris 8 system with
Perl 5.8.5) from 3.0.1 to 3.0.2 and am having problems that didn't
exist in 3.0.1.  Running "spamassassin -D --lint < /dev/null" reveals:

testbed:1:50 [/] # spamassassin -D --lint < /dev/null
debug: SpamAssassin version 3.0.2
debug: Score set 0 chosen.
[...]
debug: diag: module not installed: DBI ('require' failed)
[...]
debug: diag: module not installed: Net::LDAP ('require' failed)
[...]
warning: description for RM_sw_LeadingPrep is over 50 chars
warning: description for YM_B_CANSPAM_1 is over 50 chars
warning: description for OACYS_DISGUISED_P0RN is over 50 chars
warning: description for RM_fw_LeadingPrep is over 50 chars
warning: description for SUPPORT_AT_MICROSOFT is over 50 chars
warning: description for YM_B_CANSPAM_2 is over 50 chars
warning: description for SUPPORT_AT_SUPPORT is over 50 chars
warning: description for HINET is over 50 chars
warning: description for YM_B_CANSPAM_3 is over 50 chars
warning: score set for non-existent rule PENIS_ENLARGE2
warning: score set for non-existent rule NO
warning: score set for non-existent rule MICROSOFT_EXECUTABLE
warning: score set for non-existent rule PENIS_ENLARGE
[...]
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x53c0ec) 
implements
'check_post_dnsbl'
debug: running meta tests; score so far=-2.623
Failed to run meta SpamAssassin tests, skipping some: Search pattern not
terminated at (eval 60) line 376.
[...]
lint: 13 issues detected.  please rerun with debug enabled for more 
information.

Questions:

(1) Do the descriptions all have to be reduced to under 50 characters,
     or is this just an informational diagnostic?  (Yes, I am aware
     from reading the list that this 50 character restriction is a
     new-in-3.0-ism and that I probably have unedited 2.63 rulesets)

(2) (a) Most importantly, since it seems to be fatal - how can I find
		out what file is being complained about ("Search pattern not
         terminated at (eval 60) line 376.")?

     (b) Also, is there any dbg() statement I can add to
		PerMsgStatus.pm::do_meta_tests() to help determine where this
		problem is occurring?

Thanks,

	- Greg

Re: Problems after upgrading from 3.0.1 to 3.0.2 via CPAN

[Loren Wilton <lw...@earthlink.net>]

> I just upgraded my Testbed SA installation (on a Solaris 8 system with
> Perl 5.8.5) from 3.0.1 to 3.0.2 and am having problems that didn't
> exist in 3.0.1.  Running "spamassassin -D --lint < /dev/null" reveals:
>
> warning: description for RM_sw_LeadingPrep is over 50 chars
> warning: description for YM_B_CANSPAM_1 is over 50 chars
> warning: description for OACYS_DISGUISED_P0RN is over 50 chars
> warning: description for RM_fw_LeadingPrep is over 50 chars
> warning: description for SUPPORT_AT_MICROSOFT is over 50 chars
> warning: description for YM_B_CANSPAM_2 is over 50 chars
> warning: description for SUPPORT_AT_SUPPORT is over 50 chars
> warning: description for HINET is over 50 chars
> warning: description for YM_B_CANSPAM_3 is over 50 chars
> warning: score set for non-existent rule PENIS_ENLARGE2
> warning: score set for non-existent rule NO
> warning: score set for non-existent rule MICROSOFT_EXECUTABLE
> warning: score set for non-existent rule PENIS_ENLARGE

I think all of these were there in 301 and you just didn't notice.  The
description length errors are obviously all on some local rules you have in
your local.cf or similar.  These got by in 2.6x, and were a real pain to us
at SARE in 3.0.  So far as I know these are just annoying, but the rules
still work.

The end warnings are self-explanatory.  The MS_Executable rule was deleted
very early in 3.0, before 3.0.0.  Not sure about the penile rules, but thye
might have suffered a similar fate.

The "NO" rule makes me think you have a broken rule that is probably missing
an underscore after a leading "NO".  This one might cause you some
undetected problems, so you better hunt it down and erradicate it.

> debug: running meta tests; score so far=-2.623
> Failed to run meta SpamAssassin tests, skipping some: Search pattern not
> terminated at (eval 60) line 376.

Can't help you much on this one.  However, it is doubtless in your local
rules, is a meta, and might be related to that "NO" rule spotted above.  I'd
just search out all the metas, there probably aren't that many.

        Loren