DOCUMENT:Q238020
TITLE   :XIMS: NNTP Service Converts Two-Digit Years Incorrectly
PRODUCT :IIS; MCIS
PROD/VER:4.0; 2.0
OPER/SYS:WINDOWS NT

-------------------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Commercial Internet System version 2.0 
 - Microsoft Internet Information Server version 4.0 
-------------------------------------------------------------------------------

SYMPTOMS
========

The Network News Transfer Protocol (NNTP) service may not properly convert
two-digit years to four digits. For example, if you specify the year 2000 using
"00", the service may convert the two-digit year to 1900 instead of 2000.

When a messaging client attempts to post a message to an NNTP server using a
two-digit year, the fact that the two-digit year is converted incorrectly may
cause an error message similar to the following to be displayed:

   441 (647) Article Rejected -- The Date in the date header is too old.

Microsoft is currently not aware of any messaging clients that post messages
using two-digit years.

RESOLUTION
==========

A supported software update that corrects this problem is now available from
Microsoft, but it has not been fully regression tested and should be applied
only to systems experiencing this specific problem. If you are not severely
affected by this specific problem, Microsoft recommends that you wait for the
next Microsoft Windows NT Server version 4.0 service pack that contains this
software update.

To resolve this problem immediately, contact Microsoft Product Support Services
to obtain the software update. For a complete list of Microsoft Product Support
Services phone numbers and information on support costs, please go to the
following address on the World Wide Web:

   http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this software update should have the following file
attributes or later:

Component: Mail Server

+---------------------------+
| File name   | Version     | 
+---------------------------+
| Nntpsvc.dll | 5.5.1877.29 | 
+---------------------------+

If you are running Windows NT 4.0 Service Pack 5 or Service Pack 4:

This software update has been posted to the following Internet location as
Q238020i.exe (x86) and Q238020a.exe (Alpha):

   ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/
   hotfixes-postSP5/Y2K/NNTP-fix/

To determine if a localized version of this software update is available, change
"USA" in the URL above to the appropriate localized abbreviation. Click here
(ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/readme.txt) for a list
of these abbreviations.

STATUS
======

Microsoft has confirmed this to be a problem in the Microsoft products listed at
the beginning of this article.

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

After you apply the software update, two-digit years are converted to four
digits according to the following table:

+----------------------------------+
| Two-digit year | Four-digit year | 
+----------------------------------+
| 00-49          | 2000-2049       | 
+----------------------------------+
| 50-99          | 1950-1999       | 
+----------------------------------+

For more information about how Microsoft products are affected by year 2000 (Y2K)
issues, please see the following Microsoft World Wide Web site:

   http://www.microsoft.com/year2000/

Additional query words: Y2K
============================================================================

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.