…ding the SMIMEA record associated with the dynamically created email address. [ RFC5321 ] and its predecessors have always made it clear that only the recipient MTA is allowed to interpret the local-part of an address. Therefore, sending MUAs and MTAs supporting this specificatio…

…7.4. Additional Registered Clauses for "Received" Fields Per the provisions in [RFC5321], IANA has added two additional- registered-clauses for Received fields as defined in Section 4.3 of this document: o "tls": Indicates the TLS cipher used (if applicable) o "group": Indicates …

…enclosed entity as UTF-8 encoded. If sent using a 7-bit transport (e.g., SMTP [ RFC5321 ]), in general, a UTF-8 XML MIME entity must use a content-transfer-encoding of either quoted-printable or base64. For an 8-bit clean transport (e.g., 8BITMIME ESMTP or NNTP), or a binary clea…

…4 . Additional Registered Clauses for "Received" Fields Per the provisions in [ RFC5321 ], IANA has added two additional- registered-clauses for Received fields as defined in Section 4.3 of this document: o "tls": Indicates the TLS cipher used (if applicable) o "group": Indicates…

…il to establish a connection with servers of pre-existing protocols like SMTP [ RFC5321 ] and HTTP, while allowing HTTP servers to opt-in to supporting this protocol if Fette & Melnikov Standards Track [Page 10] RFC 6455 The WebSocket Protocol December 2011 desired. This is achie…

…il to establish a connection with servers of pre-existing protocols like SMTP [ RFC5321 ] and HTTP, while allowing HTTP servers to opt-in to supporting this protocol if Fette & Melnikov Standards Track [Page 10] RFC 6455 The WebSocket Protocol December 2011 desired. This is achie…

…il to establish a connection with servers of pre-existing protocols like SMTP [ RFC5321 ] and HTTP, while allowing HTTP servers to opt-in to supporting this protocol if Fette & Melnikov Standards Track [Page 10] RFC 6455 The WebSocket Protocol December 2011 desired. This is achie…

…ail to establish a connection with servers of pre-existing protocols like SMTP [RFC5321] and HTTP, while allowing HTTP servers to opt-in to supporting this protocol if desired. This is achieved by having a strict and elaborate handshake, and by limiting the data that can be inser…

…I Standard [ RFC3986 ] and a number of application specifications (e.g., SMTP [ RFC5321 ] and HTTP [ RFC2616 ]) do not permit non-ASCII labels in DNS names used with those protocols, i.e., only the A-label form of IDNs is permitted in those contexts. If only A-labels are used, di…

…rms used in this specification are defined in the EAI overview [RFC4952] or in [RFC5321], [RFC5322], or the MIME documents [RFC2045], [RFC2047], [RFC2183], and [RFC2231]. This document depends on [RFC5335] and [RFC5504]. Key words used in those documents are used in this document…

…il to establish a connection with servers of pre-existing protocols like SMTP [ RFC5321 ] and HTTP, while allowing HTTP servers to opt-in to supporting this protocol if Fette & Melnikov Standards Track [Page 10] RFC 6455 The WebSocket Protocol December 2011 desired. This is achie…

…text of status notifications is specified at the end of this section. An SMTP [ RFC5321 ] server that advertises both the SMTPUTF8 extension RFC6531 ] and the DSN extension [ RFC3461 ] MUST accept a UTF-8 address type in the ORCPT parameter including 8-bit UTF-8 characters. This …

…ail to establish a connection with servers of pre-existing protocols like SMTP [RFC5321] and HTTP, while allowing HTTP servers to opt-in to supporting this protocol if Fette & Melnikov Standards Track [Page 10] RFC 6455 The WebSocket Protocol December 2011 desired. This is achiev…

…text of status notifications is specified at the end of this section. An SMTP [ RFC5321 ] server that advertises both the SMTPUTF8 extension RFC6531 ] and the DSN extension [ RFC3461 ] MUST accept a UTF-8 address type in the ORCPT parameter including 8-bit UTF-8 characters. This …

…il to establish a connection with servers of pre-existing protocols like SMTP [ RFC5321 ] and HTTP, while allowing HTTP servers to opt-in to supporting this protocol if Fette & Melnikov Standards Track [Page 10] RFC 6455 The WebSocket Protocol December 2011 desired. This is achie…