Description of problem:
It seems that Evolution has made a number of useful improvements to the interoperability with Microsoft Exchange since release 3.22.x. A version bump to the latest release series of Evolution would be useful.
Version-Release number of selected component (if applicable):
$ rpm -qi evolution
Name : evolution
Version : 3.22.6
Release : 10.el7
Install Date: Wed 02 Aug 2017 02:06:33 PM EDT
Group : Applications/Productivity
Size : 50230273
License : GPLv2+ and GFDL
Signature : RSA/SHA256, Tue 30 May 2017 01:55:24 AM EDT, Key ID 199e2f91fd431d51
Source RPM : evolution-3.22.6-10.el7.src.rpm
Build Date : Mon 29 May 2017 05:53:38 PM EDT
Build Host : x86-030.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor : Red Hat, Inc.
URL : https://wiki.gnome.org/Apps/Evolution
Summary : Mail and calendar client for GNOME
Evolution is the GNOME mailer, calendar, contact manager and
communications tool. The components which make up Evolution
are tightly integrated with one another and act as a seamless
personal information-management tool.
If this is not super critical request I would like aks to consider postponing to 7.6
Aligning the update with a point release of RHEL seems to make sense. I would not rate any of the corresponding issues with Evolution 3.22.x as critical.
Thanks for a bug report. Please note that this means to bring also evolution-data-server (eds), evolution-ews and evolution-mapi. While there is not much issue with the two later, the eds is a problem, because it's a critical core part of the desktop, due to multiple other applications than just evolution connecting to its services, including GNOME Shell itself (the gnome-shell-calendar-server, which shows events in the clock popup). That means that an update of Evolution may eventually require update of other packages as well.
*** Bug 1576528 has been marked as a duplicate of this bug. ***
Verified with RHEL-7.6-20180812.n.0
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.