Loading

How MX records work with email delivery

Publiseringsdato: Nov 22, 2023
Beskrivelse
This information is applicable to both Lightning Experience and Salesforce Classic.

Salesforce like any other mail application tries to deliver mail to the hosts specified in the MX records for the domain in the recipients email address. For example, considering the email address test@salesforce.com the sending MTA (Mail Transfer Agent) uses DNS to look up the MX record associated with the Salesforce domain and make an SMTP connection to the MTA with the lowest MX priority. MX records can be checked from most machines using the command line however this is the view of DNS you are getting from your domain that could be different to the DNS information available to users on the internet. To validate a more global view of DNS try a tool such as MXtoolbox to check MX records.
Løsning
MXtoolbox example:
http://mxtoolbox.com/SuperTool.aspx?action=mx%3asalesforce.com&run=toolpage

MTAs always try to deliver to the MX record with the lowest preference in the MX list. When they cannot deliver to this MX they try to deliver to the one with the next highest preference. When MTAs cannot deliver to any legitimate MX record for the domain they attempt delivery at increasing intervals for periods from about 4 hours up 72 hours depending on how the MTA has been configured. Salesforce MTAs do this for up to approximately 24 hours.

If organizations are using email relaying in Salesforce, our MTAs do not use MX records as with normal delivery. They only send mail to the MX record, hostname, or IP address in the email relay settings (IP addresses are not recommended). A best practice is to use an MX record in the email relay settings area in Salesforce or a hostname however a hostname only represents one specific MTA and doesn't offer the redundancy that using an MX record does.
Knowledge-artikkelnummer

000386476

 
Laster
Salesforce Help | Article