Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!aramis!lear
From: lear@aramis.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Your subscription to list I-AMIGA
Message-ID: <294@aramis.RUTGERS.EDU>
Date: Thu, 26-Feb-87 18:35:28 EST
Article-I.D.: aramis.294
Posted: Thu Feb 26 18:35:28 1987
Date-Received: Sat, 28-Feb-87 07:36:39 EST
References: <1043@rutgers.RUTGERS.EDU> <1082@ulowell.cs.ulowell.edu>
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 30
Keywords: moderation, traffic, filters, info-amiga, daemons, backbone
Summary: It's not MY fault!

Regarding the recent bitnet verbiage, until those messages started to
appear on comp.sys.amiga, I had no idea that that cruft was being sent
to INFO-AMIGA.  I have investigated the matter to some extent and it
turns out to be a side effect of the LISTSERV software.  Here is what
is going on:

People on the ARPANet/Bitnet send to INFO-AMIGA@rutgers.edu to get
their articles posted to the USENET.  I, in turn, collect all the
USENET articles and digestify a small percentage of them.  Each digest
takes about an hour to do, so depending on the week, I send out
somewhere between 1 and 4 digests.

Anyway, then there is this matter of the bitnet recipients.  The
software used to distribute the digest to bitnet users requires that
it have a "owner" name to post to, from, and everywhere in between.
As an "owner", info-amiga receives all sorts of cruft.  Because of
it's nature, I thought that this address was being spared all that
cruft.  Well, I was wrong.  I will contact the bitnet people and try
to clear the problem up asap.

Sorry about those messages, but in the meantime, let me restate my
opinion - that being that there is a lot of cruft on this list that
could be cut out by using (a) local distribution options or (b) mail
or (c) nothing.  Please consider these options when posting.

					...eliot
-- 

[lear@rutgers.rutgers.edu]
[{harvard|pyrnj|seismo|ihnp4}!rutgers!lear]