6/21/2023 0 Comments Exif editor total commander![]() This specification defines an initial set of entry names availableįor use with mailbox and server annotations. Use of control or punctuation characters in entry names is strongly Result in a BAD response in any IMAP command in which they are used. With octet values in the range 0x00 to 0x19. ![]() To represent line ends in a multi-line string value.Įntry names MUST NOT contain asterisk ("*") or percent ("%")Ĭharacters and MUST NOT contain non-ASCII characters or characters Clients MUST use the CRLF (0x0D 0x0A) character octet sequence The value of an entry is NIL (has no value), or a string or binaryĭata of zero or more octets. NOT contain two consecutive "/" characters and MUST NOT end with a Or change the values of any annotation entry, assuming it hasĮach annotation is an entry that has a hierarchical name, with eachĬomponent of the name separated by a slash ("/"). The protocol changes to IMAP described below allow a client to access Provided as the first argument to the command.įor example, a general comment being added to a mailbox may have anĮntry name of "/comment" and a value of "Really useful mailbox". Mailbox name is provided as the first argument to the SETMETADATAĬommand, or to the server as a whole when the empty string is Annotations can be added to mailboxes when a An annotation contains a uniquely named entry, Mailboxes or the server as a whole may have zero or more annotationsĪssociated with them. RFC 5464 The IMAP METADATA Extension February 2009 3. Whitespace and line breaks have been added to the examples in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in thisĭocument are to be interpreted as described in. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", In examples, "C:" and "S:" indicate lines sent by the client and The rest of this document describes the data model and protocol This extension makes the following changes to the IMAP protocol: The METADATA extension adds two new commands and one new untagged Support the "ENABLE" extension to allow clients to turn Of this extension by returning "METADATA-SERVER" as one of theĪ server that supports unsolicited annotation change responses MUST Supported capabilities in the CAPABILITY command response.Ī server that supports only server annotations indicates the presence The presence of this extension by returning "METADATA" as one of the The server can choose to support only serverĪnnotations or both server and mailbox annotations.Ī server that supports both server and mailbox annotations indicates The annotations can be associated with specific mailboxes or the To set and retrieve "annotations" or "metadata" on an IMAP server. The goal of the METADATA extension is to provide a means for clients RFC 5464 The IMAP METADATA Extension February 2009 1. Entry and Attribute Registration Template. Unsolicited METADATA Response without Values. Private versus Shared and Access Control. RFC 5464 The IMAP METADATA Extension February 2009ġ. Information to be made available to anyone logging in to the server. To that mailbox, or a "message of the day" containing server status For example, this would allowĬomments about the purpose of a particular mailbox to be "attached" It is possible to have annotations on a per-mailboxīasis or on the server as a whole. Permits clients and servers to maintain "annotations" or "metadata" ![]() The METADATA extension to the Internet Message Access Protocol Official Protocol Standards" (STD 1) for the standardization stateĪnd status of this protocol. Please refer to the current edition of the "Internet ![]() Internet community, and requests discussion and suggestions for This document specifies an Internet standards track protocol for the RFC 5464: The IMAP METADATA Extension Įrrata Exist Network Working Group C. ![]()
0 Comments
Leave a Reply. |