…T command [ RFC2389 ]. The UTF-8 feature is a line containing the exact string "UTF8". This string is not case sensitive, but SHOULD be transmitted in upper case. The response to a FEAT command SHOULD be: C> feat S> 211- <any descriptive text> S> ... S> UTF8 S> ... S> 211 end The…

…EAT command [RFC2389]. The UTF-8 feature is a line containing the exact string "UTF8". This string is not case sensitive, but SHOULD be transmitted in upper case. The response to a FEAT command SHOULD be: C> feat S> 211- <any descriptive text> S> ... S> UTF8 S> ... S> 211 end The…

…EAT command [RFC2389]. The UTF-8 feature is a line containing the exact string "UTF8". This string is not case sensitive, but SHOULD be transmitted in upper case. The response to a FEAT command SHOULD be: C> feat S> 211- <any descriptive text> S> ... S> UTF8 S> ... S> 211 end The…

…T command [ RFC2389 ]. The UTF-8 feature is a line containing the exact string "UTF8". This string is not case sensitive, but SHOULD be transmitted in upper case. The response to a FEAT command SHOULD be: C> feat S> 211- <any descriptive text> S> ... S> UTF8 S> ... S> 211 end The…

…T command [ RFC2389 ]. The UTF-8 feature is a line containing the exact string "UTF8". This string is not case sensitive, but SHOULD be transmitted in upper case. The response to a FEAT command SHOULD be: C> feat S> 211- <any descriptive text> S> ... S> UTF8 S> ... S> 211 end The…

…r handle email messages. As specified in [RFC5336], an SMTP protocol extension "UTF8SMTP" is used to prevent the transmission of messages with UTF-8 header fields to systems that cannot handle such messages. Use of this SMTP extension helps prevent the introduction of such messag…

…r handle email messages. As specified in [RFC5336], an SMTP protocol extension "UTF8SMTP" is used to prevent the transmission of messages with UTF-8 header fields to systems that cannot handle such messages. Use of this SMTP extension helps prevent the introduction of such messag…

…handle email messages. As specified in [ RFC5336 ], an SMTP protocol extension "UTF8SMTP" is used to prevent the transmission of messages with UTF-8 header fields to systems that cannot handle such messages. Use of this SMTP extension helps prevent the introduction of such messag…

…handle email messages. As specified in [ RFC5336 ], an SMTP protocol extension "UTF8SMTP" is used to prevent the transmission of messages with UTF-8 header fields to systems that cannot handle such messages. Use of this SMTP extension helps prevent the introduction of such messag…

…ction ; 10.3.3 for a pointer to the registry of ; valid values ;cleartext = 1*( UTF8-octets [CR] LF) ; dash-escaped per RFC 4880 Section 7.1 cleartext = *((line-dash / line-from / line-nodash) [CR] LF) line-dash = ("- ") "-" *UTF8-char-not-cr ; MUST include initial "- " line-from…

…nes, et al. Standards Track [Page 4] RFC 7515 JSON Web Signature (JWS) May 2015 UTF8(STRING) denotes the octets of the UTF-8 [ RFC3629 ] representation of STRING, where STRING is a sequence of zero or more Unicode [ UNICODE ] characters. ASCII(STRING) denotes the octets of the AS…

…nes, et al. Standards Track [Page 4] RFC 7515 JSON Web Signature (JWS) May 2015 UTF8(STRING) denotes the octets of the UTF-8 [RFC3629] representation of STRING, where STRING is a sequence of zero or more Unicode [UNICODE] characters. ASCII(STRING) denotes the octets of the ASCII …

…nes, et al. Standards Track [Page 4] RFC 7515 JSON Web Signature (JWS) May 2015 UTF8(STRING) denotes the octets of the UTF-8 [ RFC3629 ] representation of STRING, where STRING is a sequence of zero or more Unicode UNICODE ] characters. ASCII(STRING) denotes the octets of the ASCI…

…nes, et al. Standards Track [Page 4] RFC 7515 JSON Web Signature (JWS) May 2015 UTF8(STRING) denotes the octets of the UTF-8 [ RFC3629 ] representation of STRING, where STRING is a sequence of zero or more Unicode UNICODE ] characters. ASCII(STRING) denotes the octets of the ASCI…

…. . . . 3 2. LANG Capability . . . . . . . . . . . . . . . . . . . . . . . 4 3. UTF8 Capability . . . . . . . . . . . . . . . . . . . . . . . 6 3.1. The UTF8 Command . . . . . . . . . . . . . . . . . . . . . 7 3.2. USER Argument to UTF8 Capability . . . . . . . . . . . . . 9 4. N…