Yes, I meant blank in the sense of empty; it is definitely incorrect to have a space there.
-- 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, 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 +0000, Seymour J Metz wrote: >You need a blank line after the header ... > Not merely blank; the standards say "empty", sometimes in Network conventions, <CR><LF><CR><LF>. Some hosts enforce this and don't recognize <CR><LF><SP><CR><LF>. I can't think of an example where a non-empty blank line is syntactically valid within headers. >... whether or not it contains MIME fields. With rare exceptions, header >fields are case insensitive. >________________________________________ >From: Paul Gilmartin >Sent: Friday, April 5, 2019 1:10 PM > >>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 ----- > >><HTML> >><BODY> >><PRE STYLE="FONT: MONOSPACE"> >>Any advice as to why these commands are not formatting the email message >>"body"? > >I'm pretty sure you need an empty line between the MIME headers and the message >body. > >Mainframes are kinda hostile to empty lines. CMS is worse than z/OS. > >Are email headers case-insensitive? -- 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
