This TSR update rebuilt the Exim configuration back to the pre-autofixer (/scripts/autorepair exim_disable_chunking) configuration.
Was this intentional ?
Was this intentional ?
We haven't made any changes to srs_config, so I wonder why it's complaining about this setting.*** Running check_exim_config ***
Configuration file has an invalid syntax. Please try the edit again.
Error message from syntax check:
2018-01-23 02:43:30 Exim configuration error in line 2 of /var/cpanel/exim_hidden/srs_config:
"srs_config" option set for the second time
-= BEGIN exim.conf chunk -=
* * F,2h,15m; G,16h,1h,1.5; F,4d,8h
# End of Exim 4 configuration
#!!# cPanel Exim 4 Config
==><==
domainlist blocked_domains = lsearch;/etc/blockeddomains
chunking_advertise_hosts = ""
hide srs_config = vz8Gq__D4NB6WXVUTYPx98r6eYqKpLqQ:60:5
-= END exim.conf chunk -=
Resetting “Exim CF and ReplaceCF Configuration” to defaults...
Configuration file has an invalid syntax. Please try the edit again.
Error message from syntax check:
2018-01-23 02:43:31 Exim configuration error in line 2 of /var/cpanel/exim_hidden/srs_config:
"srs_config" option set for the second time
-= BEGIN exim.conf chunk -=
* * F,2h,15m; G,16h,1h,1.5; F,4d,8h
# End of Exim 4 configuration
#!!# cPanel Exim 4 Config
==><==
domainlist blocked_domains = lsearch;/etc/blockeddomains
chunking_advertise_hosts = ""
hide srs_config = vz8Gq__D4NB6WXVUTYPx98r6eYqKpLqQ:60:5
-= END exim.conf chunk -=
Resetting “Exim ACL Configuration” to defaults...
Configuration file has an invalid syntax. Please try the edit again.
Error message from syntax check:
2018-01-23 02:43:31 Exim configuration error in line 2 of /var/cpanel/exim_hidden/srs_config:
"srs_config" option set for the second time
-= BEGIN exim.conf chunk -=
* * F,2h,15m; G,16h,1h,1.5; F,4d,8h
# End of Exim 4 configuration
#!!# cPanel Exim 4 Config
==><==
domainlist blocked_domains = lsearch;/etc/blockeddomains
chunking_advertise_hosts = ""
hide srs_config = dqwdqdqwdqwqQ:60:5
-= END exim.conf chunk -=
It's not present in the new configuration on any of the new servers.hide srs_config = vz8Gq__D4NB6WXVUTYPx98r6eYqKpLqQ:60:5
A "Exim Update Failures" notification should have been sent via the configured contact method (WHM >> Contact Manager) if your Exim configuration was reset or could not be modified. Custom Exim configurations are automatically reset if they conflict with the changes associated with critical Exim updates. Feel free to open a support ticket using the link in my signature if you need help applying the update or restoring specific custom changes to your Exim configuration file.When the experimental SRS option for Exim was enabled, the secret key used to sign SRS email was visible inside the exim.conf file. This setting is now stored in a separate file that is not world-readable.
What exactly is required by us? Do we need to make any changes (other than revert the changes besides the srs_config setting)?Hello,
The specific change is noted in today's full disclosure of the recent security update:
A "Exim Update Failures" notification should have been sent via the configured contact method (WHM >> Contact Manager) if your Exim configuration was reset or could not be modified. Custom Exim configurations are automatically reset if they conflict with the changes associated with critical Exim updates. Feel free to open a support ticket using the link in my signature if you need help applying the update or restoring specific custom changes to your Exim configuration file.
Thank you.
For any others experiencing this issue, this will restore your previous customized configuration while still providing the benefit of the protections from the TSR update.We had a similar incident where all the Exim configurations were reset.
I had to restore the Exim configurations from the backup and delete the hide srs_config before saving.