From: Lyndon Nerenberg <lyndon@orthanc.ab.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] manual suggestions and upas/fs bug
Date: Tue, 17 Sep 2002 14:18:44 -0600 [thread overview]
Message-ID: <200209172018.g8HKIjsl057973@orthanc.ab.ca> (raw)
In-Reply-To: Your message of "Tue, 17 Sep 2002 00:34:50 EDT." <1a1c6bd5d1263339dd2bb6315eb56c5d@cs.cmu.edu>
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
next prev parent reply other threads:[~2002-09-17 20:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 4:34 David Swasey
2002-09-17 20:18 ` Lyndon Nerenberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-17 23:05 Russ Cox
2002-09-18 2:06 ` Lyndon Nerenberg
2002-09-18 17:03 ` rob pike, esq.
2002-09-17 13:28 Russ Cox
2002-09-17 4:58 Russ Cox
2002-09-16 19:29 David Swasey
2002-09-17 1:58 ` Lyndon Nerenberg
2002-09-17 8:47 ` Douglas A. Gwyn
2002-09-17 9:17 ` Lucio De Re
2002-09-18 8:37 ` Douglas A. Gwyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200209172018.g8HKIjsl057973@orthanc.ab.ca \
--to=lyndon@orthanc.ab.ca \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).