On Wed, 2006-08-23 at 22:32 +0200, Paul J Stevens wrote: > Oleg Lapshin wrote:
> > Info COMMAND: [srch1 SEARCH UID 260] > > So roundcube is using this detour to find a message seqnr for a specific > uidnr. Valid enough. > > > Debug RESPONSE: [* SEARCH 260] > > That's incorrect for a 1-message mailbox. The message sequence-nr (1) > should have been returned here, not the uid number. I'm not sure I understand, then. We should see different results from UID SEARCH... vs. plain SEARCH? * OK dbmail imap (protocol version 4r1) server 2.1 ready to run a01 login "test" test a01 OK LOGIN completed a02 select inbox * 7 EXISTS * 0 RECENT * FLAGS (\Seen \Answered \Deleted \Flagged \Draft \Recent) * OK [PERMANENTFLAGS (\Seen \Answered \Deleted \Flagged \Draft \Recent)] * OK [UIDNEXT 61] Predicted next UID * OK [UIDVALIDITY 64] UID value a02 OK [READ-WRITE] SELECT completed a02 search uid 200 * SEARCH 8 10 43 47 53 55 60 a02 OK SEARCH completed a03 uid search uid 200 * SEARCH 8 10 43 47 53 55 60 a03 OK SEARCH completed For one of those search results, I should have gotten UID's / MSN's, but not both the same result type, right? Aaron
