r Dukhovni
Sent: Sunday, February 12, 2023 10:34 PM
To: postfix-users@postfix.org
Subject: Re: SSL3 alert write:fatal:decode error
On Sun, Feb 12, 2023 at 09:23:39PM +, Marko ANGELSKI wrote:
> This is the output of the tshark - only one line:
>
{"ports":["465",&qu
On Sun, Feb 12, 2023 at 09:23:39PM +, Marko ANGELSKI wrote:
> This is the output of the tshark - only one line:
> {"ports":["465","35308"],"len":"7","tls":{"ct":"21","rv":"0x0303","rl":"2","
> ht":null,"hv":null,"sv":null}}
As expected, the only TLS packet is the fatal alert from the server
(
,"hv":null,"sv":null}}
Best regards,
Marko
-Original Message-----
From: owner-postfix-us...@postfix.org On
Behalf Of Viktor Dukhovni
Sent: Friday, February 10, 2023 9:31 PM
To: postfix-users@postfix.org
Subject: Re: SSL3 alert write:fatal:decode error
On Fri, Feb 1
On Fri, Feb 10, 2023 at 09:22:57AM +, Marko ANGELSKI wrote:
> I'm having trouble with one client (iot) not able to send emails via
> postfix. This is the log:
>
> postfix/smtps/smtpd[4420]: initializing the server-side TLS engine
> postfix/smtps/smtpd[4420]: connect from unknown[xxx.xxx.xxx.x
Marko ANGELSKI:
> Hi,
>
> I appreciate the reply, the time is all the same - everything at the same
> second.
You also deleted the useful information about what a packet was
sent by the client and what was sent by the server.
Basically, this needs all packets after the TCP handshake.
Wi
Hi,
I appreciate the reply, the time is all the same - everything at the same
second.
Marko
-Original Message-
From: Wietse Venema
Sent: Friday, February 10, 2023 1:30 PM
To: Marko ANGELSKI
Cc: postfix-users@postfix.org
Subject: Re: SSL3 alert write:fatal:decode error
Marko ANGELSKI
Marko ANGELSKI:
> Hi, all,
>
>
>
> I'm having trouble with one client (iot) not able to send emails via
> postfix. This is the log:
>
> postfix/smtps/smtpd[4420]: initializing the server-side TLS engine
You deleted the useful time information, and added the useless debug logging.
Wi
