How do I setup Google Email Relay with Salesforce Hyperforce? Undeliverable: Dashboard
Undeliverable: Dashboard
Since our internal Cloud113 org has moved to HYPERFORCE, we have been updating our Google Admin / Email Relay settings in Salesforce and the Google Workspace Admin console. HYPERFORCE has a specific set of IP addresses to set as the allow list on the Google Relay Service. Since we have activated and are using Lightning, Enhanced Email, and Send Email through Gmail, we were surprised to see an email error when we expected to see Sales & Project Dashboards that we have subscribed to in Salesforce.
These Dashboard emails are very important to our team…why were they failing?
We found that the Google Email Relay we initially set up is responsible for handling non-end user emails from the Salesforce Platform. So my quest began to figure out why they were failing, and how to fix them. It’s actually really simple. Salesforce has posted a HYPERFORCE-specific list to allow. We don’t have the ability to allow domains in Google as a sender, but rather IP addresses. While this is not the most scalable solution, this is the fastest way to get our Dashboard Emails back online and running.
Feel free to copy these for easy entry into Google. You can also find them in this Salesforce help article: https://help.salesforce.com/s/articleView?id=000388992&type=1
HYPERFORCE – Email Relay USA
This list is easy to copy / paste.
3.136.176.246 3.211.218.161 18.116.99.79 18.223.105.148 44.234.243.86 44.236.41.178 44.237.70.168 44.238.67.234 52.13.153.245 52.13.32.219 52.88.39.26 52.201.77.107 54.148.13.220 54.166.102.102 100.21.3.223 |
Here’s how to add them to Google
- Login to your Admin Panel
- Navigate to Apps > Google Workspace > Setting for Gmail > Routing
- Scroll down to SMTP relay service
- Click: ADD ANOTHER RULE
We named the rule to SFDC – Hyperforce (https://help.salesforce.com/s/articleView?id=000388992&type=1) and it didn’t error! Great. Now we have a documented reference without looking it up somewhere else.
Now it’s on our blog. That’s big-brained, that’s !+!=#