Mark Crispin <[EMAIL PROTECTED]> writes: > On Tue, 11 Jun 2002, Simon Josefsson wrote: >> > In other words, it should do: >> > 00015 UID SEARCH 1:60 BODY target >> > 00016 UID SEARCH 61:120 BODY target >> > etc. until it reaches the number of messages in the mailbox: >> > 00020 UID SEARCH 300:343 BODY target >> >> This isn't a complete example -- the client will want to have the UID >> of the matched messages as well > > It will. Note that the command is UID SEARCH, not UID. > > In other words, it takes sequences as an argument, but returns UIDs.
Oops! Sorry, yes, I now agree that Eudora should use the above instead, and it was a complete example. (Altough the client would of course need to figure the number of articles in the mailbox, which it probably receives after SELECT.) >> So there isn't >> a generic recommendation possible to give here, which I believe is >> symptomatic of something missing in the protocol. > > Do you now agree that you were mistaken? I realize that it can be > complicated, but the functionality *is* there. Still, my own use of UID SEARCH UID cannot be replaced by the above, since I need to know what happened to all relevant articles in the group before I create the window containing those articles. UID SEARCH UID is painful in large groups. A mechanism to better "synch" IMAP servers with IMAP clients with local caches or disconnected support would be useful, and is what I think is lacking in IMAP.
