From: IBM Mainframe Discussion List on behalf of
Grant Taylor <023065957af1-dmarc-requ...@listserv.ua.edu>
Sent: Sunday, August 30, 2020 11:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
On 8/29/20 6:50 PM, Seymour J Metz
On 8/29/20 6:50 PM, Seymour J Metz wrote:
According to the IETF, every bounce is a DSN but not every DSN is a bounce.
Would you please cite your source?
I also wonder if we're having somewhat of a semantic issue. I'm
specifically referring to a bounce (which is a superset of the latter)
Friday, August 28, 2020 10:31 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
On 8/28/20 5:44 PM, Seymour J Metz wrote:
> Doing a direct to MX session will let you see rejection messages,
> but your firewall may not allow that and even if it does you could
> get a
;
Sent: Friday, August 28, 2020 10:32 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
On 8/28/20 5:46 PM, Seymour J Metz wrote:
> A DSN *is* a standard bounce.
Yes. But not all bounces are DSNs.
--
Grant. . . .
un
On 8/28/20 5:46 PM, Seymour J Metz wrote:
A DSN *is* a standard bounce.
Yes. But not all bounces are DSNs.
--
Grant. . . .
unix || die
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
On 8/28/20 5:44 PM, Seymour J Metz wrote:
Doing a direct to MX session will let you see rejection messages,
but your firewall may not allow that and even if it does you could
get a subsequesen DSN.
If you are the sending system, you would be the one to generate said
DSN. So ... why would
816-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 +, Seymour J Metz wrote:
>Once CSSMTP has submitted your e-mail, it has no involvement. You should ge
@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
You seem to be asking for an impossibility here because the email
protocol as currently implemented doesn't support this.There is no
way for a sender of email to distinguish between email that is accepted
by its target domain but classed
M-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
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 bounce
ct: Re: Sending email from the Mainframe
On 8/28/20 7:39 AM, Joel C. Ewing wrote:
> You seem to be asking for an impossibility here because the email
> protocol as currently implemented doesn't support this.
There is a way to have a relatively good indication if a message w
On 8/28/20 11:46 AM, Statler, David wrote:
You may be able to utilize the "Undeliverable" feature in the CSSSMTP
Config setup. You can specify the action to take (store or delete)
on a dead letter and a unix directory to store it in.
What does CSSMTP do if I send email from a perfectly valid
, Len
Sent: Friday, August 28, 2020 6:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
Does anyone have JCL that sends an email, using CSSMTP, from the Mainframe and
if it is unable to be delivered, for any reason, sends an email back to the
Sender with a correspondi
On 8/28/20 7:39 AM, Joel C. Ewing wrote:
You seem to be asking for an impossibility here because the email
protocol as currently implemented doesn't support this.
There is a way to have a relatively good indication if a message was
displayed or not. It relies on HTML and unique per message
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
On 8/28/20 5:57 AM, Sasso, Len wrote:
Does anyone have JCL that sends an email, using CSSMTP, from the
Mainframe and if it is unable to be delivered, for any reason, sends
an email back to the Sender with a corresponding message?
I'm guessing that since CSSMTP is involved, the JCL / job is
On Fri, 28 Aug 2020 08:39:33 -0500, Joel C. Ewing wrote:
>
> It would have to be a highly unusual
>situation before most informed users would ever allow a receipt to be
>returned.
>
... very dangerous - there's tremendous fraud involved.
-- gil
You seem to be asking for an impossibility here because the email
protocol as currently implemented doesn't support this. There is no
way for a sender of email to distinguish between email that is accepted
by its target domain but classed (correctly or incorrectly) as spam and
thrown into the
On Fri, 28 Aug 2020 13:01:54 +, 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
There are products that can do this, JES2MAIL is one we use, z/osmf can be used
but I have configured z/osmf to use the lan (MS) smtp server and use jes2eds
notification
//NFY NOTIFY EMAIL='u...@domain.com' after the jobcard.
not support it.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Sasso, Len
Sent: Friday, August 28, 2020 7:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
Does
com>
From: IBM Mainframe Discussion List on behalf of
Timothy Sipples
Sent: Friday, July 24, 2020 5:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
[External: Use caution with links & attachments]
Grant Taylor asks:
>What happens to em
Grant Taylor asks:
>What happens to email if CSSMTP (AT-TLS) is configured
>to *require* encryption and the receiving system doesn't
>support encryption?
Fundamentally the same thing(s) that happen when the network connection is
down or too slow (times out), for whatever reasons. Network
gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Grant Taylor [023065957af1-dmarc-requ...@listserv.ua.edu]
Sent: Thursday, July 23, 2020 4:48 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
On
On 7/23/20 2:27 PM, Seymour J Metz wrote:
Are you assuming direct-to-MX?
Given the prior comments about wanting to not smart host / off-load to a
different local SMTP server, yes, I'm assuming direct-to-MX with my
comments / questions.
Are you assuming using a mail server not under the
o: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
On 7/23/20 1:24 AM, Seymour J Metz wrote:
> But what, someone may ask, if the realy connects to a box that doesn't
> support TLS 1.2? The same thing as if the traffic from CSSMTP were
> unencrypted, and not the conc
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Grant Taylor [023065957af1-dmarc-requ...@listserv.ua.edu]
Sent: Thursday, July 23, 2020 12:17 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
On 7/23/20 12:17 AM, Timothy Sipples wrote
On 7/23/20 12:17 AM, Timothy Sipples wrote:
I don't know why you're questioning Len's expressed*requirement*.
Experience. Specifically experience that has included being down stream
of multiple telephone games. Person A tells person B that they require
/encryption/. Then person B tells
On 7/23/20 1:24 AM, Seymour J Metz wrote:
But what, someone may ask, if the realy connects to a box that doesn't
support TLS 1.2? The same thing as if the traffic from CSSMTP were
unencrypted, and not the concern of the z/OS staff unless the relay
is also running on z/OS.
What happens to
Cell: (518) 894-0879
Fax: (518) 257-4300
len.sa...@gdit.com
URL: www.gdit.com<http://www.gdit.com>
From: IBM Mainframe Discussion List on behalf of
Timothy Sipples
Sent: Thursday, July 23, 2020 2:17 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Timothy Sipples [sipp...@sg.ibm.com]
Sent: Thursday, July 23, 2020 2:17 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
Grant Taylor wrote:
>That me
Grant Taylor wrote:
>That means that z/OS's CSSMTP will be near or on par with other SMTP
>servers and related problems securing SMTP traffic. Most of which have
>to do with the capabilities of the receiving SMTP server, which is
>outside of CSSMTP's control.
First of all, here's what Len Sasso
ginal Message-
From: IBM Mainframe Discussion List On Behalf Of
Grant Taylor
Sent: Wednesday, July 22, 2020 10:52 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
On 7/22/20 2:17 AM, Timothy Sipples wrote:
> CSSMTP. No problem. IBM explains how to set up TLS
On 7/22/20 2:17 AM, Timothy Sipples wrote:
CSSMTP. No problem. IBM explains how to set up TLS with CSSMTP here
(current z/OS 2.4 documentation link, subject to change):
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.halz002/cssmtp_tls.htm
That means that z/OS's
Len Sasso wrote:
>We are using CSSMTP to send email from the Mainframe.
>All our messages must implement TLS 1.2 or higher for
>transport level encryption.
>What you using?
CSSMTP. No problem. IBM explains how to set up TLS with CSSMTP here
(current z/OS 2.4 documentation link, subject to
We send everything plain text to the corporate email server and let them handle
it!
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Tony Thigpen
Sent: Tuesday, July 21, 2020 11:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sending email from the Mainframe
We found it easier to set up a small SMTP relay box on an Intel platform
and let it do all the TLS heavy lifting.
Tony Thigpen
Sasso, Len wrote on 7/21/20 9:44 AM:
We are using CSSMTP to send email from the Mainframe. All our messages must
implement TLS 1.2 or higher for transport level
We are using CSSMTP to send email from the Mainframe. All our messages must
implement TLS 1.2 or higher for transport level encryption.
What you using?
Please Be Safe!
Thank You!
Len Sasso
Systems Administrator Senior
CSRA, A General Dynamics Information Technology Company
327 Columbia TPKE
37 matches
Mail list logo
