exim.variables.conf.custom broken

tomputer

tomputer

Verified User
Joined
Apr 5, 2016
Messages
37
Location
The Netherlands
Since DirectAdmin version 1.646 we have issues on servers with exim.variables.conf.custom. We have many servers with custom openssl_options, tls_require_ciphers, tls_certificate or other settings.

For example:
Code: 
/usr/local/directadmin/custombuild/build exim_conf

2023-01-05 14:41:20 Exim configuration error in line 28 of /etc/exim.variables.conf:
  "openssl_options" option set for the second time

I tried the commands below but that does not insert/merge the custom settings with the default settings:
Code: 
mkdir /usr/local/directadmin/custombuild/custom/exim
mv /etc/exim.variables.conf.custom /usr/local/directadmin/custombuild/custom/exim/
/usr/local/directadmin/custombuild/build exim_conf

I've read the release notes but there is no information how to keep the exim.variables.conf.custom?
 
Last edited:
Richard G said:
Are you sure this is not working anymore? Or is the docs saying 2 seperate things?

Because the docs still say that the .conf.custom files are still used:

Configuring and customizing Exim | Directadmin Docs

DirectAdmin Knowledge Base
docs.directadmin.com

@fln @smtalk can you explain this confusion caused by the documentation? Which is correct now?
Click to expand...
I believe /etc/exim.variables.conf.custom is still in use but (some) settings are now added for a second time.

The custombuild/build script still contains code to merge /etc/exim.variables.conf.custom and /etc/exim.variables.conf.default in a temporary /etc/exim.variables.conf.merged file.
 
Thanks for bringing this to our attention. File exim.variables.conf.custom should continue working as it used to before. The only change with 1.646 release is the way we perform the file merge. It seems new merge logic does not ignore extra whitespaces between the variable name and the = symbol. We will push out an update to take care of that soon.

The problem could be manually fixed by making sure the variables in custom file would have the same amount of whitespace symbols between the variable name and = symbol.
 
This file is not merged with the defaults we provide. It is just included in the configs if exists. It is not affected at all by the changes and will work as before.
 
We are getting the same error when adding untrusted_set_sender to exim.variables.conf.custom:
Exim configuration error in line 9 of /etc/exim.variables.conf:
"untrusted_set_sender" option set for the second time
Click to expand...

Any way around this?
 
You must log in or register to reply here.
Back
Top