When Salesforce sends an email, it uses DNS (Domain Name System) to look up the MX (Mail Exchange) records for the recipient's email domain. MX records specify which mail servers accept incoming email for that domain.
For example, when sending to test@salesforce.com, the Salesforce MTA (Mail Transfer Agent) performs a DNS lookup for the salesforce.com domain, finds its MX records, and attempts an SMTP (Simple Mail Transfer Protocol) connection to the mail server with the lowest MX priority number.
You can check MX records from most machines using a command-line DNS lookup. However, command-line results reflect the DNS view from your local network, which may differ from what is visible to users on the public internet.
To validate a global view of MX records, use an external tool such as MXtoolbox (see Additional Resources).
This information applies to both Lightning Experience and Salesforce Classic.
MTAs (Mail Transfer Agents) always attempt delivery to the MX record with the lowest preference number first. If delivery to that MX record fails, the MTA tries the next record in the list with the next highest preference number.
When an MTA cannot deliver to any legitimate MX record for the domain, it retries delivery at increasing intervals. Retry periods typically range from approximately 4 hours to 72 hours, depending on how the sending MTA is configured. Salesforce MTAs retry delivery for up to approximately 24 hours.
If your organization uses email relaying in Salesforce, Salesforce MTAs do not use standard MX record lookups for delivery. Instead, they send email only to the MX record, hostname, or IP address specified in the Email Relay settings in Salesforce.
Best practice: Use an MX record (not an IP address) in the Salesforce Email Relay settings. An MX record provides redundancy by pointing to multiple mail servers, whereas a hostname represents only one specific MTA with no failover.
000386476

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.