![](/file/18315/Y2K_Resource_Nov99.iso/webcon~1/usa/year2k/images/spacer.gif)
Microsoft Year 2000 Readiness Disclosure & Resource Center |
![](/file/18315/Y2K_Resource_Nov99.iso/webcon~1/usa/year2k/images/spacer.gif) |
![](/file/18315/Y2K_Resource_Nov99.iso/webcon~1/usa/year2k/images/spacer.gif) |
![](/file/18315/Y2K_Resource_Nov99.iso/webcon~1/usa/year2k/images/spacer.gif) | Microsoft Mail for PC Networks 3.5 (Swedish) - DOS
Product Summary |
Product: Microsoft Mail for PC Networks Version: 3.5 |
Category: Compliant* Operating System: DOS |
Language: Swedish |
Release Date: 09 Jun 1995 |
Operational Range: |
01 Jan 1970 - 31 Dec 2035 |
Prerequisites: |
Year 2000 product software updates identified below |
Product Dependencies: |
Windows NT 3.51, MS-DOS 6.22 |
Clock Dependencies: |
Windows NT System clock, PC BIOS |
Last Updated: |
03 Jun 1999 | |
Product Details |
This document is applicable to Microsoft Mail for PC Networks components, Win Mail Client 3.5, Remote Mail Client 3.2.
** Microsoft Mail for PC Networks itself operates within a range of January 1, 1970 - February 5, 2035. In many cases Microsoft Mail will operate in ranges that extend beyond these parameters, however when using Microsoft Schedule+ 1.0 or the Novell MHS gateway, the date range is January 1, 1970 û December 31, 2019.
This document covers the Microsoft Mail for PC Networks components and discusses how to resolve the known Year 2000 issues. This document covers products that are directly included with the Microsoft Mail product, or related components that can be added or purchased separately. These components combined together are referred to as Microsoft Mail or Microsoft Mail for PC Networks. There are individual components that may be called out specifically in order to give more details on how they use dates or how some features should be tested. The document is specific to the Swedish versions of specific components. Additional components that were not localized are covered in the English documentation for MS Mail for PC Networks.
What are the prerequisites? Microsoft Mail 3.5 has no known issues when using it with the provided Year 2000 product software updates.
The Microsoft Mail Year 2000 product software updates for the client and server are on: ftp://ftp.microsoft.com/bussys/mail/pcmail-public/swe/all-y2k
To resolve known issues with Microsoft Mail 3.5, software updates need to be applied in two main areas: 1. Microsoft Mail 3.5 server, 2. Windows Remote Mail Client 3.2 These component software updates are only required if the component is used by the customer. For instance, if the customerÆs mail environment does not include the Windows Remote Mail Client then this specific software update would not be needed.
This is a list of the components and their executable names that have product software updates:
Microsoft Mail 3.5 components:
Administrator program ADMY2K.EXE
Directory Synchronization components DIRSY2K.EXE
External program EXTY2K.EXE
Microsoft Mail Windows Remote 3.2 client:
Windows Remote client REMCY2K.EXE
The set of instructions for installing the Microsoft Mail client and server components can be found at: ftp://ftp.microsoft.com/bussys/mail/pcmail-public/swe/all-y2k/Readmeus.txt
The following Knowledge Base articles provide a summary of each known year 2000 issue that were updated in the Microsoft Mail 3.5 components.
Note: These Knowledge Base articles are available at http://support.microsoft.com/support/c.asp
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
Q192156: Y2K: NTMMTA Incorrectly Logs Dates after 1999
Q192158: Y2K: NTMMTA Dirsync Process Incorrectly Logs Dates Beyond 1999
Q192199: DOS Remote Client Displays Year 100 on or after Year 2000
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
Q191962: FAX: Problems Configuring Gateway to Stop in Year 2000 or Later
Q192084: X400: Incorrect Date on Message Sent Through X.400 Gateway
Q192085: MHS: Incorrect Date Recorded in Sent.log and Recv.log Files
What was tested with Microsoft Mail 3.5?
Listed below are the gateways and clients that were tested with Microsoft Mail for PC Networks 3.5. Also listed is the version that was tested.
- Mail Gateway 3.0 for MS-DOS Swedish 3.5 Fax Gateway
- Mail Gateway 3.0 for MS-DOS Swedish 3.5 FAX Access
- Mail Gateway 3.0 for MS-DOS Swedish 3.5 MHS Gateway
- Mail Gateway 3.0 for MS-DOS Swedish 3.5 MHS Access
- Mail Gateway 3.0 for MS-DOS Swedish 3.5 SMTP Gateway
- Mail Gateway 3.0 for MS-DOS Swedish 3.5 SMTP Access
- Mail Gateway 3.2 for MS-DOS Swedish 3.5 X400 Gateway
- Mail Gateway 3.2 for MS-DOS Swedish 3.5 X400 Access
- Mail Client 3.5 Swedish on MS-DOS 6.22, Windows 3.11, Windows NT 3.51
- Mail Remote 3.2 Swedish on MS-DOS 6.22, Windows 3.11
- Schedule + 1.0 for Windows Swedish 3.5
- In addition, the following clients were tested with the Microsoft Mail service provider on Windows 95
- Windows Inbox
- Exchange Client 5.0
- Outlook 97
- Outlook 98
- Schedule+ 7 and higher
- MMF Clean Utility
- Tested Microsoft Mail 3.5 Post Office and components on Netware Year 2000 compliant networks
What was not tested with Microsoft Mail 3.5?
- 3COM gateway
- ATT gateway
- MCI gateway
- SNADS gateway
- PROFS gateway
- Resource Kit tools
- Internal Microsoft utilities
- Microsoft Mail Server for Macintosh
- Macintosh clients
Two-digit shortcut handling:
There are some components within Microsoft Mail 3.5 that store dates in 2 digits. For these cases any date that has the value 50-99 are interpreted as 1950-1999. Values that are 00-49 are interpreted as 2000-2049. This is also the case when mail comes from other mail systems that only store dates with 2 digits.
Does 2-digit shortcut handling workaround everything?
No. There are currently two known products that do not handle 2-digit dates as expected. Microsoft Schedule+ 1.0 supports a date range of 1920 to 2018. Dates within this range work as expected; dates that extend past December 31, 2018 will be handled as 1900 dates. For instance the year 2020, would become 1920. This is also true for the Novell MHS gateway. The Novell MHS gateway only supports dates through the end of 2018.
Common date usage errors:
Microsoft Mail 3.5 supports Internet (SMTP) and X.400 standards with these respective gateways. These gateways provide connectivity with other vendorsÆ messaging systems. In doing so, Microsoft has had to adapt Microsoft Mail 3.5 to convert any 2-digit dates received from and/or expected by those non-Microsoft systems. Microsoft cannot assure customers of the accuracy of a non-Microsoft receiving environment or the reliability of the date data being passed to Microsoft Mail 3.5.
Testing guidelines and recommendations:
Setup a test environment that simulates the customer Microsoft Mail 3.5 topology. When this is setup, change the system time on servers to be December 31, 1999. Then start sending messages and let the date roll over to January 1, 2000. Use any applications that may have been written to use the Microsoft Mail 3.5 environment. These are any workflow, collaboration, etc., applications that the company uses to run their business. Microsoft recommends that the customer roll the date forward to various dates in the range 12/31/1999 to 12/31/2018 and test many different scenarios. | |
Return to Search Screen
Legend of Symbols: |
* |
The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document. |
# |
The product is compliant with an acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product. |
+ |
The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details. |
Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
If after reviewing this information you have additional questions related to this product, click here.
YEAR 2000 READINESS DISCLOSURE
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT 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 TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.
ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|