From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200209172018.g8HKIjsl057973@orthanc.ab.ca>
From: Lyndon Nerenberg <lyndon@orthanc.ab.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] manual suggestions and upas/fs bug
In-reply-to: Your message of "Tue, 17 Sep 2002 00:34:50 EDT."
             <1a1c6bd5d1263339dd2bb6315eb56c5d@cs.cmu.edu>
Date: Tue, 17 Sep 2002 14:18:44 -0600
Topicbox-Message-UUID: ed456bca-eaca-11e9-9e20-41e7f4b1d025

We have both client and server bugs here.

   -> 9X2 SELECT Inbox
   <- * FLAGS (\Answered \Flagged \Draft \Deleted \Seen)
   <- * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)]
   <- * 0 EXISTS
   <- * 0 RECENT
   <- * OK [UIDVALIDITY 1031763467]
   <- 9X2 OK [READ-WRITE] Completed

Notice how the server states there are no messages in the mailbox.

   -> 9X3 STATUS Inbox (MESSAGES UIDVALIDITY)

This command should not be issued, for several reasons.

    1) The SELECT response already told the client the number of messages.

    2) The SELECT response already told the client the uidvalidity
       of the mailbox.

    3) Queries to the currently selected folder should be done using
       FETCH and LIST. STATUS is for querying folders other than the
       selected one, and is not guaranteed to be fast.  (In many
       servers, selecting a folder causes the meta data about the folder
       to assembled and cached. SELECT will not use that data cache
       since its assuming you want to know something about a folder
       other than the selected one.)

   <- * STATUS Inbox (MESSAGES 0 UIDVALIDITY 1031763467)
   <- 9X3 OK Completed

And *again* the server said there were no messages, thus

   -> 9X4 UID FETCH 1:* UID

is completely bogus. That message range is invalid, and the client
should know that. However, the server should be responding with
something like

   9X4 BAD Invalid sequence in FETCH

instead of dumping core (and that's the server bug I mentioned).

--lyndon