Bug 142 - Add a mode for syntax-checking rules files
Summary: Add a mode for syntax-checking rules files
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 2.30CVS
Hardware: All All
: P3 enhancement
Target Milestone: ---
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-27 08:05 UTC by Bart Schaefer
Modified: 2002-08-22 07:09 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bart Schaefer 2002-03-27 08:05:46 UTC 
Maybe there's an easy way to do this already that I'm just not finding, but
I occassionally 
introduce syntax errors into the local.cf file and end up
having a lot of tests skipped until I 
notice the problem in my procmail logs.

It's be nice if there were an option to run 
spamassassin so that it would load
and thereby syntax-check all the rules files, and then exit 
with success or
failure based on the success of loading the files.
Comment 1 Craig Hughes 2002-04-10 02:10:00 UTC 
It's called "make test"
Comment 2 Bart Schaefer 2002-04-10 08:29:08 UTC 
I don't want to rebuild spamassassin, or even need to have access to the
build tree, just to check 
the syntax of one new rule added to local.cf.

I also believe that "make test" should be 
ignoring the locally installed
rules to begin with, because local changes to the scores might 
cause the
test results to change, producing bogus test failures.
Comment 3 Justin Mason 2002-08-22 15:09:21 UTC 
ok, now in CVS for 2.40