Re: "elmo-imap416 BAD UID SEARCH invalid argument" upon updating summary

[David Maus <dmaus@ictsoc.de>]

Hi,

At Mon, 13 Oct 2014 20:35:02 +0200,
Juliusz Chroboczek wrote:
> 
> > [11:43:37] -> * FLAGS (\Answered \Flagged \Deleted \Draft \Seen)
> > [11:43:37] -> * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags
> 
> [...]
> 
> > [11:43:37] <-- elmo-imap416 uid search keyword $Forwarded
> > [11:43:37] -> elmo-imap416 BAD UID SEARCH invalid argument
> 
> Could you please try forwarding one message (to yourself), and see whether
> this fixes the problem?  It should have the side effect of putting the
> $Forwarded flag into the FLAGS list.
> 
> (I don't have time right now to check the spec to see whether the server
> is buggy or merely intolerant.)
> 

I can confirm that Kerio Connect 8.3.2 shows the same behavior: If I
perform a search for a flag that does not exist, the server issues an
error.

,----
| 0x1 SELECT Inbox
| * FLAGS (\Deleted \Seen \Answered \Draft \Flagged $MDNSent $Forwarded $AutoJunk $AutoNotJunk $Junk $NotJunk)
| * 29264 EXISTS
| * 0 RECENT
| * OK [UNSEEN 29109] Message 29109 is first unseen
| * OK [UIDVALIDITY 1285775412] UID validity
| * OK [UIDNEXT 44065] Predicted next UID
| * OK [PERMANENTFLAGS (\Deleted \Seen \Answered \Draft \Flagged $MDNSent $Forwarded $AutoJunk $AutoNotJunk $Junk $NotJunk)] Permanent flags
| 0x1 OK [READ-WRITE] SELECT completed
| 0x2 uid search keyword $Junk
| * SEARCH
| 0x2 OK UID SEARCH completed in 0.03 s
| 0x3 uid search keyword Junk
| 0x3 BAD UID SEARCH Malformed search request
`----

Limiting the search operation to flags that are listed in the FLAGS or
PERMANENTFLAGS response seems like a solution for this problem.

I couldn't find something about this case in the specs.

Best,
  -- David

> -- Juliusz
> 
> 

-- 
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de