Re: [exim] debugging tls handshake failure

On 2022-11-23, Viktor Dukhovni via Exim-users wrote: > So, have you tried configuring a complete certificate chain (ideally > without the Android compatibility crutch). Did that make any > difference? Well, since doing that I haven't seen any fatal alerts in the logs. But I also haven't had

Re: [exim] debugging tls handshake failure

On 2022-11-23, Kirill Miazine via Exim-users wrote: > • Julian Bradfield via Exim-users [2022-11-23 18:25]: > [...] >> Kirill wrote: >> >> something in base64 which got saved as such:) > > I wonder why... Because when you save an article in slrn, it saves the entire article. There doesn't

Re: [exim] debugging tls handshake failure

• Julian Bradfield via Exim-users [2022-11-23 18:25]: [...] > Kirill wrote: > > something in base64 which got saved as such:) I wonder why... > Asking I think for any information, as he sees something similar. Will > do. exactly: https://marc.info/?l=exim-users=166919251811778=2 -- ## List

Re: [exim] debugging tls handshake failure

On Wed, Nov 23, 2022 at 06:25:29PM +, Julian Bradfield via Exim-users wrote: > >If the server in question is "london.jcbradfield.org", then another > >potential issue is a missing intermediate issuer certificate. Your > >certificate chain has only the leaf server certificate without the >

Re: [exim] debugging tls handshake failure

Thank you for the various replies! Viktor wrote: >> 2022-11-21 21:10:42 TLS error on connection from >> r218.notifications.rbs.co.uk [130.248.154.218] (gnutls_handshake): A TLS >> fatal alert has been received. > >OpenSSL would usually log the alert number (and associated text string), >from

Re: [exim] debugging tls handshake failure

• Julian Bradfield via Exim-users [2022-11-21 21:41]: > I should like to know what's happening here: > > 2022-11-21 21:10:42 TLS error on connection from r218.notifications.rbs.co.uk > [130.248.154.218] (gnutls_handshake): A TLS fatal alert has been received. I see similar on a number of

Re: [exim] debugging tls handshake failure

On 21/11/2022 21:41, Julian Bradfield via Exim-users wrote: Is there a way to get more information? Oh, yes, do ensure you're running with Exim's debug facilities enabled. Commandline option or ACL modifier. -- Cheers, Jeremy -- ## List details at

Re: [exim] debugging tls handshake failure

On 21/11/2022 21:41, Julian Bradfield via Exim-users wrote: I should like to know what's happening here: 2022-11-21 21:10:42 TLS error on connection from r218.notifications.rbs.co.uk [130.248.154.218] (gnutls_handshake): A TLS fatal alert has been received. However, I can't see how to get any

Re: [exim] debugging tls handshake failure

On Mon, Nov 21, 2022 at 09:41:12PM +, Julian Bradfield via Exim-users wrote: > I should like to know what's happening here: > > 2022-11-21 21:10:42 TLS error on connection from r218.notifications.rbs.co.uk > [130.248.154.218] (gnutls_handshake): A TLS fatal alert has been received. OpenSSL

Re: [exim] debugging tls handshake failure

On Mon, Nov 21, 2022 at 09:41:12PM +, Julian Bradfield via Exim-users wrote: > I should like to know what's happening here: > > 2022-11-21 21:10:42 TLS error on connection from r218.notifications.rbs.co.uk > [130.248.154.218] (gnutls_handshake): A TLS fatal alert has been received. > If

[exim] debugging tls handshake failure

I should like to know what's happening here: 2022-11-21 21:10:42 TLS error on connection from r218.notifications.rbs.co.uk [130.248.154.218] (gnutls_handshake): A TLS fatal alert has been received. However, I can't see how to get any more information. I've tried setting add_environment =