                  ==================================
                  X400GATE.EXE VERSION 3.2.14 UPDATE
                  ==================================

ARTICLE-ID:Q107445

The information in this article applies to version 3.2 of the Microsoft
Mail Gateway to X.400.

This update includes the following files:

      X400GATE.EXE (515,348 bytes, dated 02/09/95,   2:18 P.M.)
      README.TXT    (10,237 bytes, dated 10/28/94,  8:30 P.M.)
      XREAD.TXT (this file)

---------------------------------------------------------------------
| INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY    |
| ACCOMPANY THIS DOCUMENT (collectively referred to as a Microsoft   |
| Software Library [MSL] file) IS PROVIDED "AS IS" WITHOUT WARRANTY  |
| OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT        |
| LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR        |
| FITNESS FOR A PARTICULAR PURPOSE. The user assumes the entire risk |
| as to the accuracy and the use of this MSL file. This MSL file     |
| may be copied and distributed subject to the following conditions: |
| 1) All text must be copied without modification and all pages must |
| be included; 2) If software is included, all files must be copied  |
| without modification; 3) All components of this MSL file must be   |
| distributed together; and 4) This MSL file may not be distributed  |
| for profit.                                                        |
|                                                                    |
| Copyright 1993-1995 Microsoft Corporation. All Rights Reserved.    |
| Microsoft is a registered trademark of Microsoft Corporation.      |
 --------------------------------------------------------------------

SUMMARY
=======

Microsoft provides a replacement for the X400GATE.EXE file that is included
with version 3.2 of Microsoft Mail Gateway to X.400. The replacement file
corrects a number of problems in the original X400GATE.EXE file.

For complete information about obtaining and installing the X400GATE.EXE
file, see the "To replace your X.400 executable files" section at the end
of this article.

MORE INFORMATION
================

This replacement file corrects the following problems:

 - Characters with diacritical marks (accents) are improperly encoded.

 - The encoded information type (EIT) for ISO-6937 is improperly
   encoded.

 - The gateway does not update the RECV.LOG file for messages received
   by the gateway.

 - The gateway hangs if the subject line contains enough spaces (ASCII
   32D or 20H) after the subject text to cause the total length to be
   74 or more characters.

 - The gateway hangs if a user forwards or replies to a message that
   was previously returned by the X.400 gateway (usually because of a
   bad address). This forward or reply message adds characters to the
   subject line, changing the total length to 74 or more characters,
   with spaces in the seventy-fourth and following positions.

 - The gateway tp4 stack incorrectly replies to a recovery packet and
   displays "ERROR: Pconnect..."

 - The gateway hangs after it processes two messages that have large
   distribution lists.

 - The gateway generates an "ERROR 58" message when it transmits mail
   or attachments to an ISODE Openpath user, even though the user
   successfully receives the message.

 - The gateway generates invalid minor synchronization points, causing
   an "ERROR 3." If debug mode is used, the error "DEBUG (tp4_recv):
   connection x: tp_receive() failed" occurs.

 - The gateway begins to create nondelivery reports. If the External
   Mail program tries to deliver these reports, the following error
   occurs in the SYSTEM.LOG file: "Message was not delivered: routing
   file was corrupted."

 - The gateway generates a free-form name longer than the 64 character
   limit specified in NIST, causing the message to be rejected by the
   receiving message transfer agent (MTA).

 - The gateway runs out of memory when you use ISO6937 as message body
   text. The gateway then misplaces subsequent messages, reporting the
   error "ERROR 3 (AttachP2): ISO6937 conversion failed."

 - If the gateway is configured to use a checkpoint size of 10, it may
   display the error "DEBUG (T4 SEND): CONNECTION 32: TP SEND() FAILED: 3."
   It then will not process any more messages.

 - If a large (4000 or more names) custom address map exists, the gateway
   may process messages slowly.

 - Read receipts and delivery notifications may be sent to the incorrect
   address by Softswitch EMX if the unique identifier the Microsoft Mail
   Gateway to X.400 places on each message is not unique.

To replace your X.400 executable files
--------------------------------------

At the MS-DOS command prompt, type the following and press ENTER

   copy <path>\x400gate.exe <destination>

where <path> is the drive and directory where you ran the self-extracting
X400GA.EXE file and <destination> is the drive and directory where your
X.400 executable files currently reside. For example, if the X.400
executable files are located in the MAILEXE directory on drive C and you
ran the self-extracting file from the TEST directory on drive D, type the
following command:

   copy d:\test\x400gate.exe c:\mailexe

NOTE: The X400GATE.EXE file typically resides on the postoffice server in
the Mail executables directory as well as on the machine where the gateway
is running. Make sure all copies are updated appropriately.
