Article ID: 306140 - View products that this article applies to.
This article was previously published under Q306140
This article has been archived. It is offered "as is" and will no longer be updated.
When an Internet Message Access Protocol, Version 4rev1 (IMAP4) client requests header information for a large number of messages, the IMAP4 front-end servers may drop the connection to the IMAP4 client.
This problem can occur if the IMAP4 frond-end server is unable to handle certain packets that the back-end server sends in response to IMAP4 requests from clients that want to download header information for messages that are stored on the server. If the IMAP4 frond-end server is unable to handle the packets, the front-end server drops the connection to the client.
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.
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, submit a request to 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. The English version of this fix should have the following file attributes or later:
Collapse this tableExpand this table
NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.