<?xml version="1.0" encoding="windows-1252"?>
<node id="865460" title="Re^3: Module to limit email floods?" created="2010-10-15 07:41:07" updated="2010-10-15 07:41:07">
<type id="11">
note</type>
<author id="626051">
dwm042</author>
<data>
<field name="doctext">
[RatKing],&lt;br&gt;&lt;br&gt;
It's far more than a nice idea that will not work. Just work in a place where hundreds of scripts send out thousands of emails a day -- I've had more than one job with those parameters -- and the alternative is not only desirable but eventually necessary. Doing systems administration via email trail is a way to waste alerts, fill email boxes and waste admin time.&lt;br&gt;&lt;br&gt;

No on-the-job script should ever send out an email alert. It should alert a monitoring tool, such as the aforementioned Nagios. A higher end layer of software, or a help desk, can decide to alert admins *if necessary*. This is the kind of thing that a smart shop can automate and a foolish shop will drown admins in electronic paper.&lt;br&gt;&lt;br&gt;

Things get missed in floods of spam. So the smart thing to do is stop the spamming, consolidate the reporting, and push the alerting to a decision making layer. Status messages can then be consolidated in a web interface, as they should be.&lt;br&gt;&lt;br&gt;</field>
<field name="root_node">
865339</field>
<field name="parent_node">
865432</field>
</data>
</node>
