…otocol (POP) [RFC1939], and/or Simple Mail Transfer Protocol (SMTP) Submission [RFC6409] usually has Transport Layer Security (TLS) [RFC5246] support but often does not use it in a way that maximizes end-user confidentiality. This specification describes current recommendations f…
…col (POP) [ RFC1939 ], and/or Simple Mail Transfer Protocol (SMTP) Submission [ RFC6409 ] usually has Transport Layer Security (TLS) [ RFC5246 ] support but often does not use it in a way that maximizes end-user confidentiality. This specification describes current recommendation…
… 6532 [ RFC6532 ]. 11. The SMTPUTF8 extension is valid on the submission port [ RFC6409 ]. It may also be used with the Local Mail Transfer Protocol (LMTP) [ RFC2033 ]. When these protocols are used, their use should be reflected in the trace field WITH keywords as appropriate [ …
…RFC 6532 [RFC6532]. 11. The SMTPUTF8 extension is valid on the submission port [RFC6409]. It may also be used with the Local Mail Transfer Protocol (LMTP) [RFC2033]. When these protocols are used, their use should be reflected in the trace field WITH keywords as appropriate [RFC3…
… RFC 6532 RFC6532 ]. 11. The SMTPUTF8 extension is valid on the submission port RFC6409 ]. It may also be used with the Local Mail Transfer Protocol (LMTP) [ RFC2033 ]. When these protocols are used, their use should be reflected in the trace field WITH keywords as appropriate [ …
… used between Message User Agents (MUAs) and Message Submission Agents (MSAs) [ RFC6409 ]. In [ RFC6186 ], a protocol is specified that enables an MUA to dynamically locate the MSA based on the user's email address. SMTP connection security considerations for MUAs implementing [ …
…hose email addresses that are actually under their control (see Section 6.1 of [RFC6409] ). Another means to verify the identity of individual users is message cryptography, such as Pretty Good Privacy (PGP) ([ RFC4880 ]) or S/MIME ([ RFC5751 ]). 11.5 . Untrusted Information Sour…
…y imagine modifications to message submission servers (as described in RFC 6409 RFC6409 ]) so that they would perform downgrading operations or perhaps even upgrading ones. Such operations would permit receiving messages with one or more of the internationalization extensions dis…
…t set. The table below lists SMTP service extensions. Both message submission [ RFC6409 ]and mail transfer RFC-ietf-emailcore-rfc5321bis-43 ] may use these extensions unless otherwise specified. Note The SMTP Extension names/keywords registered in this section are for general use…
…t set. The table below lists SMTP service extensions. Both message submission [ RFC6409 ]and mail transfer RFC-ietf-emailcore-rfc5321bis-43 ] may use these extensions unless otherwise specified. Note The SMTP Extension names/keywords registered in this section are for general use…
…ately, some widely deployed mail software interpreted "smtps" as "submissions" [RFC6409] and used that port for email submission by default when an end user requested security during account setup. If a new port is assigned for the submissions It should say: Historically, port 46…
…ately, some widely deployed mail software interpreted "smtps" as "submissions" [RFC6409] and used that port for email submission by default when an end user requested security during account setup. If a new port is assigned for the submissions It should say: Historically, port 46…