XFOR: Internet Mail Service Converts Two-Digit Years Incorrectly

 Last reviewed: March 5, 1998
Article ID: Q182040
The information in this article applies to:
  • Microsoft Exchange Server, versions 5.0 and 5.5

SYMPTOMS

When you receive a message that has a two-digit year field through the Internet Mail Service, the year may not be properly converted to four digits. This problem is not likely to occur before the year 2000.

CAUSE

The Internet Mail Service does not properly convert two-digit years to four digits for the year 2000.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

MORE INFORMATION

After you apply the fix described in the Status section of this article, the two-digit years convert to four digits according to the following table: 

   Two-digit year   Four-digit year
   --------------------------------
   00-49            2000-2049
   50-99            1950-1999
For additional information about date conversion problems with the Internet Mail Service, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q173491
   TITLE     : XFOR: Message to IMC via Telnet with Year 1900

Additional query words: imail y2k
Keywords : kbbug5.00 XFOR kbbug5.50
Version : WINDOWS:5.0,5.5
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbfix

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.

Last reviewed: March 5, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.