On Wed, Apr 03, 2024 at 09:23:26AM +0300, Levente Birta via Postfix-users wrote:
> > The other possibility, is that the client never tried TLS 1.3, and was
> > implemented by a clueless keyboard-monkey, who decided to always send
> > the fallback SCSV even though there was no fallback. That's
On 03/04/2024 01:08, Viktor Dukhovni via Postfix-users wrote:
On Thu, Mar 28, 2024 at 09:58:13AM +0200, Levente Birta via Postfix-users wrote:
That's worth a try:
588 inet ... smtpd
-o smtpd_tls_security_level=encrypt
-o smtpd_tls_mandatory_protocols=TLSv1.2
On Thu, Mar 28, 2024 at 09:58:13AM +0200, Levente Birta via Postfix-users wrote:
> > That's worth a try:
> >
> > 588 inet ... smtpd
> > -o smtpd_tls_security_level=encrypt
> > -o smtpd_tls_mandatory_protocols=TLSv1.2
> > ...
>
> Limiting to only TLSv1.2 did the
On 28/03/2024 05:16, Viktor Dukhovni wrote:
On Wed, Mar 27, 2024 at 08:37:12PM -0400, Wietse Venema wrote:
Viktor Dukhovni:
And the server, objects, since it supports TLS 1.3. Now you need to
figure out why the client is signalling fallback.
Would it be feasibe to set up a dedicated
On Wed, Mar 27, 2024 at 03:28:38PM +0200, Levente Birta via Postfix-users wrote:
> Please help me out with the following error. It's a not very old DVR
> equipment sending notification emails on submission with TLS.
>
> Before (with Centos 7 and postfix 3.6) was working, but now, with rocky 8
>
