1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/docs/rfc/rfc2062.txt	Mon Sep 14 15:17:45 2009 +0900
     1.3 @@ -0,0 +1,451 @@
     1.4 +
     1.5 +
     1.6 +
     1.7 +
     1.8 +
     1.9 +
    1.10 +Network Working Group                                         M. Crispin
    1.11 +Request for Comments: 2062                      University of Washington
    1.12 +Category: Informational                                    December 1996
    1.13 +
    1.14 +
    1.15 +           Internet Message Access Protocol - Obsolete Syntax
    1.16 +
    1.17 +Status of this Memo
    1.18 +
    1.19 +   This memo provides information for the Internet community.  This memo
    1.20 +   does not specify an Internet standard of any kind.  Distribution of
    1.21 +   this memo is unlimited.
    1.22 +
    1.23 +Abstract
    1.24 +
    1.25 +   This document describes obsolete syntax which may be encountered by
    1.26 +   IMAP4 implementations which deal with older versions of the Internet
    1.27 +   Mail Access Protocol.  IMAP4 implementations MAY implement this
    1.28 +   syntax in order to maximize interoperability with older
    1.29 +   implementations.
    1.30 +
    1.31 +   This document repeats information from earlier documents, most
    1.32 +   notably RFC 1176 and RFC 1730.
    1.33 +
    1.34 +Obsolete Commands and Fetch Data Items
    1.35 +
    1.36 +   The following commands are OBSOLETE.  It is NOT required to support
    1.37 +   any of these commands or fetch data items in new server
    1.38 +   implementations.  These commands are documented here for the benefit
    1.39 +   of implementors who may wish to support them for compatibility with
    1.40 +   old client implementations.
    1.41 +
    1.42 +   The section headings of these commands are intended to correspond
    1.43 +   with where they would be located in the main document if they were
    1.44 +   not obsoleted.
    1.45 +
    1.46 +6.3.OBS.1.      FIND ALL.MAILBOXES Command
    1.47 +
    1.48 +   Arguments:  mailbox name with possible wildcards
    1.49 +
    1.50 +   Data:       untagged responses: MAILBOX
    1.51 +
    1.52 +   Result:     OK - find completed
    1.53 +               NO - find failure: can't list that name
    1.54 +               BAD - command unknown or arguments invalid
    1.55 +
    1.56 +
    1.57 +
    1.58 +
    1.59 +
    1.60 +
    1.61 +Crispin                      Informational                      [Page 1]
    1.62 +
    1.63 +RFC 2062                     IMAP4 Obsolete                December 1996
    1.64 +
    1.65 +
    1.66 +      The FIND ALL.MAILBOXES command returns a subset of names from the
    1.67 +      complete set of all names available to the user.  It returns zero
    1.68 +      or more untagged MAILBOX replies.  The mailbox argument to FIND
    1.69 +      ALL.MAILBOXES is similar to that for LIST with an empty reference,
    1.70 +      except that the characters "%" and "?" match a single character.
    1.71 +
    1.72 +   Example:    C: A002 FIND ALL.MAILBOXES *
    1.73 +               S: * MAILBOX blurdybloop
    1.74 +               S: * MAILBOX INBOX
    1.75 +               S: A002 OK FIND ALL.MAILBOXES completed
    1.76 +
    1.77 +6.3.OBS.2.      FIND MAILBOXES Command
    1.78 +
    1.79 +   Arguments:  mailbox name with possible wildcards
    1.80 +
    1.81 +   Data:       untagged responses: MAILBOX
    1.82 +
    1.83 +   Result:     OK - find completed
    1.84 +               NO - find failure: can't list that name
    1.85 +               BAD - command unknown or arguments invalid
    1.86 +
    1.87 +      The FIND MAILBOXES command returns a subset of names from the set
    1.88 +      of names that the user has declared as being "active" or
    1.89 +      "subscribed".  It returns zero or more untagged MAILBOX replies.
    1.90 +      The mailbox argument to FIND MAILBOXES is similar to that for LSUB
    1.91 +      with an empty reference, except that the characters "%" and "?"
    1.92 +      match a single character.
    1.93 +
    1.94 +   Example:    C: A002 FIND MAILBOXES *
    1.95 +               S: * MAILBOX blurdybloop
    1.96 +               S: * MAILBOX INBOX
    1.97 +               S: A002 OK FIND MAILBOXES completed
    1.98 +
    1.99 +6.3.OBS.3.      SUBSCRIBE MAILBOX Command
   1.100 +
   1.101 +   Arguments:  mailbox name
   1.102 +
   1.103 +   Data:       no specific data for this command
   1.104 +
   1.105 +   Result:     OK - subscribe completed
   1.106 +               NO - subscribe failure: can't subscribe to that name
   1.107 +               BAD - command unknown or arguments invalid
   1.108 +
   1.109 +      The SUBSCRIBE MAILBOX command is identical in effect to the
   1.110 +      SUBSCRIBE command.  A server which implements this command must be
   1.111 +      able to distinguish between a SUBSCRIBE MAILBOX command and a
   1.112 +      SUBSCRIBE command with a mailbox name argument of "MAILBOX".
   1.113 +
   1.114 +
   1.115 +
   1.116 +
   1.117 +Crispin                      Informational                      [Page 2]
   1.118 +
   1.119 +RFC 2062                     IMAP4 Obsolete                December 1996
   1.120 +
   1.121 +
   1.122 +   Example:    C: A002 SUBSCRIBE MAILBOX #news.comp.mail.mime
   1.123 +               S: A002 OK SUBSCRIBE MAILBOX to #news.comp.mail.mime
   1.124 +               completed
   1.125 +               C: A003 SUBSCRIBE MAILBOX
   1.126 +               S: A003 OK SUBSCRIBE to MAILBOX completed
   1.127 +
   1.128 +
   1.129 +6.3.OBS.4.      UNSUBSCRIBE MAILBOX Command
   1.130 +
   1.131 +   Arguments:  mailbox name
   1.132 +
   1.133 +   Data:       no specific data for this command
   1.134 +
   1.135 +   Result:     OK - unsubscribe completed
   1.136 +               NO - unsubscribe failure: can't unsubscribe that name
   1.137 +               BAD - command unknown or arguments invalid
   1.138 +
   1.139 +      The UNSUBSCRIBE MAILBOX command is identical in effect to the
   1.140 +      UNSUBSCRIBE command.  A server which implements this command must
   1.141 +      be able to distinguish between a UNSUBSCRIBE MAILBOX command and
   1.142 +      an UNSUBSCRIBE command with a mailbox name argument of "MAILBOX".
   1.143 +
   1.144 +   Example:    C: A002 UNSUBSCRIBE MAILBOX #news.comp.mail.mime
   1.145 +               S: A002 OK UNSUBSCRIBE MAILBOX from #news.comp.mail.mime
   1.146 +               completed
   1.147 +               C: A003 UNSUBSCRIBE MAILBOX
   1.148 +               S: A003 OK UNSUBSCRIBE from MAILBOX completed
   1.149 +
   1.150 +6.4.OBS.1       PARTIAL Command
   1.151 +
   1.152 +   Arguments:  message sequence number
   1.153 +               message data item name
   1.154 +               position of first octet
   1.155 +               number of octets
   1.156 +
   1.157 +   Data:       untagged responses: FETCH
   1.158 +
   1.159 +   Result:     OK - partial completed
   1.160 +               NO - partial error: can't fetch that data
   1.161 +               BAD - command unknown or arguments invalid
   1.162 +
   1.163 +      The PARTIAL command is equivalent to the associated FETCH command,
   1.164 +      with the added functionality that only the specified number of
   1.165 +      octets, beginning at the specified starting octet, are returned.
   1.166 +      Only a single message can be fetched at a time.  The first octet
   1.167 +      of a message, and hence the minimum for the starting octet, is
   1.168 +      octet 1.
   1.169 +
   1.170 +
   1.171 +
   1.172 +
   1.173 +Crispin                      Informational                      [Page 3]
   1.174 +
   1.175 +RFC 2062                     IMAP4 Obsolete                December 1996
   1.176 +
   1.177 +
   1.178 +      The following FETCH items are valid data for PARTIAL: RFC822,
   1.179 +      RFC822.HEADER, RFC822.TEXT, BODY[<section>], as well as any .PEEK
   1.180 +      forms of these.
   1.181 +
   1.182 +      Any partial fetch that attempts to read beyond the end of the text
   1.183 +      is truncated as appropriate.  If the starting octet is beyond the
   1.184 +      end of the text, an empty string is returned.
   1.185 +
   1.186 +      The data are returned with the FETCH response.  There is no
   1.187 +      indication of the range of the partial data in this response.  It
   1.188 +      is not possible to stream multiple PARTIAL commands of the same
   1.189 +      data item without processing and synchronizing at each step, since
   1.190 +      streamed commands may be executed out of order.
   1.191 +
   1.192 +      There is no requirement that partial fetches follow any sequence.
   1.193 +      For example, if a partial fetch of octets 1 through 10000 breaks
   1.194 +      in an awkward place for BASE64 decoding, it is permitted to
   1.195 +      continue with a partial fetch of 9987 through 19987, etc.
   1.196 +
   1.197 +      The handling of the \Seen flag is the same as in the associated
   1.198 +      FETCH command.
   1.199 +
   1.200 +   Example:    C: A005 PARTIAL 4 RFC822 1 1024
   1.201 +               S: * 1 FETCH (RFC822 {1024}
   1.202 +               S: Return-Path: <gray@cac.washington.edu>
   1.203 +               S: ...
   1.204 +               S: .........  FLAGS (\Seen))
   1.205 +               S: A005 OK PARTIAL completed
   1.206 +
   1.207 +6.4.5.OBS.1     Obsolete FETCH Data Items
   1.208 +
   1.209 +   The following FETCH data items are obsolete:
   1.210 +
   1.211 +      BODY[<...>0]   A body part number of 0 is the [RFC-822] header of
   1.212 +                     the message.  BODY[0] is functionally equivalent to
   1.213 +                     BODY[HEADER], differing in the syntax of the
   1.214 +                     resulting untagged FETCH data (BODY[0] is
   1.215 +                     returned).
   1.216 +
   1.217 +      RFC822.HEADER.LINES <header_list>
   1.218 +                     Functionally equivalent to BODY.PEEK[HEADER.LINES
   1.219 +                     <header_list>], differing in the syntax of the
   1.220 +                     resulting untagged FETCH data (RFC822.HEADER is
   1.221 +                     returned).
   1.222 +
   1.223 +
   1.224 +
   1.225 +
   1.226 +
   1.227 +
   1.228 +
   1.229 +Crispin                      Informational                      [Page 4]
   1.230 +
   1.231 +RFC 2062                     IMAP4 Obsolete                December 1996
   1.232 +
   1.233 +
   1.234 +      RFC822.HEADER.LINES.NOT <header_list>
   1.235 +                     Functionally equivalent to
   1.236 +                     BODY.PEEK[HEADER.LINES.NOT <header_list>],
   1.237 +                     differing in the syntax of the resulting untagged
   1.238 +                     FETCH data (RFC822.HEADER is returned).
   1.239 +
   1.240 +      RFC822.PEEK    Functionally equivalent to BODY.PEEK[], except for
   1.241 +                     the syntax of the resulting untagged FETCH data
   1.242 +                     (RFC822 is returned).
   1.243 +
   1.244 +      RFC822.TEXT.PEEK
   1.245 +                     Functionally equivalent to BODY.PEEK[TEXT], except
   1.246 +                     for the syntax of the resulting untagged FETCH data
   1.247 +                     (RFC822.TEXT is returned).
   1.248 +
   1.249 +Obsolete Responses
   1.250 +
   1.251 +   The following responses are OBSOLETE.  Except as noted below, these
   1.252 +   responses MUST NOT be transmitted by new server implementations.
   1.253 +   Client implementations SHOULD accept these responses.
   1.254 +
   1.255 +   The section headings of these responses are intended to correspond
   1.256 +   with where they would be located in the main document if they were
   1.257 +   not obsoleted.
   1.258 +
   1.259 +7.2.OBS.1.      MAILBOX Response
   1.260 +
   1.261 +   Data:       name
   1.262 +
   1.263 +      The MAILBOX response MUST NOT be transmitted by server
   1.264 +      implementations except in response to the obsolete FIND MAILBOXES
   1.265 +      and FIND ALL.MAILBOXES commands.  Client implementations that do
   1.266 +      not use these commands MAY ignore this response.  It is documented
   1.267 +      here for the benefit of implementors who may wish to support it
   1.268 +      for compatibility with old client implementations.
   1.269 +
   1.270 +      This response occurs as a result of the FIND MAILBOXES and FIND
   1.271 +      ALL.MAILBOXES commands.  It returns a single name that matches the
   1.272 +      FIND specification.  There are no attributes or hierarchy
   1.273 +      delimiter.
   1.274 +
   1.275 +   Example:    S: * MAILBOX blurdybloop
   1.276 +
   1.277 +
   1.278 +
   1.279 +
   1.280 +
   1.281 +
   1.282 +
   1.283 +
   1.284 +
   1.285 +Crispin                      Informational                      [Page 5]
   1.286 +
   1.287 +RFC 2062                     IMAP4 Obsolete                December 1996
   1.288 +
   1.289 +
   1.290 +7.3.OBS.1.      COPY Response
   1.291 +
   1.292 +   Data:       none
   1.293 +
   1.294 +      The COPY response MUST NOT be transmitted by new server
   1.295 +      implementations.  Client implementations MUST ignore the COPY
   1.296 +      response.  It is documented here for the benefit of client
   1.297 +      implementors who may encounter this response from old server
   1.298 +      implementations.
   1.299 +
   1.300 +      In some experimental versions of this protocol, this response was
   1.301 +      returned in response to a COPY command to indicate on a
   1.302 +      per-message basis that the message was copied successfully.
   1.303 +
   1.304 +   Example:    S: * 44 COPY
   1.305 +
   1.306 +7.3.OBS.2.      STORE Response
   1.307 +
   1.308 +   Data:       message data
   1.309 +
   1.310 +      The STORE response MUST NOT be transmitted by new server
   1.311 +      implementations.  Client implementations MUST treat the STORE
   1.312 +      response as equivalent to the FETCH response.  It is documented
   1.313 +      here for the benefit of client implementors who may encounter this
   1.314 +      response from old server implementations.
   1.315 +
   1.316 +      In some experimental versions of this protocol, this response was
   1.317 +      returned instead of FETCH in response to a STORE command to report
   1.318 +      the new value of the flags.
   1.319 +
   1.320 +   Example:    S: * 69 STORE (FLAGS (\Deleted))
   1.321 +
   1.322 +Formal Syntax of Obsolete Commands and Responses
   1.323 +
   1.324 +   Each obsolete syntax rule that is suffixed with "_old" is added to
   1.325 +   the corresponding name in the formal syntax.  For example,
   1.326 +   command_auth_old adds the FIND command to command_auth.
   1.327 +
   1.328 +   command_auth_old ::= find
   1.329 +
   1.330 +   command_select_old
   1.331 +                   ::= partial
   1.332 +
   1.333 +   date_year_old   ::= 2digit
   1.334 +                       ;; (year - 1900)
   1.335 +
   1.336 +   date_time_old   ::= <"> date_day_fixed "-" date_month "-" date_year
   1.337 +                       SPACE time "-" zone_name <">
   1.338 +
   1.339 +
   1.340 +
   1.341 +Crispin                      Informational                      [Page 6]
   1.342 +
   1.343 +RFC 2062                     IMAP4 Obsolete                December 1996
   1.344 +
   1.345 +
   1.346 +   find            ::= "FIND" SPACE ["ALL."] "MAILBOXES" SPACE
   1.347 +                       list_mailbox
   1.348 +
   1.349 +   fetch_att_old   ::= "RFC822.HEADER.LINES" [".NOT"] SPACE header_list /
   1.350 +                       fetch_text_old
   1.351 +
   1.352 +   fetch_text_old  ::= "BODY" [".PEEK"] section_old /
   1.353 +                       "RFC822" [".HEADER" / ".TEXT" [".PEEK"]]
   1.354 +
   1.355 +   msg_data_old    ::= "COPY" / ("STORE" SPACE msg_att)
   1.356 +
   1.357 +   partial         ::= "PARTIAL" SPACE nz_number SPACE fetch_text_old SPACE
   1.358 +                       number SPACE number
   1.359 +
   1.360 +   section_old     ::= "[" (number ["." number]) "]"
   1.361 +
   1.362 +   subscribe_old   ::= "SUBSCRIBE" SPACE "MAILBOX" SPACE mailbox
   1.363 +
   1.364 +   unsubscribe_old ::= "UNSUBSCRIBE" SPACE "MAILBOX" SPACE mailbox
   1.365 +
   1.366 +   zone_name       ::= "UT" / "GMT" / "Z" /                ;; +0000
   1.367 +                       "AST" / "EDT" /                     ;; -0400
   1.368 +                       "EST" / "CDT" /                     ;; -0500
   1.369 +                       "CST" / "MDT" /                     ;; -0600
   1.370 +                       "MST" / "PDT" /                     ;; -0700
   1.371 +                       "PST" / "YDT" /                     ;; -0800
   1.372 +                       "YST" / "HDT" /                     ;; -0900
   1.373 +                       "HST" / "BDT" /                     ;; -1000
   1.374 +                       "BST" /                             ;; -1100
   1.375 +                       "A" / "B" / "C" / "D" / "E" / "F" / ;; +1 to +6
   1.376 +                       "G" / "H" / "I" / "K" / "L" / "M" / ;; +7 to +12
   1.377 +                       "N" / "O" / "P" / "Q" / "R" / "S" / ;; -1 to -6
   1.378 +                       "T" / "U" / "V" / "W" / "X" / "Y"   ;; -7 to -12
   1.379 +
   1.380 +Security Considerations
   1.381 +
   1.382 +   Security issues are not discussed in this memo.
   1.383 +
   1.384 +
   1.385 +
   1.386 +
   1.387 +
   1.388 +
   1.389 +
   1.390 +
   1.391 +
   1.392 +
   1.393 +
   1.394 +
   1.395 +
   1.396 +
   1.397 +Crispin                      Informational                      [Page 7]
   1.398 +
   1.399 +RFC 2062                     IMAP4 Obsolete                December 1996
   1.400 +
   1.401 +
   1.402 +Author's Address
   1.403 +
   1.404 +   Mark R. Crispin
   1.405 +   Networks and Distributed Computing
   1.406 +   University of Washington
   1.407 +   4545 15th Aveneue NE
   1.408 +   Seattle, WA  98105-4527
   1.409 +
   1.410 +   Phone: (206) 543-5762
   1.411 +   EMail: MRC@CAC.Washington.EDU
   1.412 +
   1.413 +
   1.414 +
   1.415 +
   1.416 +
   1.417 +
   1.418 +
   1.419 +
   1.420 +
   1.421 +
   1.422 +
   1.423 +
   1.424 +
   1.425 +
   1.426 +
   1.427 +
   1.428 +
   1.429 +
   1.430 +
   1.431 +
   1.432 +
   1.433 +
   1.434 +
   1.435 +
   1.436 +
   1.437 +
   1.438 +
   1.439 +
   1.440 +
   1.441 +
   1.442 +
   1.443 +
   1.444 +
   1.445 +
   1.446 +
   1.447 +
   1.448 +
   1.449 +
   1.450 +
   1.451 +
   1.452 +
   1.453 +Crispin                      Informational                      [Page 8]
   1.454 +