38 lines
1.1 KiB
Plaintext
38 lines
1.1 KiB
Plaintext
MBOX-Line: From pruiter at ca.ibm.com Wed Jan 9 21:04:46 2008
|
|
To: imap-protocol@u.washington.edu
|
|
From: Perry Ruiter <pruiter@ca.ibm.com>
|
|
Date: Fri Jun 8 12:34:41 2018
|
|
Subject: [Imap-protocol] Question on FETCH example in RFC3501
|
|
In-Reply-To: <1199939792.8850.111.camel@hurina>
|
|
Message-ID: <OF18A22368.8F402169-ON882573CC.001B46DD-882573CC.001BE898@ca.ibm.com>
|
|
|
|
>Also if client sends two commands, the server may mix them:
|
|
>
|
|
>1 fetch 1:2 flags
|
|
>2 fetch 1:2 uid
|
|
>* 1 fetch (flags (\seen))
|
|
>* 1 fetch (uid 100)
|
|
>* 2 fetch (flags ())
|
|
>* 2 fetch (uid 101)
|
|
>2 ok
|
|
>1 ok
|
|
|
|
For someone new to the protocol this could be a confusing example since
|
|
the tags are the same as the message numbers and they may somehow think
|
|
the message numbers in the untagged responses tie back to the command with
|
|
that tag. Probably better as:
|
|
a fetch 1:2 flags
|
|
b fetch 1:2 uid
|
|
* 1 fetch (flags (\seen))
|
|
* 1 fetch (uid 100)
|
|
* 2 fetch (flags ())
|
|
* 2 fetch (uid 101)
|
|
b ok
|
|
a ok
|
|
|
|
Perry Ruiter
|
|
250-658-6517
|
|
-------------- next part --------------
|
|
An HTML attachment was scrubbed...
|
|
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20080109/bd02fc42/attachment.html>
|