Marc MERLIN via Exim-users <[email protected]> writes: > Mmmh, not what I expected quite, but upgrading exim4 seems to have fixed > the issue. Relevant updates: > Unpacking libnet-ssleay-perl (1.85-2+b1) over (1.77-1+b1) ... > Unpacking libssl1.1:i386 (1.1.1b-2) over (1.1.0f-4) ... > Unpacking libgnutls30:i386 (3.6.7-3) over (3.6.6-2) ... > Unpacking libgnutls-dane0:i386 (3.6.7-3) ... > Unpacking libsasl2-modules-db:i386 (2.1.27+dfsg-1) ... > Unpacking libsasl2-2:i386 (2.1.27+dfsg-1) over (2.1.25.dfsg1-2) ... > Unpacking exim4-daemon-heavy (4.92-7) over (4.87-3+b1) ... > > And now things work again.
Thanks for the hint! That helped a lot. I was so sure the problem was on the other end, since I did upgrade that and hadn't touched the exim installation. I hit this after upgrading my sendmail smarthost to buster. I guess that enabled TLSv1.3 support on the smarthost side. Upgrading exim to 4.92-8 (from current sid) fixed the issue. I was also running the odd combo of a new libgnutls30 (from sid) with an old exim4 package (from stretch). So I guess I did it to myself.. But at least we are two :-) Bjørn -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
