Additional Notes About Microsoft Mail for PC Networks, Versions 3.5 Japanese Edition
Rev.2      2000/1/13

This document contains information Installing Microsoft Mail for PC Networks 
update for Y2K.

STEP TO INSTALL
================

Download the compressed update file for your specific issue. 
Select the appropriate files as indicated by the following list:
		
		Administrator program 			ADMY2K.EXE
		Directory Synchronization components 	DIRSY2K.EXE
		External program			EXTY2K.EXE
		FAX Gateway program			FAXGY2K.EXE
		
1.  Download appropriate file to a temporary location on the servers local hard 
    drive.
2.  Unzip the file by typing the file name of the self-extracting archive
    at the command prompt with the -d option.
    Example: The command to extract the External update is EXTY2K -d.
3.  To update ensure that the Microsoft Mail component to be updated is not running. 
4.  Rename the current file's extension (EXE or OVL) to BAK and replace with the 
    updated version. 
5.  Restart the Microsoft Mail component.

NOTE: The EXTERNAL.EXE and *.OVL files typically reside on the
postoffice server in the Mail executables directory, as well as on
the machine transferring messages to and from the database. Make
sure you update all copies of the EXTERNAL.EXE and *.OVL files.

The DIRSY2K.EXE and EXTY2K.EXE contains the component updates for the DOS and NT MMTA.

STEP TO INSTALL
==============

Download the compressed update file for your specific issue. 
Select the appropriate files as indicated by the following list:
		
		DOS & Windows Remote client		REMCY2K.EXE
		
1.  Download the file to a temporary location on the servers local hard 
    drive.
2.  Unzip the file by typing the file name of the self-extracting archive
    at the command prompt with the -d option.
    Example: The command to extract the Remote client update is REMCY2K -d.
3.  To update ensure that the Microsoft Mail Remote client is not running. 
4.  Rename the current file's extension (EXE or DLL) to BAK and replace with the 
    updated version.  


Note: Use the Jxxxxxx number to query the Microsoft Knowledge Base for an 
article about that bug.

Article ID:
J046004(Q191886): Y2K: Reqmain.exe Displays the Incorrect Date after 1999
J046005(Q191887): Y2K: Srvmain.exe Displays Incorrect Date after 1999
J046006(Q191888): Y2K: Dispatch Incorrectly Displays Year
J046007(Q191889): Y2K: Rebuild.exe Displays Incorrect Date after 1999
J046008(Q191905): Y2K: Key Dirsync Logs Display Incorrect Date after 1999
J046009(Q191907): Y2K: Import.exe Displays Incorrect Date after 1999
J046010(Q191942): Y2K: External.exe Displays Dates Incorrectly after 1999
J046011(Q191943): Y2K: Seconds in Time Field Incorrect after 1999
J046012(Q192156): Y2K: NTMMTA Incorrectly Logs Dates after 1999
J046013(Q192158): Y2K: NTMMTA Dirsync Process Incorrectly Logs Dates Beyond 1999
J046014(Q192239): Postmaster Messages Display Incorrect Date After 2000
J046015(Q192242): Admin Print Functions after Year 2000 Show Incorrect Date Format
J046016(Q192243): Administrator Program Incorrectly Displays Date After Year 2000
J046017(Q191962): FAX: Problems Configuring Gateway to Stop in Year 2000 or Later
J051994(Q192238): Windows Remote Client May Display Date Incorrectly After 2000

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT 
WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, 
INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN 
NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES 
WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS 
PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN 
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR
LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING 
LIMITATION MAY NOT APPLY. 

©1996 Microsoft Corporation