Changing:
severity -> enhancement
milestone -> 3.0

Subject: Re: [SAdev]  Tool to expand on test results

Here's a tool that works for me. A couple of notes:

1) Doesn't like CR/LF pairs on the input email. Don't know if that's 
really a problem for anyone...
2) It's setup to be run on the machine running spamassassin/spamd. Works 
by parsing the SA config files so that any local rules/scores are picked 
up as well.
3) Output could be made prettier...

--Rich



bugzilla-daemon@hughes-family.org wrote:
> http://www.hughes-family.org/bugzilla/show_bug.cgi?id=1557
> 
> robert@accettura.com changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>            Severity|normal                      |enhancement
>    Target Milestone|2.60                        |3.0
> 
> 
> 
> ------- Additional Comments From robert@accettura.com  2003-02-25 09:04 -------
> Changing:
> severity -> enhancement
> milestone -> 3.0
> 
> 
> 
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Spamassassin-devel mailing list
> Spamassassin-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/spamassassin-devel


-- 

_________________________________________________________

Rich Puhek
ETN Systems Inc.
2125 1st Ave East
Hibbing MN 55746

tel:   218.262.1130
email: rpuhek@etnsystems.com
_________________________________________________________
#!/usr/bin/perl -w
#
#
#  splain_sa.pl  -- Explain the spamassassin tests that "hit" on this rule.


#Default settings...
$rule_location="/usr/share/spamassassin";

my %score;
my %rule;

$status="FALSE";

# read input email, find X-Spam-Status line to determine what hit.
while (<>) {
	chop;
	next if ( (!/\s*tests=/) and ($status eq "FALSE") );
	$status="TRUE";
	last if ( /version=/ );
	s/^\s*//;
	s/tests=//;
	push @tests, split /,/;
};


# read through SA config files. Build list of rules with descriptions and scores.
# look for lines like: describe\s(ruleset)\s(description) and 
#                      score\s(ruleset)\s(score)
#
# parse local.cf last to overwrite desc. and scores...

@files=`ls $rule_location/*.cf`;

foreach $file (@files) {
	#warn "opening: $file\n";
	open (RULE,$file) or die "unable to open $file $!\n";
	
	while (<RULE>) {
		chop;
		next unless ( /^(describe)\s*(\S*)\s*(.*)$/ or
				/^(score)\s*(\S*)\s*(.*)$/ );
		$type=$1;
		$test=$2;
		$value=$3;
		if ($type eq "describe") {
			$desc{$test} = $value;
			next;
		};
		if ($type eq "score") {
			$score{$test} = $value;
			next;
		};
		warn "error: soemthin's wrong, I shouldn't be here\n";
		next;
	};
	
	close RULE;
};


#once the lists are generated, iterate over the matched rules, print info.
print "The email matched the following rules:\n";
foreach $test (@tests) {
	next if $test =~ /^\W*$/;
	$score{$test} = "undefined" if (!defined($score{$test}));
	$desc{$test}  = "undefined" if (!defined($desc{$test}));
	
	print "test: $test score: $score{$test} desc: $desc{$test}\n";
};

I suspect this is less of an issue with the report safe method of encapsulating
spam (which maybe wasn't implemented when this was reported?). spamassassin -t
should probably do just fine.

Furthermore, with the number of potential formats for header lines, this may be
best left as a site-specific thing? It would be technically difficult to do this
with required generality, IMHO.

Marking WONTFIX to clean up bugzilla.