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 1392567 - Sync CategoryList with mail Labels
Summary: Sync CategoryList with mail Labels
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution-ews
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Milan Crha
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1764818
TreeView+ depends on / blocked
 
Reported: 2016-11-07 19:07 UTC by Don Pellegrino
Modified: 2020-03-31 19:54 UTC (History)
5 users (show)

Fixed In Version: evolution-ews-3.28.5-4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1764818 (view as bug list)
Environment:
Last Closed: 2020-03-31 19:54:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 201167 0 High RESOLVED Complete implementation of category syncing 2020-09-04 09:08:02 UTC
GNOME Bugzilla 787908 0 Normal RESOLVED Microsoft Exchange Categories Missing 2020-09-04 09:08:02 UTC
Red Hat Product Errata RHSA-2020:1080 0 None None None 2020-03-31 19:54:47 UTC

Description Don Pellegrino 2016-11-07 19:07:47 UTC 
Description of problem:

When using the Microsoft Exchange backend for Mail, Calendar, Contacts, Tasks, etc., the categories from the Exchange server are not synchronized with the category list in Evolution.

How reproducible:

Always

Steps to Reproduce:
1. Connect Evolution to a Microsoft Exchange server using the EWS component.
2. Create a new Task

Actual results:

Observe that the list of available categories to assign is not synchronized with the set managed on the Exchange server.

Expected results:

Some form of category synchronization is needed.

Additional info:

Note that Evolution can be connected to local, Gmail, and Exchange accounts simultaneously. The set of categories should be a managed superset of Gmail tags, Exchange categories, and others with explicit tractability to which is being managed and synchronized where.
Comment 2 Milan Crha 2016-11-08 13:21:56 UTC 
(In reply to Donald Pellegrino from comment #0)
> Note that Evolution can be connected to local, Gmail, and Exchange accounts
> simultaneously. The set of categories should be a managed superset of Gmail
> tags, Exchange categories, and others with explicit tractability to which is
> being managed and synchronized where.

Thanks for a bug report. You are right, the problem as such is not that simple. I even do not know whether the EWS protocol allows to list all available "categories", because the evolution as such does not share it with other instances by any means, even other than through the items and what is set on them, which is not the same.
Comment 3 Don Pellegrino 2016-11-08 13:42:14 UTC 
It looks like some work was done on category synchronization and organized under upstream bug 201167.
Comment 4 Milan Crha 2017-03-09 18:36:22 UTC 
(In reply to Donald Pellegrino from comment #3)
> It looks like some work was done on category synchronization and organized
> under upstream bug 201167.

That bug is very old, it had been closed in time when evoltuion-ews did not even exist.

This might need some more work in evolution-ews itself, definitely first upstream, then get it to RHEL with some future update. Unfortunately, I looked what the EWS protocol offers and the closest sounds GobalCategories, but when looking more closely it's for other means. The other 'category' related elements are for existing items, not to get list of existing/predefined categories, thus the most the evolution-ews could do is to add any newly recognized categories to the list of available categories, which means that: a) newly added, but unused, categories won't be noticed until used; b) it would be only adding to the list of categories, without a way to remove from the categories, which is something one most likely doesn't want to see. Thus I'm afraid there is currently no way to receive predefined categories from an exchange server using EWS protocol. This checked with an Exchange 2013 documentation [1].

[1] https://msdn.microsoft.com/en-us/library/aa565683(v=exchg.150).aspx
Comment 5 Don Pellegrino 2017-09-19 13:43:02 UTC 
Thanks for identifying the relevant Microsoft Exchange Server documentation. Lacking the ability to directly get an enumeration of all categories defined on the Exchange server, I suppose an option would be to calculate the union of all categories assigned to items the client has seen.

However, it seems that Evolution is not displaying the Exchange categories as Evolution labels at all. Therefore, perhaps some other bug report is needed to generally address how tagging via Exchange categories and Evolution labels is handled in Evolution.
Comment 6 Milan Crha 2017-09-20 09:04:07 UTC 
I agree. Let's wait for the result of the upstream bug report, then it could be either backported to RHEL or it might get to RHEL with some update.
Comment 8 Milan Crha 2018-11-01 13:13:03 UTC 
This had been fixed upstream recently, within [1]. It's a one-way sync, only from the Exchange server to Evolution.

[1] https://gitlab.gnome.org/GNOME/evolution-ews/issues/24
Comment 12 Michal Odehnal 2019-10-25 11:02:00 UTC 
No longer reproducible with evolution-ews-3.28.5-4.el7
Comment 14 errata-xmlrpc 2020-03-31 19:54:27 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.

https://access.redhat.com/errata/RHSA-2020:1080
Note You need to log in before you can comment on or make changes to this bug.