Pawel Salek <[EMAIL PROTECTED]> wrote:
> Server that answers NO follows the specification but is useless.

If the message is, in fact, no longer available by the time FETCH
arrives, then I would instead call it "honest".

> "Server says that message number xx exists but when I ask for it, it
> says it cannot provide it"? Seems like an internal server error to
> me.

Look at the situation more closely: earlier, the server said this
message was present.  Later, when a FETCH command is given, the server
says it can't provide the message.  So the server is accurately
reporting a change of state.  The server never says that the message
both exists and doesn't exist *at the same time*.  It reports the
truth at each moment, but of course the truth can change over time.


paul

Reply via email to