Some software failing to upgrade, exim broken in production

[Protected]

I recently ran an upgrade via the custombuild UI in directadmin. Unusually, three DA components failed to upgrade:

ProFTPd 1.3.7c update to 1.3.7e
Exim 4.95 update to 4.96
RoundCube 1.5.3 update to 1.6.0

They will not upgrade even if I retry. Unfortunately, exim.conf DID get updated, and right now all e-mail running through the server is being dropped. The following message is logged for every attempt:

Failed to expand return path "${srs_encode {...} {$return_path} {$original_domain}}": "${srs_encode" is not a known operator (or a } is missing in a variable reference

I'm assuming fixing the upgrade flow such that exim can be upgraded will resolve the problem. How should I make this happen without losing any data or settings? Thanks.

 

[smtalk]

What's the error when you try to build exim?

 

[Protected]

This is the entire output:

Executing /usr/local/directadmin/plugins/custombuild/admin/build exim..
Found /usr/local/directadmin/custombuild/exim-4.96.tar.gz
Extracting ...
Done.
Downloading        exim-4.96/Local/Makefile...

######################################################################## 100.0%
Making Makefile changes for 4.96+
Trying to make exim...
/bin/sh scripts/source_checks

>>> Creating links to source files...
>>> Creating lookups/Makefile for building dynamic modules
Done!

I'm on Debian 11.

 

[Protected]

OK, I get more stuff in the command line. This is the first error:

cc exim_lock.c
buildconfig.c:35:10: fatal error: ctype.h: No such file or directory
   35 | #include <ctype.h>
      |          ^~~~~~~~~
compilation terminated.

 

[Protected]

Any way to roll back the exim config for now? Lot of people without e-mail.

server /usr/local/directadmin/custombuild # ./build set eximconf_release 4.95
4.95 is not a valid setting for eximconf_release option.

I don't want to try to work around SRS because I'm afraid of long term impact to reputation.

 

[Protected]

Fixed by reinstalling the requirements except for roundcube, which requires a newer version of php and gets automatically downgraded back to current version on install. I imagine the requirements changed at some point, which was causing the issue.