Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
XFOR: Connector for cc:Mail Cannot Route Mail with Message Headers Larger Than 4 KB
Article ID: 266711 - View products that this article applies to.
This article was previously published under Q266711
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:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
A message that contains a message header that is larger than 4 kilobytes (KB), or 4,096 bytes, is returned by the Microsoft Exchange Connector for Lotus cc:Mail with a non-delivery report (NDR).
The Lotus cc:Mail Import/Export utility version 8.2x and earlier limits message headers to 4 KB (4,096 bytes). The Connector for cc:Mail uses the Import/Export utility to process messages and adheres to this limitation.
To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/191014/EN-US/ )XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.
With the Lotus cc:Mail Import/Export utility version 8.2x and later, the message header limit is raised to 160 KB (163,840 bytes).
To make the Connector for cc:Mail recognize the new message header limitation, you must perform the following steps.
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.
Article ID: 266711 - Last Review: October 26, 2006 - Revision: 3.1