Question, and I don't know if any clients do it this way either
but wouldn't a BAD code make a client who memorised a password forget it, as opposed to a NO error?
Coud this be why?
I don't see why it would. BAD is a protocol error, not a problem with the data in the command.
It's supposed to be used when the command is malformed, or when the client sends an empty command, or when the command is unknown (e.g. a command from an extension spec the server doesn't understand/support), or that kind of thing.
But it should be a NO when the client merely sends "bad" data, such as an incorrect password to an otherwise valid and well-formed LOGIN command, or when the server can't perform a fetch because e.g. a message was deleted by another client on a concurrent session... stuff like that.
Anyway, I don't want to start another 513-v-553 issue. :( It was just a simple question. -- And I think if I'd thought better of it, I would have only asked Sam (directly) rather than bothering the list with it. ;-)
-jab
------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
