---
schema_version: "1"
id: c2f7bb3ff26e079aa5a4deaf5a8cd3792cb27348e8c3ed1306006937767bc1e7
title: Enable Email Security Compliance
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/emailadmin_enable_email_security_compliance.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.emailadmin_enable_email_security_compliance.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1f82675bf121b5b61b2f753468f4a55044c78ceb360d86a5575cdb6fab3135ef
description: Email Security Compliance updates the envelope from address in emails sent from Salesforce. With this feature enabled, the email header from address is your email address, but the envelope from address is *.bnc.salesforce.com. Salesforce’s Sender Policy Framework (SPF) record authorizes the IPs used by our message transfer agents (MTAs) to send email from our domain. Email sent from Salesforce passes SPF checks even if you don’t have an SPF record for your email domain.
products:
  - Security
release: "264"
---
# Enable Email Security Compliance

Email Security Compliance updates the envelope from address in emails sent from Salesforce. With this feature enabled, the email header from address is your email address, but the envelope from address is `*.bnc.salesforce.com`. Salesforce’s Sender Policy Framework (SPF) record authorizes the IPs used by our message transfer agents (MTAs) to send email from our domain. Email sent from Salesforce passes SPF checks even if you don’t have an SPF record for your email domain.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: all editions except <strong>Database.com</strong></td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permissions">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d106190e63">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d106190e63 ">To configure email deliverability:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d106190e63 ">Customize Application</td>

          </tr>
        </tbody>
      </table>

1. From [Setup](https://help.salesforce.com/s/articleView?id=xcloud.basics_nav_setup.htm&type=5&language=en_US), use the Quick Find box to find and select **Deliverability**.
2. In the Email Security Compliance (Emails from Salesforce or Email Relay Only) section, select **Enable compliance with standard email security mechanisms**.
3. Optionally, select **Enable Sender ID compliance** to have receiving mail servers use the Sender ID email authentication protocol to verify the sender. This setting also populates the Sender field in the envelope of every email you send from Salesforce with no-reply@salesforce.com. If you enable this option, the recipient's email client may append the phrase “Sent on behalf of” to the “From:” field of emails received from Salesforce.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-security-264-0-0-production-enus/8cecd769-ab2d-4e07-addf-c4f2927925e1/images/icon_note.png)
    
    Note If your Salesforce org was created in Summer '24 or later, you can't enable Sender ID compliance in Email Deliverability settings. Most recipients don’t use Sender ID anymore. Unless you know that the recipient of your email requires Sender ID, we don’t recommend that you enable this feature. See [Microsoft Exchange’s article on Sender ID](https://docs.microsoft.com/en-us/exchange/antispam-and-antimalware/antispam-protection/sender-id?view=exchserver-2019) for more information.
4. Click **Save**.

#### See Also

- [Sender Policy Framework (SPF)](https://help.salesforce.com/s/articleView?id=xcloud.emailadmin_spf_overview.htm&release=264.0.0&type=5 "The Sender Policy Framework (SPF) email authentication method aims to reduce spam and fraud by making it harder for email senders to hide their identity. SPF detects email spoofing by providing a process to verify who is permitted to send emails on your behalf. SPF improves message deliverability, protects the credibility and reputation of your domains, and enhances user trust and confidence. Salesforce uses SPF and recommends that you do, too.")