Update to permit the caching of incoming SMTP messages as IPM.Note in Exchange Server 2003

Article translations Article translations
Article ID: 832492 - View products that this article applies to.
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
Expand all | Collapse all

On This Page

Summary

When you send Simple Mail Transfer Protocol (SMTP) mail to a Microsoft Exchange 2000 Server or a Microsoft Exchange Server 2003 public folder, the message class is IPM.Post. In Microsoft Exchange Server 5.5, the message class of a message that is sent to a public folder is IPM.Note. Therefore, if you have a message-archiving system where the e-mail messages must be stored without being changed or converted, you may not be able to archive messages from the public folder. This article describes an update that you can use to configure the setting of the PR_MESSAGE_CLASS attribute of SMTP messages that are sent to public folders as IPM.Note instead of as IPM.Post.

Note "SMTP mail" refers to mail that is not from a MAPI source.

More information

Cumulative rollup information

To resolve this problem, obtain the Exchange 2003 Server Post-RTM store rollup. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
838236 How to obtain the Exchange Server 2003 Server post-RTM Store rollup

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart your computer after you apply this software update.

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 file attributes) 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
---------------------------------------------------------
15-Nov-2003  02:02  6.5.6980.42      49,152  Mdbevent.dll     
15-Nov-2003  02:41  6.5.6980.42   3,186,176  Mdbmsg.dll       
15-Nov-2003  02:05  6.5.6980.42      24,064  Mdbrole.dll      
17-Nov-2003  17:16  6.5.6980.42      13,312  Mdbtask.dll      
17-Nov-2003  17:15  6.5.6980.42   5,038,592  Store.exe        

Hotfix installation information

After you install this update, the message class of incoming messages to public folders may be changed to IPM.Note (instead of IPM.Post). You can configure this new setting by creating the "Incoming defaults to IPM.Note" registry value.

To have us create the "Incoming defaults to IPM.Note" registry value for you, go to the "Fix it for me" section. To create the "Incoming defaults to IPM.Note" registry value yourself, go to the "Let me fix it myself" section.

Fix it for me

To set the "Incoming defaults to IPM.Note" registry value automatically, click the Fix it button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.
Collapse this imageExpand this image
assets fixit1
Fix this problem
Microsoft Fix it 50335
Collapse this imageExpand this image
assets fixit2

Note this wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note if you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Let me fix it myself

To create the "Incoming defaults to IPM.Note" registry value yourself, in the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\<ServerName>\Public-<GUID>

Value name: Incoming defaults to IPM.Note
Value type: DWORD
Value data: 0 or 1 (0 is default value) (0=false)
Important This value name is case-sensitive. The default behavior without the registry key is that incoming messages appear as IPM.Post. If you set the registry value to 0 (zero), the default behavior continues, and incoming messages appear as IPM.Post. If you set the registry value to 1, the behavior changes, and new SMTP mail messages from a non-MAPI source appear as IPM.Note.

To enable this functionality, you must configure these registry settings on all Exchange servers that host public folders. You do not have to configure these registry settings on Exchange servers that do not host public folders. Additionally, you must configure these registry settings for each public folder database on the particular server where you want to enable this functionality.

After you make these registry changes, you must restart the Microsoft Exchange Information Store service to enable this new functionality.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More information

For more information about terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
817903 New naming schema for Exchange Server software update packages

Properties

Article ID: 832492 - Last Review: September 18, 2013 - Revision: 9.0
Applies to
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange Server 2003 Enterprise Edition
Keywords: 
kbmsifixme kbfixme kbautohotfix kbqfe kbhotfixserver kbfix kbbug kbexchange2003presp1fix KB832492

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com