Microsoft KB Archive/829870

= Mail clients cannot access some PGP-encrypted messages after you upgrade from Exchange 2000 Server to Exchange Server 2003 =

Article ID: 829870

Article Last Modified on 10/25/2007

-

APPLIES TO


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

-



SYMPTOMS
After you upgrade a computer that is running Microsoft Exchange 2000 Server to Microsoft Exchange Server 2003, e-mail messages that were sent before the upgrade and that are encrypted with Pretty Good Privacy (PGP) encryption are no longer accessible.

When you try to open a PGP-encrypted message in Microsoft Outlook, you may receive the following error message:

Cannot open this item.

When you try to open a PGP-encrypted message in Microsoft Outlook Web Access (OWA), you may receive the following error message:

HTTP 500 - Internal Server Error

When you try to open a PGP-encrypted message in the Mdbvu32.exe utility, you may receive the following error message:

MAPI_E_NO_SUPPORT

If you move the mailbox that contains the PGP-encrypted e-mail back to an Exchange 2000 computer, you can access the message and you receive no error message.



CAUSE
This problem occurs because the Exchange 2003 Virus Scanning API returns a MAPI_E_NO_SUPPORT error and blocks access to a message that is encrypted with PGP encryption.



Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Exchange Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;[LN;CNTACTMS]

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
Because of file dependencies, this update requires Exchange 2003.

Restart requirement
You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other software updates.

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 --  29-Oct-2003  03:24  6.5.6980.38        49,152  Mdbevent.dll 29-Oct-2003 04:03  6.5.6980.38     3,186,176  Mdbmsg.dll 29-Oct-2003 03:27  6.5.6980.38        24,064  Mdbrole.dll 29-Oct-2003 17:35  6.5.6980.38        13,312  Mdbtask.dll 29-Oct-2003 17:34  6.5.6980.38     5,039,104  Store.exe



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



MORE INFORMATION
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

817903 New naming schema for Exchange Server software update packages

Additional query words: xadm VSAPI

Keywords: kbqfe kbhotfixserver kberrmsg kbexchangeowa kbfix kbbug kbexchange2003presp1fix KB829870

-

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

© Microsoft Corporation. All rights reserved.