Arnt Gulbrandsen <[EMAIL PROTECTED]> wrote: > A tagged NO means something is wrong with that command.
What you're describing sounds more like BAD. RFC3501, 2.2.2: # There are three possible server completion responses: OK (indicating # success), NO (indicating failure), or BAD (indicating a protocol # error such as unrecognized command or command syntax error). Also, 6.3.1 (SELECT command): # Result: OK - select completed, now in selected state # NO - select failure, now in authenticated state: no # such mailbox, can't access mailbox # BAD - command unknown or arguments invalid Note that "can't access mailbox" is mentioned distinctly from "no such mailbox". And, more to the point: 6.4.5 (FETCH command): # Result: OK - fetch completed # NO - fetch error: can't fetch that data # BAD - command unknown or arguments invalid > An untagged BYE ALERT means that the server is closing the > connection and requests that the user be alerted. The user would also be notified for NO [ALERT], right? So the only difference is closing the connection? How might that help? paul
