DKIM and SPF settings | Community
Skip to main content
August 10, 2015
Solved

DKIM and SPF settings

  • August 10, 2015
  • 2 replies
  • 7349 views

Is it ok to have the DKIM setting verified and SPF configuration pending? Will this impact deliverability rate? the reason why i am asking this question is because i set up couple of domains in Marketo. While the DKIm status shows verified, SPF shows configuration pending. I tried working with the IT team but not able to fix this. I am concerned if this will impact my deliverability or is it ok?

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 SanfordWhiteman

... without an approved SPF - most things went straight to Spam.


I strongly doubt SPF was the cause because your SPF record is not consulted by the recipients of Marketo-generated emails (Marketo's SPF record for mktomail.com is used).*

On the other hand, if your DKIM setup was messed up enough that messages were signed, but failed signature verification -- that would cause rampant failures.

* Bad SPF will affect deliverability of person-to-person mail, but not Marketo-to-person mail.

2 replies

Neil_Robertson6
New Participant
August 11, 2015

It depends. There are peffectly good reasons why Marketo will stay pending configuration (even with a valid SPF setup).  It will stay pending if your SPF setup uses redirects.  The Marketo SPF check is extremely primitive and does not respect redirect rules.  Our SPF for example is AOK and has been verified by both IT and Markto - yet all our domains are Pending Confiuguration.

August 13, 2015

Thank you so much. It makes sense now. While our SPF settings were configured by IT and Marketo, it was showing pending configurations.

Niel- yesterday  a marketo support guy actually fixed this issue for us. Not sure how he did it.

August 10, 2015

I believe it may affect your deliverability some. We have had recent troubles with DKIM and SPF, and found without an approved SPF - most things went straight to Spam.

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
August 10, 2015

... without an approved SPF - most things went straight to Spam.


I strongly doubt SPF was the cause because your SPF record is not consulted by the recipients of Marketo-generated emails (Marketo's SPF record for mktomail.com is used).*

On the other hand, if your DKIM setup was messed up enough that messages were signed, but failed signature verification -- that would cause rampant failures.

* Bad SPF will affect deliverability of person-to-person mail, but not Marketo-to-person mail.

Josh_Hill13
New Participant
August 11, 2015

I agree here.

Pending just means the DNS changes haven't propagated enough for Marketo to see and verify it.