Bug 905591 - Error while refreshing folder
Error while refreshing folder
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution-mapi (Show other bugs)
All Linux
medium Severity high
: rc
: ---
Assigned To: Matthew Barnes
Desktop QE
: Patch
Depends On:
Blocks: 960054 906341
  Show dependency treegraph
Reported: 2013-01-29 12:48 EST by Jiri Koten
Modified: 2015-09-27 22:14 EDT (History)
2 users (show)

See Also:
Fixed In Version: evolution-mapi-0.32.2-2.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-11-21 00:09:52 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
evolution-mapi-0.28.3-exchange2010-2.patch (6.72 KB, patch)
2013-01-30 08:06 EST, Milan Crha
no flags Details | Diff

  None (edit)
Description Jiri Koten 2013-01-29 12:48:21 EST
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):

How reproducible:

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.
Comment 2 Milan Crha 2013-01-30 07:40:07 EST
Two related upstream bug reports:

Comment 3 Milan Crha 2013-01-30 08:06:05 EST
Created attachment 690374 [details]

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.
Comment 5 Milan Crha 2013-05-09 06:24:56 EDT
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).
Comment 11 errata-xmlrpc 2013-11-21 00:09:52 EST
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.


Note You need to log in before you can comment on or make changes to this bug.