Exim4 issue with upgrade

During upgrade I saw this;

[ * ] Health check complete. Starting upgrade from 1.7.2 to 1.7.3...
=============================================================================

[ - ] Now applying patches and updates for version v1.7.3...
grep: /etc/exim4/exim4.conf.template: No such file or directory
[ * ] File Manager is up to date (7.9.2)...
[ * ] Rainloop is up to date (1.17.0)...
[ ! ] Upgrading Roundcube to version 1.6.1...
[ ! ] Update Hestia PHP dependencies...
[ * ] Updating Cloudflare IP Ranges for Nginx...
[ * ] phpMyAdmin is up to date (5.2.1)...
etc

My fault; I may have renamed exim4.conf.template to exim4.conf because/when custom changes I made would not ‘take’ after exim4 restart. So how do I correct this?

Apply the patch file manually:

Are there any more, say, since early march, that patched on the same file? I have not seen this

grep: /etc/exim4/exim4.conf.template: No such file or directory

inside the log, but only during apt update… so I may have missed these earlier on.

[ * ] Update exim4.conf.template ...
patching file /etc/exim4/exim4.conf.template
Hunk #1 succeeded at 127 (offset 5 lines).
Hunk #2 succeeded at 133 (offset 5 lines).
Hunk #3 succeeded at 137 (offset 5 lines).

  • Exim: Never show HELO for authenticated users (#3462 @myvesta)
1 Like

Just to be sure I understand this; Is exim4 actually loading config from exim4.conf.template ?
Or does there need to be an exim4.conf as well?
This seems really weird, since my previous experience with exim4 did not have that .template file anywhere…

So far I know exim4.conf doesn’t need to exists it just creates the config based on exim4.conf.template