4.96-58-g4e9ed49f8
. It was a build of exim that is in between version 4.96 and version 4.97 (version 4.97 is not yet finished). The number 58 meant release is 58 commits ahead of initial exim 4.96 release.4.96-58-g4e9ed49f8
to 4.96.1
means losing 58 commits of exim development towards exim 4.97 but gaining extra 5 commits that fixes the security issue.4.96.1-7-g79877b70e
it will be the 4.96.1 release plus some fixes from the 4.97 development. The fixes are not picked by us - it is taken from upstream exim git branch exim-4.96.1+fixes.spf_guess
spf_header_comment
spf_received
spf_result
spf_result_guessed
spf_smtp_comment
spf_smtp_comment_template
Will you be releasing a fix for older systems running for example Debian 9 as well?In the mean time we will release a new exim build4.96.1-7-g79877b70e
it will be the 4.96.1 release plus some fixes from the 4.97 development. The fixes are not picked by us - it is taken from upstream exim git branch exim-4.96.1+fixes.
Will you be releasing a fix for older systems running for example Debian 9 as well?
./build update
./build exim
Yes. Commands you wrote would work. You just need to:Great, how exactly though? Just a:
/usr/local/directadmin/directadmin update
or ./build update
or via GUI./build exim
or GUIversions.txt
file to 4.96.1
.4.96.1
with a lineexim:4.96.1:
in file /usr/local/directadmin/custombuild/custom_versions.txt
.Yes. Commands you wrote would work. You just need to:
- Update DA to the latest version with
/usr/local/directadmin/directadmin update
or./build update
or via GUI- Rebuild exim with
./build exim
or GUI
cd /usr/local/directadmin/custombuild
./build update
./build exim
RHEL/CentOS 6 is not supported by DirectAdmin anymore.
Commit SHA | d75a0f404a0850bf0538e69033c16748bb606f20 |
Latest Commit SHA | d75a0f404a0850bf0538e69033c16748bb606f20 |
Last Updated | Mon Oct 2 20:22:11 2023 |
RHEL/CentOS 6
even before the release hot-fix. You would have receive the same error even if you would not have updated. We do not have any functional CentOS 6 system, so rely only on your reports here.Okay thanks so far, I will upgrade this server this month to have this issue solved for meOhh I finally understand the problem. CB did not supportRHEL/CentOS 6
even before the release hot-fix. You would have receive the same error even if you would not have updated. We do not have any functional CentOS 6 system, so rely only on your reports here.
The support for RHEL 6 in CB was dropped before it was considered EOL by DirectAdmin and even before it got merged to DirectAdmin.
I am sorry to inform this exim update will not be available on RHEL/CentOS 6 systems ?. The update on RHEL 6 systems is essentially noop, it bumps the entry in versions.txt but CB can not buid exim for this distro.
Same goes for Debian 8. The update should work on Debian 9.
hi fln.,Ohhh, by remote I immediately assumed you are referring the remote code execution vulnerabilities that are the main topic of this thread.
If it is some other issue with exim, would be great to report in our ticketing system or in a separate forum thread.