XIMS: FETCH Command Cannot Contain More Than Five Body Arguments (225142)
The information in this article applies to:
- Microsoft Commercial Internet System 2.0
This article was previously published under Q225142 SYMPTOMS
If an Internet Message Access Protocol version 4 (IMAP4) client sends a FETCH command with more than five instances of the BODY argument, the server may indicate that the command is invalid. In particular, the problem is known to occur when an IMAP4 client attempts to retrieve a message that contains four or more attachments using the FETCH command. For example, the client may send a command similar to the following:
. uid fetch 1 (BODY[HEADER] BODY[1.MIME] BODY[2.MIME] BODY[2.HEADER] BODY[3.MIME] BODY[3.HEADER] BODY[3.1.MIME] BODY[3.2.MIME])
The server returns the following response:
. BAD UID FETCH Fetch attribute.
Note that the problem occurs regardless of the specific body sections that are specified in the BODY arguments. The problem is not client-specific, but it is known to occur with Netscape Messenger version 4.5 and Microsoft Outlook Express.
CAUSE
The IMAP4 service does not allow FETCH commands to contain more than five instances of the BODY argument.
RESOLUTIONA 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. To resolve this problem, 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 usual 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 Service
STATUSMicrosoft has confirmed that this is a problem in Microsoft Commercial Internet System version 2.0.
| Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbfix kbQFE KB225142 |
|---|
|