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 1090568 - Read notification is still proposed after being notified
Summary: Read notification is still proposed after being notified
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution-ews
Version: 7.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1174417
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-23 15:33 UTC by Benjamin Bellec
Modified: 2015-11-19 07:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Handle Read Receipt doesn't work Consequence: evolution-ews accounts do not handle read receipt Fix: add handling of read receipt Result: Read Receipt received in an evolution-ews account can be handled properly
Clone Of:
Environment:
Last Closed: 2015-11-19 07:55:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 656805 0 None None None Never
Red Hat Product Errata RHBA-2015:2226 0 normal SHIPPED_LIVE evolution bug fix and enhancement update 2015-11-19 08:37:43 UTC

Description Benjamin Bellec 2014-04-23 15:33:56 UTC 
Description of problem:
I configured Gnome Evolution to manage my professional email account (on a Exchange 2007 Server) using evolution-ews.
When someone send me an email with a read notification, Evolution proposes me to send the notificiation to the sender of the email. I then click to send the notification, which it receives correctly.
But, later, if I go back on the email, Evolution still proposes me to send a read notification. If I click again, the initial sender again receives a new read notification.

I don't know if it's a bug or an enhancement, anyway it would be nice that Evolution records which notification have already been sent. I don't want to spam my colleagues :-)

Version-Release number of selected component (if applicable):
evolution-3.8.5-21.el7.x86_64 (from RHEL 7.0 RC DVD)
evolution-ews-3.8.5-8.el7.x86_64

Steps to Reproduce:
1. Open Evolution
2. Tell someone (or yourself) to send you an email with a read notification request
3. Read this email and send the read notification
4. Close Evolution
5. Open Evolution
6. Go back on this email

Actual results:
Evolution says that the sender want a notification.

Expected results:
Evolution should says that the sender have already been notified.
Comment 2 RHEL Program Management 2014-05-03 05:48:15 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3 Milan Crha 2014-05-06 17:41:45 UTC 
Thanks for a bug report. There is a similar bug report upstream [1], which I will use for the initial work. Once it's done there, in the upstream code, then the change can be backported to RHEL. The bug [1] is not exactly about the same thing/behaviour, but I'll use it as a general bug for Read Receipt issues.

From my initial testing, the server itself sends automatically read-receipts to the sender, while evolution also generates a message and sends it separately. that is a (default?) behaviour on an Exchange 2010 server. Yours Exchange 2007 can behave slightly differently. This needs fixing anyway, because the sender may not receive the read confirmation twice.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=656805
Comment 4 Benjamin Bellec 2014-05-06 18:29:01 UTC 
Good to heard that :-)
Comment 5 Milan Crha 2014-05-07 10:52:55 UTC 
The above-mentioned upstream bug contains a fix now.
Comment 7 Jiri Koten 2015-05-14 08:57:17 UTC 
It should be fixed in evolution-ews-3.12.11-1.el7
Comment 11 errata-xmlrpc 2015-11-19 07:55:55 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://rhn.redhat.com/errata/RHBA-2015-2226.html
Note You need to log in before you can comment on or make changes to this bug.