But it doesn't use telnet!

When testing mail, I'll often have a customer do something like "telnet mailserver 25" or "telnet mailserver 110". The purpose, of course, is to do command line testing of smtp or pop (see How do I test a smtp connection?, How do I test an imap server? and How do I test a popd connection?)

Strangely enough, three times this week I've had the same response: "But we don't have telnet enabled on the server". More surprising to me was that at least two of these were from people I thought would know better: that is, they knew that adding a port number at the end of the telnet made it contact a different port. Apparently the confusion was elsewhere: they thought that a telnet program would be answering this request, noticing the different port number, and forwarding the traffic to something else (which is actually exactly what inetd and xinetd do, of course). Complicating things further, one explained that he knew inetd would be handling the request, but he still thought that telnet had to be running on the server because the origin of the connection was by telnet.

The answering daemon has no clue what program created the connection request it is talking to. Whether it was telnet, nc, Outlook Express or another smtp server is completely unimportant and completely unknown. Well, that's not completely true: it's vaguely possible that an answering daemon might hazard a guess based on heuristic analysis of how the other end makes requests, and a packet sniffer might make even better guesses based on packet header information, but that's all pretty esoteric and meaningless in this context.

It's always interesting to see how people have constructed an incorrect view of how something works. All of us have our own fuzzy areas where knowledge blends with invention and wishful thinking.

Macworld Mac Basics Superguide $12.95
Macworld Mac Basics Superguide, Leopard Edition $12.95
Macworld Mac Gems Superguide $12.95
Macworld Mac OS X Hints Superguide, Leopard Edition $12.95

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.