On Tue, 1 Nov 2016 09:47:35 -0500, Elardus Engelbrecht wrote:
>Hilary Hurwitz wrote:
>
>>But I have a few problems with this.
>>If the email fails the job ends with a 0, and until a rejection email
>>arrives back to me, I have no idea of problems.
>
>>I have a feeling we have a hole in the knowledge of our tcp people here. Is
>>this the way to work ? Surely the job should be able to know if the email was
>>sent?
>
>Rather use CSSMTP as others suggested.
>
Looking in a Config Guide, I see:
CSSMTP processes a mail message directly from the JES spool data set ...
... Appears to be another batch process that hardly addresses Hilary's concern.
CMS Pipelines is wonderful here. I can
PIPE stuff | TCPCLIENT LOCALHOST 25 /* (roughly) */
... and get a response code back from each command and act on it. Does
XMITIP do likewise? Of course if an error is detected by a downstream
MTA, the response is spooled.
The Config Guide emphasizes that CSSMTP is not a server; you still need
one of those.
How does "cat headers+messages | sendmail -toi" work nowadays? You
might get to it with BPXWUNIX.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
