Route Email Through AWS Direct Connect (DX) for Hyperforce

Configure an Email Relay and Email Domain Filter

These steps are described in detail in Set Up Email Relay and Set Up an Email Domain Filter. You can follow these abbreviated instructions to configure an email relay and domain filter for each of your email domains. Read the articles for more complete information.

This example uses yourdomain.com as the host.

Configure the Email Relay

1. From Setup, in the Quick Find box, enter Email Relays, and select Email Relays.
2. Select Create Email Relay.
3. For Host, enter the hostname, yourdomain.com. Accept the other defaults or customize the values according to  Set Up Email Relay, then save.
   
     

Configure the Domain Filter

1. From Setup, in the Quick Find box, enter Email Domain Filters, and then select Email Domain Filters.
2. Select Create Email Domain Filter.
3. Configure these settings with these values:
   1. Sender Domain: *
   2. Recipient Domain: yourdomain.com
   3. Email Relay: Select the Email Relay created in the previous step.
   4. Active: Check the box
4. Save the page.
   
    

If you have multiple email domains, repeat these steps to route each domain to its own relay.

If you prefer to route multiple domains to the same relay, enter the domains in Recipient Domain of the email filter, separated by commas. In this example, yourdomain.com, yourdomain.au, and yourdomain.eu all route to the same relay.

Get IP Addresses for Your Email Relay

After you configure the email relay and domain filter, you must add Hyperforce email IP addresses to your router’s allowlist. The article Ensure you can receive email from the Salesforce application contains a table of IPs used for email relay MTAs for Hyperforce instances, organized by country. Allow all of the IPs specified for your country. If you’re not sure of your country, read Where is my Salesforce instance located? The first 3 letters of your instance name are your country.

Test Your Email Relay Configuration

Before enabling your email relay configuration in production, test it in a sandbox organization to make sure the configuration is valid and mail flows smoothly. After you've validated the sandbox configuration, you can turn on the same configuration in production. 

Here are some scenarios you can use to test your email setup.

• Outbound System Emails from Salesforce
  • Make sure you can receive emails that Salesforce sends to your users. For example:
  • Create a new user in one of the configured relay domains and check if you get a welcome email
  • Reset a user's password in one of the configured relay domains and check if you get a password reset email
• Outbound User Emails
  • Send an email to a user in one of the configured relay domains and make sure they can receive it.
• Inbound Emails
  • Create an inbound email service, like email2apex or email2case.
  • Send an inbound email to the service you created and make sure it routes to the Salesforce network correctly.

As you test each scenario, confirm the expected results by checking the email logs. You can read more about email logs in Use Email Logs to Monitor Emails Sent from Salesforce.

• Outbound Verifications
  • Check that the recipient received the email and that it was routed correctly. 
  • Make sure the relay address is filled out and matches your expectations. 
  • Confirm that the email domain of the recipient matches the relay rules you set up. 
  • Verify that the email was delivered by checking for a log line with Mail_Event=D. 
  • Check that the remote host is the IP of the relay that you configured in the relay rules.
    
    
• Inbound Verifications
  • Make sure the inbound email was received, routed, and processed by Salesforce correctly. 
  • Check that there's at least one Mail_Event=R and one Mail_Event=D log line for the message that you sent to the email services address. There can be more than one log line for a single inbound email, if the system forwarded the email through several internal steps.

Regenerate Inbound Email Service Addresses

If you generated inbound email service addresses while your org was in our first-party datacenters, your inbound mail continues to route through the first-party datacenter even after your org migrates to Hypeforce. To route inbound emails exclusively through Hyperforce, regenerate your service addresses after the migration.

See the knowledge article Recreate error free inbound routing addresses for detailed instructions on regenerating your inbound email service addresses.