Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!ucbcad!ucbvax!MACOM4.ARPA!little
From: little@MACOM4.ARPA (Mike Little)
Newsgroups: comp.protocols.tcp-ip
Subject: Null TCP/SLIP msg and list-servers
Message-ID: <8710231351.AA11280@MACOM4.ARPA>
Date: Fri, 23-Oct-87 09:51:28 EST
Article-I.D.: MACOM4.8710231351.AA11280
Posted: Fri Oct 23 09:51:28 1987
Date-Received: Sun, 25-Oct-87 15:32:35 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14

I don't know what's wrong, but several people have been telling me they've
received multiple copies of my null message.  The message was sent because
the launch button is right next to the kill button (a case in point for
user interface designers and missile operators).  Only one copy was sent
from here as far as I can tell (I only got one copy back).  An interesting
note about the TCP/IP list is that it takes many hours to service a single
message, the null message having about six hours turnaround to myself.  I
have noticed delivery in excess of ten hours from origination.  Made me 
wonder if the list is serviced singly, top to bottom.  Would a divide-and-
conquer technique work here (multiple mail-list machines working on divided
parts of the whole list) or is this really a CPU bound situation?
					-Mike
P.S. I do appreciate the few people who have sent me replies giving
	me a heads up on the empty message - thanks.