Bug 363531 - TLS negotiation was unsuccessful
Summary: TLS negotiation was unsuccessful
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: crypto (show other bugs)
Version: 5.1.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-25 23:42 UTC by sedrubal
Modified: 2022-12-10 05:13 UTC (History)
4 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 sedrubal 2016-05-25 23:42:57 UTC
I want to send a mail using SMTP with STARTTLS. With other programs (thunderbird, k9mail) there is not problem but kmail complains about a unsuccessful TLS negotiation.

First warning dialogue:

> The server failed the authenticity check (mail.rommel.stw.uni-erlangen.de).
> 
> The certificate authority's certificate is invalid
> The certificate cannot be verified for internal reasons

Clicking on "Continue" works, clicking on "Details" displays the expected TLS certificate (I thinkt everything is correct). Clicking on "Cancel" displays:

> Your SMTP server claims to support TLS, but negotiation was unsuccessful.
> You can disable TLS in the SMTP account settings dialog.

Is there a way to debug such issues (displaying the conversation between kmail and the SMTP Server)?

The server is exim4.
Comment 1 Gerry Gavigan 2016-06-01 22:06:07 UTC
I've just suffered a similar problem - offered in case it helps 

configure kmail -> sending account ->, modify -> advanced tab, and you might find the TLS box checked,
Comment 2 sedrubal 2016-06-03 06:26:04 UTC
Yes, it is checked, because the server supports TLS and I want to use TLS ;) it is working with Thunderbird, K9-mail, evince and many other MUAs...
Comment 3 kdebugs.anon134 2016-08-15 03:36:20 UTC
I am having the same problem described above.  This problem is repeatable 100% of the time.  I can not send emails via SMTP using TLS over port 587 in KMail Version 4.14.10.  :(  :(  Everything worked correctly in KMail yesterday, and now with no configuration changes, this problem appeared.   Sending emails *without* transport encryption  over port 587 works correctly.

Here are the error details:
1)  A dialog box pops up titled "Server Authentication - Mail Dispatcher Agent", containing the following message:
"The server failed the authenticity check (smtp.q.com).

The certificate authority's certificate is invalid
The root certificate authority's certificate is not trusted for this purpose
The certificate cannot be verified for internal reasons"

2)  I click on the button labeled "Details".  A new Dialog box pops up labeled "KDE SSL Information - Mail Dispatcher Agent" containing the following message:
"Current connection is secured with SSL.
Address: smtp.q.com
IP address: 205.169.121.111
Encrypttion: AES, using 256 bits of a 256 bit key
Details: Auth = RSA, Kx = RSA, MAC = SHA-1
SSL Version: SSLv3
Certificate chain: [greyed out drop-down menu]mail.q.com
======== Start Tabs =========
[Tab: Subject]
Common name: mail.q.com
Organization: CenturyLink
Organizational unit: Interactive Services Group
Country: US
State: Louisiana
City: Monroe
[Tab:Issuer]
Common name: Symantec Class 3 Secure Server SHA256 SSL CA
Organization: Symantec Corporation
Organizational unit: Symantec Trust Network
Country: US
State: [blank]
City: [blank]
======== End Tabs =========
Trusted:
NO, there were errors:
The certificate authority's certificate is invalid
The root certificate authority's certificate is not trusted for this purpose
The certificate cannot be verified for internal reasons
Validity period: 08/04/16 12:00 AM to 08/16/17 11:59 PM
Serial number: 41:5b:6d:03:67:ea:aa:ba:df:f7:a5:68:66:9e:f0:60
MD5 digest: acc7ed0f204b8991296cb80aa368e88a
SHA1 digest: b60c6182356616ee3dfb36d1df7f4c081cd5d7d7"

3)  Then I click the dialog button labeled "Close".

I am very puzzled by this, in part because KMail is configured to use TLS, yet the certificate information displayed is for SSL.  I am further puzzled that the SMTP  server is configured as "smtp.q.com", and NOT "mail.q.com" as suggested by the SSL certificate information in the second dialog box.

Like sedrubal stated above, I too can send emails via SMTP using TLS using port 587 in Firebird version 45.2.

If it would help, I can temporarily donate  an email address with CenturyLink; yet, I can not guarantee it will work outside the USA.

I was on the phone with my clown of an ISP (CenturyLink) for 4 hours, and they were not able to resolve the problem - which leaves me quite screwed.

Please, please help!  :(  I really like KMail and REALLY do not want to switch to Thunderbird or anything else.
Comment 4 kdebugs.anon134 2016-08-15 03:37:55 UTC
I forgot to add that my system is using openSUSE Leap 42.1 for x86_64.
Comment 5 kdebugs.anon134 2016-08-15 03:52:50 UTC
I also forgot to add that after closing the first 2 dialog boxes, a new dialog box appears titled "Connection Failed - Mail Dispatcher Agent" containing the following message:
"Your SMTP server claims to support TLS, but negotiation was unsuccessful.
You can disable TLS in the SMTP account settings dialog"
Comment 6 Terényi, Balázs 2017-09-15 07:29:29 UTC
The same here with IMAP and a Letsencrypt cert on OpenSuSE Leap 42.2 with KMail Version 5.3.0 KDE Frameworks 5.26.0 Qt 5.6.1.
Comment 7 Justin Zobel 2022-11-10 08:52:08 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 8 Bug Janitor Service 2022-11-25 05:16:17 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2022-12-10 05:13:33 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!