Exim+Nginx

evgeni22385

Verified User
Joined
Feb 13, 2022
Messages
5
cant get Exim and Dovecot work, did run this:
cd /usr/local/directadmin/custombuild
./build update
./build set exim yes
./build set eximconf yes
./build set eximconf_release 4.5
./build set spamassassin yes
./build update
./build exim
./build exim_conf

and found in logs

Feb 13 17:37:15 *** exim[32629]: 2022-02-13 17:37:15 Exim configuration error in line 19 of /etc/exim.variables.conf:
Feb 13 17:37:15 *** exim[32629]: user apache was not found


dont have apache only nginx, will be glad for any help
 
this line
line 19 of /etc/exim.variables.conf

changed it from apache to nginx and now it working xD
 
changed it from apache to nginx and now it working xD
So on the next update, you will have to edit it again. ;)

Create a file called exim.variables.conf.custom and add that line into there.
Then next time your change will be kept and not overwritten.
 
The documentation could be a bit more clear here though since it says to put custom Exim variables in exim.variables.conf.custom though that file isn't included anywhere in the default Exim configuration files. Seems like changes to this custom file are added to the exim.variables.conf file only if you issue a ./build exim_conf afterwards. Maybe this should be added on:


and in the exim.variables.conf for example like:
Code:
#Do not edit this file directly
#edit /etc/exim.variables.conf.custom and execute /usr/local/directadmin/custombuild/build exim_conf
 
Seems like changes to this custom file are added to the exim.variables.conf file only if you issue a ./build exim_conf afterwards.
Oh I didn't know that. I thought an Exim restart was all that was needed, but according to the docs, you're correct.

that file isn't included anywhere in the default Exim configuration files
No because it's a custom files. Normally you have to create custom files yourself. Normally /custom directory's are used for this, except for Exim, there the .custom extension is used in files.

only if you issue a ./build exim_conf afterwards. Maybe this should be added on:
What do you mean? It does say that in the docs.
 
You probably have better eyes
On my age? LoL, I'm sure I don't anyway. :)

However, you are partly correct. It's not mentioned directly where both the exim.strings and exim.variables is mentioned but it's lower.

In this case also the exim.variables.conf.custom is used to make a change (the port in this case) and there it does state a ./build exim_config is required afterwards.

However I do agree with you that it should also state this in the upper part, so things will be kept together.
 
Back
Top