…with Service Extensions RFC-ietf-emailcore-rfc5321bis-43 ESMTPA ESMTP with AUTH RFC3848 ESMTPS ESMTP with STARTTLS RFC3848 ESMTPSA ESMTP with both STARTTLS and AUTH RFC3848 LMTP Local Mail Transfer Protocol RFC3848 LMTPA LMTP with AUTH RFC3848 LMTPS LMTP with STARTTLS RFC3848 LMT…

…with Service Extensions RFC-ietf-emailcore-rfc5321bis-43 ESMTPA ESMTP with AUTH RFC3848 ESMTPS ESMTP with STARTTLS RFC3848 ESMTPSA ESMTP with both STARTTLS and AUTH RFC3848 LMTP Local Mail Transfer Protocol RFC3848 LMTPA LMTP with AUTH RFC3848 LMTPS LMTP with STARTTLS RFC3848 LMT…

…ording TLS Ciphersuite in "Received" Header Field The ESMTPS transmission type [RFC3848] provides trace information that can indicate that TLS was used when transferring mail. However, TLS usage by itself is not a guarantee of confidentiality or security. The TLS ciphersuite prov…

…rding TLS Ciphersuite in "Received" Header Field The ESMTPS transmission type [ RFC3848 ] provides trace information that can indicate that TLS was used when transferring mail. However, TLS usage by itself is not a guarantee of confidentiality or security. The TLS ciphersuite pro…

…their use should be reflected in the trace field WITH keywords as appropriate [ RFC3848 ]. 3.2 . The SMTPUTF8 Extension An SMTP server that announces the SMTPUTF8 extension MUST be prepared to accept a UTF-8 string [ RFC3629 ] in any position in which RFC 5321 specifies that a <m…

… their use should be reflected in the trace field WITH keywords as appropriate [RFC3848]. 3.2. The SMTPUTF8 Extension An SMTP server that announces the SMTPUTF8 extension MUST be prepared to accept a UTF-8 string [RFC3629] in any position in which RFC 5321 specifies that a <mailb…

…their use should be reflected in the trace field WITH keywords as appropriate [ RFC3848 ]. 3.2 . The SMTPUTF8 Extension An SMTP server that announces the SMTPUTF8 extension MUST be prepared to accept a UTF-8 string [ RFC3629 ] in any position in which RFC 5321 specifies that a <m…