XFOR: Incorrect Time Stamp on Messages Sent from NZDT Zone

Last reviewed: February 12, 1998
Article ID: Q178094
The information in this article applies to:
  • Microsoft Exchange Server, version 5.5
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

Internet mail sent from an Exchange Server computer located in the New Zealand time zone during Daylight Savings Time is received with an incorrect time stamp outside this time zone.

STATUS

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

New Zealand Daylight Savings Time (NZDT) is not a defined time zone. NZDT is actually +13 hours GMT. Time zone selections in Windows NT are displayed in + or - GMT with a maximum of +/-12 hours GMT.

A new registry entry labeled "NewTimeZones" has been added to the registry.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

Besides the hotfix mentioned above, the following key may be added as necessary to allow for non-defined time zones:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS
   \ParametersSystem\InternetContent

NOTE: The above registry key is one path; it has been wrapped for readability.

This value MUST be defined as REG_MULTI_SZ type. You can define any number of zone codes and associated time offsets. Each zone-offset string must be in the following format:

   ZZZZ;[+|-]hh:mm

where ZZZZ is the zone code (can be any # of characters, terminated by a
';'), hh is the hour offset (from GMT), and mm is the minute offset (from
GMT).
Keywords          : XFOR kbbug5.50
Version           : WINDOWS: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: February 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.