non-deliverable messages

[POS...@usc-isif.arpa]

The sending of a message to a mailing list like msggroup can be seen as
a two step process.

The first step is the sending of a single message from the author to a
mailing-list service.

The second step is the sending of many messages by the mailing-list service
to the many subscribers to the mailing-list.

Any error in the first step should be reported to the author.

Any error in the second step should be reported to the manager of the
mailing-list service.

--jon.
-------

[David Siegel]

It would seem to me that this problem could be solved as follows:

Have one internet host be a central mailing-list wide distribution
center. All internet wide mailing-lists will have an address at that
cite. (This also solves another common problem of not know where
Info-So-and-so is located) The mail forwarding software at that cite
can then be hacked to send all failed messages to
info-so-and-so-request. If the load this would put on a particular
host is too large, the central cite could forward the messages to
other machines for redistribution.

In addition, this central cite could have some kind of on-line package
(like the NIC query system) to allow users to add and delete there
names from any of this lists. This could all be done automatically,
taking some of the load off the mailing list maintainer.

[DonWint...@xerox.arpa]

AMEN

hou3c!ka]