Numer ID artykułu: 891850 - Zobacz jakich produktów dotyczą zawarte w tym artykule porady.
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:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows registry
When you send an encrypted message from Louts Notes to Microsoft Exchange Server 2003 by using Exchange Connector for Lotus Notes, Exchange 2003 does not send a second non-delivery report (NDR) for the encrypted message. Typically, this problem occurs when the auto-forward feature is configured for the Lotus Notes client.
Exchange 2003 cannot parse messages that are encrypted by Lotus Notes. Therefore, Exchange 2003 sends an NDR to the Lotus Notes client. If the auto-forward feature is configured for the Lotus Notes client, the NDR is returned to Exchange 2003. If Exchange 2003 sends a second NDR in response to the returned NDR, a message loop occurs between Exchange 2003 and the Lotus Notes client.
To avoid this message loop, Exchange 2003 does not send a second NDR. However, if Exchange 2003 does not send a second NDR, the encrypted message that generated the first NDR is lost.
Service pack informationTo resolve this problem, obtain the latest service pack for Exchange Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/836993/EN-US/ )How to obtain the latest service packs for Exchange Server 2003
Hotfix informationWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
After you install the hotfix that is described in this section, you must create the DropBadMailIfNotNDR registry entry. If the DropBadMailIfNotNDR value is set to 1, Exchange 2003 routes the NDR to the Exchange.Bad folder of the Lotus Notes server. Depending on the number of NDRs and the size of the NDRs, the hard disk volume of the Lotus Notes server may be affected. You must regularly examine the Exchange.Bad folder and the hard disk volume.
To create and to enable the DropBadMailIfNotNDR registry entry, follow these steps:
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=supportNote 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.
File informationThe 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 --------------------------------------------------------- 27-Jan-2005 21:03 6.5.7232.74 41,984 Lsntsmex.exe
PrerequisitesBecause of file dependencies, this hotfix requires Exchange 2003 Service Pack 1 (SP1). For more information about how to obtain the latest Exchange 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/836993/ )How to obtain the latest service packs for Exchange Server 2003
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 Exchange Server 2003 Service Pack 2.
Microsoft continues to update the tools that support interoperability among Lotus Domino R5 and Lotus Domino 6, Microsoft Exchange Server 2003, and Microsoft Windows Server 2003 Active Directory. The updated tools for Lotus Domino replace the following tools that are included with Exchange Server 2003 and with Microsoft Exchange Server 2003 Service Pack 2:
http://technet.microsoft.com/en-us/interopmigration/bb403105.aspxThese updated tools provide additional functionality and address several issues that customers reported with earlier versions of the tools.
For more information about the terminology that Microsoft uses for software that is corrected after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684For more information about the naming schema for Exchange Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
817903The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
(http://support.microsoft.com/kb/817903/ )New naming schema for Exchange Server software update packages
Numer ID artykułu: 891850 - Ostatnia weryfikacja: 5 listopada 2007 - Weryfikacja: 5.4
Contact us for more help