RE: SNDDST Confirmation of Delivery - Internet (Outside World)

Peter,

The problem with email is that there is NO reliable method of delivery
confirmation.

SNDDST might "think" it got delivered, but what it is really saying is
that it got delivered to your main SMTP server.  Which then has to
deliver it to the next SMTP server.  And there might be more after
that!  And of course, it says nothing about it got delivered to
somebody's "inbox".  Nor if it got delivered to an inbox, did it
actually get read?

And most SMTP servers will hold on to mail for 5+ days before they give
up on delivering to the next location.

You must be careful about what is truly meant by "delivered" in the
email world!

Bob


-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Peter_Vidal@pall.com
Sent: Monday, September 30, 2002 11:16 AM
To: midrange-l@midrange.com
Subject: SNDDST Confirmation of Delivery - Internet (Outside World)

Hi list.

A friend of mine has this problem.  They want to send email to their
vendors
automatically when material is short.  They are actually using SNDDST
for
internal emails.  I have read about QRYDST but I still do not know how
to they
work together to achieve this goal.  I also read that we have to be
careful
because the entries may go up to 9999 and then we will have problems.

How can this task be achieved if SNDDST is being used and a
confirmation of
delivery is needed in order to update some other files with this
"delivery
confirmed" data?