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 649420 - Work around QRESYNC bug in Zimbra's IMAP server
Work around QRESYNC bug in Zimbra's IMAP server
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Mailer
3.8.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[imapx]
: 660588 677414 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-05-04 23:47 UTC by Laurent Aguerreche
Modified: 2013-09-14 16:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Laurent Aguerreche 2011-05-04 23:47:06 UTC
After a few days (less than one week) I always get a big message in red in Evolution that says:

G00194 BAD parse error: invalid message sequence number: 1,114,600,762,816,834

These numbers can be different but not the message. The solution is always the same, I have to remove all emails into '~/.local/share/evolution/mail/imapx/me\@imap.free.fr/' and so download them again later.

When Evolution is in this state but I try anyway to read an 'old' email -- which means an emails that isn't cached on my machine -- I see the following error in the message window: 'SELECT INBOX failed: parse error: invalid message sequence number: 1,114,600,762,816,834'  So, the same message...

The remote IMAPx server is Zimbra but I don't know which version (it is provided by the French ISP Free for all its customers).

I can add that I don't encounter any problem during the days it works: I mean that the emails are immediately presented by Evolution when the Zimbra servers got them.



Here an example of what occurs with an 'old' email I'm trying to read:



DB SQL operation [SELECT uid, flags, size, dsent, dreceived, subject, mail_from, mail_to, mail_cc, mlist, part, labels, usertags, cinfo, bdata FROM 'INBOX' ] started

Database succesfully closed 
[imapx:A] camel_imapx_read: buffer is '* STATUS "INBOX" (MESSAGES 832 UIDNEXT 67422 UIDVALIDITY 1 UNSEEN 3 HIGHESTMODSEQ 370502)
A00005 OK STATUS completed
'
[imapx:A] token '*'
[imapx:A] got untagged response
[imapx:A] token TOKEN 'STATUS'
[imapx:A] Have token 'STATUS' id 0
[imapx:A] token STRING 'INBOX'
[imapx:A] token '('
[imapx:A] token TOKEN 'MESSAGES'
[imapx:A] token TOKEN '832'
[imapx:A] token TOKEN 'UIDNEXT'
[imapx:A] token TOKEN '67422'
[imapx:A] token TOKEN 'UIDVALIDITY'
[imapx:A] token TOKEN '1'
[imapx:A] token TOKEN 'UNSEEN'
[imapx:A] token TOKEN '3'
[imapx:A] token TOKEN 'HIGHESTMODSEQ'
[imapx:A] token TOKEN '370502'
[imapx:A] token ')'
[imapx:?] find_full: comparing namespace '' to name 'INBOX'
[imapx:A] Got folder path 'INBOX' for full 'INBOX'
[imapx:A] token '
'
[imapx:A] token TOKEN 'A00005'
[imapx:A] Got completion response for command 00005 'STATUS'
[imapx:A] token TOKEN 'OK'
[imapx:A] token TOKEN 'STATUS'
[imapx:A] ** Starting next command
[imapx:A] * no, no jobs
[imapx:A] folder INBOX is not selected, total 842 / 832, unread 0 / 3, modseq 370339 / 370502, uidnext 67409 / 67422: will rescan
DB Operation ended. Time Taken : 0,012124
###########
[imapx:A] adding command, fmt = 'UID FETCH %s:* (UID FLAGS)'
[imapx:A] got string '67412'
[imapx:A] completing command buffer is [29] 'UID FETCH 67412:* (UID FLAGS)'
[imapx:A] enqueue job 'UID FETCH 67412:* (UID FLAGS)'
[imapx:A] ** Starting next command
[imapx:A] Selecting folder 'INBOX' for command 'FETCH'(0x7f08d000e800)
[imapx:A] adding command, fmt = 'SELECT %f'
[imapx:A] got folder 'INBOX'
[imapx:?] looking up path INBOX -> INBOX
[imapx:A] SELECT QRESYNC 1 370339
[imapx:A] adding command, fmt = ' (QRESYNC (%lu %lu %s:%s'
[imapx:A] got glong '1'
[imapx:A] got glong '370339'
[imapx:A] got string '259'
[imapx:A] got string '67411'
[imapx:A] adding QRESYNC seq/uidset  (1,114,600,762,816,834 259,15061,61120,66696,67351,67395)
[imapx:A] adding command, fmt = ' (1,114,600,762,816,834 '
[imapx:A] adding command, fmt = '259,15061,61120,66696,67351,67395)'
[imapx:A] adding command, fmt = '))'
[imapx:A] completing command buffer is [101] 'SELECT INBOX (QRESYNC (1 370339 259:67411 (1,114,600,762,816,834 259,15061,61120,66696,67351,67395)))'
[imapx:A] Starting command (active=1,) A00007 SELECT INBOX (QRESYNC (1 370339 259:67411 (1,114,600,762,816,834 259,15061,61120,66696,67351,67395)))
[imapx:A] camel_imapx_write: 'A00007 SELECT INBOX (QRESYNC (1 370339 259:67411 (1,114,600,762,816,834 259,15061,61120,66696,67351,67395)))
'
[imapx:A] camel_imapx_read: buffer is '* 832 EXISTS
* 0 RECENT
* OK [UNSEEN 830] mailbox contains unseen messages
* OK [UIDVALIDITY 1] UIDs are valid for this mailbox
* OK [UIDNEXT 67422] next expected UID is 67422
* FLAGS (\Answered \Deleted \Draft \Flagged \Seen $Forwarded $MDNSent Forwarded $Junk $NotJunk Junk JunkRecorded NonJunk NotJunk receipt-handled)
* OK [PERMANENTFLAGS (\Answered \Deleted \Draft \Flagged \Seen $Forwarded $MDNSent Forwarded receipt-handled \*)] junk-related flags are not permanent
* OK [HIGHESTMODSEQ 370502] modseq tracked on this mailbox
A00007 BAD parse error: invalid message sequence number: 1,114,600,762,816,834
'
[imapx:A] token '*'
[imapx:A] got untagged response
[imapx:A] token TOKEN '832'
[imapx:A] token TOKEN 'EXISTS'
[imapx:A] Have token 'EXISTS' id 832
[imapx:A] exists: 832
[imapx:A] token '
'
[imapx:A] token '*'
[imapx:A] got untagged response
[imapx:A] token TOKEN '0'
[imapx:A] token TOKEN 'RECENT'
[imapx:A] Have token 'RECENT' id 0
[imapx:A] recent: 0
[imapx:A] token '
'
[imapx:A] token '*'
[imapx:A] got untagged response
[imapx:A] token TOKEN 'OK'
[imapx:A] Have token 'OK' id 0
[imapx:A] token '['
[imapx:A] token TOKEN 'UNSEEN'
[imapx:A] token TOKEN '830'
[imapx:A] token ']'
[imapx:A] token '*'
[imapx:A] got untagged response
[imapx:A] token TOKEN 'OK'
[imapx:A] Have token 'OK' id 0
[imapx:A] token '['
[imapx:A] token TOKEN 'UIDVALIDITY'
[imapx:A] token TOKEN '1'
[imapx:A] token ']'
[imapx:A] token '*'
[imapx:A] got untagged response
[imapx:A] token TOKEN 'OK'
[imapx:A] Have token 'OK' id 0
[imapx:A] token '['
[imapx:A] token TOKEN 'UIDNEXT'
[imapx:A] token TOKEN '67422'
[imapx:A] token ']'
[imapx:A] token '*'
[imapx:A] got untagged response
[imapx:A] token TOKEN 'FLAGS'
[imapx:A] Have token 'FLAGS' id 0
[imapx:A] token '('
[imapx:A] token TOKEN '\Answered'
[imapx:A] token TOKEN '\Deleted'
[imapx:A] token TOKEN '\Draft'
[imapx:A] token TOKEN '\Flagged'
[imapx:A] token TOKEN '\Seen'
[imapx:A] token TOKEN '$Forwarded'
[imapx:A] token TOKEN '$MDNSent'
[imapx:A] token TOKEN 'Forwarded'
[imapx:A] token TOKEN '$Junk'
[imapx:A] token TOKEN '$NotJunk'
[imapx:A] token TOKEN 'Junk'
[imapx:A] token TOKEN 'JunkRecorded'
[imapx:A] token TOKEN 'NonJunk'
[imapx:A] token TOKEN 'NotJunk'
[imapx:A] token TOKEN 'receipt-handled'
[imapx:A] token ')'
[imapx:A] flags: 0000089f
[imapx:A] token '
'
[imapx:A] token '*'
[imapx:A] got untagged response
[imapx:A] token TOKEN 'OK'
[imapx:A] Have token 'OK' id 0
[imapx:A] token '['
[imapx:A] token TOKEN 'PERMANENTFLAGS'
[imapx:A] token '('
[imapx:A] token TOKEN '\Answered'
[imapx:A] token TOKEN '\Deleted'
[imapx:A] token TOKEN '\Draft'
[imapx:A] token TOKEN '\Flagged'
[imapx:A] token TOKEN '\Seen'
[imapx:A] token TOKEN '$Forwarded'
[imapx:A] token TOKEN '$MDNSent'
[imapx:A] token TOKEN 'Forwarded'
[imapx:A] token TOKEN 'receipt-handled'
[imapx:A] token TOKEN '\*'
[imapx:A] token ')'
[imapx:A] token ']'
[imapx:A] token '*'
[imapx:A] got untagged response
[imapx:A] token TOKEN 'OK'
[imapx:A] Have token 'OK' id 0
[imapx:A] token '['
[imapx:A] token TOKEN 'HIGHESTMODSEQ'
[imapx:A] token TOKEN '370502'
[imapx:A] token ']'
[imapx:A] token TOKEN 'A00007'
[imapx:A] Got completion response for command 00007 'SELECT'
[imapx:A] token TOKEN 'BAD'
[imapx:A] token TOKEN 'parse'
[imapx:A] Select failed
[imapx:A] Cancelling command 'FETCH'(0x7f08d000e800) for folder 'INBOX'
[imapx:A] ** Starting next command
[imapx:A] * no, no jobs
[imapx:A] Removed folder INBOX from connection folder list - op done
Comment 1 Laurent Aguerreche 2011-05-04 23:48:58 UTC
The version of Evolution I use comes from Fedora 15 64 bits, packages are:
evolution-3.0.1-1.fc15.x86_64
evolution-data-server-3.0.1-1.fc15.x86_64
Comment 2 Oded Arbel 2011-06-12 09:53:11 UTC
I have a similar problem, with both Evolution 2.32 and Evolution 3.0 - I'm using a Zimbra server as well, which may or may not be related.

The main problem is that I sometimes access my Email using Evolution and sometimes using other clients or using the Zimbra web interface - then if I delete a message and later use Evolution, I get this error - for example this is from 2.32 but its very similar to the error from 3.0:
----
Error while Refreshing folder 'INBOX'.
SELECT INBOX failed: parse error: invalid message sequence number: 1,149,311,365,383
----

I usually get this right of the start because the last email that Evolution was on before using another client, is often an email that has been removed - because I read emails in LIFO order and file them away to other folders immediately after reading. So more often then not the email that Evolution tries to display when it first starts, is an email that is no longer in that folder.

When that happens (every couple of days), there is no rescuing the situation and I have to shutdown Evolution and remove the mail cache directory.
Comment 3 Yonathan Dossow 2011-11-29 22:33:53 UTC
I have the same problem, evo 3.2.2, imapx, and zimbra 7.1.3.

It appears to happen only on the INBOX, and the workarround is to disable the use of Quick Resync in the account preferences
Comment 4 Milan Crha 2012-01-12 10:22:56 UTC
*** Bug 660588 has been marked as a duplicate of this bug. ***
Comment 5 Baptiste Mille-Mathias 2012-01-12 10:55:39 UTC
Hi (I'm the author of the bug 660588).

My remote server is also a zimbra server (the one from the ISP free.fr).
it may be related.
Comment 6 Stéphane Démurget 2012-10-27 10:53:15 UTC
I also use the ISP free.fr and I had the same error, unchecking "Quick Resync" indeed work around the issue.
Comment 7 Milan Crha 2013-03-13 16:47:19 UTC
*** Bug 677414 has been marked as a duplicate of this bug. ***
Comment 8 Milan Crha 2013-03-13 16:55:30 UTC
Still there, unfortunately. A co-worker deleted some mails on the server side and after that run evolution and once the imapx reached that folder it wasn't able to move any further, due to out-of-sync with the server.
Comment 9 Matthew Barnes 2013-05-30 21:08:29 UTC
This is arguably a Zimbra bug, but I worked around it in our IMAPX backend.

Fixed for E-D-S 3.9.3 and 3.8.3 in:

https://git.gnome.org/browse/evolution-data-server/commit/?id=89b3af25c429bb57db9f4e38d31a862c2dca98df

https://git.gnome.org/browse/evolution-data-server/commit/?h=gnome-3-8&id=fe53fde76b9521638b57e28250de8af16e58d206