Bug 1392567
Summary: | Sync CategoryList with mail Labels | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Don Pellegrino <don> | |
Component: | evolution-ews | Assignee: | Milan Crha <mcrha> | |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | |
Severity: | low | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 7.3 | CC: | don, mcrha, modehnal, tpelka, vbenes | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | evolution-ews-3.28.5-4 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1764818 (view as bug list) | Environment: | ||
Last Closed: | 2020-03-31 19:54:27 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1764818 |
Description
Don Pellegrino
2016-11-07 19:07:47 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. It looks like some work was done on category synchronization and organized under upstream bug 201167. (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 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. 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. 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 No longer reproducible with evolution-ews-3.28.5-4.el7 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 |