…., for storing images), and this extension uses the "literal8" syntax element [ RFC4466 ] to allow such data to be written to or read from the server. size The size of the value, in octets. Set automatically by the server, read-only to clients. If the client requests the size att…

…., for storing images), and this extension uses the "literal8" syntax element [ RFC4466 ] to allow such data to be written to or read from the server. size The size of the value, in octets. Set automatically by the server, read-only to clients. If the client requests the size att…

…EATE command for that purpose (using the syntax defined in RFC 4466 section 2.2 RFC4466 ]). The new OPTIONAL "USE" parameter is followed by a parenthesized list of zero or more special-use attributes, as defined above. In some server implementations, some special uses may imply a…

…ut not defined below are as defined by RFC3501 ], with the new definitions in [ RFC4466 ] superseding those in RFC3501 ]. Except as noted otherwise, all alphabetic characters are case- insensitive. The use of upper or lower case characters to define token strings is for editorial…

…guages [ RFC4646 ], UTF-8 [ RFC3629 ], and Collected Extensions to IMAP4 ABNF [ RFC4466 ]. command-any =/ language-cmd ; LANGUAGE command is valid in all states language-cmd = "LANGUAGE" *(SP lang-range-quoted) response-payload =/ language-data language-data = "LANGUAGE" SP "(" l…

…guages [ RFC4646 ], UTF-8 [ RFC3629 ], and Collected Extensions to IMAP4 ABNF [ RFC4466 ]. command-any =/ language-cmd ; LANGUAGE command is valid in all states language-cmd = "LANGUAGE" *(SP lang-range-quoted) response-payload =/ language-data language-data = "LANGUAGE" SP "(" l…

…on to indicate which one to advertise.) 6 . Interaction with BINARY Extension [ RFC4466 ] updated the non-terminal "literal8" defined in [ RFC3516 ] to allow for non-synchronizing literals if both BINARY [ RFC3516 ] and LITERAL+ extensions are supported by the server. This docume…