Exim 4.80

interfasys

interfasys

Verified User
Joined
Oct 31, 2003
Messages
2,100
Location
Switzerland
Great news, exim now supports SNI :)
WARNING: This release contains backwards incompatible changes.

This release contains backwards incompatible changes. PLEASE read the
README.UPDATING file before upgrading. These changes affect OpenSSL,
GnuTLS and LDAP.
OpenSSL default options have changed to be more secure, including
disabling of SSLv2 by default (and adding support for TLSv1.1 and
TLSv1.2 if using OpenSSL 1.0.1 or newer); GnuTLS has been updated to use
a new API and stop honouring some options starting gnutls_*; users of
LDAP can now distinguish "comma in data" from "multi-valued attribute".
There are more details, covering more changes, in README.UPDATING.

We now enable accept_8bitmime by default, as the Exim maintainers agree
with Dan Bernstein about the best way to deal with the 8BITMIME
extension.

Building Exim should now be easier, with pkg-config support. We now
support use of the TLS Server Name Indication (SNI) extension, both as
client and as server, so Exim can present different TLS identities to
different clients on the same port. We have new authentication drivers,
for gsasl and heimdal_gssapi. The ${eval...} expansion operator now
supports 64-bit arithmetic (on 64-bit platforms). Exim can now be
started with support for inetd "wait-mode", which should be a precursor
to socket activation support for your OS's init system.
Click to expand...
 
Hello,

Since there are some "major" changes, I'm going to leave the versions.txt at 4.77 for a few days.
The 4.80 binaries are present on files1 right now.

If you'd like to use them, edit the versions.txt, find the line
Code: 
exim:4.77:dc1f29f687556f0f0e98fbde19f98ef4
and change it to be
Code: 
exim:4.80:
and build exim normally.

After a few days of testing, if all goes well, I'll add it to the versions.txt.

John
 
Good idea John.

OpenSSL default options have changed to be more secure, including
disabling of SSLv2 by default (and adding support for TLSv1.1 and
TLSv1.2 if using OpenSSL 1.0.1 or newer);
Click to expand...
I presume this means that one better can also use a newer exim.conf to have those new options present and enabled by default?
 
This is a generic response as I have NOT studied the release notes.

Defaults are always enabled by default :) unless you add something to exim.conf to turn them off.

Someone needs to try it out, hopefully on both on the SpamBlocker Version 2 as distributed by DirectAdmin, and on SpamBlocker Version 4 as distributed by me.

I don't have time right now, so I'm hoping someone will.

Jeff
 
We're using it on our live test box without any issues. Default SB 2.1.1.
If I am reading the 4.80 notes correctly, just like you mentioned, they'll be the defaults.. likely something we have not touched on.
It will most likely just disable the use of the older/insecure SSL methods, which people shouldn't be using anyway.
It doesn't seem like we'll need to make any changes.

John
 
Thanks for the reports. If someone will remind me in about two weeks, presuming no problems found, I'll start working on another release to take advantage of some things I've found, plus any special configuration settings we want to add to take advantage of in the new release.

Jeff
 
DirectAdmin Support said:
Hello,

Since there are some "major" changes, I'm going to leave the versions.txt at 4.77 for a few days.
The 4.80 binaries are present on files1 right now.

If you'd like to use them, edit the versions.txt, find the line
Code: 
exim:4.77:dc1f29f687556f0f0e98fbde19f98ef4
and change it to be
Code: 
exim:4.80:
and build exim normally.

After a few days of testing, if all goes well, I'll add it to the versions.txt.
Click to expand...

If I change the versions.txt, what happen then next time you add a new Exim version to custombuild, will I have to manually change versions.txt again in order to get the new version?

It's now seven days since you posted this, if there is no reported problems with Exim 4.80 yet, can you add it for everybody in custombuild now?
 
Thank you. But I am not able to install Exim 4.80. This is my problem:

I edit /usr/local/directadmin/custombuild/versions.txt and change the line exim:4.77:dc1f29f687556f0f0e98fbde19f98ef4 to be only exim:4.80: , then I save the changes in the file.

Then I delete /usr/local/directadmin/custombuild/exim-4.77.tar.gz

Then I do ./build exim

However the problem is that when doing ./build exim, then instantly the versions.txt file change back to have the line exim:4.77:dc1f29f687556f0f0e98fbde19f98ef4 instead of exim:4.80: , I tried several times. So it only install the old version 4.77

What am I doing wrong? Does anybody else have this problem?
 
Thanks. But now I am confused. I have this in options.conf

Code: 
clean=yes
clean_old_tarballs=no
clean_old_webapps=no
downloadserver=files1.directadmin.com
cleanapache=no

I did manually try to change "clean=yes" to "clean=no" and then did ./build exim, but it did not help, it reverted and installed old version.

What confuses me is that you write "clean off" and "clean on", I do not have that in my options.conf, I only have "clean=yes" not "on" or "off".

Is it the same thing when I manually change options.conf to "clean=no"? Because I did that, and it did not help.
 
Yes, sorry is just yes and no...

Ok, sorry was wrong variable:


Code: 
./build set autover no
./build exim
./build set autover yes

Regards
 
Ah, so it was autover! Thanks! Upgraded one server to exim 4.80 without any problems. Upgrading two more servers soon. Thanks a lot! :)
 
No problem :)

Update us if everything is fine in some days (let's say 3/5/7 days) so John can make it avaible to everyone.

Regards
 
I have now upgraded from exim 4.77 to exim 4.80 on all three servers, and there is no problems. I have tested emails, and checked log files. Everything looks great. I am running CentOS 6.2 64bit on all three servers.

Yes, I will post new reply in few days to let you know if everything is still running without problems. :)
 
It has been almost a week since I've upgraded on Debian, no problems.

Good thing they added lots of the newest ssl support, tls 1.1, 1.2 and SNI.
 
Hello,

files1.directadmin.com has been updated to exim 4.80.
Allow 24 hours for all other files mirrors to rsync the new versions.txt.

John
 
You must log in or register to reply here.
Back
Top