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

Thomas Ward teward at thomas-ward.net
Wed Sep 25 16:37:02 UTC 2019


This requires the SRU template and all requisite information including
test cases to determine if this is SRUable.

Please refer to https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
for details.  Once you apply the SRU template, if you still need a
sponsor for this, please resubscribe ubuntu-sponsors to the bug.

You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.

  Sypheed not (or no longer) using SNI for SSL connections

Status in sylpheed package in Ubuntu:

Bug description:
  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

To manage notifications about this bug go to:

More information about the Ubuntu-sponsors mailing list