Dovecot customised config main.local overwritten by update
I read in Configure Dovecot - Documentation - cPanel Documentation and Dovecot Custom Configuration. that I should be able to make permanent changes to the dovecot configuration by creating and modifying a 'main.local' file.
Last week, after the update to 64.0 (build 15) I noticed some unexpected behaviour, and found this in the logs:
And I arrived at work to find the configuration file reset to default and all my customisation bypassed. Should I be prepared for this to happen on every update in the future?
[2017-04-19 22:19:38 +0700] This system"s custom Dovecot configuration appears to be older than the cPanel-supplied configuration. The system will rename the custom configuration to "/var/cpanel/templates/dovecot2.2/main.default.outdated.2017-04-19T15:19:38Z.2924591
2" and install a default configuration.
[2017-04-19 22:19:39 +0700] The local template file '/var/cpanel/templates/dovecot2.2/main.local' is invalid. The system will rename
it to /var/cpanel/templates/dovecot2.2/main.local.broken.1492615178.uq4E4yAAP6aXjr9R.
[2017-04-19 22:19:39 +0700] This system"s custom Dovecot configuration appears to be older than the cPanel-supplied configuration. The system will rename the custom configuration to "/var/cpanel/templates/dovecotSNI/main.default.outdated.2017-04-19T15:19:39Z.8056296
7" and install a default configuration.
And I arrived at work to find the configuration file reset to default and all my customisation bypassed. Should I be prepared for this to happen on every update in the future?
-
Hello, We made some updates to the Dovecot configuration in cPanel 64 that affects template customization. Here's the relevant section from the documentation.
Thank you.0 -
Hello @km9, I'm happy to see that information helped you address the issue. We created a blog post with steps you can take to better prepare for changes in new versions of cPanel at: Update Prep: How to Test Your Software with the Upcoming Versions of cPanel & WHM | cPanel Blog Thank you. 0
Please sign in to leave a comment.
Comments
3 comments