>I've already read the flame to this posting, and I agree that it's
>uncalled for. The information above is very useful for charging
>back users/departments against channel utilization, and if you've
>got all of your mail going out a single gateway (what a concept ;),
>then that's the best place to measure it. You can also use the data
>for other things like: if someone who's just put in their two week
>notice is starting to mail Size:Big_Megabyte messages, or is increasing
>the frequency of their smaller messages, that is a red flag IMO.
When I ran a similar thing on one machine, I discovered that
the top mail recipient one week was:
someone @
some .
machine: 15mb
some-mailing-list-errors: 15mb
At that point, I cross-indexed the summary and determined
that someone was on a very high volume mailing list and his account
had been deleted when he left the company. So, it was nice to be able
to fix that.
I've also found that when some mailing list sends a huge
number of messages to 5 or 6 users, it's time to politely, "ahem"
and suggest an internal mail exploder.
One guy's "fascism" is another guy's "good systems managment"
but I don't think we're going to clarify the dividing line in this
mailing list. At least I hope we don't try.
mjr.
|
|
