Cool. Having it as part of the Logwatch report would be just fine with
me. I have created a short logwatch script to count and show me a
running total of each spam score number, but your script I'm sure is a
lot better than mine. Would you be willing to release yours to the open
source community, or would you ask for some sort of compensation?
Dan Schaefer
Application Developer
Performance Administration Corp.
Martin Gregorie wrote:
On Fri, 2009-07-03 at 12:03 -0400, Daniel Schaefer wrote:
If you have found something similar to this, good. If you have created
your own script to do this, better. If Spamassassin has this script
created already and I missed it, even better.
I wrote my own but it is somewhat specialized because:
- it runs as part of the logwatch report rather than being a cron job.
This is the easiest way I know to restrict the scan to the last 24
hours of the maillog.
- one section of its report comes from maillog entries generated by my
spamkiller utility, but this just shows totals for clean, spam and
total messages.
- it is designed to monitor only my own custom rules. It reads local.cf
to get a list of them and ignores everything else.
- by default it only reports the top ten firing rules.
- it has options to list all rules alphabetically or ranked by hit rate.
- written in Perl, but what else would you expect from an SA reporting
tool?
Martin
