RE: EDIINT MIME Constructs within Multipart/Mixed Messages

[John Hitchins <jhitchins@xxxxxxxxxxxxxxx>]

Hi,

Yes, fix the trailing boundary and it is valid MIME but would it be accepted
in the CommerceNet Interop Tests?

I.e. Will all the Apps tested by CommerceNet accept and correctly process
this construct?

Cheers.

/jh 

--
John Hitchins                  | Harbinger UK,
jhitchins@xxxxxxxxxxxxxxx      | Quay West. Trafford Wharf Road,
http://www.harbinger.co.uk     | Manchester, M17 1HH, England.
                               | Tel: +44 161 872 2022
                               | Fax: +44 161 872 2024
    The views represented here are mine and not necessarily
                     those of Harbinger UK.


> -----Original Message-----
> From:	John Mani [SMTP:John.Mani@xxxxxxxxxxx]
> Sent:	Monday, November 16, 1998 8:28 PM
> To:	drummond@xxxxxxxxxx; jhitchins@xxxxxxxxxxxxxxx
> Cc:	edipilot@xxxxxxxxxxxxxxxxxx; ietf-ediint@xxxxxxx
> Subject:	Re: EDIINT MIME Constructs within Multipart/Mixed Messages
> 
> 
> > 
> > To aid in interoperability can we get clarification as to whether
> including
> > the EDIINT MIME constructs within a Multipart/Mixed message is allowed
> under
> > as1 and/or the CommerceNet pilot.
> > 
> > i.e. Is the following construct allowed? -
> 
> Hmm .. why wouldn't it be ? It needs a valid terminating boundary and/or
> more bodyparts, but other than that it looks valid MIME
> 
> -john
> 
> > 
> > To: <recipient>
> > From: <sender>
> > MIME-Version: 1.0
> > Content-Type: Multipart/Mixed; boundary=boundary1
> > 
> > --boundary1
> > Content-Type: Application/EDIFACT
> > Content-Transfer-Encoding: base64
> > 
> > HGFGKGFL
> > ...
> > KJHFHGRKHR
> > 
> > --boundary1
> > 
> 
> 
> -----------------------------------------------------------------------
> Message addressed to: edipilot@xxxxxxxxxxxxxxxxxx
> Archive available at: http://lists.commerce.net/archives/edipilot/
> To (un)subscribe send a message with "subscribe" or "unsubscribe" in the
> body to: edipilot-request@xxxxxxxxxxxxxxxxxx