GNOME Bugzilla – Bug 757633
folder changes only pushed to imap server on folder change
Last modified: 2015-11-05 15:01:21 UTC
When using an IMAP folder, if I mark a message deleted in Evolution another client will not see that message deleted until I open a different folder in Evolution (or expunge, of course). This makes using Evolution with other IMAP clients on the same mail accounts/boxes troublesome. I suspect this is being done for performance reasons perhaps? Is it really gaining that much performance, particularly if the IMAP server and Evolution are co-located on the name local high-speed network? Some alternative options: 1) Only batch for a limited amount of time, like say, 5 seconds * Perhaps this should be configurable 2) Make this behaviour optional based on: a) A user selectable item like a preference checkbox b) A heuristic such as seeing messages changing status (i.e. deleted, unread->read, etc. indicating that the mail account/box is being read by other clients c) Latency of IMAP operations, inferring locality of and/or load on IMAP server Combinations of the above are also possible of course. #2 is probably the low hanging fruit here.
Thanks for a bug report. Running multiple IMAP clients simultaneously is discouraged, if for nothing else, then for the \Recent flag, which will see only one client, the first noticing the newly received message. Nonetheless, this is done in 3.18.x, since bug #699529. *** This bug has been marked as a duplicate of bug 699529 ***
(In reply to Milan Crha from comment #1) > Thanks for a bug report. NP > Running multiple IMAP clients simultaneously is > discouraged, That might be good in theory, but it's certainly not anywhere near reality. With mobile/personal devices in addition to the desktop and laptop devices people already use it's inevitable that multiple clients are going to access the same mailboxes and folders. > if for nothing else, then for the \Recent flag, which will see > only one client, the first noticing the newly received message. Fair enough. > Nonetheless, this is done in 3.18.x, since bug #699529. Awesome! F23, here I come. :-)