On Fri, 10 Jan 2025, Viktor Dukhovni via Exim-users wrote:
On Thu, Jan 09, 2025 at 11:14:38PM +0100, Gandalf Corvotempesta via Exim-users
wrote:
but i've seen the exact error enabling the debug log, so the real error is
available in some way.
I don't think I have seen that in the logs you h
but i've seen the exact error enabling the debug log, so the real error is
available in some way.
Il gio 9 gen 2025, 19:04 Adam D. Barratt
ha scritto:
> On Thu, 2025-01-09 at 11:58 +0100, Gandalf Corvotempesta via Exim-users
> wrote:
> > Probably, a better error message, as a wrong server name i
On Thu, Jan 09, 2025 at 11:14:38PM +0100, Gandalf Corvotempesta via Exim-users
wrote:
> but i've seen the exact error enabling the debug log, so the real error is
> available in some way.
Wrong end of the connection. Only the sender of a TLS alert knows the
details of why the alert was sent. T
Il giorno gio 9 gen 2025 alle ore 10:40 Jeremy Harris via Exim-users
ha scritto:
> We don't know that the client end actually saw that, because you've
> not shown us the debug from the client.
That's what i'm trying to do but I don't know how to enable the debug
for just one transport.
I can't se
Il giorno gio 9 gen 2025 alle ore 11:01 Jeremy Harris via Exim-users
ha scritto:
> Enable it in ACL, like you did on the smarthost. Use conditions that
> pick out that one message.
Solved.
the exim cliend does a certificate hostname validation (i wasn't aware
of this), and the certificated on th
On Thu, 2025-01-09 at 11:58 +0100, Gandalf Corvotempesta via Exim-users
wrote:
> Probably, a better error message, as a wrong server name in
> certificate is a very very common error, would greatly simply
> debugging than a generic "Certificate is bad"
>
TLS libraries generally don't expose such
Il giorno mer 8 gen 2025 alle ore 13:28 Jeremy Harris via Exim-users
ha scritto:
> The smarthost received an alert fron the client, saying that the client
> did not like the smarthost's cert
>
> > SMTP>> 421 smarthost.server lost input connection
>
> ... and then the connection from the client was
Il giorno mer 8 gen 2025 alle ore 13:28 Jeremy Harris via Exim-users
ha scritto:
> > SMTP>> 250-smarthost.server Hello 4.3.2.1.bc.googleusercontent.com [1.2.3.4]
> > 250-SIZE 104857600
> > 250-8BITMIME
> > 250-PIPELINING
> > 250-PIPECONNECT
> > 250-AUTH PLAI
On 09/01/2025 09:49, Gandalf Corvotempesta via Exim-users wrote:
Il giorno gio 9 gen 2025 alle ore 10:40 Jeremy Harris via Exim-users
ha scritto:
We don't know that the client end actually saw that, because you've
not shown us the debug from the client.
That's what i'm trying to do but I don'
On 09/01/2025 09:01, Gandalf Corvotempesta via Exim-users wrote:
The log above should show that auth is advertised from the smarthost,
so the client should authetnicate
Actually, we only know that the smarthost transmitted an advertisement
of AUTH (and, insecure methods in cleartext; a poor
10 matches
Mail list logo
