On 31/05/2022 21:14, Viktor Dukhovni via Exim-users wrote:
TLS alerts report error conditions from the remote peer. If your server
logs a TLS alert, that alert was generated on the remote end. So if
this is a connection from a client to your server, then the "certificate
expired" condition is
On 31/05/2022 20:53, Heiko Schlittermann via Exim-users wrote:
TLS error on connection from r209.notifications.natwest.com
[130.248.154.209]:44104 I=[167.235.252.255]:25 (SSL_accept):
error:14094415:SSL routines:ssl3_read_bytes:sslv3 alert certificate expired
Is there any chance that the clien
I have some legitimate-looking hosts from a major bank producing log lines
like this when attempting incoming connections to a public MX:
TLS error on connection from r209.notifications.natwest.com
[130.248.154.209]:44104 I=[167.235.252.255]:25 (SSL_accept):
error:14094415:SSL routines:ssl3_re
The updated Exim pages from the EPEL project for RHEL 7 & 8 (and related
distributions e.g. CentOS) as well as Fedora 34 are now in the process of
being pushed to the stable repositories and should be there in the next few
hours or so:
https://bodhi.fedoraproject.org/updates/?packages=exim
Th
On 06/05/2021 14:54, Konstantin Boyandin via Exim-users wrote:
The last known EPEL Exim version is 4.94 #2, built on March 25, 2021. It
wasn't difficult to build Exim from sources and replace insecure EPEL
version, but it's not exactly my understanding of fun.
An update was available for EPEL
