On February 24, 2020 8:47:49 AM UTC, Viktor Dukhovni
wrote:
>>
>> On Feb 24, 2020, at 2:27 AM, Michael wrote:
>>
>> Feb 22 08:50:07 mail postfix/smtpd[12952]: connect from
>bendel.debian.org[82.195.75.100]
>> Feb 22 08:50:07 mail postfix/smtpd[12952]: setting up TLS connection
>from bendel.
i forgot:
On Monday, February 24, 2020 9:47:49 AM CET, Viktor Dukhovni wrote:
Were TLS sessions failing from all senders or just particular systems?
it seemes to me, that all tls sessions failed, since no mail was delivered
at all after the switch.
greetings...
hey,
On Monday, February 24, 2020 9:47:49 AM CET, Viktor Dukhovni wrote:
This looks like a client (or firewall, etc. in between) that does not
correctly support TLS 1.3. What's new on your system is not Postfix 3.4,
but a sufficiently recent version of OpenSSL that has TLS 1.3 support.
i came
>
> On Feb 24, 2020, at 2:27 AM, Michael wrote:
>
> Feb 22 08:50:07 mail postfix/smtpd[12952]: connect from
> bendel.debian.org[82.195.75.100]
> Feb 22 08:50:07 mail postfix/smtpd[12952]: setting up TLS connection from
> bendel.debian.org[82.195.75.100]
> Feb 22 08:50:07 mail postfix/smtpd[129
hey,
first, let me thank you for your answer. i really appreciate this!
On Monday, February 24, 2020 12:20:27 AM CET, Viktor Dukhovni wrote:
smtpd_tls_security_level = may
smtpd_tls_lloglevel = 1
That's fine, but not consistent with the verbose logging below, did you
temporarily set a higher
On Sun, Feb 23, 2020 at 10:45:14PM +0100, Michael wrote:
> After upgrading from debian stretch (providing postfix 3.1.14) to
> buster (providing postfix 3.4.8), I just found out that no incoming
> mail was received any longer. Digging a little deeper showed me that
> turning of tls resolved this
hey,
after upgrading from debian stretch (providing postfix 3.1.14) to buster
(providing postfix 3.4.8), i just found out that no incoming mail was
received any longer. digging a little deeper showed me that turning of tls
resolved this issue. but then again, there was no tls...
i would appr
