Honestly I didn't. I discovered the hard-coded String[]("TLSv1") in
MailConnection#getConnectedTLSSocket(), which is (imho) a bit odd.Imho, users should either be allowed to specify the enabled (and supported) protocols or to use the default ones provided by the jdk classes :) This is already done for MailConnection#getConnectedSSLSocket but not for the TLS handling. Am Mittwoch, den 02.12.2020, 13:09 +0100 schrieb Romain Manni-Bucau: > Hi Richard, > > Did you try a custom socket factory? In such a case you fully control > it. > > Romain Manni-Bucau > @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book > > > Le mer. 2 déc. 2020 à 13:01, Zowalla, Richard < > richard.zowa...@hs-heilbronn.de> a écrit : > > Hi, > > > > I did some debugging and found, that TLSv1 is hard-coded in > > MailConnection.java in v1.0.0 of Geronimo Java Mail. > > > > I filled a JIRA [1], which contains a patch proposal. > > > > Happy to receive some feedback. > > > > Thanks in advance, > > Richard > > > > [1] https://issues.apache.org/jira/browse/GERONIMO-6792 > >
smime.p7s
Description: S/MIME cryptographic signature
