FTPmail

During the early years of the Internet, Internet access was limited to a few locations. High speed links were not available for most users, and online connectivity was rare and expensive. Download of large files (then considered to be over a few megabytes) was nearly impossible due to bandwidth limitations, as well as frequent errors and lost connections. The original FTP specification did not allow for a session to be resumed, and the transmission had to restart from the beginning.

FTPmail gateways allowed people to retrieve such files. The file was broken into smaller pieces and encoded using a popular format such as uuencode. The receiver of the email messages would later reassemble the original file and decode it. As the file was broken into smaller pieces, the chances of losing the transmission was much smaller. In case of loss of connectivity, the transmission could be restarted from that part. The process was slower but much more reliable. It also allowed people who accessed the Internet only through email using dial-up lines to download files that were located remotely. Unlike FTP, files could be transferred through FTPmail even if the user did not have an online Internet connection (for example, using BBSes or other specialized e-mail software).

Servers located at universities, such as ftpmail@sunsite.unc.edu and bitftp@pucc.princeton.edu, were popular. Some of these servers hosted software archives containing early versions of Linux and other GNU software. Access to these repositories via FTPmail was instrumental in allowing people from foreign countries to access these tools at a time where online connectivity was impossible from their location.

FTPmail services were common in the early 1990s, but dwindled in importance as more users gained direct internet access through SLIP, PPP and other Dial-up access internet protocols. FTP also has lost popularity in favor of other methods for file transfer, notably HTTP which is available to virtually all Internet users.

An email is sent to a FTPmail server with the command to be performed, inserted as the body of the message. The server then processes the request by logging on to the remote site, retrieving the file, encoding it, and returning the result via email.

• File Transfer Protocol