On 6/18/2013 11:43 AM, Steve Jenkins wrote:

> That STILL sounds less simple than those four lines, but you make an
> excellent point, Stan (as usual). I'll look into that in anticipation of
> the next issue that will surely come up. :)

Well sure, quick hacks are always easy.  Call me a purist, "no frills",
"efficiency freak", maybe "reliability freak", or just plain freak. ;)
A few of salient points:

1.  The header alone may be a kilobyte, for a msg body of a few
    dozen bytes--horrible overhead, a waste of resources.

2.  An SNMP/syslog message will be one or two lines, a few dozen bytes

3.  Comcast's SMTP relay may delay delivery due to any number of
    causes.  You don't control it.  You can't look at nor flush its
    queue.  Do you need these alerts in real time?  Guaranteed delivery?

4.  SNMP/syslog is realtime.  You control it.


SNMP/syslog were designed specifically for this type of application.
They are better suited.  While using SMTP is not wholly inappropriate,
it's far from optimal.  And, is Comcast's relay infrastructure reliable
in the long term for sending such alerts?

-- 
Stan

Reply via email to