Hi @JBrenna,
unfortunately, I couldn’t join the Admin HUG on this topic and pose my question there but you said you’re following the community article and this would be the best way to reach you. So, I’ hoping you can help with our dilemma.
We have a bit of a struggle with these updates internally as our IT doesn’t want to add SPF for HubSpot to our top level domains (internal policy, no exceptions).
However, we have a few use cases for which we need to send from our TLDs instead of a subdomain as we usually do.
One would be using our marketeers’ actual email addresses (firstname.lastname@company.com) as the from address by using personalization token {owner.email} to send out automated marketing emails.
Side note: The personal email addresses are also connected by the users in HubSpot, not sure if this makes a difference here.
For the TLDs, DKIM and DMARC are added but no SPF for HubSpot.
As the Google and Yahoo updates states, without SPF they would be blocked or sent to SPAM.
However, when we ran a test and send out one of those emails to ourselves, we received an SPF pass for the sender IP.
We did a separate SPF check and actually, this domain/ sender IP is not authorized in regard to SPF.
We’re fairly confused now as to why the email received an SPF pass by the receiving provider when it doesn’t have SPF.
Any idea why?