Bug 1337259

Summary:	[IMAPx] Disable and hide "Use Quick Resync if the server supports it"
Product:	Red Hat Enterprise Linux 7	Reporter:	Matěj Cepl <mcepl>
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.3	CC:	jkoten, mbarnes, mcrha, vbenes
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	evolution-data-server-3.12.11-32.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-04 00:25:49 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 Matěj Cepl 2016-05-18 16:04:03 UTC

Description of problem:
Hi, I have been told today that yet another error popping up on my Evolution (for the Red Hat Zimbra account) is probably caused by the option Quick Resync being switched on (I don't know why, I know it is not a default, but I have been carrying this profile for a long long time, so who knows how it did happen). And just when I switched it off for one account, in the other account (plain dovecot) I got some other error claiming that QRESYNC command failed.

If the QRESYNC setting is still unfinished and not enterprise ready, why do we have it even allowed to be switched on in RHEL. Couldn't we hide it in the settings dialogs?

Version-Release number of selected component (if applicable):
evolution-3.12.11-18.el7.x86_64
evolution-data-server-3.12.11-31.el7.x86_64

How reproducible:
errors are popping up all the time

Comment 1 Milan Crha 2016-05-18 16:23:28 UTC

Thanks for a bug report. You are right that the QResync either works, or breaks things heavily. I recall a user whom claimed that he has a new message on the server, but not shown in the evolution. We realized after some investigation that it was the QResync, which caused the misbehaviour in the new message delivery.

Comment 5 errata-xmlrpc 2016-11-04 00:25:49 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-2016-2206.html