Comment # 10 on bug 1207963 from 
(In reply to Yasuhiko Kamata from comment #8)
> Thanks for testing again, I've found one more problem.
> 
> Due to upgrading of openssl-3, "libssl.so.3" and "libcrypto.so.3" should be
> included in candidate file names.
> (Because they are dynamically (manually) loaded as mentioned above, these
> file names should be specified in source code).
> 
> So I updated the patch and submitted again.
> Could you upgrade it and test again?
> I'll leave this report open.

Some progress I think with TLS.MinProtocol = TLSv1.2

After the latest patch, TLS for SMTP worked right away.  So that's fixed for
sure.

I had a lot of trouble with POP because somehow experimenting with the POP
settings sometimes resets the POP port to 110. It took quite some time for me
to realise that had been reset.  

I was further confused when I set the port back to 995. I was getting the error
dialog: "Could not connect to host Your POP3 server claims to support TLS but
negotiation was unsuccessful. You can disable TLS in KDE using the crypto
settings module..".  

I decided to enable POP SSL instead of TLS and I checked that the port stayed
set at 995.  At which point pop started to work, including after a reboot (for
most of my testing I just made sure kmail3 and any kdeinit processes had exited
before restarting kmail).

As with the openssl command, a kmail pop connection occasionally fails, perhaps
because I try too frequently.  BTW, the openssl command I use is:

   openssl  s_client  -connect  pop.actrix.co.nz:995

I think the failure may be prior to login, so it is possible to test against
this server without having a username or password.

I just looked in my backups at old copies of .kde/share/config/kmailrc.  It
seems prior to all this trouble commencing, I was actually using POP on port
110 with TLS, which was not supposed to be a TLS port. I have no idea how that
was working.  

Now POP on port 995 TLS doesn't work, but 995 SSL does. That's fine by me, but
I don't know whether that is a true pass for this patch.

You are receiving this mail because: