2016
DOI: 10.17487/rfc7817
|View full text |Cite
|
Sign up to set email alerts
|

Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related Protocols

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0

Year Published

2018
2018
2021
2021

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(8 citation statements)
references
References 21 publications
0
8
0
Order By: Relevance
“…• The STARTTLS extension [16], [19] to SMTP allows the use of TLS in communications between SMTP clients and servers. Specifically for MTA-to-MTA communication, every inbound MTA that supports this extension announces it by including the keyword "STARTTLS" in the response to the SMTP Extended Hello ("EHLO") command issued by the outbound MTA.…”
Section: B Email Security Standardsmentioning
confidence: 99%
“…• The STARTTLS extension [16], [19] to SMTP allows the use of TLS in communications between SMTP clients and servers. Specifically for MTA-to-MTA communication, every inbound MTA that supports this extension announces it by including the keyword "STARTTLS" in the response to the SMTP Extended Hello ("EHLO") command issued by the outbound MTA.…”
Section: B Email Security Standardsmentioning
confidence: 99%
“…Clients MUST implement the certificate validation mechanism described in [RFC7817]. Once the TLS session is established, POP3 [RFC1939] protocol messages are exchanged as TLS application data for the remainder of the TCP connection.…”
Section: Implicit Tls For Popmentioning
confidence: 99%
“…Clients MUST implement the certificate validation mechanism described in [RFC7817]. o All Mail Access Servers and Mail Submission Servers implementing TLS SHOULD log TLS cipher information along with any connection or authentication logs that they maintain.…”
Section: Implicit Tls For Imapmentioning
confidence: 99%
See 2 more Smart Citations