I agree that a mail to SPOOL gateway would be nice and an RFE would be appropriate. I'm not sure that I would call dropping the facility a glaring deficiency, but it is certainly unfortunate.
I assume that IBM simply wants people to use an e-mail client off of the mainframe. No, adding errors-to doesn't change anything; you still need an external mail application to read the response once SMTP is gone. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Paul Gilmartin <0000000433f07816-dmarc-requ...@listserv.ua.edu> Sent: Friday, August 28, 2020 9:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Sending email from the Mainframe On Fri, 28 Aug 2020 13:01:54 +0000, Seymour J Metz wrote: >Once CSSMTP has submitted your e-mail, it has no involvement. You should get a >DSN if there is a problem, but, unlike SMTP, CSSMTP does not handle incoming >mail. The inability to handle Delivery Status Notifications is a glaring deficiency of CSSMTP, worthy of an RFE to repair this regression. Might this be partly mitigated by supplying an "Errors-to:" header? Was security a motivator for ending support of incoming mail, possibly because DSNs often reproduce the entire, possibly sensitive, email bodies? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
