Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Thread

Statistics Script?

Statistics Script?

2005-09-01 by Michael Wallendahl

Has anyone already written a script to parse Sendmail's maillog file and 
display some detailed statistics about milter-greylist actions?  I 
thought I'd ask on the list before I try a crack at it.

Statistics like:

* Local users and their rejected message count so I can give them a 
report stating how many messages were blocked by the filter.
* Average delay time for accepted e-mail per user and per sending ip (to 
more easily find domains with badly behaving or multiple outbound mailers)
* Total count of rejected messages per IP to help identify high volume 
spammers.

Thanks,
Mike

Re: [milter-greylist] Statistics Script?

2005-09-08 by Techwolf

On Wed, 2005-08-31 at 23:13 -0700, Michael Wallendahl wrote:
> Has anyone already written a script to parse Sendmail's maillog file and 
> display some detailed statistics about milter-greylist actions?  I 
> thought I'd ask on the list before I try a crack at it.
> 
> Statistics like:
> 
> * Local users and their rejected message count so I can give them a 
> report stating how many messages were blocked by the filter.
> * Average delay time for accepted e-mail per user and per sending ip (to 
> more easily find domains with badly behaving or multiple outbound mailers)
> * Total count of rejected messages per IP to help identify high volume 
> spammers.
> 
> Thanks,
> Mike
> 

This would be a good one to submit to the logwatch folks at
http://www.logwatch.org/

I did some quick mods/patches/changes to logwatch to parse the milter-
greylist lines. Just a simple rejects list to each mailbox. Gives an
idea how many spammers try to spam a mailbox. One can see some
interesting trends over the months.

-- 
Techwolf
Techwolf@...
http://www.techwolf.net/index.html
gpg and PGP public keys on web site.

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.