Loading
Sales Productivity
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Set Up Email Relay

            You are here:

            1. Salesforce Help
            2. Docs
            3. Seller Productivity

            Set Up Email Relay

            You can set up an email relay for Salesforce-generated email by configuring Salesforce to automatically route email through your company’s Simple Mail Transfer Protocol (SMTP) server. If your company sends email from more than one email domain, you can configure an email relay for each domain.

            Required Editions

            Available in: Salesforce Classic and Lightning Experience
            Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions
            User Permissions Needed
            To configure email relay: Email Administration, Customize Application, and View Setup

            If you plan to activate bounce management and email compliance management, confirm with your email admin that your company allows relaying email sent from Salesforce.

            1. From Setup, in the Quick Find box, enter Email Relays, and select Email Relays.
            2. Select Create Email Relay.
            3. For Host, enter a mail domain, hostname or IP address.
              If you provide a name, Salesforce checks for valid Domain Name Service (DNS) mail exchange (MX) records first. If none are found, we look for a DNS Address (A) record. If you plan to use Transport Layer Security (TLS) with this connection, enter the hostname instead of the IP address. TLS requires the hostname for verifying certificates.

              Here are examples of valid formats.

              • Mail domain: myemaildomain.com
              • Mail server hostname: mail.myemaildomain.com
              • IP address: 100.121.20.5
            4. For Port, enter the number of your company’s SMTP server.
              Obtain this information from your email administrator. Email relaying is supported on port numbers 25, 587, 10025, and 11025.
            5. Select a TLS Setting. This setting controls whether Salesforce uses TLS for SMTP sessions.
              • Off—TLS is turned off. SMTP session continues through an insecure connection.
              • Preferred—If the remote server supports TLS, Salesforce upgrades the current SMTP session to use TLS. If TLS is unavailable, Salesforce continues the session without TLS. This setting is the default.
              • Required—Salesforce continues the session only if the remote server supports TLS. If TLS is unavailable, Salesforce terminates the session without delivering the email.
              • Preferred Verify—If the remote server supports TLS, Salesforce upgrades the current SMTP session to use TLS. Before the session begins, Salesforce verifies that a valid certificate authority has signed the certificate and that the common name presented in the certificate matches the domain or mail exchange of the current connection. If TLS is available but the certificate isn’t signed or the common name doesn’t match, Salesforce disconnects the session and doesn’t deliver the email. If TLS is unavailable, Salesforce continues the session without TLS.
              • Required Verify— Salesforce continues the session only if the remote server supports TLS, a valid certificate authority has signed the certificate, and the common name presented in the certificate matches the domain or mail exchange to which Salesforce is connected. If any of these criteria aren’t met, Salesforce terminates the session without delivering the email.
              If you use TLS verification, an MX or an A record for your hostname is required in Public DNS. Canonical Name (CNAME) DNS records can’t be used for relays with TLS verification.
            6. Optionally, to enable authentication with a username and password for this email relay.
              1. Select Enable SMTP Auth.
                When you enable this setting, the TLS Setting changes to the required value, Required Verify.
              2. In the Auth Type field, select a Simple Authentication and Security Layer (SASL) mechanism to use for SMTP authentication.
                • To use the PLAIN SASL mechanism, select Auth Plain. This is the default Auth Type when you enable SMTP Auth.
                • To use the LOGIN SASL mechanism, select Auth Login.

                Salesforce supports only the PLAIN and LOGIN SASL mechanisms.

              3. For Username, enter the username for SMTP authentication.
              4. For Password, enter the password for SMTP authentication.
              5. In the Confirm Password field, reenter the password for SMTP authentication.

              Before you enable SMTP authentication, test this feature in a sandbox to ensure that it works as expected with your email relay. Some email services don’t support SMTP authentication for email relays.

              If you deselect Enable SMTP Auth, Salesforce saves your authentication credentials but doesn’t route email to your company’s email server using SMTP authentication.

            7. Save your changes.
            8. Set up an email domain filter. You must set up an email domain filter for email relay to work.

            Salesforce recommends that you send a test message each time you change the email relay configuration.

            If you set up multiple email relays in one org, they’re processed in the priority order of their email domain filters. By default, email domain filters are evaluated in the order that they were created. To change the evaluation order, use the PriorityNumber field on the EmailDomainFilter object SOAP API. If no matching rule for email relay is found, then the email is sent via the Salesforce Mail servers.

            See Also

             
            Loading
            Salesforce Help | Article