Due to ISP change I had to change the IP and hostname for the server.
Then when checking DKIM etc it bothered me to see the old server name, wondering what the ramifications were. - hence my first unanswered request in Septermber 25.
Then setting up a new server once VMin 8 had EL10 compatibility, and I saw that it had changed to a number. That was a nuisance as I had to keep checking what it was if I was testing DKIM with eg mxtoolbox. So much easier if it is the hostname.
So I started this thread and it just felt like I was at fault for asking.
Turns out it’s just a label, and no good reason why it shouldn’t be the hostname, also no good reason why we shouldn’t be able to change it if we choose.
Seriously, probably 99% won’t ever touch it.
Once I get EL10 working 100% with VMin 8 with no bugs, I probably won’t ever change it after the initial change.
Maybe just add it to the docs and people like me can find it if they feel the need.
Even this thread won’t be as useful as it could have been as it has become so long.
You need to click No to: Signing of outgoing mail enabled, then Save and return to the form. You can then edit the selector, click Yes to the above question and Save again.
Then again, does Signing of outgoing mail enabled need to be disabled to change it?
I have manually edited /etc/opendkim.conf, then gone to that page and hit Save without disabling/enabling. The Save action appears to do it all for me.
Yes, it’s already there. Check the commit in the link above.
That would add two DKIM DNS records to the DNS zone, meaning it won’t remove the one with the old selector.
I think this is why Jamie decided to use a text label instead of always showing it as an editable input field.
I believe it would be better to always keep it as an input field and handle the complexity on the server side rather than in the UI. @Jamie, we should be the ones handling complexity, not the users.