On Fri, Jan 10, 2025 at 10:31:12AM +0100, Gandalf Corvotempesta via Exim-users
wrote:
> Also, the server seems to get the error sent directly from the client
> when it's closing the connection, so the client i think will be able
> to also send the real error to the server, isn't it?
No, SSL/TLS
Il giorno ven 10 gen 2025 alle ore 06:33 Andrew C Aitchison via
Exim-users ha scritto:
> I don't think I have seen that in the logs you have sent to the list.
You are correct, because i didn't post the client log.
After enabling the debug and reading the certificate CN error,
correction was trivi
Il giorno gio 9 gen 2025 alle ore 23:35 Viktor Dukhovni via Exim-users
ha scritto:
> Wrong end of the connection. Only the sender of a TLS alert knows the
> details of why the alert was sent. The recipient (in this case server)
> knows only the alert number, and can only report a fairly general
On 10/01/2025 05:31, Andrew C Aitchison via Exim-users wrote:
In that case, can and should we make exim-as-client report
why it rejected the server's certificate in the main log ?
The operational problem would then become the amount of cruft
in the log, were every possible item of information r
