Bug 1638486

Summary: IMAP connection to imap.gmail.com returns self-signed certificate when SNI not set
Product: [Fedora] Fedora Reporter: Andrey V. Henneberg <safir>
Component: claws-mailAssignee: Andreas Bierfert <andreas.bierfert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 29CC: andreas.bierfert, bugs.michael
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-11 18:35:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot of dialog with expanded certificate details (russian localization). none

Description Andrey V. Henneberg 2018-10-11 17:44:07 UTC
Created attachment 1492989 [details]
Screenshot of dialog with expanded certificate details (russian localization).

Description of problem:
When the Claws Mail connects to imap.gmail.com, it receives self-signed sertificate for host invalid2.invalid. The same problem was already fixed for openssl and fetchmail. And the same problem is actual for Sylpheed.

Version-Release number of selected component (if applicable):
3.16.0

How reproducible:
Yes

Steps to Reproduce:

1. Create account in Claws Mail for GMail account, if needed.
2. Connect to imap.gmail.com (to fetch mail or rebuild folders tree).
3. Expand certificate details.

Actual results:
Self-signed certificate and caution about it.

Expected results:
Valid certificate from Google

Additional info:

Comment 1 Andrey V. Henneberg 2018-10-11 17:45:51 UTC
Description of the same problem in Sylpheed: https://sylpheed.sraoss.jp/redmine/issues/306

Comment 2 Michael Schwendt 2018-10-11 18:12:29 UTC
See bug 1629151 for some background.

Comment 3 Michael Schwendt 2018-10-11 18:35:43 UTC

*** This bug has been marked as a duplicate of bug 1629151 ***