Home Library Learn Samples Downloads Support Community Forums
MSDN Library
Open Specifications
Standards
Microsoft Exchange Server and Outlook Standards
[MS-STANOIMAP]: Outlook Internet Message Access Protocol (IMAP) Standards Support
2 Standards Support Statements
2.2 Clarifications
2.2.1 [RFC3501] Section 2.2.1, Client Protocol Sender and Server Protocol Receiver
2.2.2 [RFC3501] Section 2.2.2, Server Protocol Sender and Client Protocol Receiver
2.2.3 [RFC3501] Section 2.3, Message Attributes
2.2.4 [RFC3501] Section 2.3.1.1, Unique Identifier (UID) Message Attribute
2.2.5 [RFC3501] Section 2.3.2, Flags Message Attribute
2.2.6 [RFC3501] Section 2.3.3, Internal Date Message Attribute
2.2.7 [RFC3501] Section 2.3.4, [RFC2822] Size Message Attribute
2.2.8 [RFC3501] Section 2.3.5, Envelope Structure Message Attribute
2.2.9 [RFC3501] Section 2.3.6, Body Structure Message Attribute
2.2.10 [RFC3501] Section 2.4, Message Texts
2.2.11 [RFC3501] Section 3.4, Logout State
2.2.12 [RFC3501] Section 4.3, String
2.2.13 [RFC3501] Section 4.3.1, 8-bit and Binary Strings
2.2.14 [RFC3501] Section 5.1, Mailbox Naming
2.2.15 [RFC3501] Section 5.1.2, Mailbox Namespace Naming Convention
2.2.16 [RFC3501] Section 5.2, Mailbox Size and Message Status Updates
2.2.17 [RFC3501] Section 5.3, Response When No Command in Progress
2.2.18 [RFC3501] Section 5.4, Autologout Timer
2.2.19 [RFC3501] Section 5.5, Multiple Commands in Progress
2.2.20 [RFC3501] Section 6.1.1, CAPABILITY Command
2.2.21 [RFC3501] Section 6.1.2, NOOP Command
2.2.22 [RFC3501] Section 6.2, Access Without Establishing Authentication
2.2.23 [RFC3501] Section 6.2.2, AUTHENTICATE Command
2.2.24 [RFC3501] Section 6.2.3, LOGIN Command
2.2.25 [RFC3501] Section 6.3.1, SELECT Command
2.2.26 [RFC3501] Section 6.3.2, EXAMINE Command
2.2.27 [RFC3501] Section 6.3.8, LIST Command
2.2.28 [RFC3501] Section 6.3.9, LSUB Command
2.2.29 [RFC3501] Section 6.3.10, STATUS Command
2.2.30 [RFC3501] Section 6.3.11, APPEND Command
2.2.31 [RFC3501] Section 6.4.1, CHECK Command
2.2.32 [RFC3501] Section 6.4.2, CLOSE Command
2.2.33 [RFC3501] Section 6.4.4, SEARCH Command
2.2.34 [RFC3501] Section 6.4.5, FETCH Command
2.2.35 [RFC3501] Section 6.4.6, STORE Command
2.2.36 [RFC3501] Section 6.4.7, COPY Command
2.2.37 [RFC3501] Section 6.4.8, UID Command
2.2.38 [RFC3501] Section 6.5, Client Commands ? Experimental/Expansion
2.2.39 [RFC3501] Section 7, Server Responses
2.2.40 [RFC3501] Section 7.1, Server Responses — Status Responses
2.2.41 [RFC3501] Section 7.1.1, OK Response
2.2.42 [RFC3501] Section 7.1.5, BYE Response
2.2.43 [RFC3501] Section 7.2.1, CAPABILITY Response
2.2.44 [RFC3501] Section 7.2.2, LIST Response
2.2.45 [RFC3501] Section 7.2.5, SEARCH Response
2.2.46 [RFC3501] Section 7.2.6, FLAGS Response
2.2.47 [RFC3501] Section 7.3.2, RECENT Response
2.2.48 [RFC3501] Section 7.4.2, FETCH Response
2.2.49 [RFC3501] Section 11.1, STARTTLS Security Considerations
Expand Minimize
This topic has not yet been rated - Rate this topic

2.2.34 [RFC3501] Section 6.4.5, FETCH Command

V0052:

The specification states: "There are three macros which specify commonly-used sets of data items, and can be used instead of data items."

Microsoft Office Outlook 2007, Microsoft Outlook 2010, Microsoft Outlook 2013

Outlook does not use these macros.

V0053:

The specification defines BODY[<section>] <<partial>> as one of the data items that can be fetched.

Office Outlook 2007, Outlook 2010, Outlook 2013

Outlook does not issue a FETCH command with the BODY[<section>] <<partial>> data item. The data items that Outlook can fetch are specified in V0054 and V0055 in this section.

V0054:

The specification defines BODY.PEEK[<section>] <<partial>> as one of the data items that can be fetched, where <section> is a set of zero or more part specifiers delimited by periods. The specification defines a part specifier as either a part number or one of the following: HEADER, HEADER.FIELDS, HEADER.FIELDS.NOT, MIME, and TEXT.

Office Outlook 2007, Outlook 2010, Outlook 2013

Outlook uses either the HEADER part specifier or zero part specifiers; Outlook does not use a part number and does not use <partial>. Therefore, the BODY.PEEK data item has the following forms in an Outlook fetch:

  • BODY.PEEK[]

  • BODY.PEEK[HEADER]

V0055:

The specification defines data items that can be fetched.

Office Outlook 2007, Outlook 2010, Outlook 2013

Outlook issues a FETCH command with data items as follows. For more details about the BODY.PEEK data item, see V0054 in this section.

To all servers:

  • (UID)

  • (UID FLAGS)

Only to IMAP4 servers that do not send "IMAP4rev1" as a listed capability in a CAPABILITY response as specified in [RFC3501] section 6.1.1:

  • (UID FLAGS RFC822.SIZE RFC822.HEADER INTERNALDATE)

  • (UID FLAGS RFC822)

  • (UID FLAGS RFC822.SIZE RFC822.HEADER)

  • (UID FLAGS RFC822.PEEK)

Note:  The RFC822.PEEK data item was obsoleted by [RFC2060]. However, Outlook still uses the RFC822.PEEK data item, as specified here.

Only to IMAP4 servers that send "IMAP4rev1" as a listed capability in a CAPABILITY response:

  • (UID FLAGS RFC822.SIZE BODY.PEEK[HEADER] INTERNALDATE)

  • (UID FLAGS BODY.PEEK[])

  • (UID FLAGS RFC822.SIZE BODY.PEEK[HEADER])

  • (UID FLAGS BODY.PEEK[])

Did you find this helpful?
(1500 characters remaining)
© 2013 Microsoft. All rights reserved.
|
Site Feedback
© 2013 Microsoft. All rights reserved.