On 8/28/20 7:36 AM, Paul Gilmartin wrote:
The inability to handle Delivery Status Notifications is a glaring deficiency of CSSMTP, worthy of an RFE to repair this regression.
DSNs / MDNs / other non-standard bounces don't need to come back into CSSMTP. The just need to come back into an SMTP server. It can be any SMTP server, including the main corporate SMTP server.
It is entirely possible to send messages from CSSMTP and have the bounces go back to a different server, and then collect bounces or otherwise process them there.
Might this be partly mitigated by supplying an "Errors-to:" header?
Unnecessary.
Was security a motivator for ending support of incoming mail, possibly because DSNs often reproduce the entire, possibly sensitive, email bodies?
You can influence what is returned by using the optional "RET=HDRS" parameter to the MAIL FROM statement. Standards compliant servers should only return the headers and not the message body.
-- Grant. . . . unix || die ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
