RE: MAPI and EDIINT

[John Hitchins <jhitchins@xxxxxxxxxxxxxxx>]

Hi,

At this point no signatures have been involved, just plain EDI data, with
the Application/EDIFACT as an attachment within a Multipart/Mixed rather
than as the sole bodypart. Looking forward this would indicate that when
signatures are added, the message would be a Multipart/Mixed with a
Multipart/Signed as one of the bodyparts.

Anyway, the main reason I was asking was to get a clarification of the CNet
pilot and as1 as to whether the EDIINT MIME constructs, Application/EDI???,
Multipart/Signed etc, are allowed to be attachments within a Multipart/Mixed
message or have to be the sole bodypart in the message?

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:	Dale Moberg [SMTP:Dale_Moberg@xxxxxxxxxxxx]
> Sent:	Wednesday, November 11, 1998 4:49 PM
> To:	'CNet EDIPilot'; John Hitchins
> Subject:	Re: MAPI and EDIINT
> 
> Hi John,
> 
> If the MIME type is "multipart/mixed", the application does not have any
> clue
> that it should process the message body as a "multipart/signed." So the
> response
> would most likely be to handle the included MIME types in whatever manner
> those types are handled. For example, EDI would possibly go into the
> insecure
>  EDI hopper, the signature file would probably just be stored as an
> attachment,
>  if I understand what you are saying.
> 
>  No one during the test, to my recollection anyway,
> has sent that particular MIME format;.
> 
> The format does not conform to  what the applicability
> statement specifies as the convention for EDI transport. So I guess the
> application
> behavior is undefined in terms of an EDIINT application, and just the
> normal MIME
> handling would come into play.
> 
> Others?
> 
> Bye
> Dale Moberg
> 
> 
> 
> 
> 
> 
> 
> John Hitchins <jhitchins@xxxxxxxxxxxxxxx> on 11/10/98 12:12:54 PM
> Ext: Unknown
> 
> To:   "'CNet EDIPilot'" <edipilot@xxxxxxxxxxxxxxxxxx>, "'IETF EDIINT'"
>       <ietf-ediint@xxxxxxx>
> cc:    (bcc: Dale Moberg/Sterling Commerce)
> Subject:  MAPI and EDIINT
> 
> 
> 
> 
> Hi,
> Just a small question about the CommerceNet Interoperability tests -
> 
> The problem -
> When using Microsoft MAPI to create an Internet mail message containing
> EDI
> data you end up with a Multipart/Mixed message with one of the body parts
> being the rfc1767 application/edi????
> i.e. -
> To: <edi@xxxxxxxxxxxxxxx>
> From: <edi@xxxxxxxxxxxxxxx>
> Content-Type: Multipart/Mixed; boundary=b1
> --b1
> Content-Type: Application/EDIFACT
> ..
> ..<EDI Data>
> ..
> --b1
> 
> Is this format of message, multipart/mixed, allowed by the CommerceNet
> Interoperability tests and do any/all of the Applications being tested
> support it?
> Cheers for your help.
> /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.
> 
> -----------------------------------------------------------------------
> 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
> 
> 
> 
> 
> -----------------------------------------------------------------------
> 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