What mail client discovery is for
When someone adds an email address to a mail app, the app needs more than the address and password. It must find a server for sending messages and a server for reading them, along with the right ports and connection security settings. DNS service records, usually called SRV records, provide one way for an app to discover those servers from the domain in the email address.
Discovery is not universal. Some mail apps check SRV records, while others use a provider-specific configuration service or ask the user to enter settings. Publishing correct records can make setup easier for compatible clients, but it does not guarantee automatic setup in every app. Keep clear manual setup instructions available as a fallback.
The SRV records for submission and IMAP
Mail submission is the service a client uses to send a message through its mail provider. The SRV name _submission._tcp.example.com can point clients toward a submission server, commonly on port 587. Incoming mail accessed through IMAP over an implicit TLS connection can be advertised at _imaps._tcp.example.com, commonly on port 993. Here, example.com represents the domain in the user's email address.
An SRV record supplies a priority, a weight, a port and a target hostname. For example, _submission._tcp.example.com could have the value 0 1 587 mail.example.com, while _imaps._tcp.example.com could have 0 1 993 mail.example.com. These values are illustrations, not settings to copy without checking your provider. A lower priority number is preferred; weight helps distribute choices among records with the same priority. The target should resolve to an address and should be a hostname rather than an IP address.
Ports, encryption and what DNS cannot promise
Port 587 typically starts a submission connection in plain text and then upgrades it with STARTTLS before credentials are sent. Port 993 uses TLS from the beginning of the IMAP connection. Other configurations exist, including implicit-TLS submission on port 465, which may be advertised using _submissions._tcp. An organization may also offer IMAP on port 143 with STARTTLS, but a client should not assume that an advertised port alone makes an unencrypted login safe.
An SRV record identifies a possible destination; it does not prove that the service is working, that TLS is configured correctly or that a particular authentication method is available. The client still needs to negotiate a secure connection and validate the server certificate against the name its connection rules require. DNS also does not publish a user's password. Never place credentials in an SRV record, a public setup page or a troubleshooting screenshot.
Do not confuse client settings with mail-routing records
An MX record tells other mail systems where to deliver messages addressed to a domain. It is not a reliable source for the server or port a person's mail app should use. The submission and IMAP servers might share a hostname with an MX server, but they do not have to. Likewise, SPF, DKIM and DMARC records support aspects of outgoing mail authorization and authentication; they do not tell an app how to read a mailbox.
If your mail provider supplies hostnames and ports, use those documented settings when creating discovery records. Check whether the provider supports SRV-based discovery and whether it uses a different setup method as well. A domain can have perfectly valid mail-routing records while automatic client setup remains unavailable or points to the wrong service.
A practical check before publishing
Start with the provider's confirmed submission and IMAP hostnames, ports and TLS modes. Add the relevant SRV records in the DNS zone for the email domain, then check that each record's name, port and target match the intended service. Confirm that the target hostname resolves and that the server accepts connections using the advertised security mode. If you offer multiple targets, make sure each is a usable alternative before assigning priorities and weights.
If setup fails, inspect the SRV answer directly and compare it with the provider's instructions. Then test the server connection separately: a correct DNS answer cannot fix an unavailable port, a certificate problem or rejected credentials. Finally, try a mail client known to use the discovery method you published. This helps distinguish a DNS mistake from an app that simply does not consult those records.



