RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 750916 - Evolution should offer TLSv1 for IMAPS handshake
Summary: Evolution should offer TLSv1 for IMAPS handshake
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution-data-server
Version: 6.1
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-02 19:42 UTC by Daniel Sands
Modified: 2014-01-02 11:09 UTC (History)
3 users (show)

Fixed In Version: evolution-data-server-2.32.3-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-21 05:04:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Patch to offer TLSv1 for SSL-based connections to IMAP server (717 bytes, application/octet-stream)
2011-11-02 19:42 UTC, Daniel Sands 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1540 0 normal SHIPPED_LIVE Low: evolution security, bug fix, and enhancement update 2013-11-21 00:40:51 UTC

Description Daniel Sands 2011-11-02 19:42:37 UTC 
Created attachment 531432 [details]
Patch to offer TLSv1 for SSL-based connections to IMAP server

Description of problem:
The Exchange Servers that I connect to (version 2011) are configured to offer IMAP, but require secure SSL.  Apparently the latest versions require TLSv1, as they will disconnect without a reply if TLSv1 is not offered.

Version-Release number of selected component (if applicable):
evolution-data-server-2.28.3-15.el6

How reproducible:
Always

Steps to Reproduce:
1. Find a recent Exchange Server that offers IMAPS.  Server may have been hardened to require newer/more secure protocols.
2. Set up an IMAP account that connects to the secure port
3. Attempt to send/receive mail
  
Actual results:
Exchange Server disconnects.  Evolution reports an unexpected disconnect.

Expected results:
Successful mail retrieval

Additional info:
Fix is trivial.  Patch attached.
Comment 2 RHEL Program Management 2011-11-02 20:08:57 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 3 Milan Crha 2013-05-09 14:00:28 UTC 
Thanks for a bug report. Why not just use TLS then? I mean in account preferences, you can choose there to use SSL or TLS, thus use TLS, if server requires it. I was able to connect to exchange 2010 and Exchange 2007 servers, but I do not recall whether it was with SSL, TLS, or even without both of these.

Also note of this change [1], which may or may not be related.

[1] https://git.gnome.org/browse/evolution-data-server/commit/?id=b1a5cb02bc7412
Comment 4 Daniel Sands 2013-05-09 18:09:08 UTC 
The TLS option should really be called "STARTLS" because that's the avenue it uses.  It assumes that the connection is initially open IMAP and upon receipt of the server greeting it sends the STARTTLS command.  This is not the same at all as making TLS an option for establishing secure communications over IMAPS.

The referred change only deprecates SSLv2.  SSLv3 is the current "best" that Evolution (at least the version used in RHEL6) allows.  But Exchange wants TLS.
Comment 5 Milan Crha 2013-05-10 07:43:05 UTC 
OK, I'd say we can do it, patch available. We only should make sure that other servers will work with this change as well.
Comment 9 Milan Crha 2013-06-11 15:52:24 UTC 
Used change in evolution-data-server-2.32.3-3.el6 covers both IMAP and IMAP+.
Comment 17 errata-xmlrpc 2013-11-21 05:04:08 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1540.html
Note You need to log in before you can comment on or make changes to this bug.