[Bug 1799345] [NEW] Sypheed not (or no longer) using SNI for SSL connections

Launchpad Bug Tracker 1799345 at bugs.launchpad.net
Wed Sep 25 16:28:16 UTC 2019

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

Problem appeared after upgrading from Ubuntu 18.04 to 18.10.
When starting Sylpheed, connecting to imap.gmail.com over SSL, I get a warning embedded in the SSL certificate:  "Subject: /OU=No SNI provided; please fix your client./CN=invalid2.invalid "

May be related to this bug report about 'fetchmail' in redhat enterprise when it was still using TLSv1.2 instead of TLSv1.3:

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: sylpheed 3.5.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 23 00:27:01 2018
InstallationDate: Installed on 2016-06-05 (869 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: sylpheed
UpgradeStatus: Upgraded to cosmic on 2018-10-21 (1 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498

** Affects: sylpheed (Ubuntu)
     Importance: Undecided
         Status: Triaged

** Tags: amd64 apport-bug cosmic patch
Sypheed not (or no longer) using SNI for SSL connections
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.

More information about the Ubuntu-sponsors mailing list