On Thu, 26 Sep 2002 12:21:37 -0700, Larry Osterman wrote:
> I feel obliged to toss out that when you select a mailbox when you are
> unauthenticated, the Exchange IMAP server does:
> [snip]
> I don't have access to a UW IMAP server to see what it does....
If you don't need to be logged in, try <UW userid>.deskmail.washington.edu
UW imapd always reads a complete line before transmitting any response. In
the case of SELECT when unauthenticated, it responds with:
tag BAD Command unrecognized/login please: SELECT
to a SELECT when non-authenticated, or to anything else. It doesn't even
check to see if there is such a command as SELECT, hence:
* OK ....
. blurdybloop
. BAD Command unrecognized/login please: BLURDYBLOOP
On Thu, 26 Sep 2002 13:03:24 -0700, Vladimir A. Butenko wrote:
> So, they are non-compliant. And, heh, -
> * OK CommuniGate Pro IMAP Server 4.0b9a at xxx.stalker.com ready
> . select sss
> . BAD not logged in
> is not compliant, either :-) So, as you can see as developers we are more in
> agreement with you than you might think.
I agree that BAD is the correct error; and disagree about that being not
compliant. It is a protocol-level error, because the protocol is in the wrong
state.
If there's something in the document that can be construed to imply otherwise,
that should be amended.
