Search DominoPower's 11,320 Lotus-related article archive 
Home
EasyPrint
News details Click here for the RSS feed's XML code. This is not a browser URL.
Articles-only Click here for the RSS feed's XML code. This is not a browser URL.
Twitter Feed Click here for the Twitter feed.
LIST MANAGEMENT
A history of list servers
By John Buckman

This month we're featuring an article on the integration of Lyris ListManager with Domino. To get a little perspective on list servers, we've asked John Buckman, CEO and founder of Lyris Technologies, to provide this fascinating look at the history of list servers.

The killer application on the Internet has always been email. It's the single most-used function online, far outstripping file transfers, Web browsing, and game playing. This is largely because of email's utility. Adding to its one-on-one correspondence function, email quickly expanded its functions to include distribution of messages for discussion groups and dispersal of periodical publications.

These add-ons have become indispensable parts of the online experience. Consequently, list server software that makes email discussion lists and email broadcasting possible has also become an integral component of electronic commerce.

The first list server
In 1981, BITNET (Because It's Time Network) was among the earliest networks that existed before the Internet. It was created in the United States to connect computer systems run by The City University of New York and Yale University.

Development of the U.S. BITNET network was funded by a grant from IBM. BITNET was run by CREN (Corporation for Research and Educational Networking) in the U.S., while EARN (European Academic and Research Network) ran BITNET in Europe. In 1982, CREN and EARN used a leased telephone circuit to connect their two networks.

EDUCOM in Europe created the first list server software used on the BITNET network. The initial goal of the list server was to enable scientists in Europe to quickly share research with colleagues in other parts of the world, thereby increasing the rate of scientific progress.

The first list server ran on an IBM VM mainframe, since BITNET used IBM's NJE (Network Job Entry) protocol for inter-machine communication. The VMS operating system also supported this protocol. Consequently, many Digital VAX (Virtual Address Extension) minicomputers (which also ran VMS) were connected via BITNET.

The administration of the first list server was quite primitive and lacked automation. For instance, each discussion group had a single email address set up as a simple email "exploder" that automatically sent each received message to all members of the list.

To subscribe or unsubscribe from the mailing list, members sent an email message to the address LISTSERV@BITNET-HOSTNAME. The listserv@ address wasn't a front end for a software program. Instead, it was an email address for a human who would read the message and manually add or remove people from the distribution list file.


1  ·  2  ·  3  ·  4  ·  Next »
Other articles you might like
Home > Strategies > Email Management (60 articles)
   Using the Notes Client with Gmail
   Using the Notes client with Hotmail (or not)
   Is English-only a viable mail management strategy?
Home > Social Computing > Messaging (10 articles)
   A Sametime plugin for Trillian
   DAMO deep-six: is there a future for Outlook/Domino integration?
   Why I STILL recommend Domino over Exchange
Get Weekly Email Updates
Subscribe to our regular weekly email newsletter. It's packed with tips, reviews, deep analysis, and the latest news.
 
Recent DominoPower Articles
Lotusphere 2010: mobility and collaboration
2010: A Lotusphere of change
Five trends for 2010
DominoPower TV Episode 1: Inside a strategy session with Teamstudio
More about Domino log files
Say goodbye to the Uh-Ohs. Long live the Tens.
Why your log.nsf might not be purging properly
Latest Lotus Headlines
SnTT: XPages Blank Calendar Control (Part 2), adding data
Have your Lotus Notes calendar display multiple time zones
Sample Database for Microsoft Office and Lotus Symphony Integration
Symphony 3.0 beta signals another attack on Office
Enabling DAOS on a database - new recommendation
Need your opinion on some new policy settings for Mail
Sometimes IBM Lotus Domino HTTP RPC Agents aren't the answer...
>> Read all the news
More from the ZATZ journals
Computing Unplugged: The iPad: Apple's latest heartbreaker
David Gewirtz Online: CNN commentary and analysis
OutlookPower: Running auto-respond rules when Outlook is closed
-- Advertisement --

Learn Notes and Domino 8 at your place and pace!
Learn Notes and Domino in your office and/or home! TLCC's highly acclaimed distance learning courses for users, developers, and admins will enhance your career and your resume.

The many included activities and demos will make you a pro! Expert instructor help is a click away.

Click here to try a FREE demo course!!

-- Advertisement --

Integrate your Notes Applications with Microsoft Office and Symphony
Integra for Notes Integrates Microsoft Office and/or IBM Lotus Symphony
Requires NO change to the design of the appliation or Installations of DLL's and EXE's
  • Integra is a ready to use solution, enhance static reports with Excel data analysis, pivot tables, macros
  • User friendly aproach, using a point and click access to features
  • Reports from any Lotus Notes databases
  • Runs reports through a Notes client, web browser and scheduled basis
  • Allows use of LotusScript for advanced data manipulation
  • Enables self service reporting capabilities to end-users


Learn more at www.integra4notes.com.
ZATZ Home  ·  News  ·  Back Issues  ·  Credits/Trademarks ·  Link To Us
Copyright © 1998-2010, ZATZ Publishing. All rights reserved worldwide.
Editor's Login