Bug 1223479

Summary:	[IMAPx] Process untagged EXPUNGE response only once
Product:	Red Hat Enterprise Linux 7	Reporter:	Milan Crha <mcrha>
Component:	evolution-data-server	Assignee:	Milan Crha <mcrha>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	jkoten, mcrha
Target Milestone:	rc	Keywords:	Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	evolution-data-server-3.12.11-6.el7	Doc Type:	Bug Fix
Doc Text:	Cause: IMAP account messages locally removed after delete of other message while still being left on the server Consequence: an EXPUNGE operation response in an IMAP folder could be delivered multiple times, in each running connection, which caused repeated message delete from the local summary Fix: process the EXPUNGE operation response only in the connection which invoke the EXPUNGE operation Result: only server-side deleted messages are removed from the local cache	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 07:58:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Milan Crha 2015-05-20 15:33:15 UTC

It could happen that a message move in an IMAPx account caused multiple messages being removed from the view, even they were left in the original folder, as stated at an upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=734300

Steps:
a) configure a Google mail account using IMAPx, at least two concurrent
   connections, no QResync, no IDLE (Listen for server change notification)
b) have a folder with at least 6 messages
c) move, by drag&drop, three messages to another GMail folder, can be one
   by one, just start from the previous of the last
d) select the new destination folder and move the messages back, again
   start with the previous of the last message
e) repeat c) & d) for couple times; it happens one that the UI will remove not
   only the moved message, but also the next of it.

The upstream bug report contains more detailed description of the cause.

Comment 4 errata-xmlrpc 2015-11-19 07:58:30 UTC

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.

https://rhn.redhat.com/errata/RHBA-2015-2226.html