FINAL NOTIFICATION: SPF Configuration Error | Community
Skip to main content
A
Anonymous
August 18, 2015
Solved

FINAL NOTIFICATION: SPF Configuration Error

  • August 18, 2015
  • 1 reply
  • 3487 views

Hi!

Yesterday i've received one notification with the title "FINAL NOTIFICATION: SPF Configuration Error". What this means?

SPF information for youlead.pt is not configured correctly in the domain's DNS record.

SPF status it's always saying "Pending Configuration" after several attempts to make it valid.

How can i validade it? What information should i enter to solve the error?

Thanks,

David Pereira

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Justin_Cooperm2

    SPF should be setup for any domain that you are sending email through Marketo with. You do this by adding an SPF record to your domain's DNS record. This declares to the world that the domain owner has authorized Marketo's servers to send email on behalf of this domain. If you don't set it up, it doesn't mean that Marketo won't send out your email. It just means that recipient email services are more likely to immediately put your message in the SPAM folder.

    Best practice is to have both DKIM and SPF setup for your domain:

    • SPF assure the recipient that the domain owner has authorized the sending server to send mail for the domain.
    • DKIM assures the recipient that the contents of the message were not altered during transit.

    Full instructions can be found here: https://docs.marketo.com/display/DOCS/Set+up+SPF+and+DKIM+for+your+Email+Deliverability

    1 reply

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    August 18, 2015

    If you're sending email from youlead.pt, best practice is to have an SPF TXT record, and you should indeed have one to protect person-to-person email (i.e. email sent via Outlook.com in your particular case). 

    You don't need your SPF set up for Marketo-to-person mail, though.  So I'd just ignore it.  I see you do have the Marketo DKIM record M1._domainkey.youlead.pt set up, and if that's shown as validated in Marketo, that's far more important.

    To set up your SPF record for youlead.pt, you need to account for all servers that may send with MAIL FROM: <*@youlead.pt>.  While this may only be Outlook.com, you must do a real inventory to be sure (for example, if you use another ESP or any other outbound mailserver, that must be listed as well).

    Justin_Cooperm2
    Justin_Cooperm2Accepted solution
    Level 10
    August 19, 2015

    SPF should be setup for any domain that you are sending email through Marketo with. You do this by adding an SPF record to your domain's DNS record. This declares to the world that the domain owner has authorized Marketo's servers to send email on behalf of this domain. If you don't set it up, it doesn't mean that Marketo won't send out your email. It just means that recipient email services are more likely to immediately put your message in the SPAM folder.

    Best practice is to have both DKIM and SPF setup for your domain:

    • SPF assure the recipient that the domain owner has authorized the sending server to send mail for the domain.
    • DKIM assures the recipient that the contents of the message were not altered during transit.

    Full instructions can be found here: https://docs.marketo.com/display/DOCS/Set+up+SPF+and+DKIM+for+your+Email+Deliverability

      SanfordWhiteman
      SanfordWhiteman
      Level 10
      August 19, 2015

      SPF governs the MAIL FROM (envelope sender).  Marketo uses MAIL FROM <*@mktomail.com>, so the SPF record for the customer domain isn't consulted.  It's easily verified that an SPF pass for Marketo-generated email is possible without any SPF record at all for the customer-operated domain, or with an ostensibly "failing" SPF record, since the record for mktomail.com is used.  (Unless there is some other type of subscription where you use the customer domain in the MAIL FROM.)

      Terms & ConditionsAccessibility statement

      Loading footer...