Attention: The Marketo Community will undergo scheduled maintenance on Tuesday, August 20th between 10-11 PM PDT. During this time, the Community and its content will not be accessible. We apologize for any inconvenience this may cause.
Why: SPF information for ArezzoSky.com is not configured correctly in the domain's DNS record
What to do now?
Contact your IT resource that maintains the DNS record for ArezzoSky.com. Ensure SPF is configured correctly, referring to Marketo documentation if needed.
Does Anyone know how to solve this error.
Regards,
Abhi
Solved! Go to Solution.
Hi Abhijit,
It looks like you have not correctly added Marketo to your SPF record. Currently, you have the following:
TXT | arezzosky.com | 60 min | v=spf1 a mx include:websitewelcome.com ~all |
Which, to break this down, means you've allowed your website (the a listed), your normal email provider, and websitewelcome.com authority to send emails with the arezzosky.com domain—but not Marketo! Go into your Hostgator cPanel, and you should find something like "DNS Zone Editor." You'll want to edit the TXT record you see me mention above to be v=spf1 a mx include:websitewelcome.com include:mktomail.com ~all. In fact, while you're in there, you may want to fix your DKIM key for m1 (Marketo)—it's currently returning as invalid. 😕
Did you check your DNS record and the instructions?
You did not provide the SPF text you used.
Hi Abhijit,
It looks like you have not correctly added Marketo to your SPF record. Currently, you have the following:
TXT | arezzosky.com | 60 min | v=spf1 a mx include:websitewelcome.com ~all |
Which, to break this down, means you've allowed your website (the a listed), your normal email provider, and websitewelcome.com authority to send emails with the arezzosky.com domain—but not Marketo! Go into your Hostgator cPanel, and you should find something like "DNS Zone Editor." You'll want to edit the TXT record you see me mention above to be v=spf1 a mx include:websitewelcome.com include:mktomail.com ~all. In fact, while you're in there, you may want to fix your DKIM key for m1 (Marketo)—it's currently returning as invalid. 😕
(Of course, the SPF record for arezzosky.com is irrelevant for mail with an envelope sender @*.mktomail.com anyway...)