I have searched the forum for this exact minor glitch and could not find it, however I found a similar issue recently for SPF records. I report this here, but please note this is more a bother than a blocking issue.
In a nutshell, I have established the connection between WP mail SMTP and a google account (on a G suite account). I then spent quite a bit of time RTFM to ensure the mail is 100% kosher re SPF/DKIM/DMARC.
Bottomline: the mail ths is sent by WP mail SMTP is 100% perfect re SPF/DKIM/DMARC (based on mail-tester.com and an mx host administered by true internet dinosaurs). So thanks, the integration works like a charm!
… however the “test email” feature of WP mail SMTP still tells me:
Action Needed: It doesn’t look like the DKIM record required by Google has been added to your domain
which is, in fact, inaccurate. This could have other people scratching their heads, so maybe this ought to be fixed?
[Afterthought] The reason why this may be the case is possible related to the fact that the DNS text key under which the DKIM public key is made available is not the “default” one from google, and was customized to c2b._domainkey. This is possible in G suite, however this maybe not be the most mainstream set up: the bother might thus be self-inflicted.- This topic was modified 8 hours, 31 minutes ago by . Reason: Possible reason for the behaviour