Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
and don't forget to implement the correct DKIM-Alignment: Not the senders Domain rather than the From:-Domain. Since the DKIM-Key has to be for the domain of the From-address, visible in any case for the famous unknown user.
Is this really needed? How often would you use it?
The more interesting part of a UI would be to move the key management to a different back-end, which would imply also using the modern certstore domain wide database which could simplify DKIM configuration cross domain.
But usually you have just a couple of gateway which require DKIM keys.
I just performed the steps on my server and did a quick write up.
It involves DNS TXT record updates, which would be another part to automate if you already have DNS TXT record interation configured for ACME DNS-01.
But this would be quite some work, for an operation not performed often - In contrast to certificate renewals.
https://blog.nashcom.de/nashcomblog.nsf/dx/enable-dkim-domino.htm
-- Daniel