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 224351 - IMAP mailboxes do not update correctly when mail is marked or deleted.
IMAP mailboxes do not update correctly when mail is marked or deleted.
Status: RESOLVED DUPLICATE of bug 216927
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other other
: Normal major
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2002-05-07 14:55 UTC by chet
Modified: 2002-05-09 20:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description chet 2002-05-07 14:55:36 UTC 
Description of Problem:


Steps to reproduce the problem:
1. Connect to IMAP account with Evolution &
another client.
2. In other client mark messages as read, delete
messages, expunge.

Actual Results:
In Evolution these changes are not shown, even if
you click Send/Receive.  Nothing can be done
except to shut down and restart the mailer.

Expected Results:
Changes to the IMAP folder should be seen in the
mail client.  This feature works in other mail
clients.

How often does this happen? 
100%

Additional Information:
To enable multiple access to the same IMAP folder
you may have to do something like this: (WU imapd)

1. In a shell run /usr/sbin/impad
2. Type "1 create #driver.mbx:TestFolder", then "2
logout"
3. Add messages to TestFolder.
Comment 1 Gerardo Marin 2002-05-07 16:06:35 UTC 

*** This bug has been marked as a duplicate of 217990 ***
Comment 2 chet 2002-05-09 17:02:33 UTC 
This is NOT a duplicate of 17990.

bug 217990 states that "If another IMAP client access the server and
modifies the mailbox, Evolution will detect it and resynchronize.
However in the process it fails to update the vFolders."

However, I am pointing out that if another IMAP client access the
server and modifies the mailbox, Evolution *** WILL NOT *** detect it
and resynchronize.  Further, there is NO WAY to make it resync other
than to shut down and restart Evolution.
Comment 3 Jeffrey Stedfast 2002-05-09 20:15:30 UTC 
while I experience this problem to some degree (ie, if another client
changes message flags), I don't have a problem if the other client
expunges messages (ie, evolution detects that the other client has
expunged).

The problem is that IMAP does not notify each client of updates in the
message flags, we have to re-query to find that out. How often do you
requery for message flags? I dunno, but too often and it slows things
down a lot if you have a lot of messages. Too little and you get
complaints like this one.

anyways, not going to even bother with this bug until I get a chance
to rewrite the IMAP code.

*** This bug has been marked as a duplicate of 216927 ***