Hm, I still see the “records not matching” error in nethserver.
I tested with 7 dkim checker websites and either they say dkim record ok (but 0 bits) or they say the record is invalid or no record found or “We were not able to retrieve the key length, there is maybe an issue in that key” or another site reports: “This doesn’t seem to be a valid RSA public key: RSA.xs:178: OpenSSL error: bad base64 decode at blib/lib/Crypt/OpenSSL/RSA.pm (autosplit into blib/lib/auto/Crypt/OpenSSL/RSA/new_public_key.al) line 91.”
As this is our prod. system (and I certainly will make a snapshot before trying) I’d like to know if reinstalling nethserver-mail-server should not affect the rest of the nethserver (accounts, settings like connectors and everything else related/configured)?
And maybe move the whole /etc/opendkim folder, not just the default.txt? Or would you not recommend that?
I moved /etc/opendkim folder, reinstalled nethserver-mail-server and opendkim and did an /etc/e-smith/events/actions/nethserver-mail-create-opendkim-key and finally restarted opendkim service.
I also used another browser (edge) than before (firefox) for creating the TXT record by copy/pasting the key in registar webinterface. And here we are again with the wrong " and thus the records not matching error
I can ask them again to recreate the record for me as their webinterface probably has an issue, but I worry that I will hit the same result as above - being key not valid or 0 bits… We’ll see…
Well - true in a way dan35 but then again I am not sure what exactly the problem is as the " apparently are ok because I now check with the same 5 dkim checker tools and in contrary to the key without the additional 2 " now the opendkim checker sites report that the key is valid and is 2048 bits so the key that I had the registar modified was apparently not good, but the one created by their webinterface with the two additional " is…
So is this officially an assigned/accepted bug of nethserver ui now and will it be fixed? Anything else I could provide?
I guess, I will rollback to the snapshot I did earlier without reinstall of above packages to be on the safe side and recreate the old key @registar by webinterface with the two additional " " and wait for a fix in nethserver.
Which screenshots from where do you mean exactly. I already added screenshots above, but can do them again. What do you mean? From neth cockpit, webinterface registar, dig?
