|
From: Evan F. <EF...@di...> - 2004-04-15 14:23:41
|
Hi Mark,
Thanks! Your solution worked perfectly - I inserted the line -
do_log(0, "SA HITS: " . $spam_level . " SA TESTS: " . $sa_tests);
just before
$sa_tests = join(",\n ", split(/,\s*/,$sa_tests));
(to avoid the extra "\n"'s in the output). Works great, now I can grep to my
heart's content! :)
Are there any plans to create a token for the test list to insert into log
templates in future releases? This works great for now, but I'm just
curious, as I'm now maintaining a few of our own customizations to the code
that will make upgrades tricky (it worries me when I'm the only one at work
who has any understanding of the system).
Thanks again!
Evan
-----Original Message-----
From: Mark Martinec [mailto:Mar...@ij...]
Sent: Wednesday, April 14, 2004 6:17 PM
To: ama...@li...
Subject: Re: [AMaViS-user] logging rule hits for non-spam
Perhaps it would be easiest to add a call to do_log(0, "...") into
sub spam_scan (where most spam-related information is collected)
log whatever information you need, and parse that later. E.g.:
do_log(0, "SA TESTS: ".$sa_tests);
|