Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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
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.
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