Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

The whole site in one document for easy reference!
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  TCP/IP Key Applications and Application Protocols
           9  TCP/IP File and Message Transfer Applications and Protocols (FTP, TFTP, Electronic Mail, USENET, HTTP/WWW, Gopher)
                9  TCP/IP Electronic Mail System: Concepts and Protocols (RFC 822, MIME, SMTP, POP3, IMAP)
                     9  TCP/IP Electronic Mail Access and Retrieval Protocols and Methods
                          9  Other TCP/IP Electronic Mail Access and Retrieval Methods

Previous Topic/Section
Other TCP/IP Electronic Mail Access and Retrieval Methods
Previous Page
Pages in Current Topic/Section
1
2
Next Page
TCP/IP World Wide Web Electronic Mail Access
Next Topic/Section

TCP/IP Direct Server Electronic Mail Access
(Page 2 of 2)

Pros and Cons of Direct Server E-Mail Access

These techniques are much more commonly associated with timesharing systems, which commonly use the UNIX family of operating systems than others. They are also often combined; for example, remote access is often provided for UNIX users, but most companies don't want users logging in directly to the SMTP server. Instead, an Internet service provider might run an SMTP server on one machine called “mail.companyname.com” and also operate a different server that is designed for client access called “users.companyname.com”. A user could access e-mail by dialing into the “users” machine, which would employ NFS to access user mailboxes on the “mail” machine.

Direct server access is a method that has been around for decades. At one time, this was how the majority of people accessed e-mail, for two main reasons. First, if you go back far enough, protocols like POP or IMAP had not yet been developed; the TCP/IP e-mail system as a whole predates them by many years and direct access was the only option back then. Second, the general way that e-mail and networks were used years ago was just different than it is today. Most individuals did not have PCs at home, and there was no Internet as we know it. Remotely accessing a UNIX server using a modem or Telnet for e-mail and other services was just “the way it was done”.

I myself got started using direct server access for e-mail over 10 years ago, and still use this today. I Telnet in to a client machine and use a UNIX e-mail program called elm to access and manipulate my mailbox. To me, this provides numerous advantages. First and most importantly, I can access my e-mail using Telnet from any machine on the Internet, anywhere around the world. Second, since I am logged in directly, I get immediate notification when new mail arrives, without having to routinely check for new mail. Third, my mailbox is always accessible and all my mail is always on a secure server in a professionally-managed data center. Fourth, I have complete control over my mailbox and can edit it, split it into folders, write custom “spam” filters, or do anything else I need to do.

This probably sounds good, but most people today do not use direct server access because of the disadvantages of this method. One big issue is that you must be logged in to the Internet to access your e-mail. Another one, perhaps even larger, is the need to be familiar with UNIX and a UNIX e-mail program. UNIX is simply not as “user-friendly” as a graphical operating systems such as Windows or the Apple Macintosh. For example, my UNIX e-mail program doesn't support color and cannot show me attached graphic images. I must extract images and other files from MIME messages and transfer them to my own PC for viewing.

Most people today don't know UNIX and don't want to know it. They are much happier using a fancy graphical e-mail program based on POP3 or IMAP4. However, there are still a number of us old UNIX dinosaurs around who feel the benefits of direct access outweigh the drawbacks. Oh, one other benefit that I forgot to mention is that it's very hard to get a virus in e-mail when you use UNIX.

Key Concept: Instead of using a dedicated protocol like POP3 or IMAP4 to retrieve mail, on some systems it is possible for a user to have direct server access to e-mail. This is most commonly done on UNIX systems, where protocols like Telnet or NFS can give a user shared access to mailboxes on a server. This is the oldest method of e-mail access; it provides the user with the most control over his or her mailbox, and is well-suited to those who must access mail from many locations. The main drawback is that it means the user must be on the Internet to read e-mail, and it also usually requires familiarity with the UNIX operating system, which few people use today.



Previous Topic/Section
Other TCP/IP Electronic Mail Access and Retrieval Methods
Previous Page
Pages in Current Topic/Section
1
2
Next Page
TCP/IP World Wide Web Electronic Mail Access
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.