Re: Rexx not processing email formatting

If those quotation marks are part of the output of the Rexx routine, that's the issue. E-mail program would not treat those lines as the commands they purport to be, because the lines don't begin with a recognizable command they begin with a string that consists of the double quote PLUS the com

Re: Rexx not processing email formatting

; Sent: Sunday, April 7, 2019 4:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Rexx not processing email formatting On Sun, 7 Apr 2019 18:26:32 +, Seymour J Metz wrote: >The separator line must have only CRLF; >... True. However, since CMS and VM spool abominate empty records, the VM

Re: Rexx not processing email formatting

On Sun, 7 Apr 2019 18:26:32 +, Seymour J Metz wrote: >The separator line must have only CRLF; >... True. However, since CMS and VM spool abominate empty records, the VM SMTP daemon strips trailing blanks, there by forgiving nonempty blank lines and, in turn, breaking classic uudecode whic

Re: Rexx not processing email formatting

equ...@listserv.ua.edu> Sent: Friday, April 5, 2019 3:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Rexx not processing email formatting On Fri, 5 Apr 2019 17:25:58 +, Seymour J Metz wrote: >You need a blank line after the header ... > Not merely blank; the standards say "empty"

Re: Rexx not processing email formatting

l 5, 2019 4:20 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Rexx not processing email formatting Seymour J Metz wrote: >With rare exceptions, header fields are case insensitive. And one of those rare exceptions is itself exceptional: the left-hand part of an email address (the "lis

Re: Rexx not processing email formatting

: IBM Mainframe Discussion List on behalf of Phil Smith III Sent: Friday, April 5, 2019 5:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Rexx not processing email formatting Gil wrote: >"sanity prevailed, and nobody but nobody" still does not suffice to excuse www >facilities &g

Re: Rexx not processing email formatting

arc-requ...@listserv.ua.edu> Sent: Friday, April 5, 2019 6:28 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Rexx not processing email formatting On Fri, 5 Apr 2019 16:53:01 -0500, Bill Giannelli wrote: >this is what the email received looks like: >"MIME-Version: 1.0" &g

Re: Rexx not processing email formatting

I've now tried both coding the hex values (with hex on) and the null line with the jcl symbol. neither works. Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the

Re: Rexx not processing email formatting

On Fri, 5 Apr 2019 17:33:57 -0500, Bill Giannelli wrote: >The blank line has spaces. >This is in-stream data within JCL. So I dont know how to code a "null" line. > Long ago, in an experiment, I did it by feeding a RECFM=VB file to INTRDR. Need to have at least one line longer than 80, and two l

Re: Rexx not processing email formatting

The blank line has spaces. This is in-stream data within JCL. So I dont know how to code a "null" line. thanks Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the

Re: Rexx not processing email formatting

On Fri, 5 Apr 2019 16:53:01 -0500, Bill Giannelli wrote: >this is what the email received looks like: >"MIME-Version: 1.0" >"CONTENT-TYPE:TEXT/HTML" > >"" >"" >"" >TEXT*** > Does the line (which you didn't surround with quotation marks) between "CONTENT-TYPE:TEXT/HTML" and

Re: Rexx not processing email formatting

Gil wrote: >"sanity prevailed, and nobody but nobody" still does not suffice to excuse www >facilities >that willy-nilly convert case of local part of entered email addresses. Sure, that's obnoxious. If nothing else, maybe you like reading your email as joethel...@whatever.com

Re: Rexx not processing email formatting

this is what the email received looks like: "MIME-Version: 1.0" "CONTENT-TYPE:TEXT/HTML" "" "" "" TEXT*** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.

Re: Rexx not processing email formatting

On Fri, 5 Apr 2019 15:37:39 -0500, Bill Giannelli wrote: >apparently (I just found out) the rexx routine FTPs the email "file" to a >server. and then AO sends out that email from that server. unfortunately I do >not have access to that server right now. > What do the headers look like as the em

Re: Rexx not processing email formatting

further clarification: previously we had this message sent to email in a job thru SMTP and the format commands worked. But now my shop is using this rexx / AO routine and the format commands are just spit out as text. thanks Bill --

Re: Rexx not processing email formatting

On Fri, 5 Apr 2019 16:20:31 -0400, Phil Smith III wrote: > >And one of those rare exceptions is itself exceptional: the left-hand part of >an email address (the "lists" in "li...@akphs.com") is theoretically >case-sensitive per the RFC. But sanity prevailed, and nobody but nobody >implements tha

Re: Rexx not processing email formatting

apparently (I just found out) the rexx routine FTPs the email "file" to a server. and then AO sends out that email from that server. unfortunately I do not have access to that server right now. Bill -- For IBM-MAIN subscribe / s

Re: Rexx not processing email formatting

On Fri, 5 Apr 2019 15:30:23 -0500, Bill Giannelli wrote: >Thank you all for your help and replies! >What we have is a rexx routine sending the message to AO. AO sends it to email >and the formatting now does not work. > Still "does not"? Can you capture the headers on the receiving system a

Re: Rexx not processing email formatting

Thank you all for your help and replies! What we have is a rexx routine sending the message to AO. AO sends it to email and the formatting now does not work. thanks Bill -- For IBM-MAIN subscribe / signoff / archive access in

Re: Rexx not processing email formatting

Seymour J Metz wrote: >With rare exceptions, header fields are case insensitive. And one of those rare exceptions is itself exceptional: the left-hand part of an email address (the "lists" in "li...@akphs.com") is theoretically case-sensitive per the RFC. But sanity prevailed, and nobody but

Re: Rexx not processing email formatting

On Fri, 5 Apr 2019 17:25:58 +, Seymour J Metz wrote: >You need a blank line after the header ... > Not merely blank; the standards say "empty", sometimes in Network conventions, . Some hosts enforce this and don't recognize . I can't think of an example where a non-empty blank line is synta

Re: Rexx not processing email formatting

Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> Sent: Friday, April 5, 2019 1:10 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Rexx not processing email formatting On Fri, 5 Apr 2019 11:07:56 -0500, Bill Giannelli wrote: >We have a rexx on z/OS to send out emails. but when output

Re: Rexx not processing email formatting

> MIME-Version: 1.0 > CONTENT-TYPE:TEXT/HTML Where are you putting this? The contents of an e-mail message has a header and a body, separated by a blank line, and those fields have to be in the message header or in a MIME header. mail from: f...@bar.baz rcpt to: some...@example.com data from:f.

Re: Rexx not processing email formatting

On Fri, 5 Apr 2019 11:07:56 -0500, Bill Giannelli wrote: >We have a rexx on z/OS to send out emails. but when output to email (outlook) >it treats any formatting command as text: >MIME-Version: 1.0 >CONTENT-TYPE:TEXT/HTML < - here - > > >