… ] suggested that non-ASCII field names be encoded according to the method in [ RFC2047 ], this practice doesn't seem to have been followed widely. This specification makes three sets of recommendations for three different states of workflow. 5.1.1 . Avoid Non-ASCII Field Names F…

… can be encoded in <hfvalue> as follows: 1. MIME encoded words (as defined in [ RFC2047 ]) are permitted in header field values, but not in an <hfvalue> of a "body" <hfname>. Sequences of characters that look like MIME encoded words can appear in an <hfvalue> of a "body" <hfname>…

…was originally limited to [ ASCII ] in 7-bit form. MIME RFC2045 ] [ RFC2046 ] [ RFC2047 ] provides the ability to use additional character sets, but this support is limited to body part data and to special encoded-word constructs that were only allowed in a limited number of plac…

…does not provide a mechanism for internationalized email addresses. In RFC 2047 RFC2047 ], MIME defines an encoding mechanism for some specific message header fields to accommodate non-ASCII data. However, it does not permit the use of email addresses that include non-ASCII chara…

This is a purely informative rendering of an RFC that includes verified errata. This rendering may not be used as a reference. The following 'Verified' errata have been incorporated in this document: EID 504 , EID 506 Network Working Group K. Moore Request for Comments: 2047 Univ…

…ut Requirements A message that is not compliant with [RFC5322], [RFC2045], and [RFC2047] can be subject to attempts by intermediaries to correct or interpret such content. See Section 8 of [RFC4409] for examples of changes that are commonly made. Such "corrections" may invalidate…

…text (such as in the Subject: field) to be encoded (as required by MIME format [RFC2047]). This specification describes a change to the email message format that is related to the SMTP message transport change described in the associated document [RFC4952] and [RFC5336], and that…

…text (such as in the Subject: field) to be encoded (as required by MIME format [RFC2047]). This specification describes a change to the email message format that is related to the SMTP message transport change described in the associated document [RFC4952] and [RFC5336], and that…

… RFC2634 ] and [ RFC5035 ]. [ MIME-SPEC ] refers to [ RFC2045 ], [ RFC2046 ], [ RFC2047 ], [ RFC2049 ], [ RFC6838 ], and [ RFC4289 ]. [ SMIMEv2 ] refers to [ RFC2311 ], [ RFC2312 ], [ RFC2313 ], [ RFC2314 ], and [ RFC2315 ]. [ SMIMEv3 ] refers to [ RFC2630 ], [ RFC2631 ], [ RFC26…

… to [ RFC2634 ] and [ RFC5035 ]. [ MIME ] refers to [ RFC2045 ], [ RFC2046 ], [ RFC2047 ], [ RFC2049 ], [ RFC4288 ], and [ RFC4289 ]. [ SMIMEv2 ] refers to [ RFC2311 ], [ RFC2312 ], [ RFC2313 ], [ RFC2314 ], and [ RFC2315 ]. [ SMIMEv3 ] refers to [ RFC2630 ], [ RFC2631 ], [ RFC26…

…ext (such as in the Subject: field) to be encoded (as required by MIME format [ RFC2047 ]). This specification describes a change to the email message format that is related to the SMTP message transport change described in the associated document [ RFC4952 ] and [ RFC5336 ], and…

…quirements A message that is not compliant with [ RFC5322 ], [ RFC2045 ], and [ RFC2047 ] can be subject to attempts by intermediaries to correct or interpret such content. See Section 8 of [RFC4409] for examples of changes that are commonly made. Such "corrections" may invalidat…

…it characters in mailto URLs are forbidden. MIME encoded words (as defined in [ RFC2047 ]) are permitted in header values, but not for any part of a "body" hname. Hoffman, et. al. Standards Track [Page 2] RFC 2368 The mailto URL scheme July 1998 3 . Semantics and operations A mai…

…it characters in mailto URLs are forbidden. MIME encoded words (as defined in [ RFC2047 ]) are permitted in header values, but not for any part of a "body" hname. Hoffman, et. al. Standards Track [Page 2] RFC 2368 The mailto URL scheme July 1998 . Semantics and operations A mailt…

…ext (such as in the Subject: field) to be encoded (as required by MIME format [ RFC2047 ]). This specification describes a change to the email message format that is related to the SMTP message transport change described in the associated document [ RFC4952 ] and [ RFC5336 ], and…