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 659020 - Destination folder not updated after transfer_messages call
Destination folder not updated after transfer_messages call
Status: RESOLVED FIXED
Product: evolution-mapi
Classification: Applications
Component: Mail
3.1.x
Other Linux
: Normal normal
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2011-09-14 08:49 UTC by sean finney
Modified: 2011-09-15 08:46 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
ema patch (526 bytes, patch)
2011-09-15 08:44 UTC, Milan Crha 		committed Details | Review

Description sean finney 2011-09-14 08:49:31 UTC 
Running master as of a week or two back.

I have evo-mapi set up with a few filters that automatically move some messages to subfolders of INBOX.  the messages are correctly filtered, but the subfolders are not flagged as containing new messages until I manually switch over to them and check.  I'm not sure that it happens for 100% of the messages (maybe not after first start up), but once it starts happening it continues to happen, at least.
Comment 1 Milan Crha 2011-09-15 07:07:07 UTC 
Do you have the target folder selected when the message is shown there, or not? It might make a difference, as when you select it then the folder refreshes, thus I guess you have it selected in time of a new message arrival.
Comment 2 Milan Crha 2011-09-15 07:16:09 UTC 
Confirming for the "folder selected", I see all about "Filtering message", but the folder doesn't update on its own.
Comment 3 Milan Crha 2011-09-15 08:44:29 UTC 
Created attachment 196595 [details] [review]
ema patch

for evolution-mapi;

The transfer_messages function didn't call update on the destination folder, thus others didn't know the change. It's also because ema uses server-side message moving, which is better than decoding/encoding the message through Camel internals. This patch adds the necessary refresh call to it.
Comment 4 Milan Crha 2011-09-15 08:46:19 UTC 
Created commit 5fe4acb in ema master (3.1.92+)