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.

Description of problem:
Evolution with Exchange MAPI account has a problem to refresh a folder after msg was moved/deleted from different client. 

Version-Release number of selected component (if applicable):
evolution-2.28.3-30.el6
evolution-mapi-0.28.3-11.el6
openchange-1.0-4.el6
samba4-libs-4.0.0-53.el6.rc4

How reproducible:
100%

Steps to Reproduce:
1. Start evolution
2. Send yourself a new msg 
3. Sync, e.g. Click Send/Receive
4. Read the msg, e.g. wait to download it and be marked as read
5. Close evolution
6. Delete the msg from different client. I have used owa web app.
7. Start evolution again 
  
Actual results:
Error while refreshing folder, msg is still present in the folder

Expected results:
No error, folder is updated - msg is no longer present 

Additional info:
Also when this happened, evolution also failed to send a new msg. I had to restart it again and click Send/Receive which seems to fix the issue, new msg was send and deleted msg was removed from the folder.

Two related upstream bug reports:

https://bugzilla.gnome.org/show_bug.cgi?id=608379
https://bugzilla.gnome.org/show_bug.cgi?id=653489

Created attachment 690374 [details]
evolution-mapi-0.28.3-exchange2010-2.patch

for evolution-mapi;

Backported the two upstream patches into one.

What happened here is that the QueryRows failed, the server returned MAPI_E_NOT_IMPLEMENTED (0x80040FFF), when evolution-mapi asked to query 0 (zero) rows from a table. This could happen when the folder didn't receive any new messages in the folder since the last fetch. Exchange 2007/2003 servers didn't suffer of this, but I agree with the change in the Exchange 2010 server, because it's useless to ask to query no rows.

Only the first upstream patch (see comment #2) is included in 0.32.2, the second didn't make it into that version, thus after bug #883017 lands, the patch at comment #3 will need adaptation (simplification).

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