Bug 374795 - qt.network.ssl: QSslSocket::startClientEncryption: cannot start handshake on non-plain connection
Summary: qt.network.ssl: QSslSocket::startClientEncryption: cannot start handshake on ...
Status: RESOLVED NOT A BUG
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-09 08:49 UTC by Hrvoje Senjan
Modified: 2017-12-21 13:41 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hrvoje Senjan 2017-01-09 08:49:23 UTC
says the log, thus making master kmail kaputt! Maybe wrong component though
Comment 1 Rex Dieter 2017-02-16 15:59:41 UTC
I guess I'm seeing this too today on my f25 box with kmail-16.12.2, unable to setup google mail account.
Comment 2 Daniel Vrátil 2017-02-16 16:11:54 UTC
If you have self-compiled kdepim-runtime and you installed it into a custom (non-/usr) prefix, then you must manually copy libkdexoauth2.so (from $prefix/lib/sasl2) to /usr/lib(64)/sasl2 - unfortunately libsasl ignores environment variables and only looks for plugins into /usr.
Comment 3 Rex Dieter 2017-02-16 17:10:44 UTC
Turns out in my case I needed to set 
https://www.google.com/settings/security/lesssecureapps
first.

Dan helpfully pointed out (on irc) that future releases of kdepim will include an OAuth authentication plugin, so this will no longer be necessary.
Comment 4 KDE 2017-12-21 13:41:33 UTC
I'm not sure why this is resolved ... I've been hitting this continually in KMail 5.5.3 ever since I've upgraded to Kubuntu 17.10.  It seems to happen quite consistently when initial authentication times out and needs to be refreshed. It can be fixed by switching the accounts offline, then back on, but is a *serious* pain.