Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site hou3c.UUCP Path: utzoo!watmath!clyde!burl!hou3c!DMS%MIT-OZ@MIT-MC.ARPA From: DMS%MIT-OZ@MIT-MC.ARPA (David Siegel) Newsgroups: net.mail.msggroup Subject: non-deliverable messages Message-ID: Date: Mon, 30-Apr-84 16:43:00 EDT Article-I.D.: hou3c.525 Posted: Mon Apr 30 16:43:00 1984 Date-Received: Tue, 1-May-84 07:59:20 EDT Sender: ka@hou3c.UUCP (Kenneth Almquist) Lines: 15 To: POSTEL@USC-ISIF.ARPA Cc: msggroup@BRL-AOS.ARPA In-Reply-To: Msg of 30 Apr 1984 15:34-EDT from POSTEL at Usc-Isif.ARPA 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.