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):
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
Error while refreshing folder, msg is still present in the folder
No error, folder is updated - msg is no longer present
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:
Created attachment 690374 [details]
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.