Re: SNDEMAIL and /tmp

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

SNDEMAIL writes the e-mail message to /tmp, then hands it off to the 
QtmmSendMail API.  That API, after scrutinizing it's parameters, passes 
the information to a background job that will remove the file from /tmp 
and put it into the mail queue.

So there's a tiny period of time between the time you call SNDEMAIL and 
the time the background job removes the file where it should continue to 
reside in /tmp -- but that should be a very small amount of time.

The fact that a file is missing from /tmp does NOT guarantee that it was 
delivered successfully.  The fact that a file remains in /tmp is not a 
guarantee that it was not delivered.  It all depends on what the error is.

However, it's safe to assume that if a file remains in /tmp for more 
than a few minutes, *something* is wrong, and PROBABLY means that those 
files are no longer needed.


John McKee wrote:
> We have a program that sends multiple emails in the event of an error.  Each
> email is to one person.  After reading the thread about files in /tmp, I
> checked our system.  There are 11 files there.  But, all are sent to the same
> address.  Since the program thst sends the emails is sending to other addresses
> as well, I am assuming that the reason these are still here is that the email
> could not be sent.  Is that a valid assumption?  Is there any other reason
> these specific emails would remain?  The email address used is NOT the last
> email sent by the CL, if that makes any difference.
>
> John McKee