Microsoft KB Archive/839483

= Validation of cryptographic signatures does not complete correctly in a transport event sink on Exchange 2000 Server or on Exchange Server 2003 =

Article ID: 839483

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange 2000 Server Standard Edition

-



Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
In Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003, when you use the Microsoft Collaboration Data Objects for Microsoft Exchange Library (CDOEX) to configure a transport event sink that handles incoming e-mail messages and validates cryptographic signatures, validation of the cryptographic signatures does not complete correctly.



CAUSE
This problem occurs because when messages are handled in the transport event sink by CDOEX, the S/MIME content of the message is altered and the S/MIME validation of the cryptographic signature cannot complete correctly.



Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Exchange Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

836993 How to obtain the latest service packs for Exchange Server 2003

Hotfix information
To resolve this problem, obtain the August 2004 Exchange 2000 Server Post-Service Pack 3 update rollup.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

870540 Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3 update rollup

Prerequisites
Because of file dependencies, this update requires Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 How to obtain the latest Exchange 2000 Server service pack

File information
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version            Size    File name --     11-May-2004  12:23  6.0.6592.0      3,919,872  Cdoex.dll



MORE INFORMATION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

After you apply this hotfix, you must edit the registry and add the CDOHighFidelityInSinks value to the following registry subkey:

To add this registry value:  Click Start, click Run, type regedit, and then click OK. Expand the following subkey:

 Right-click Parameters, point to New, and then click DWORD Value. Type CDOHighFidelityInSinks, and then press ENTER to name the value. Right-click CDOHighFidelityInSinks, and then click Modify.</li> In the Value data box, type 00000001, and then click OK.</li> Close Registry Editor.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

This problem was first corrected in Microsoft Exchange Server 2003 Service Pack 2.

Keywords: kbqfe kbhotfixserver kbfix kbexchange2000presp4fix kbbug KB839483

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.