…racters in SMTP envelope and mail header field values. The UTF8SMTP extension ([RFC4952], [RFC5335], and [RFC5336]) allows UTF-8 characters in SMTP envelope and mail header field values. If an envelope address or header field contains non-ASCII characters, the message cannot be d…
…acters in SMTP envelope and mail header field values. The UTF8SMTP extension ([ RFC4952 ], [ RFC5335 ], and RFC5336 ]) allows UTF-8 characters in SMTP envelope and mail header field values. If an envelope address or header field contains non-ASCII characters, the message cannot b…
…apability to use international characters in envelope addresses, discussed in [ RFC4952 ] and specified in [ RFC5336 ]. o The capability to express those addresses, and information related to them and based on them, in mail header fields, defined in this document. This document s…
…ction The Email Address Internationalization (UTF8SMTP) extension document set [RFC4952] [RFC5336] [RFC5335] [RFC5337] expands Email address structure, syntax, and email header format. To avoid rejection of internationalized email messages, the downgrading mechanism [RFC5504] con…
…apability to use international characters in envelope addresses, discussed in [ RFC4952 ] and specified in [ RFC5336 ]. o The capability to express those addresses, and information related to them and based on them, in mail header fields, defined in this document. This document s…
… of the extension model for internationalized addresses and headers appears in [RFC4952], referred to as "the framework document" or just as "Framework" elsewhere in this specification. This document specifies an SMTP extension to permit internationalized email addresses in envel…
…tion The Email Address Internationalization (UTF8SMTP) extension document set [ RFC4952 ] [ RFC5336 ] [ RFC5335 ] [ RFC5337 ] expands Email address structure, syntax, and email header format. To avoid rejection of internationalized email messages, the downgrading mechanism [ RFC5…
…of the extension model for internationalized addresses and headers appears in [ RFC4952 ], referred to as "the framework document" or just as "Framework" elsewhere in this specification. This document specifies an SMTP extension to permit internationalized email addresses in enve…
… is not part of the address at all. This document is a replacement for RFC 4952 RFC4952 ]; it reflects additional issues, shared terminology, and some architectural changes identified since that document was published. It obsoletes that document. The experimental descriptions of …
…dress the needs of the ongoing Email Address Internationalization effort (see [ RFC4952 ]). In particular, this specification does not include syntax for fallback addresses. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",…
…Internationalization (EAI) experiment described in the EAI Framework document [ RFC4952 ] (for background, please see the charter of the EAI working group) and should be evaluated within the context of EAI. As part of the overall EAI work, email messages may be transmitted and de…
…Internationalization (EAI) experiment described in the EAI Framework document [ RFC4952 (for background, please see the charter of the EAI working group) and should be evaluated within the context of EAI. As part of the overall EAI work, email messages may be transmitted and deli…
…dress the needs of the ongoing Email Address Internationalization effort (see [ RFC4952 ]). In particular, this specification does not include syntax for fallback addresses. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",…
… NOTES-- The term is used in draft-ietf-eai-mailinglist-03.txt, which refers to rfc4952. RFC 4954 , "SMTP Service Extension for Authentication", July 2007 Note: This RFC has been updated by RFC 5248 Source of RFC : IETF - NON WORKING GROUP Area Assignment: app Errata ID: 1020 Sta…
… NOTES-- The term is used in draft-ietf-eai-mailinglist-03.txt, which refers to rfc4952. RFC 4954 , "SMTP Service Extension for Authentication", July 2007 Note: This RFC has been updated by RFC 5248 Source of RFC : IETF - NON WORKING GROUP Area Assignment: app Errata ID: 1020 Sta…