…tus Codes RFC2034 None RFC2034 RFC2034 IETF SHOULD IETF IETF STARTTLS Start TLS RFC3207 None RFC3207 RFC3207 IETF MAY IETF IETF NO-SOLICITING Notification of no soliciting RFC3865 Soliciting-keywords RFC3865 RFC3865 IETF MAY IETF IETF MTRK Message Tracking RFC3885 RFC3885 RFC3885…

…tus Codes RFC2034 None RFC2034 RFC2034 IETF SHOULD IETF IETF STARTTLS Start TLS RFC3207 None RFC3207 RFC3207 IETF MAY IETF IETF NO-SOLICITING Notification of no soliciting RFC3865 Soliciting-keywords RFC3865 RFC3865 IETF MAY IETF IETF MTRK Message Tracking RFC3885 RFC3885 RFC3885…

… and AUTH | [ RFC4954 ] [ RFC6531 ] | | UTF8SMTPS | ESMTP with SMTPUTF8 and | [ RFC3207 ] [ RFC6531 ] | | | STARTTLS | | | UTF8SMTPSA | ESMTP with SMTPUTF8 and both | [ RFC3207 ] [ RFC4954 ] | | | STARTTLS and AUTH | [ RFC6531 ] | | UTF8LMTP | LMTP with SMTPUTF8 | [ RFC6531 ] | |…

…PUTF8 and AUTH | [RFC4954] [RFC6531] | | UTF8SMTPS | ESMTP with SMTPUTF8 and | [RFC3207] [RFC6531] | | | STARTTLS | | | UTF8SMTPSA | ESMTP with SMTPUTF8 and both | [RFC3207] [RFC4954] | | | STARTTLS and AUTH | [RFC6531] | | UTF8LMTP | LMTP with SMTPUTF8 | [RFC6531] | | UTF8LMTPA …

… and AUTH | [ RFC4954 ] [ RFC6531 ] | | UTF8SMTPS | ESMTP with SMTPUTF8 and | [ RFC3207 ] [ RFC6531 ] | | | STARTTLS | | | UTF8SMTPSA | ESMTP with SMTPUTF8 and both | [ RFC3207 ] [ RFC4954 ] | | | STARTTLS and AUTH | [ RFC6531 ] | | UTF8LMTP | LMTP with SMTPUTF8 | [ RFC6531 ] | |…

… with SMTP AUTH | [RFC4954] [RFC5336] | | UTF8SMTPS | UTF8SMTP with STARTTLS | [RFC3207] [RFC5336] | | UTF8SMTPSA | UTF8SMTP with both | [RFC3207] [RFC4954] | | | STARTTLS and SMTP AUTH | [RFC5336] | +---------------+----------------------------+----------------------+ 5. Securit…

… SMTP AUTH | [ RFC4954 ] [ RFC5336 ] | | UTF8SMTPS | UTF8SMTP with STARTTLS | [ RFC3207 ] [ RFC5336 ] | | UTF8SMTPSA | UTF8SMTP with both | [ RFC3207 ] [ RFC4954 ] | | | STARTTLS and SMTP AUTH | [ RFC5336 ] | +---------------+----------------------------+----------------------+ .…

…C 8461 MTA-STS September 2018 1 . Introduction The STARTTLS extension to SMTP [ RFC3207 ] allows SMTP clients and hosts to negotiate the use of a TLS channel for encrypted mail transmission. While this opportunistic encryption protocol by itself provides a high barrier against pa…

…d non-TLS clients; the use of TLS is negotiated via the SMTP STARTTLS command [ RFC3207 ]. The server signals TLS support to the client over a cleartext SMTP connection, and, if the client also supports TLS, it may negotiate a TLS-encrypted channel to use for email transmission. …

…or the use of email protocols with TLS used the STARTTLS mechanism: [RFC2595], [RFC3207], and [RFC3501]. With STARTTLS, the client establishes a cleartext application session and determines whether to issue a STARTTLS command based on server capabilities and client configuration.…

…the use of email protocols with TLS used the STARTTLS mechanism: [ RFC2595 ], [ RFC3207 ], and [ RFC3501 ]. With STARTTLS, the client establishes a cleartext application session and determines whether to issue a STARTTLS command based on server capabilities and client configurati…

…n name that is the domain name that the client thought it was connecting to." [ RFC3207 . MAY WISH TO The phrase "MAY WISH TO" indicates a behavior that might seem appealing to some people, but which is regarded as ridiculous or unnecessary by others. This phrase is frequently us…

… protection standards available. Examples of such mechanisms include SMTP-TLS [ RFC3207 ], SMTP-Auth [ RFC4954 ], OpenPGP RFC4880 ], and S/MIME [ RFC3851 ]. The core of the Internet Mail architecture does not impose any security requirements or functions on the end-to-end or hop-…

…and without Transport Layer Security (TLS) [ RFC5246 ] as defined for SMTP in [ RFC3207 ]. Example: service record _submission._tcp SRV 0 1 587 mail.example.com. 3.2 . IMAP This specification adds two SRV service labels for IMAP [ RFC3501 ]: _imap: Identifies an IMAP server that …

…apply to the sections of rfc 2487, but the links in https://tools.ietf.org/html/rfc3207#page-8 point back to the section numbers in RFC 3207. Either the section numbers referred to should be RFC 3207 numbers (the correction i'm proposing here), or the links within the HTML versio…