…ncoded in quoted-printable or base64. For 8-bit clean transport (e.g., 8BITMIME[RFC1652] ESMTP or NNTP[RFC0977]), UTF-8 does not need to be encoded. Over HTTP[RFC2616], no content-transfer- encoding is necessary and UTF-16 may also be used. Security considerations: See Section 10…

…aders, and (finally) a requirement for support of the 8BITMIME SMTP extension [ RFC1652 ] so that all of these can be transported through the mail system without having to overcome the limitation that headers do not have content-transfer-encodings. 1.3 . Terminology This document…

… this extension MUST provide support for, and announce, the 8BITMIME extension [RFC1652]. 8. The reverse-path and forward-path of the SMTP MAIL and RCPT commands are extended to allow Unicode characters encoded in UTF-8 in mailbox names (addresses). 9. The mail message body is ex…

…ort these without re-encoding them, the SMTP specification supports an option [ RFC1652 ] that permits the transport of such textual Crocker Informational [Page 43] RFC 5598 Email Architecture July 2009 content. However, the [ RFC1652 ] option does not address the use of 8-bit co…

…aders, and (finally) a requirement for support of the 8BITMIME SMTP extension [ RFC1652 ] so that all of these can be transported through the mail system without having to overcome the limitation that headers do not have content-transfer-encodings. 1.3 . Terminology This document…

…this extension MUST provide support for, and announce, the 8BITMIME extension [ RFC1652 ]. 8. The reverse-path and forward-path of the SMTP MAIL and RCPT commands are extended to allow Unicode characters encoded in UTF-8 in mailbox names (addresses). 9. The mail message body is e…

…ncoded in quoted-printable or base64. For 8-bit clean transport (e.g., 8BITMIME[RFC1652] ESMTP or NNTP[RFC0977]), UTF-8 does not need to be encoded. Over HTTP[RFC2616], no content-transfer- encoding is necessary and UTF-16 may also be used. Security considerations: See Section 10…

… containing a message/global is downgraded from 8-bit to 7-bit as described in [RFC1652], an encoding may be applied to the message; if the message travels multiple times between a 7-bit environment and an environment implementing UTF8SMTP, multiple levels of encoding may occur. …

…containing a message/global is downgraded from 8-bit to 7-bit as described in [ RFC1652 ], an encoding may be applied to the message; if the message travels multiple times between a 7-bit environment and an environment implementing UTF8SMTP, multiple levels of encoding may occur.…

…containing a message/global is downgraded from 8-bit to 7-bit as described in [ RFC1652 ], an encoding may be applied to the message; if the message travels multiple times between a 7-bit environment and an environment implementing UTF8SMTP, multiple levels of encoding may occur.…

… may encounter a SMTP server that does not support the 8BITMIME SMTP extension [RFC1652]. The server does not support "8bit" or "binary" data. Implementers need to consider converting "8bit" data to "base64" or "quoted-printable" encoded form and adjust the "Content-Transfer-Enco…

…may encounter a SMTP server that does not support the 8BITMIME SMTP extension [ RFC1652 ]. The server does not support "8bit" or "binary" data. Implementers need to consider converting "8bit" data to "base64" or "quoted-printable" encoded form and adjust the "Content-Transfer-Enc…