Bug 182835 - Kmail - SSL negotation fails when attempting to connect to imaps server.
Summary: Kmail - SSL negotation fails when attempting to connect to imaps server.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-02 09:22 UTC by Darryl
Modified: 2015-04-12 10:15 UTC (History)
0 users

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 Darryl 2009-02-02 09:22:02 UTC
Version:            (using KDE 4.2.0)
Compiler:          gcc 4.2.4 
OS:                Linux
Installed from:    Gentoo Packages

This bug recurs on both Gentoo and Arch Linux AMD64 machines.  When kmail attempts to connect to the IMAPS server SSL negotiation fails.  Both email servers in question are running on SME Server.  I understand others running Arch Linux have been unable to connect to GMail using SSL.

Relevant console output from Arch Linux is as follows:

kio_imap4(6888)/kio_imap IMAP4Protocol::dispatch: IMAP4::dispatch - command= 48
kio_imap4(6888)/kio_imap IMAP4Protocol::dispatch: IMAP4::dispatch - command= 49
kio_imap4(6888)/kio_imap IMAP4Protocol::makeLogin: IMAP4::makeLogin - checking login
kio_imap4(6888)/kio_imap IMAP4Protocol::makeLogin: IMAP4::makeLogin - alreadyConnected false
kio_imap4(6888)/kio (TCPSlaveBase) KIO::TCPSlaveBase::disconnectFromHost:
kdeinit4: PID 6887 terminated.
kio_imap4(6888)/kssl KIO::TCPSlaveBase::startTLSInternal: Initial SSL handshake failed. encryptionStarted is false , cipher.isNull() is true , cipher.usedBits() is 0 , the socket says: "Unknown error" and the list of SSL errors contains 0 items.
kio_imap4(6888)/kio (TCPSlaveBase) KIO::TCPSlaveBase::disconnectFromHost:
kio_imap4(6888)/kssl KIO::TCPSlaveBase::startTLSInternal: Initial SSL handshake failed. encryptionStarted is false , cipher.isNull() is true , cipher.usedBits() is 0 , the socket says: "Unknown error" and the list of SSL errors contains 0 items.
kmail(6873)/kio (KIOJob) KIO::SlaveInterface::dispatch: error 123 "mail.barlow.com.au: SSL negotiation failed"
kio_imap4(6888)/kio_imap IMAP4Protocol::makeLogin: makeLogin - NO login
kio_imap4(6888)/kio_imap IMAP4Protocol::dispatch: IMAP4::dispatch - command= 50
kdeinit4: Got EXT_EXEC '/usr/bin/knotify4' from launcher.
kdeinit4: preparing to launch /usr/bin/knotify4
klauncher(6879)/kio (KLauncher) KLauncher::processRequestReturn: "/usr/bin/knotify4" (pid 6891) up and running.
knotify(6892) KNotify::event: 1 ref= 0
kdeinit4: PID 6891 terminated.
kmail(6873)/kdeui (KNotification) KNotification::slotReceivedId: 0
kmail(6873)/kdeui (KNotification) KNotification::close: 0
kmail(6873)/kdeui (KNotification) KNotification::~KNotification: -2
Comment 1 Darryl 2009-02-03 00:05:48 UTC
I want to correct an important error in my bug report.  At least one other user of Arch actually indicated that they were able to connect to Gmail with SSL, not "unable" to as in the report.  My apologies.
Comment 2 Laurent Montel 2015-04-12 10:15:18 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.