Mark Crispin <[EMAIL PROTECTED]> writes: > On Wed, 25 Sep 2002 14:58:15 +0200, Simon Josefsson wrote: >> Would it improve the standard to make this more obvious? The text >> that the argument is based on is located inside parentheses in a >> comment inside the ABNF without saying how to handle the error or why >> it is an error. > > Well, sections 5.5 and 7.4.1 don't do that; they simply explain that it is > alright for it to be an error. > > Here's my latest stab at the rule for seq-number. I hope this is clearer?
It looks alright. > seq-number = nz-number / "*" > ; message sequence number (COPY, FETCH, STORE > ; commands) or unique identifier (UID COPY, > ; UID FETCH, UID STORE commands). > ; * represents the largest number in use. In > ; the case of message sequence numbers, it is > ; the number of messages in a non-empty mailbox. > ; In the case of unique identifiers, it is the > ; unique identifier of the last message in the > ; mailbox or, if the mailbox is empty, the > ; UIDNEXT value. Except possibly this new UIDNEXT thing. Cyrus IMAP for one doesn't do this. In this case I think it is better to have * mean a non-existing article instead of UIDNEXT. . select INBOX.Drafts * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1025092571] * OK [UIDNEXT 1] . OK [READ-WRITE] Completed . FETCH * UID . NO No matching messages . UID FETCH * UID . OK Completed
