HP3000-L Archives

May 2001, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Simonsen, Larry" <[log in to unmask]>
Reply To:
Simonsen, Larry
Date:
Thu, 3 May 2001 16:56:45 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (52 lines)
This is what we do.  We also distribute reports via e-mail.  Its like the
standard printer.

-------------------------------------------------
Larry Simonsen                Phone: 801-489-2450
Flowserve Corporation     Fax: 801-491-1750
PO Box 2200                    http://www.Flowserve.com
Springville, UT 84663      e-mail: [log in to unmask]
-------------------------------------------------
All opinions expressed herein are my own and reflect, in no way, those of my
employer.

 -----Original Message-----
From:   [log in to unmask] [mailto:[log in to unmask]]
Sent:   Thursday, May 03, 2001 2:13 PM
To:     [log in to unmask]
Subject:        OT: email as the best common denominator

X-no-Archive:yes
I have been talking up an idea in our office, and now I am started to
question if I am just enamored with an idea that is less practical than I
imagine, or if I have an idea that has merit.

I am proposing that we use email as the best common denominator for
automated notifications. I propose that we set up "container" distributions
list, such as [log in to unmask] This container distribution list
could then contain a single address that can be changed as needed. This way,
if duties change, or for those duties that we rotate weekly or monthly, the
contained address can be changed as needed (which is a bit of a drag for the
email administrator). Also, the actual target email address would need to be
configured in the email server's address book (this I know less about).

Now, that contained address could be the SMTP for someone's pager, cell
phone, or other message-capable device (which assumes and depends on the
reliability of such devices and services, and raises the question of how to
handle failures, which is not a trivial question). Or, it could just be
someone's standard email address (company or private), if that's how they
choose to monitor things, when it's their turn to monitor things.

So, what am I forgetting? Or not thinking of? Has anyone done anything like
this, either on a small scale or a large scale? And how well did it work?
And If it didn't work, could it have been made to work?

Greg Stigers
http://www.cgiusa.com

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2