Unable to send custom email via GEL Script from a client domain with an s43 DKIM key.
search cancel

Unable to send custom email via GEL Script from a client domain with an s43 DKIM key.

book

Article ID: 144900

calendar_today

Updated On:

Products

Clarity PPM SaaS

Issue/Introduction

The aim is to send a custom email notification from the Clarity SaaS environment using GEL Scripts.


Emails can be sent using a gel:email tag with the ‘from’ address as ‘[email protected]<OUR SITE NAME HERE>.com.au’


Emails can NOT be sent using the email:email tag with the ‘from’ address ‘[email protected]<OUR SITE NAME HERE>’. 
Emails like this can be sent only using ‘@ca.com’.


It was attempted to get around this using a DKIM key provided by the Broadcom IT team.
The following was added by the client's DNS team.

s43._domainkey  IN      TXT     ( "v=DKIM1; k=rsa; "
          "p=MIGfM. . . <DETAILS CHANGED FOR PRIVACY HERE> . . . 2PVT0g/yS+Eu. . . <DETAILS CHANGED FOR PRIVACY HERE> . . .8sL0/Wm. . . <DETAILS CHANGED FOR PRIVACY HERE> . . .AB" )  ; ----- DKIM key s43 for <OUR SITE NAME HERE>.com.au’


However, this does not work. The client team advise: "The selector is not correct, should be s43, not dkimrelay."




Is there an issue with the signing of the DKIM key?
Can this be sent from our custom domain email address?



Environment

Release : 15.6

Component : CA PPM SAAS OPERATIONS INFRASTRUCTURE

Resolution

The key was checked by the Broadcom Team and was advised to be an s43 key.

The communication around which domains were in use was not taken to root cause, but a possible contributing factor.


STEPS TAKEN TO RESOLVE ISSUE

The resolution was that the client site switched to using the "@ca.com" email id.

They no longer used "@<OUR SITE NAME HERE>.com.au".

Attachments