DKIM removal ordering not right when renaming a domain

Submitted by beat on Mon, 04/27/2020 - 02:28

Nothing urgent, but the DKIM removal attempt happens after the domain has been renamed, so it's failing, but then it recognizes it again, so seams not an issue, just makes message scary.

Proposal: Don't even try to remove existing DKIM in domain rename ? That would be much better (and compatible with result now), if a domain renamed temporarily, and then is renamed back, at least DKIM remains valid.

Changing domain name to oldexample.com ..
Changing administration user to oldexample ..
Changing home directory to /home/oldexample ..
Modifying administration user ..
.. done

Modifying administration group ..
.. done

Moving home directory ..
.. done

Changing DNS domain name ..    <===== DOMAIN RENAMED BEFORE REMOVING DKIM BELOW
.. done

Changing slave domain on ns2.example.com ns1.example.com ..
.. done

Updating users ..
.. done

Removing from email domains list ..
.. done

Removing secondary mail servers mx2.example.com, mx1.example.com ..
.. done

Removing DKIM records from DNS domain secretlyconnect.com ..
.. domain not found!     <=================== HERE IS THE PROBLEM: DOMAIN ALREADY RENAMED.

Adding to email domains list ..
.. done

Setting up secondary mail servers mx2.example.com, mx1.example.com ..
.. done

Adding DKIM records to DNS domain oldsecretlyconnect.com ..
.. records already exist    <====== HERE IT SEAMS TO RECOVER.

Changing domain name in mail aliases ..
.. done

Changing home directory in website configuration ..
.. done

Changing username in website configuration ..
.. done

Changing hostname of virtual website ..
.. done

Updating home directory in PHP configuration ..
.. done

Updating log file path in Webalizer configuration ..
.. done

Updating home directory in Webalizer configuration ..
.. done

Updating domain name in Webalizer configuration ..
.. done

Updating username in Webalizer configuration ..
.. done

Updating log file path in Logrotate configuration ..
.. done

Updating home directory in Logrotate configuration ..
.. done

Updating user and group in Logrotate configuration ..
.. done

Renaming MySQL user ..
.. done

Changing administration group for MySQL database files ..
.. done

Updating protected web directories ..
.. done

Renaming Webmin user ..
.. done

Updating domain name in AWstats configuration ..
.. done

Updating user to run AWstats report as ..
.. done

Updating home directory in AWstats configuration ..
.. done

Updating log file in AWstats configuration ..
.. done

Updating paths in script database ..
.. done

Updating Webmin user ..
.. done

Re-starting DNS server ..
.. done

Re-starting slave DNS servers ..
.. done

Applying web server configuration ..
.. done

Re-loading Webmin ..
.. done

Applying web server configuration ..
.. done

Saving server details ..
.. done
Status: 
Fixed (pending)

Comments

Submitted by JamieCameron on Sun, 05/03/2020 - 17:43

We'll fix this in the next release - it's basically harmless, but also that message is confusing.