Use DNS SRV records for automatic mail services discovery #228

New Issue

Manos Pitsidianakis · 2023-06-17T22:29:59+03:00

2023-06-17 22:29:59 +03:00

From RFC8314 Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access:

https://datatracker.ietf.org/doc/html/rfc8314#section-5

MUAs SHOULD be capable of using DNS SRV records to discover Mail
Access Servers and Mail Submission Servers that are advertised by
an MSP for an account being configured. Other means of
discovering server configuration information (e.g., a database
maintained by the MUA vendor) MAY also be supported. (See
Section 5.1 for more information.)

From **RFC8314** *Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access*: https://datatracker.ietf.org/doc/html/rfc8314#section-5 > MUAs SHOULD be capable of using DNS SRV records to discover Mail Access Servers and Mail Submission Servers that are advertised by an MSP for an account being configured. Other means of discovering server configuration information (e.g., a database maintained by the MUA vendor) MAY also be supported. (See Section 5.1 for more information.)

Manos Pitsidianakis added the

enhancement

IMAP

User Experience

labels 2023-06-17 22:29:59 +03:00

Manos Pitsidianakis commented

2023-06-17 22:33:13 +03:00

Poster

From RFC6186 Use of SRV Records for Locating Email Submission/Access Services

https://datatracker.ietf.org/doc/html/rfc6186

By using SRV records as above, MUAs need initially only to prompt the
user for their email address [RFC5322]. The "local-part" and
"domain" portions are then extracted from the email address by the
MUA. The MUA uses the "domain" portion as the service domain to
perform SRV lookups for the services it wants to configure. If the
SRV lookup is successful, the target FQDN and port for the service
can be determined and used to complete MUA configuration. If an SRV
record is not found, the MUA will need to prompt the user to enter
the FQDN and port information directly, or use some other heuristic.
In the case of multiple SRV records returned for a particular
service, the MUA MUST use the priority and weight fields in the
record to determine which one to use (as per [RFC2782]).

From **RFC6186** *Use of SRV Records for Locating Email Submission/Access Services* https://datatracker.ietf.org/doc/html/rfc6186 > By using SRV records as above, MUAs need initially only to prompt the user for their email address [RFC5322]. The "local-part" and "domain" portions are then extracted from the email address by the MUA. The MUA uses the "domain" portion as the service domain to perform SRV lookups for the services it wants to configure. If the SRV lookup is successful, the target FQDN and port for the service can be determined and used to complete MUA configuration. If an SRV record is not found, the MUA will need to prompt the user to enter the FQDN and port information directly, or use some other heuristic. In the case of multiple SRV records returned for a particular service, the MUA MUST use the priority and weight fields in the record to determine which one to use (as per [RFC2782]).

Manos Pitsidianakis added this to the RFC8314 Cleartext Considered Obsolete project 2023-08-11 21:06:57 +03:00

Manos Pitsidianakis added the

Retired

label 2023-09-07 15:57:10 +03:00

Manos Pitsidianakis closed this issue

2023-09-07 15:57:18 +03:00

Sign in to join this conversation.