not sure where this comes from?
(!)_DIE: Can't locate Mail/SpamAssassin/CompiledRegexps/body_neg999.pm
in @INC (@INC contains: /var/db/spamassassin/compiled/5.008/3.002005
/var/db/spamassassin/compiled/5.008/3.002005/auto lib
/usr/local/lib/perl5/5.8.8/BSDPAN
/usr/local/lib/perl5/site_perl/5.8.8/mach
/usr/local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/site_perl
/usr/local/lib/perl5/5.8.8/mach /usr/local/lib/perl5/5.8.8) at (eval
1435) line 1.\nBEGIN failed--compilation aborted at (eval 1435) line 1.
cd
/var/db/spamassassin/compiled/5.008/3.002005/Mail/SpamAssassin/CompiledRegexps/
fl# ls
body_0.pm body_500.pm
I just added (for the first time) some priority -999 rules, and did NOT
compile it (yet)
is that a WARNING?
maybe a fundamental Question about updates/ modifications and sa-compile
my understanding is that if you modify rules after a compile, AND DON'T
COMPILE THEM YET, SA will ignore the compiled rule and run the
uncompiled one?
(this error above, does it mean that SA WON'T USE the uncompiled rule?
or TRIED to use the compiled one and failed?)
does this mean it won't use ANY compiled rules?
what about score changes? (assuming a restart of spamd inbetween)
I edit rules 'x_y_z' set score for 1.0. compile, then edit x_y_x and
change score to 1.5, and restart spamd, what score is used?)
if I have a rule 'x_y_z', and modify the REGEX for the rule, restart
spamd, what score is used?
yes, best practices says run sa-compile before spamd restart if you
edited anything, but recently, (re2c-0.13.5 ) it seems to be taking 30
mins to compile rules, even on a fast system.
so, what breaks (isn't changed) when I DON'T RUN SA-COMPILE.
--
Michael Scheidell, CTO
Phone: 561-999-5000, x 1259
> *| *SECNAP Network Security Corporation
* Certified SNORT Integrator
* King of Spam Filters, SC Magazine 2008
* Information Security Award 2008, Info Security Products Guide
* CRN Magazine Top 40 Emerging Security Vendors
* Finalist 2009 Network Products Guide Hot Companies
_________________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
_________________________________________________________________________
