3

I have a verified domain using a DKIM. The DKIM was created by the email relay, added to my DNS, and verified by the relay. Once I got the EXM set up properly and was able to add a domain, Sitecore associated it with a different DKIM that is not verified. How to I setup my domain in Sitecore with the already verified DKIM?

enter image description here

1
  • Please provide Verison of EXM. Feb 14 '17 at 21:45
3

In EXM, using Sitecore's Email Cloud Delivery service (EXM 3.4+), you have to use the DKIM Keys that are provided to you by Sitecore. This is how Sitecore recognizes that your domain is reputable.

You can find the DKIM keys in that screen by double clicking on the domain or by using the eyeball button.

From there, you should be presented a similar window to the image below where the new DKIM keys are supplied. You will want to have someone in charge of your DNS server records to update the DKIM for the domain in question and add these keys as a TXT Record. Also note, when making DNS changes, it can take as long as 72 hours for changes to take effect.

enter image description here

Once you have updated your domain keys, and Sitecore's Email Delivery Cloud Service recognizes the keys on the domain, you should see the DKIM box flip from a Yellow Triangle with an Exclamation Mark to a Green Check Mark.

Please note, this image is from EXM 3.3, but should be similar in looks.

1
  • Hi Peter! Thank You! The initial verification actually came from the Sitecore Email Cloud Service (SparkPost). The Sitecore EXM/EDS was not fully set up when we verified the domain with SparkPost. I will look into removing our current DKIM and starting the process again with our EXM/EDS up and running. Feb 15 '17 at 7:09
0

I have a somewhat related issue with EXM 3.3. A few notes in case they help.

Support have stated that the DKIM information displayed in the domain verification screen is incorrect. From SC support:

Please note that your DKIM values should be like this: v=DKIM1; k=rsa; t=y; p=SOMEVERYLONGKEYVALUE

I believe "v=DKIM1;" was missing from the instructions on that screen

Also, the SPF record must be an exact match - you can't include additional domains in that SPF record the validation method doesn't understand the specification/syntax, it just looks for an exact match.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.