Additional Notes About Microsoft Mail for PC Networks, Versions 3.2. 3.2a, 3.5 This document contains information not available in the Microsoft Mail PC for Networks documentation, as well as information on changes that occurred after publication. If you enlarge the Write window to its maximum size, this document will be easier to read. To do so, click the Maximize button in the upper-right corner of the window. To move through the document, press PAGE UP or PAGE DOWN, or click the scroll bar along the right side of the Write window. To print the document, choose Print from the File menu. For Help on using Write, press F1. Installing Microsoft Microsoft Mail for PC Networks update for Y2K issues. SERVER COMPONENTS: STEPS 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 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 OS/2 MMTA. REMOTE CLIENT: STEPS TO INSTALL =============================== Download the compressed update file for your specific issue. Select the appropriate files as indicated by the following list: 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 Qxxxxxx number to query the Microsoft Knowledge Base for an article about that bug. Article ID: Q191886: Y2K: Reqmain.exe Displays the Incorrect Date after 1999 Q191887: Y2K: Srvmain.exe Displays Incorrect Date after 1999 Q191888: Y2K: Dispatch Incorrectly Displays Year Q191889: Y2K: Rebuild.exe Displays Incorrect Date after 1999 Q191905: Y2K: Key Dirsync Logs Display Incorrect Date after 1999 Q191907: Y2K: Import.exe Displays Incorrect Date after 1999 Q191942: Y2K: External.exe Displays Dates Incorrectly after 1999 Q191943: Y2K: Seconds in Time Field Incorrect after 1999 Q192238: Windows Remote Client May Display Date Incorrectly After 2000 Q192239: Postmaster Messages Display Incorrect Date After 2000 Q192240: Remote MS-DOS Client May Sort Incorrectly After Year 2000 Q192241: DOS Remote Mail Incorrectly Changes Date/Time after Year 2000 Q192242: Admin Print Functions after Year 2000 Show Incorrect Date Format Q192243: Administrator Program Incorrectly Displays Date After Year 2000 Q197407: Dirsync Events Not Scheduled Properly in Year 2000 Non-Y2K (previous fixes included in updated files): Q135487: PC Ext: Running External and WAN Drives Q136004: PC Ext: Inaccurate Nondelivery Reports or Duplicate Mail Q136046: PC WRmt: Possible Misdirected Mail When Upgrading Address List Q147158: PC DirSync: Imports with Template Information Take Long Time Q147471: PC Ext: Remote Client Sets Hop Count to Ten Q148770: PC DirSync: IMPORT -S Hangs Computer During Dir-Sync Q165315: XFOR: MS Mail Remote Users not able to View Attachments Q194600: PC Ext: Some *SPECIAL Mssgs. Cause WinNT & OS/2 MMTAs to Fail Q194603: PC Ext: No Recipient Found while Building the Mailing List Q194733: PC Rmt: Attachments from MAC Clients Show Garbage File Names Q194734: PC WRmt: Echo and Display Commands do not Work in Remote Client Q194735: PC WRmt: Remote Mail Errors Using Custom Script Q194736: PC Adm: Admin Not Displaying X.400 Names Correctly in French Q194737: PC Adm: Admin Hangs When Listing Over 200 Postoffices Q194819: PC DirSync: Import Hangs when Processing Srvtrans.glb Q194849: PC Ext: External Fails when Run as an Idle Process of Dispatch Q194851: PC WRmt: Textborder Is Off in Remote Client Q194853: PC Rmt: Remote Mail Client Can’t Address Local FFAPI Gateway PO Q194857: PC Ext: Break Relative Param. Not Equal to Original Minutes Set 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