An attachment may not appear in Outlook Web Access when you use a MAPI client or a MTA to forward an e-mail message that has an attachment in Exchange Server 2003 (899964)



The information in this article applies to:

  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange Server 2003 Enterprise Edition

SYMPTOMS

Consider the following scenario. You receive a new e-mail message from the Internet. This e-mail message is from a non-MAPI client in Microsoft Exchange Server 2003. You use one of the following methods to forward this e-mail message that has an attachment to a Microsoft Exchange Server user:
  • You use a MAPI client to forward the e-mail message.
  • You use a Message Transfer Agent (MTA) to forward the e-mail message.
In this scenario, the attachment may no longer appear in Microsoft Outlook Web Access (OWA). However, the MAPI client can still see this attachment. Additionally, the value in the Content-Type field changes from multipart/mixed to multipart/related in the e-mail message. This behavior occurs because the e-mail message was changed to native MAPI, and then back to Internet format.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Exchange Server 2003.

For more information about Exchange Server 2003, 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

Note The fix works only for messages received through the SMTP protocol because the fix is implemented in the Microsoft Exchange transport layer.

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, we recommend that you wait for the next Microsoft 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 telephone numbers and information about support costs, visit the following Microsoft Web site: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 hotfix requires Microsoft Exchange Server 2003 Service Pack 1 (SP1).

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

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 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
   -------------------------------------------------------
   13-Sep-2005  05:37  6.5.7233.48   3,270,144  Mdbmsg.dll       
   04-Jun-2005  01:56                    3,304  Redir.asp
   13-Sep-2005  06:11  6.5.7233.48   5,182,464  Store.exe
        

WORKAROUND

The fix does not work if the e-mail message uses a MTA. To work around the MTA issue, use a SMTP bridgehead server to send the e-mail message.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Microsoft Exchange Server 2003 Service Pack 2.

Modification Type:MinorLast Reviewed:7/25/2006
Keywords:kbexchSTORE kbQFE kbfix kbBug kbpubtypekc KB899964 kbAudITPRO