Using mass-check To Test Rules
"mass-check" is a tool included in the 'masses' directory, which can be found in the SVN repository, to test rules for accuracy and hit-rate. If you're writing custom rules, you really should use this to test them.
First, you need HandClassifiedCorpora. Let's say that's made up of two mbox folders, "/path/to/ham" and "/path/to/spam".
Next, cd into the "masses" directory of the source distribution:
This will create two files, "ham.log" and "spam.log" containing the hitting rules, read from the rules dir "../rules" as they are applied to that corpus. Each line of the two log files represents details about one email message, and there's a line for every message.
mass-check also takes other options to control whether network tests are run, whether multiple processes are run in parallel, how the output is presented, etc.; read the comments at the top of the file for details. Here's some key bits:
Mass-check reads a "user_prefs" file in "spamassassin/user_prefs". You need to create this yourself, it will not be created for you.
To test your own rules, you'll need to put them in this file, and include a line containing "allow_user_rules 1"
Using network tests
For mass-checks for scoresets 1 or 3, using network tests, you need to provide the
--net switch. Ensure Net::DNS, Mail::SPF, Mail::DKIM (at least 0.31, preferrably 0.36_5 or later), Razor (InstallingRazor), Pyzor (InstallingPyzor) and DCC (InstallingDCC) are installed.
Network tests are slow unless you use the -j switch to allow mass-check to start multiple parallel scanning processes.
This is controlled using the mass-check configuration file. Do this:
or to turn it off:
Once mass-check completes
If you're using mass-check to test your own rules, the next step is to run hit-frequencies: see HitFrequencies for details. Alternatively, if you're submitting data for a new scoreset, see [RescoreMassCheck], or [NightlyMassCheck] for the nightly QA test.
mass-check [options] target ...
set configuration/rules directory
set user-prefs directory
read list of targets from <file>
specify the number of processes to run simultaneously
turn on network checks!
report Message-ID from each message
report debugging information
show progress updates during check
save rewritten message to OUT (default is /tmp/out)
print a dot for each scanned message
Only test rules matching the given regexp RE
restart all of the children after processing N messages
write all logs to stdout
log the text hit for patterns (useful for debugging)
log the URIs found
use <log> as ham log ('ham.log' is default)
use <log> as spam log ('spam.log' is default)
message selection options
no date sorting or spam/ham interleaving
only test mails received after time_t N (negative values are an offset from current time, e.g. -86400 = last day) or after date as parsed by Time::ParseDate (e.g. '-6 months')
same as --after, except received times are before time_t N
Use cached information about atime (generates files in corpus area)
don't skip big messages
only check first N ham and N spam (N messages if -n used)
only check last N ham and N spam (N messages if -n used)
simple target options (implies -o and no ham/spam classification)
subsequent targets are directories
subsequent targets are files in RFC 822 format
subsequent targets are mbox files
subsequent targets are mbx files
Just left over functions we should remove at some point:
report score from Bayesian classifier
non-option arguments are used as target names (mail files and folders), the target format is: <class>:<format>:<location>
is "spam" or "ham"
is "detect", "dir", "file", "mbx", or "mbox"
is a file or directory name. Globbing of ~ and * is supported.
"detect" is the easiest format to use. This assumes "mbox" for any file whose path contains the pattern "/\.mbox/i", "directory" for anything that is a directory, or "file" otherwise.