], as well as any .PEEK forms of these. Any partial fetch that attempts to read beyond the end of the text is truncated as appropriate. If the starting octet is beyond the end of the text, an empty string is returned. The data are returned with the FETCH response. There is no indication of the range of the partial data in this response. It is not possible to stream multiple PARTIAL commands of the same data item without processing and synchronizing at each step, since streamed commands may be executed out of order. There is no requirement that partial fetches follow any sequence. For example, if a partial fetch of octets 1 through 10000 breaks in an awkward place for BASE64 decoding, it is permitted to continue with a partial fetch of 9987 through 19987, etc. The handling of the \Seen flag is the same as in the associated FETCH command. Example: C: S: S: S: S: S: A005 PARTIAL 4 RFC822 1 1024 * 1 FETCH (RFC822 {1024} Return-Path: ... ......... FLAGS (\Seen)) A005 OK PARTIAL completed

6.4.5.OBS.1

Obsolete FETCH Data Items

The following FETCH data items are obsolete: BODY[<...>0] A body part number of 0 the message. BODY[0] is BODY[HEADER], differing resulting untagged FETCH returned). is the [RFC-822] header of functionally equivalent to in the syntax of the data (BODY[0] is

RFC822.HEADER.LINES Functionally equivalent to BODY.PEEK[HEADER.LINES ], differing in the syntax of the resulting untagged FETCH data (RFC822.HEADER is returned).

Crispin

Informational

[Page 4]

RFC 2062

IMAP4 Obsolete

December 1996

RFC822.HEADER.LINES.NOT Functionally equivalent to BODY.PEEK[HEADER.LINES.NOT ], differing in the syntax of the resulting untagged FETCH data (RFC822.HEADER is returned). RFC822.PEEK Functionally equivalent to BODY.PEEK[], except for the syntax of the resulting untagged FETCH data (RFC822 is returned).

RFC822.TEXT.PEEK Functionally equivalent to BODY.PEEK[TEXT], except for the syntax of the resulting untagged FETCH data (RFC822.TEXT is returned). Obsolete Responses The following responses are OBSOLETE. Except as noted below, these responses MUST NOT be transmitted by new server implementations. Client implementations SHOULD accept these responses. The section headings of these responses are intended to correspond with where they would be located in the main document if they were not obsoleted. 7.2.OBS.1. Data: MAILBOX Response name

The MAILBOX response MUST NOT be transmitted by server implementations except in response to the obsolete FIND MAILBOXES and FIND ALL.MAILBOXES commands. Client implementations that do not use these commands MAY ignore this response. It is documented here for the benefit of implementors who may wish to support it for compatibility with old client implementations. This response occurs as a result of the FIND MAILBOXES and FIND ALL.MAILBOXES commands. It returns a single name that matches the FIND specification. There are no attributes or hierarchy delimiter. Example: S: * MAILBOX blurdybloop

Crispin

Informational

[Page 5]

RFC 2062

IMAP4 Obsolete

December 1996

7.3.OBS.1. Data:

COPY Response none MUST NOT be transmitted by new server Client implementations MUST ignore the COPY documented here for the benefit of client may encounter this response from old server

The COPY response implementations. response. It is implementors who implementations.

In some experimental versions of this protocol, this response was returned in response to a COPY command to indicate on a per-message basis that the message was copied successfully. Example: 7.3.OBS.2. Data: S: * 44 COPY STORE Response message data

The STORE response MUST NOT be transmitted by new server implementations. Client implementations MUST treat the STORE response as equivalent to the FETCH response. It is documented here for the benefit of client implementors who may encounter this response from old server implementations. In some experimental versions of this protocol, this response was returned instead of FETCH in response to a STORE command to report the new value of the flags. Example: S: * 69 STORE (FLAGS (\Deleted))

Formal Syntax of Obsolete Commands and Responses Each obsolete syntax rule that is suffixed with "_old" is added to the corresponding name in the formal syntax. For example, command_auth_old adds the FIND command to command_auth. command_auth_old ::= find command_select_old ::= partial date_year_old ::= 2digit ;; (year - 1900) ::= <"> date_day_fixed "-" date_month "-" date_year SPACE time "-" zone_name <">

date_time_old

Crispin

Informational

[Page 6]

RFC 2062

IMAP4 Obsolete

December 1996

find

::= "FIND" SPACE ["ALL."] "MAILBOXES" SPACE list_mailbox ::= "RFC822.HEADER.LINES" [".NOT"] SPACE header_list / fetch_text_old ::= "BODY" [".PEEK"] section_old / "RFC822" [".HEADER" / ".TEXT" [".PEEK"]] ::= "COPY" / ("STORE" SPACE msg_att) ::= "PARTIAL" SPACE nz_number SPACE fetch_text_old SPACE number SPACE number ::= "[" (number ["." number]) "]" ::= "SUBSCRIBE" SPACE "MAILBOX" SPACE mailbox

fetch_att_old

fetch_text_old

msg_data_old partial

section_old subscribe_old

unsubscribe_old ::= "UNSUBSCRIBE" SPACE "MAILBOX" SPACE mailbox zone_name ::= "UT" "AST" "EST" "CST" "MST" "PST" "YST" "HST" "BST" "A" / "G" / "N" / "T" / / "GMT" / / "EDT" / / "CDT" / / "MDT" / / "PDT" / / "YDT" / / "HDT" / / "BDT" / / "B" / "C" "H" / "I" "O" / "P" "U" / "V" "Z" / ;; ;; ;; ;; ;; ;; ;; ;; ;; "E" / "F" / ;; "L" / "M" / ;; "R" / "S" / ;; "X" / "Y" ;; +0000 -0400 -0500 -0600 -0700 -0800 -0900 -1000 -1100 +1 to +7 to -1 to -7 to

/ / / /

"D" "K" "Q" "W"

/ / / /

+6 +12 -6 -12

Security Considerations Security issues are not discussed in this memo.

Crispin

Informational

[Page 7]

RFC 2062

IMAP4 Obsolete

December 1996

Author's Address Mark R. Crispin Networks and Distributed Computing University of Washington 4545 15th Aveneue NE Seattle, WA 98105-4527 Phone: (206) 543-5762 EMail: MRC@CAC.Washington.EDU

Crispin

Informational

[Page 8]