Path: utzoo!mnetor!uunet!husc6!hao!ames!ucbcad!ucbvax!UCONNVM.BITNET!SEWALL
From: SEWALL@UCONNVM.BITNET
Newsgroups: comp.sys.apple
Subject: APPLE2-L
Message-ID: <8712231538.aa19975@SMOKE.BRL.ARPA>
Date: 23 Dec 87 19:07:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 28

I saw your note about mail for APPLE2-L going to you first.
That's certainly likely to prevent the kind of mass mail robot
wars like we had yesterday.  Does that mean that mail addressed
to APPLE2-L@BROWNVM.BITNET will simply be routed to you (not
bounced altogether I hope), or must programs for the list be
sent to CC004019@BROWNVM.BITNET (or either address)?

On the notion of an INET peer site.  Another possibility would
be if one or more sites would agree to act as "redistribution
points" (you already have one UUCP site doing that).  Redistributing
requires less overhead than a peer site would require because a
redistributor would NOT RETAIN a file of previous posts.

It seems to me that UUCP backbone sites would have less traffic
if they received only one copy of each APPLE2-L message from
BROWNVM and then sent mail to whatever subscribers were registered
at that site.  The same sort of thing probably is true on arpa,
mil, csnet, gov, decnet, and so forth.

Perchance subscribers to APPLE2-L at (or with contacts at) backbone
sites who see this message on comp.sys.apple will communicate with
the appropriate systems people and see if they can't set something
up?

---------------------
ARPA:   sewall%uconnvm.bitnet@cunyvm.cuny.edu       Murphy A. Sewall
BITNET: SEWALL@UCONNVM                          School of Business Admin.
UUCP:   ...ihnp4!psuvax1!UCONNVM.BITNET!SEWALL  University of Connecticut