Comment # 5 on bug 1207963 from Michael Hamilton

I've found the cause of my continuing problem with kmail3/kdelibs3, which is no
longer really to blame.

It has something to do with /etc/crypto-policies/back-ends/opensslcnf.config.  

The file opensslcnf.conf does not appear to have changed with the upgrade to
openssl3.X.  I have a machine that has not been updated for many months with
the same file contents.  However, it seems that if I change:

   TLS.MinProtocol = TLSv1.2

to

   TLS.MinProtocol = TLSv1.0

then I no longer see any errors.  I'm not actually sure what this means.  

1) Was MinProtocol not being enforced prior to openssl3.X?  
2) Is my ISP actually still using TLSv1.0? I don't know how to confirm what
they are using.

I'm not sure if this is a bug.  The bug against KDE3 should probably be closed
as resolved. Should a new one be raised against openssl3? Or
crypto-policies-20210917.c9d86d1-1.11.noarch which owns the config file:

# rpm -q -f /etc/crypto-policies/back-ends/opensslcnf.config
crypto-policies-20210917.c9d86d1-1.11.noarch

Or is this not a bug, more of a missing release note issue.