haracter is what you
are, reputation merely what others think you are." - John Wooden
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Thursday, May 9, 2019 3:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: z/OS SMTP Question - solved
>
S
On Thu, 9 May 2019 15:08:28 -0500, Lionel B Dyck wrote:
>The issue seems to be that the z/VM RSCS, or the SMTP server, was taking the
>data and truncating it to 80 bytes.
>
>I had the site change the secure_smtp setting in the XMITIPCU configuration
>file from null to 1. This has nothing to do w
den
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Thursday, May 9, 2019 2:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: z/OS SMTP Question
On Thu, 9 May 2019 10:45:37 -0500, Lionel B Dyck wrote:
>More information and clarification.
>
>T
On Thu, 9 May 2019 10:45:37 -0500, Lionel B Dyck wrote:
>More information and clarification.
>
>The smtp email spool file is being received by RSCS and passed to the SMTP
>server on z/VM which is delivering the email BUT the text attachment is
>being truncated to 80 bytes instead of the original 1
---
From: IBM Mainframe Discussion List On Behalf Of
Seymour J Metz
Sent: Thursday, May 9, 2019 10:23 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: z/OS SMTP Question
Don't you MIME encode the dataset attached to the e-mail? Or are you saying
that the user have VB message text along with the file
age-
From: IBM Mainframe Discussion List On Behalf Of
Seymour J Metz
Sent: Thursday, May 9, 2019 10:23 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: z/OS SMTP Question
Don't you MIME encode the dataset attached to the e-mail? Or are you saying
that the user have VB message text along w
ehalf of
Lionel B Dyck
Sent: Thursday, May 9, 2019 11:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: z/OS SMTP Question
Correct - RSCS on the z/VM side. I have asked for error messages (mid last
week) and not seen those yet.
XMITIP dynamically determines the sysout dcb for the spool file bas
ginal Message-
From: IBM Mainframe Discussion List On Behalf Of
Seymour J Metz
Sent: Thursday, May 9, 2019 10:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: z/OS SMTP Question
When you write "z/VM", do you mean RSCS or the z/VM SMTP?
IAC, you might consider adding DCB options to XM
n List on behalf of
Lionel B Dyck
Sent: Thursday, May 9, 2019 10:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: z/OS SMTP Question
I had an XMITIP user send me a report of a failure and I need the help of
this group as it involves NJE and z/VM.
Their configuration is they run XMITIP on z/OS, which
I had an XMITIP user send me a report of a failure and I need the help of
this group as it involves NJE and z/VM.
Their configuration is they run XMITIP on z/OS, which generates the SMTP
email as a sysout file in the JES2 spool with a destination of a z/VM node
and user of the SMTP server on z/
On 2016-04-28, at 08:15, Jousma, David wrote:
> Speaking of SMTP (including CSSMTP), how do your shops prevent Sender
> spoofing? How do you validate that the From: in the email is authorized?
> I ask because while we use SMTP internally, mostly for mail from production
> batch jobs, we hav
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Donald J.
Sent: Thursday, April 28, 2016 9:09 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMTP question.
Does adding "NOSOURCEROUTE ENABLED" to your SMTP task config change anything?
--
D
@LISTSERV.UA.EDU
Subject: Re: SMTP question.
On Thu, 28 Apr 2016 00:05:28 +, Field, Alan
wrote:
>
>One thing we see from the failing lpar (in the SMTP log) is
>
> MAIL FROM:
>
MAIL FROM: is part of the SMTP protocol for specifying the originator of the
e-mail. What goes be
Does adding "NOSOURCEROUTE ENABLED" to your SMTP task config
change anything?
--
Donald J.
dona...@4email.net
On Wed, Apr 27, 2016, at 05:05 PM, Field, Alan wrote:
> We run SMTP on one lpar (z/OS 2.1).
>
> Recently we switched our mail server from Notes to Exchange.
>
> Mostly transparent
On Thu, 28 Apr 2016 00:05:28 +, Field, Alan
wrote:
>
>One thing we see from the failing lpar (in the SMTP log) is
>
> MAIL FROM:
>
MAIL FROM: is part of the SMTP protocol for specifying the originator of the
e-mail. What goes between the <> is supposed to be the e-mail address of the
se
We run SMTP on one lpar (z/OS 2.1).
Recently we switched our mail server from Notes to Exchange.
Mostly transparent except for one lpar, and only some jobs even then.
The failing jobs use SAS email. They run fine on 5 lpars, fail on one.
One thing we see from the failing lpar (in the SMTP log)
16 matches
Mail list logo
