After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 574784 - evolution-mapi can't fetch messages
evolution-mapi can't fetch messages
Product: evolution-mapi
Classification: Applications
Component: Mail
Other Linux
: Normal normal
: ---
Assigned To: Milan Crha
: 575558 (view as bug list)
Depends on:
Reported: 2009-03-10 16:41 UTC by Matthew Barnes
Modified: 2009-03-19 11:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

proposed ema patch (13.67 KB, patch)
2009-03-17 12:29 UTC, Milan Crha
committed Details | Review

Description Matthew Barnes 2009-03-10 16:41:11 UTC
Fedora bug:

Configured evolution-mapi account with today's rawhide
(evolution-2.25.92-1.fc11.i586, evolution-mapi-0.25.92-1.fc11.i586).  Connected
to server and loaded folder list successfully, and shows unread message count
in folders, but when I click on a folder it says that there aren't any unread
messages and says there was an error fetching them.  Exited and restarted
evolution and same problem occurred. Log is attached.

It's an Exchange 2007 server, FYI.

Output of evolution when it fails to fetch messages:
Comment 1 David Nalley 2009-03-11 02:49:39 UTC
The same behavior is displayed with Exchange 2003. 
Comment 2 Johnny Jacob 2009-03-11 03:00:32 UTC
More info :
Comment 3 Jerry Amundson 2009-03-11 22:48:43 UTC
A couple points to note here.
1. I believe a regression of sorts has occurred, mostly because I used the same account settings against the same Exchange 2003 server (clustered) while the package was under Fedora Review with (some) success.
2. The key error is OpenFolder               : MAPI_E_NOT_FOUND (0x8004010F), and not the 0x478 error which relates to _public_ folders.
Comment 4 David Nalley 2009-03-12 18:11:33 UTC
Re the comment 2 - the Exchange server I am hitting is a standalone - not clustered. 
Like Jerry Amundson points out, if I do packet captures, I see the 0x8004010F response, and if I launch evolution from the command-line the MAPI_E_NOT_FOUND shows up in stderr 

Comment 5 Johnny Jacob 2009-03-17 11:06:58 UTC
(In reply to comment #0)

> Output of evolution when it fails to fetch messages:

The folder ids are messed up here .


Comment 6 Johnny Jacob 2009-03-17 11:20:57 UTC
r126 seems to be the issue.
Comment 7 Milan Crha 2009-03-17 12:29:59 UTC
Created attachment 130818 [details] [review]
proposed ema patch

for evolution-mapi;

Ouch, I used wrong format specifier for IDs and didn't realize a mistake :(
I'm sorry. This patch does this:

Comment 8 Johnny Jacob 2009-03-17 17:45:59 UTC
*** Bug 575558 has been marked as a duplicate of this bug. ***
Comment 9 Milan Crha 2009-03-19 09:59:05 UTC
Committed to trunk. Committed revision 187.
Comment 10 Johnny Jacob 2009-03-19 11:04:06 UTC
patch available as part of release.