The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", Sent by the client and server, respectively. The examples in this document use "C:" and "S:" to indicate lines RFC 5257 IMAP ANNOTATE Extension June 2008 2. The rest of this document describes the data model and protocol SHOULD also support the Conditional STORE extension. That needs to synchronize annotations for use when offline), servers In order to provide optimum support for a disconnected client (one If a server supports annotations, then it MUST store all annotationĭata permanently, i.e., there is no concept of "session only"Īnnotations that would correspond to the behavior of "session" flagsĪs defined in the IMAP base specification. The data model used for the storage of annotations is based on theĪpplication Configuration Access Protocol. adds a new Access Control List (ACL) "bit" for use with the ACL
Annotate example code#
adds a new untagged response code for the SELECT or EXAMINEĬommands to indicate the maximum sized annotation that can be
adds two new response codes to indicate store failures of
adds a new ANNOTATE parameter for use with the SELECT/EXAMINE adds a new requirement on the COPY command. adds a new ANNOTATION data item for use in APPEND.į. adds a new ANNOTATION sort key for use in the SORT extension.Į. adds a new ANNOTATION search criterion for use in SEARCH.ĭ. adds a new ANNOTATION message data item for use in STORE.Ĭ. adds a new ANNOTATION message data item for use in FETCH.ī. This extension makes the following changes to the IMAP protocol:Ī. Supported capabilities in the CAPABILITY response. Implementation that returns "ANNOTATE-EXPERIMENT-1" as one of the The ANNOTATE extension is present in any IMAP RFC 5257 IMAP ANNOTATE Extension June 2008 1.
Annotate example registration#
Entry and Attribute Registration Template. ANNOTATION Message Data Item in FETCH Response. ANNOTATION Message Data Item in FETCH Command. ANNOTATE Parameter with the SELECT/EXAMINE Commands. Access to Standard IMAP Flags and Keywords. RFC 5257 IMAP ANNOTATE Extension June 2008ġ. Used to prevent problems with any deployments of the experimental However,Īny incompatible changes will result in a new capability name being Incompatible manner when going to Proposed Standard status. Implementers should be aware that this specification may change in an IETF solicits implementations and implementation reports in order to Hurdles to meet all of the requirements of a Proposed Standard. It did not have enough information on implementation and deployment
Annotate example how to#
Note that this document was the product of a WG that had goodĬonsensus on how to approach the problem. Marked as seen, or important, or a comment added. To specific parts of a message, so that, for example, they could be It is also possible to attach annotations ForĮxample, this can be used to attach comments and other useful Individual message parts, stored in a mailbox on the server. Permits clients and servers to maintain "meta data" for messages, or The ANNOTATE extension to the Internet Message Access Protocol It does not specify an Internet standard of any kind.ĭiscussion and suggestions for improvement are requested. This memo defines an Experimental Protocol for the InternetĬommunity. Internet Message Access Protocol - ANNOTATE Extension RFC 5257: Internet Message Access Protocol - ANNOTATE Extension Įrrata Exist Network Working Group C.
0 kommentar(er)
