Tools in the SpamAssassin masses folder

This is an overview of the scripts in the SpamAssassin masses folder. In brief these scripts are used to mass check hand classified corpora and to calculate new scores with the percpetron approach using the results of a mass check. It's necessary to calculate 4 different scoresets for the rules, depending on whether the bayes or the net option is used:

set0: no bayes, no net BR set1: no bayes, net BR set2: bayes, no net BR set3: bayes, net

A scoreset is one of the 4 columns in a score file like "../rules/50_scores.cf"

cpucount

This script counts the number of CPU in your system

usage:BR cpucount

cpucount calls:BR no other scripts

fp-fn-statistics

Tests a scoreset and *.log files for false-positives and false-negatives and returns a statistic.

usage:[BR] fp-fn-statistics [options]

fp-fn-statistics calls: BR logs-to-c with --count option

hit-frequencies

see HitFrequencies.

hit-frequencies calls:BR parse-rules-for-masses

lint-rules-from-freqs

This script analyzes the rules for usability. It therefore uses a freqs file generated by hit-frequencies (with -x -p options). It also uses a scoreset. The bad rules are returned. Following rules are marked as bad:BR Rules that rarely hit (below 0.03%) or don't hit at all, rules with a negative score that have a higher spam-hit rate than ham-hit rate, rules with a positive score that have a higher ham-hit rate than spam-hit rate, rules with score = 0.BR

usage:[BR] lint-rules-from-freqs [-f falsefreqs] [-s scoreset] < freqs > badtests

lint-rules-from-freqs calls:BR no other scripts

logs-to-c

Generates different files in the /tmp folder: "ranges.data", "scores.data", "scores.h", "tests.data", "tests.h". Those files are later used by the perceptron script. This script is also used to test scoresets and *.log files for false-positives and false-negatives (use --count).BR

usage:[BR] logs-to-c [options]

logs-to-c calls :BR parse-rules-for-massesBR score-ranges-from-freqsBR

mass-check

see MassCheck.

mass-check calls: BR no other scripts in the masses folder

mk-baseline-results

Shell script that tests a scoreset and the files "ham-test.log" and "spam-test.log" for false-positives and false-negatives with various thresholds ranging from -4 up to 20. Returns a statistic for all thresholds. BR

usage: BR mk-baseline-results scoreset

mk-baseline-results calls: BR logs-to-c

parse-rules-for-masses

Parses the rules in all *.cf files that begin with a digit and that are located in the "../rules" folder.It generates a file called "/tmp/rules.pl"
that contains a dump of two hashes (perl datatype) called %rules and %scores that can be directly included by other perl scripts using the require command. BR The %rules hash consists of a set of data for every rule. In those sets, the score of the rule, a description, the type, whether the rule is mutable and whether it is a subrule are saved. In the %scores hash one score for every rule is saved. BR

usage: [BR] parse-rules-for-masses [-d rulesdir] [-o outputfile] [-s scoreset]

parse-rules-for-masses calls: BR no other scripts

perceptron

Calculates new scores with the perceptron approach and generates a perceptron.scores file. Needs following files in the /tmp folder: "ranges.data", "scores.data", "scores.h", "tests.data", "tests.h", "rules.pl" BR

usage: [BR] perceptron [options] [BR]

perceptron calls: BR no other scripts

rewrite-cf-with-new-scores

Rewrites a cf file with new scores. Only the area with the generated scores is changed. The argument scoreset is the number of the scoreset (0-3) that is rewritten. The new cf-file is returned on the standard output.

usage: [BR] rewrite-cf-with-new-scores [scoreset] [oldscores.cf] [newsocres.cf]

rewrite-cf-with-new-scores calls: BR no other scripts

runGA

Shell script that compiles and runs the perceptron script. New scores are calculated with the perceptron approach and random 9/10 of the examples in the "*.log" files. Then the scores are tested for false-positives and false-negatives with the last 1/10 of the examples. BR Needs a "config" file in the "./" folder that contains some parameters:BR

Corresponding "*.log" files to the chosen scoreset X (named "ham-setX.log" and "spam-setX.log") are required in the "/ORIG" folder. The script generates several files in the "/tmp" folder by calling logs-to-c, and a new folder named by the options ("gen*") in the config file. This folder contains a "scores" file with the generated scores and corresponding ranges, the "*.log" files that were used for the score generation and for the testing (in "/NSBASE" and "/SPBASE" folders), lists of false-negatives and false-positives that were found in the test, a logfile that contains the used parameters for the score generation, the output of the makefile ("make.output") and a false-positives vs. false-negatives statistic ("test").BR
The runGA script also generates a "badrules" file by calling lint-rules-from-freqs, that contains rules that are not useful for different reasons (most of them hitting too rarely or not at all).BR Note that the generated scores may vary somewhat if runGA is run twice, due to the random selection of the training examples.

usage:BR runGA (parameters are saved in a "config" file)

runGA calls:BR fp-fn-statisticsBR lint-rules-from-freqs BR logs-to-c BR mk-baseline-results BR numcpus BR parse-rules-for-massesBR perceptron BR rewrite-cf-with-new-scoresBR score-ranges-from-freqsBR tenpass/split-log-into-buckets-random BR

score-ranges-form-freqs

Calculates a score-range for the rules. The magnitude of the range depends on the ranking (generated by hit-frequencies) of a rule. Immutable rules get fixed ranges at their scores. The ranges are later used by the perceptron script that tries to find the optimal scores within these ranges.BR

usage:[BR]
score-ranges-from-freqs [cffiledir] [scoreset] < freqs

score-ranges-from-freqs calls: BR parse-rules-for-massesBR

split-log-into-buckets-random

Split a mass-check log into n identically-
sized buckets, evenly taking messages from all checked corpora and preserving comments. Creates n files named "split-n.log"BR

usage: [BR] split-log-into-buckets-random [n] < LOGFILE[BR]

split-log-into-buckets-random calls:BR no other scripts