Arnt Gulbrandsen <[EMAIL PROTECTED]> wrote: > A tagged NO means something went wrong with the execution of that > command.
Ok, that's what I thought. > a) tagged NO relates to the command; untagged BYE ALERT relates only > to general server state > b) NO means the server can go on; BYE ALERT means it can't > > You mentioned ENOMEM. I'd say that's clearly a matter of general > server state, and that the server can't go on. Well, depending on the OS, it might clear itself up after a short time, like ENFILE. So the server *might* be able to answer the next request. OTOH, in the case of such resource-shortage errors, dropping the connection and letting the client reconnect would make it more likely that the problem would be cleared up by then. So I guess I'll do that for those cases. But if a particular message is inaccessible (due to wrong permissions, or being deleted (possibly by a non-IMAP agent), etc.), then NO is appropriate, since the server can still answer other requests, right? paul
