RE: MAPI and EDIINT

["Jim Reitz (Exchange)" <jimre@xxxxxxxxxxxxxxxxxxxxxx>]

If they are using Exchange Server's Internet Mail Connector as their
MAPI->MIME gateway (you say they "send them out through an Exchange box"),
then this sounds like a bug that we fixed over two years ago in Exchange 4.0
Service Pack 2 (and all subsequent releases).

This company should make sure their software is up to date. For details on
this bug, please see our KnowledgeBase article Q152863, which can be found
at:

http://support.microsoft.com/support/kb/articles/q152/8/63.asp



-----Original Message-----
From: John Hitchins [mailto:jhitchins@xxxxxxxxxxxxxxx]
Sent: Monday, November 16, 1998 3:56 AM
To: Jim Reitz (Exchange)
Cc: 'IETF EDIINT'
Subject: RE: MAPI and EDIINT


Hi,

The problem actually came from another company who are trying to implement
EDIINT on Win32 using MAPI and came to light when we tried to set up a live
demo at a trade show here in the UK.

The details I have are that they developed code, using MAPI, to create
EDIINT messages and send them out through an Exchange box and the problem
they encountered is that they were unable to create a mail message of type
Application/EDIFACT using MAPI. If my understanding is correct they create a
mail message and then attach the EDI file specifying the content type which
gives them a Multipart/Mixed message with the Application/EDIFACT as one of
the body parts, but they are unable to create a message with only the single
bodypart of type Application/EDIFACT. 

This has raised concerns at the E-Centre, formerly the Electronic Commerce
Association, as it would seem to imply that MAPI cannot be used to create an
EDIINT compliant 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:	Jim Reitz (Exchange) [SMTP:jimre@xxxxxxxxxxxxxxxxxxxxxx]
> Sent:	Tuesday, November 10, 1998 6:44 PM
> To:	'John Hitchins'
> Cc:	'ietf-ediint@xxxxxxx'
> Subject:	RE: MAPI and EDIINT
> 
> What you are seeing is likely a default mapping being performed by some
> MAPI<->MIME gateway, not "MAPI" itself. What mail server/gateway and/or
> MAPI
> service provider are you using? Exchange Server using the Internet Mail
> Connector?  Outlook with the POP3/SMTP IMEP provider installed locally?
> 
> Also -- how are you creating the application/edi using MAPI? Creating a
> MAPI
> message with a single attachment and no body?
> 
> 
> -----Original Message-----
> From: John Hitchins [mailto:jhitchins@xxxxxxxxxxxxxxx]
> Sent: Tuesday, November 10, 1998 9:13 AM
> To: 'CNet EDIPilot'; 'IETF EDIINT'
> 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.