The point here is that it *is* currently a valid sequence number. After all the next FETCH confirms this.
No, it is not a valid sequence number, and it remains an invalid sequence number until you receive an EXISTS response *in that session* that announces the validity of that sequence number.
There is no guarantee within a *single* session that a sequence number is valid. Another session could have expunged SN N while my fetch was in transit in the network.
Also incorrect. An untagged EXPUNGE can only be transmitted when a command other than FETCH, STORE, and SEARCH is in progress. Until such a command is in progress, the sequence remains valid even if the message was expunged in another session.
For example on Exchange 2000 I get the peculiar series of responses.
That behavior is now deprecated. Refer to RFC 2180; the behaviors described in 4.1.1 and 4.1.4 are now preferred over 4.1.2 and 4.1.3.
This all leads to a different question: why do you have multiple sessions open to the same mailbox from the same client? This is potentially very costly in server resources, and does not work at all with some servers. It should be avoided.
-- Mark --
http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
