This looks like something that should be posted to Bugzilla. Likely there was very little testing with allow_user_rules = 1.

       Loren

----- Original Message ----- From: "Klaus Heinz" <[EMAIL PROTECTED]>
To: <users@spamassassin.apache.org>
Sent: Sunday, May 06, 2007 1:57 AM
Subject: Re: sa-compile Problem


Wolfgang Breyha wrote:

But after restarting spamd I get lots of message complaining about missing body_400.pm up to body_1000.pm and same for body_neg400.pm to body_neg1000.pm.
 ^^^^^^^^^^^
 Are you sure about this one? I have not seen this yet.


eg.:
Can't locate Mail/SpamAssassin/CompiledRegexps/body_neg1000.pm in @INC
(@INC ....)

I see exactly the same messages. The missing modules are (in this order
but not always all of them for a single mail message)

 body_neg950.pm
 body_neg900.pm
 body_neg1000.pm
 body_1000.pm
 body_500.pm
 body_neg400.pm

The messages only appear if "allow_user_rules 1" is used in local.cf.

All modules except for body_500.pm correspond to priority values set in
60_awl.cf and 60_shortcircuit.cf. Where body_500.pm comes from I don't
know.

Mostly the messages look like this

May 6 09:25:59 silence spamd[704]: Can't locate Mail/SpamAssassin/CompiledRegex
ps/body_neg900.pm in @INC (@INC contains:
/var/spamassassin/compiled/3.002000 /var/spamassassin/compiled/3.002000/auto /var/spamassassin/compiled/3.002000 /var/spamassassin/compiled/3.002000/auto
lib /usr/pkg/lib/perl5/vendor_perl/5.8.0/i386-netbsd-thread-multi
/usr/pkg/lib/perl5/vendor_perl/5.8.0
/usr/pkg/lib/perl5/site_perl/5.8.0/i386-netbsd-thread-multi
/usr/pkg/lib/perl5/site_perl/5.8.0 /usr/pkg/
lib/perl5/5.8.0/i386-netbsd-thread-multi /usr/pkg/lib/perl5/5.8.0) at
(eval 738) line 1.

Note the duplicated paths "/var/spamassassin/compiled/3.002000
/var/spamassassin/compiled/3.002000/auto". Sometimes, I don't know why or
when, the INC array runs wild and the number of those duplicated paths
starts to grow, I have seen up to 11 occurences of those two paths in an
error message.

The error messages appear in a brand new SA 3.2.0 installation on NetBSD
3.1 with spamc/spamd, no special configuration, user rules or anything
except for the addition of "allow_user_rules 1" and the enabled plugin
Rule2XSBody. spamassassin --lint does not show any issues.
Rules were compiled with re2c 0.12.0.

A last check shows that "spamassassin -D < testmessage" does not show
the errors.

ciao
Klaus


Reply via email to