The double backslash at the end of Dell's dell.com DKIM record is not
correct; this was presumably added incorrectly to escape the escaped
semicolon, resulting in a bad key.
You can confirm this at https://dkimcore.org/c/keycheck instead of
protodave.
With no backslash (which of course is not in
I have just discovered that Exim DKIM appears to fail to parse some DKIM
keys that other systems claim are okay:
19 00:50:18 RCPT: SPF Result2=pass (Partnersresponse.dell.com /
mail04.response.dell.com [142.0.168.187])
19 00:50:19 1hHGnL-0002nj-0r PDKIM: d=dell.com s=dk2016 [failed key import]