XADM: IMAP4 Front-End Servers Drop the Connection to IMAP4 Clients (306140)



The information in this article applies to:

  • Microsoft Exchange 2000 Server

This article was previously published under Q306140

SYMPTOMS

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.

CAUSE

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.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

Component: IMAP4

File nameVersion
Imap4fe.dll6.0.4720.43

NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

Modification Type:MinorLast Reviewed:10/6/2005
Keywords:kbbug kbExchange2000preSP2fix kbfix kbQFE KB306140