![\"\"](\"https://unsung.aresluna.org/_media/traditional-but-puzzling/1.1088w.avif\")
In the 1990s, users of some Unix-based operating systems would sometimes see a peculiar error. It happened occasionally when sending an email to a person you might have already sent email to before, and in addition to the error being confusing, the message itself was particularly bewildering.
\nLet’s say you wanted to send an email to “MWichary.” Instead of a confirmation, you would see this:
\n550 mwichary... User unknown: Not a typewriter
As many strange errors tend to be, this one was at an intersection of four different things.
\nThe cause of the error was something many of you will recognize – code being anal about lower- and uppercase. Behind the scenes, a piece of software called sendmail always assumed lowercase user names, which was true early on. “MWichary” was quietly changed to “mwichary” – a user that didn’t exist – and the program reported the literal outcome, instead of its chain of reasoning.
\nThe second part was a sort of a meta-error in the error handling routine. Sendmail correctly reported back “User unknown,” but then reflexively added whatever the system error value reported, for extra debugging color. These are usually helpful, reporting things like “Host is down” or “No space left of device” – I bet you’ve seen some of the very distinctive strings if you ever did anything adventurous in the terminal.
\nIn this particular context, however, the system error was pretty useless. “Not a typewriter” meant basically “this is a program being run in the background; it’s not meant to accept any user input or write anything for the user to read.” It’s not an error as much as a condition, and is true for a lot of programs quietly doing the operating system’s bidding.
\nBut… why was the message phrased this way?
\nThat’s just history. Computers were originally connected to typewriters as input/output. Some of these typewriters were local, attached to the front panel, or console. Others were remote typewriters, or teletypewriters, often shortened to teletype or even tty. If you recognize these terms, that’s because they are still with us today!
\n![\"\"](\"https://unsung.aresluna.org/_media/traditional-but-puzzling/2.1088w.avif\")
![\"\"](\"https://unsung.aresluna.org/_media/traditional-but-puzzling/3.1088w.avif\")
You can see how “This doesn’t have input/output I can do something with” can become a terse “Not a typewriter” in an era when every character feels costly, and a typewriter is your only option for input and output. Then, the string was simply kept a few decades too long, even after typewriters were replaced by teletypes, terminals with screens, and eventually Terminal and Console apps.
\nThe fourth piece was fun with grammar: the simple choice of joining the two messages by a colon made it feel like the user was supposed to be a typewriter.
\nThe message was eventually renamed. If you encounter it today, it will say “Inappropriate ioctl for device,” which I guess is an improvement. But its code remains ENOTTY.
It’s entirely possible it will still be named that decades from now, even after we all forget what typewriters were.
\nThe title of the post comes from the explanation in the manual for the Solaris operating system.
\nOct 15, 2026
","headings":[{"level":1,"text":"“Traditional, but puzzling”","id":"traditional-but-puzzling"}]}}