I cannot get your attachment. Please do the following.
Mail to my private address ([EMAIL PROTECTED]) the object thet you are trying to attach with V5R3. I will try that on my V5R3 system and let you know. Giovanni B. Perotti ----- Original Message ----- From: "jsev400" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 11, 2005 10:51 PM Subject: [Easy400Group] Re: MMAIL attachments at V5R3 > --- In [EMAIL PROTECTED], "jbperotti" <[EMAIL PROTECTED]> wrote: >> >> The only thing I can think of, is that the characters used to make >> up the base64 conversion get corrupted for some reason. >> These characters are kept on the single-record physical file >> mmail/base64. >> Its record format is made of a single field, with CCSID 37 (use >> command dspffd mmail/base64 to verify it). >> The contents of that field are the following 64 characters(forget >> the initial and ending double quote): >> "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/" > > Have checked the file and the CCSID is 37. > A display of the file looks identical to the above. > > >> Now, if your system is running with system value QCCSID 65535, I >> would expect that the job running MMAIL commands or subprocedures, >> when it comes to the base64 module (xxxbase64) would fail in >> receiving the correct characters or the final "+/", as code page >> conversion would not take place. >> This would result in some corruption of the attachment. > > I did note the warnings in the MMAIL documentation about this as our > systems run at CCSID 65535. We have never experienced any issues with > this though. > However, I wondered if V5R3 may operate differently here. I tried > logging off/on, changing my job to CCSID 37 and sending a mail but > that didn't work. I then changed the system value to 37, logged > off/on again (and checked my job which showed as using CCSID 37) but > that made no difference either. The attachment is a STMF which has > been created using the CPYTOIMPF and STMFCODPAG(*PCASCII) RCDDLM(*CRLF). > > >> If this is the case ( system value QCCSID 65535 ) I would suggest >> that you change the job CCCSID ( e.g. chgjob ccsid(37) ) before >> running MMAIL commands or subprocedures. >> >> Again, this is what I can think of at this time. >> >> Giovanni B. Perotti >> mmail author >> >> >> >> >> >> >> --- In [EMAIL PROTECTED], "jsev400" <[EMAIL PROTECTED]> wrote: >> > >> > Hi all >> > >> > We have had the MMAIL utility installed and working for a couple of >> > years on our systems. Recently, we have upgraded one system to >> V5R3 >> > and since then, when sending attachments, the attachments are >> received >> > as gibberish. When looking at the MIME file, it looks like an >> issue >> > with the BASE64 encoding. >> > >> > Here is an example of the MIME files (partial only) for a V5R2 >> system >> > and a V5R3 system when sending the same file (and yes, the >> xxxxxxx's >> > were put in by me to remove email references :-) >> > >> > >> > V5R2: >> > ------------------------------------------------------------------ >> > Sender: xxxxxxxxxx >> > Date: Tue, 11 Oct 2005 09:37:10 +1300 >> > From: xxxxxxxxxx >> > MIME-Version: 1.0 >> > Message-ID: <xxxxxxxxxxxxxxx> >> > To: xxxxxxxxxx >> > Subject: Test >> > X-Mailer: IBM Internet Messaging Framework from eServer System >> > Importance: medium >> > Priority: normal >> > Content-Type: MULTIPART/MIXED; BOUNDARY="--PART.BOUNDARY.1" >> > >> > >> > ----PART.BOUNDARY.1 >> > Content-Type: text/plain; charset=US-ASCII >> > Content-Disposition: inline >> > Content-Transfer-Encoding: 7bit >> > >> >> > V5R2 attachment >> test >> > >> >> > >> >> > >> >> > *** Please do not reply to this email as this >> has >> > been sent from a server machine >> only. >> > >> >> > ---- >> PART.BOUNDARY.1 >> > Content-Type: application/octet-stream; >> name="QPDSPDBR.37.10.4420.txt" >> > Content-Disposition: attachment; >> filename="QPDSPDBR.37.10.4420.txt" >> > Content-Transfer-Encoding: >> base64 >> > Content-Description: >> QPDSPDBR.37.10.4420.txt >> > >> >> > >> IDU3MjJTUzEgVjVSM00wICAwNDA1MjggICAgICAgICAgICAgICBEaXNwbGF5IERhdGEgQ >> mFz >> > >> ZSBSZWxhdGlvbnMgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMTEvMTAvMDUgI >> CA4 >> > >> OjM1OjI3ICAgICAgIFBhZ2UgICAgMQ0KIERTUERCUiBDb21tYW5kIElucHV0DQogICBGa >> Wxl >> > >> ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDogRklMRSAgICAgI >> CBU >> > >> RUxORVRFWElUDQogICAgIExpYnJhcnkgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuI >> C4g >> > . >> > . >> > . >> > ------------------------------------------------------------------- >> - >> > >> > >> > V5R3: >> > ------------------------------------------------------------------- >> - >> > Sender: xxxxxxxxxx >> > Date: Tue, 11 Oct 2005 09:38:27 +1300 >> > From: xxxxxxxxxx >> > MIME-Version: 1.0 >> > Message-ID: <xxxxxxxxxxxxxxx> >> > To: xxxxxxxxxx >> > Subject: Test >> > X-Mailer: IBM Internet Messaging Framework from eServer System >> > Importance: medium >> > Priority: normal >> > Content-Type: MULTIPART/MIXED; BOUNDARY="--PART.BOUNDARY.1" >> > >> > >> > ----PART.BOUNDARY.1 >> > Content-Type: text/plain; charset=US-ASCII >> > Content-Disposition: inline >> > Content-Transfer-Encoding: 7bit >> > >> > V5R3 attachment test >> > >> > >> > >> > *** Please do not reply to this email as this has >> > been sent from a server machine only. >> > >> > ----PART.BOUNDARY.1 >> > Content-Type: application/octet- >> stream;name="QPDSPDBR.38.28.2170.txt" >> > Content-Disposition: attachment; filename="QPDSPDBR.38.28.2170.txt" >> > Content-Transfer-Encoding: base64 >> > Content-Description: QPDSPDBR.38.28.2170.txt >> > >> > >> QPX38vLi4vFA5fXZ89TwQEDw9PD18vhAQEBAQEBAQEBAQEBAQEDEiaKXk4GoQMSBo4FAw >> oGi >> > >> hUDZhZOBo4mWlaJAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBA8fFh8fBh8PVAQ >> ED4 >> > >> evP1evL3QEBAQEBAQNeBh4VAQEBA8UBADQpAxOLXxMLZQMOWlJSBlYRAyZWXpKNAQEBAQ >> EBA >> > >> QEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQ >> EBA >> > >> QEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEANC >> kBA >> > . >> > . >> > . >> > ------------------------------------------------------------ >> > >> > As you can see, the file attachment part is quite different. >> > Has anyone else experienced this? Any clues as to what might be >> > happening? >> > >> > > > > > > > > Yahoo! Groups Links > > > > > > > > > ------------------------ Yahoo! Groups Sponsor --------------------~--> Most low income households are not online. Help bridge the digital divide today! http://us.click.yahoo.com/cd_AJB/QnQLAA/TtwFAA/wbFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/Easy400Group/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
