THIS IS UNPOLISHED CODE
One of my many hats I wear at work is Email administrator. One of the toughest jobs I have is identifying mail loops that are eating up system resources. I found a great program here that did way more than I wanted, but it was written in C (powers that be wouldn't go for it). I also found this on CPAN, but it didn't do what I wanted. After performing a Super Search here, I decided to write my own. It is VERY unpolished. Ideas that someone else could use to make this a much better program are:
Provide ability to specify location of mail log
Clean up output (trailing commas, <>, etc)
Keep track of message size between pairs
Parse status messages (deffered, user unknown, etc)
If anyone finds this useful and decides to implement any of those suggestions, let me know. For now, it is functional, but it can always be better.
#!/usr/bin/perl -w
use strict;
open(SENDMAIL, "/var/adm/syslog/mail.log");
my %pairs;
my %from;
while (my $line = <SENDMAIL>) {
chomp $line;
my @fields = split(" ", $line);
next if ( $fields[6] !~ /to=/ && $fields[6] !~ /from=/ );
if ( $fields[6] =~ /from=/ ) {
$from{$fields[5]} = "\L$fields[6]";
}
else {
$pairs{"$from{$fields[5]} \L$fields[6]"}++;
}
}
close(SENDMAIL);
foreach my $key (sort {$pairs{$b} <=> $pairs{$a}} (keys(%pairs))) {
print "$pairs{$key} $key\n";
}
Thanks,
Limbic~Region
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|