Hi,
I am in the process of setting up SPF and DKIM for our domain. We have recently set up with Google Workspace and have linked it to Hubspot.
Will emails that we send from the Hubspot CRM still be tehcnicaly be sent via Google? Do I need to add at record for Google and Hubspot?
Thank you!
Hi @RebelHealth1 ,
When you set up SPF and DKIM for your domain, you’re essentially configuring your domain’s DNS records to authenticate your outgoing emails. These authentication mechanisms help prevent email spoofing and enhance the deliverability of your emails.
Your emails will be sent with whatever the email sending domain your are connecting with your HubSpot.
Hope this helps!
Thanks.
Much appreciated. Thank you for the clarification.
So you do set it up as v=spf1 include:_spf.google.com -all or v=spf1 include:5414923.spf10.hubspotemail.net +all I am confused???
Need to know the same thing if anyone can help!
Any luck on a solution?
Disappointgly no. HubSpot told me to switch domain providers in order to resolve. We don’t want to do that for multiple clients on Google Workspace and so are monitoring to see how Google treat the issue in the real world.
I found a solution. Although sloppy, it got me authenticated and seemed to work.
Hi George,
You’ll actually need both; as you send emails from both.
"v=spf1 include:_spf.google.com include:5414923.spf10.hubspotemail.net ~all"
note how in my example you have both HubSpot and Google authorised to send emails… I also changed to ~All.
The issue is,
in google domain,
when you set it up for google workspace, you can not remove/edit the SPF record.
You only can add a new record but when I did, it does not override the one from google workspace.
So the tool says, multiple SPF are found and it is an error
We don’t have an option to delete google workspace SPF record in google domain
that’s the issue
What I found afterword is that it works even when there are multiple records.
But not so sure if this is okay to do so long term.
You can view Google Workspace’s documentation on setting up multiple SPF records: Set up SPF | Apps & integrations | Google Workspace Help
Based on this I ended up configuring with:
v=spf1 include:_spf.google.com include:[YOUR_HUBSPOT_ID_HERE].spf05.hubspotemail.net ~all
After completing the setup, you can verify your spf records through this tool: SPF Check & SPF Lookup - Sender Policy Framework (SPF) - MxToolBox
It should list both your HubSpot spf records and your Google spf records with a label of “Pass”
Hope this helps. Also note that correct DMARC and MX records are required for the email sending through Google Workspace to work correctly
This is what I ended up doing and it worked as well!
@franzwilhelm The issue I’m running into is that Google Domains won’t let me modify the SPF record. I’m using HubSPot, Google Workspace and Google Domains.
The base Google spf is set auto-magically and while I can add aditional records, I have not found the secret to editing the actual record we need to update to include HubSpot. Suggestion?
Hello -
What you need to do is add a new record - a TXT record.
Should be straightforward; Navigate to DNS Tab, click “Add” and select the record type as “TXT” - then you need to paste your SPF records.
IF you already have another TXT record (which most people will for site verification) you’ll need to add it on a separate line of the existing TXT record.
You can only have one TXT record per site.
I appreciate that it should be straightforward… Yes, I can add a new TXT
record but that doesn’t update the SPF record a few lines down (Google
won’t allow that to be edited via the Manage button. What am I missing?
[image: 286C0DCB-B4F8-4209-AD5E-C44DCD6F7454_1_201_a.jpeg]
Hi Gudorf,
Your image wasn’t added.
I am assuming, Google has a fake DNS record for SPF to add their records automatically; this is likely just appended to their real record.
In any case, if you CAN add a new TXT record, add it there.
You can then test your records using https://whatsmydns.net (this will also help speed up the propagation).
And, failing a solution, I’d move off Google Domains DNS.
- It’s deprecated and closing down…
