Just to set some context here, what is failing here is SPF alignment, and not SPF authentication (which is what Google/Yahoo requires).
Absolutely understand that this may look concerning, but rest assured that it is actually expected for SPF alignment to fail because of how it works in HubSpot, but there aren't any issues as long as SPF authentication is fine (which seems to be fine in your situation).
The SPF failing is due to checking for 100% SPF alignment between the header From and the envelope From, which is only achievable with a Dedicated IP. You are currently still sending via HubSpot's shared email servers, so adding the SPF policy will add SPF authentication for your email sends via HubSpot.
When using some third-party DNS tools, you may notice a failure for the SPF protocol, which can occur when the from domain matches your domain but you're sending over a shared IP. You can safely ignore this failure if you've correctly set up DKIM and it aligns with your sending domain.
Rest assured that achieving 100% alignment is not necessary (and is even expected to fail for this particular case), and you should not see deliverability issues as a result of this as long as your DKIM is set up properly. You don't need to specifically add any other SPF records just to make it align, nor to ensure alignment.
I have the same issue. Has anyone been able to resolve the problem with the "envelope from" not matching the "from" in the email (even though all DNS settings are correct with the SPF text record) resulting in SPF failure due to DMARC alignment? The envelope always says hubspotemail.net, not mycompanydomain.com.
Just to set some context here, what is failing here is SPF alignment, and not SPF authentication (which is what Google/Yahoo requires).
Absolutely understand that this may look concerning, but rest assured that it is actually expected for SPF alignment to fail because of how it works in HubSpot, but there aren't any issues as long as SPF authentication is fine (which seems to be fine in your situation).
The SPF failing is due to checking for 100% SPF alignment between the header From and the envelope From, which is only achievable with a Dedicated IP. You are currently still sending via HubSpot's shared email servers, so adding the SPF policy will add SPF authentication for your email sends via HubSpot.
When using some third-party DNS tools, you may notice a failure for the SPF protocol, which can occur when the from domain matches your domain but you're sending over a shared IP. You can safely ignore this failure if you've correctly set up DKIM and it aligns with your sending domain.
Rest assured that achieving 100% alignment is not necessary (and is even expected to fail for this particular case), and you should not see deliverability issues as a result of this as long as your DKIM is set up properly. You don't need to specifically add any other SPF records just to make it align, nor to ensure alignment.
As a first step, I would recommend checking to see if your DKIM is successfully connected and using this tool to see if there are any SPF errors.
If you find an error, I would recommend connecting with HubSpot Technical Support, as Support is included in your subscription and they will be able to provide real-time assistance for this matter, where you are able to share screenshots and further information about this.
Best,
Kristen
Did you know that the Community is available in other languages? Join regional conversations by changing your language settings !
Thanks for reaching back out, and apologies for the delayed reply here! Sorry to hear you haven't been able to find a solution to this yet.
I would recommend connecting with HubSpot Technical Support. They wil be able to provide real-time assistance for this matter, where you are able to share screenshots and further information about this.'
Best,
Kristen
Did you know that the Community is available in other languages? Join regional conversations by changing your language settings !