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 621837 - imapx upsets server with custom flags store
imapx upsets server with custom flags store
Status: RESOLVED DUPLICATE of bug 735191
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[imapx]
Depends on:
Blocks:
 
 
Reported: 2010-06-17 00:11 UTC by David Woodhouse
Modified: 2014-09-02 16:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Woodhouse 2010-06-17 00:11:04 UTC 
I've seen this go past a couple of times, followed by a disconnection and reconnect:

Staring command (active=1,) B14548 UID STORE 18209 +FLAGS.SILENT (receipt-handled)
camel_imapx_write: 'B14548 UID STORE 18209 +FLAGS.SILENT (receipt-handled)
'
camel_imapx_read: buffer is 'B14548 BAD Command Argument Error. 11
'
Got completion response for command 14548 'STORE'
Comment 1 David Woodhouse 2010-06-17 00:18:12 UTC 
Definitely a client bug. This server never claimed to support custom flags (note no \* in the PERMANENTFLAGS response)...

001 select INBOX
* 1326 EXISTS
* 0 RECENT
* FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
* OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags
* OK [UNSEEN 989] Is the first unseen message
* OK [UIDVALIDITY 774] UIDVALIDITY value
* OK [UIDNEXT 18229] The next unique identifier value
001 OK [READ-WRITE] SELECT completed.
002 CAPABILITY 
* CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN IDLE NAMESPACE LITERAL+
002 OK CAPABILITY completed.
003 uid store 18209 +flags (\Seen)
* 1307 FETCH (FLAGS (\Seen \Answered))
003 OK STORE completed.
004 uid store 18209 +flags (receipt-handled)
004 BAD Command Argument Error. 11
Comment 2 Alex Murray 2012-10-05 03:56:24 UTC 
Am seeing this quite often with Evo 3.4.4 against MS Exchange 2003 as the IMAP server - particularly I often get the error:

Error syncing changes: Protocol Error: "Specified set of flags is not valid".

When expunging a folder or similar.
Comment 3 Milan Crha 2014-09-02 16:06:15 UTC 
This had been fixed recently at bug #735191, thus I mark this as a duplicate of it.

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