RE: Problems with Microsoft Exchange Ser

["Ghahremani, Joanne" <ghahrej@xxxxxxxxxxxxxxx>]

This might be a novel approach, but has any one asked Microsoft when they   
plan to fix their system
so that the problem doesn't occur? Joanne.

 -----Original Message-----
From: Carl Hage [SMTP:carl@xxxxxxxxx]
Sent: Wednesday, March 18, 1998 1:51 PM
To: edipilot; ietf-ediint
Subject: RE: Problems with Microsoft Exchange Ser

There may be a need to address escape mechanisms for noncompliant
email gateways in general.

I believe switching models to PKCS7 binary data is the wrong
approach. Instead a more general solution should be used, which
protects the content being exchanged.

The possible solutions that make sense to me are:

1. Wrap the whole RFC822 mesage in another MIME layer, where the
   original RFC822 headers begin on the first line of data. The
   MIME headers in the top level may either be omitted or specified
   as message/RFC822.

2. Strip the Content-Type: header from the RFC822 headers, and
   begin MIME content on the first line of the data.

Strategy 1 works with other data-corrupting gateways like ccMail,
which deletes RFC822 headers. I think this is the best approach.

These options would be enabled by a table of options maintained for
each TP. The TP agreement would supply thier email address and also
indicate a noncompliant gatway. Readers should be able to
automatically decode double wrapped MIME messages when they arrive.

By the way, does the MS-Exchange choke because of multipart signed,
but works with multipart/mixed?
 --------------------------------------------------------------------------  

Carl Hage                                              C. Hage Associates
<mailto:carl@xxxxxxxxx> Voice/Fax: 1-408-244-8410      1180 Reed Ave #51
<http://www.chage.com/chage/>                          Sunnyvale, CA   
94086