RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1291393 - [IMAPx] IDLE flag update can be applied to a wrong message
Summary: [IMAPx] IDLE flag update can be applied to a wrong message
Keywords:
Status: CLOSED DUPLICATE of bug 1265684
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution-data-server
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Milan Crha
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-14 18:46 UTC by Simo Sorce
Modified: 2016-03-07 14:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-07 14:09:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Simo Sorce 2015-12-14 18:46:55 UTC
Sometimes evolution gets confused when it makes some changes on one connection and receive them back on another IDEL connection, as races can happen in how things are applied.

Some details have already been provided to the maintainer directly, but I am available for further inquiries.

This is part of the explanation about the issue as exchanged via email:

> There are active three
> connections, A, C, and D. The C does the update of some other folder
> and clutter the log with a boring stuff. Connection D is used for the
> deletion, there was run the STORE of the \Deleted flag and the expunge.
> Finally the connection A is in IDLE on the same folder as the D, which
> is Lists/sssd-devel. The thins is that the A, while in IDLE, receives
> also flag changes in that folder, but not based on the UID, but based
> on the index number in the folder summary (that's how the server
> reports it).
> 
> The run is this:
> A - parses received flag changes in the folder
> C - stops IDLE and runs the flag receive in some other folder
> D - runs store on the \Deleted flag on the 4 messages
>   - while the A is still processing previously received data,
>     the D calls EXPUNGE and received confirmation immediatelly
>   - ignores EXPUNGE responses, because it run the EXPUNGE command
>   - two out of the 4 deleted messages are removed from the local
>     summary at the end of the EXPUNGE command of the connection D
> A - is still parsing old stuff
> D - goes into IDLE
> A - only now received the \Deleted flag changes being done at the
>     beginning in the connection D - that's too late, there are already
>     removed messages in the local summary, and the flags are received
>     with their sequence number, not with the UID
>   - sets the \Deleted flag on the 4 messages
>   - receives EXPUNGE notifications, but ignores them
> C - still receiving stored flags on the messages in the other folder

Comment 2 Milan Crha 2016-03-07 14:09:58 UTC
Changes for this are part of the changes for bug #1265684, thus I mark this as a duplicate of it.

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


Note You need to log in before you can comment on or make changes to this bug.