Mark makes a good point, except that this same system, by default, uses
those infamous "leading prompts": "Expected a HELLO command"
"Expected...user.acct..." "Account exists. User name doesn't", etc. In
contrast, "Can't initiate new sessions" seems considerably less
hazardous, particularly if it, like the others, could be changed.

- Joe Alexander

>>> "[log in to unmask]" 09/04/98 01:49pm >>>
I guess the theory is that only authoized users need to be informed
about system unavailability, and you aren't authorized until you
provide a valid login and password.

One tenet of computer security is that you give unauthorized users as
little information as possible about the system they are trying to
access.

I guess I don't see having to successfully login before being told
that the machine can't service your login, or that some other thing is
unavailable, as being a serious problem. You may disagree, of course.