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!REM@Mit-Mc.ARPA
From: REM@Mit-Mc.ARPA (Robert Elton Maas)
Newsgroups: net.mail.msggroup
Subject: Non-deliverable messages
Message-ID: <512@hou3c.UUCP>
Date: Sun, 29-Apr-84 19:57:00 EDT
Article-I.D.: hou3c.512
Posted: Sun Apr 29 19:57:00 1984
Date-Received: Mon, 30-Apr-84 05:36:53 EDT
Sender: ka@hou3c.UUCP (Kenneth Almquist)
Lines: 18
To: Jacob_Palme_QZ%QZCOM.MAILNET@Mit-Multics.ARPA
Cc: msggroup@Brl-Aos.ARPA


    (b) ARPANET mailing lists, when redistributing messages, indicate
    the postmaster at the site handling the mailing list, and not
    the original author, as the SMTP sender when redistributing
    the message.
It's not usually the job of the system postmaster to maintain random
mailing lists that are stationned at that host, rather each mailing
list has its own maintainer. A convention that has been established
recently is to have a ...-REQUEST pseudo-mailbox for each major
mailing list which vectors to the appropriate maintainer. For example:
  INFO-PCNET  (INFO-PCNET-REQUEST vectors to myself, REM)
  HUMAN-NETS  (HUMAN-NETS-REQUEST vectors to Mel Pleasant or somesuch)
  SPACE-ENTHUSIASTS, aka SPACE  (SPACE-REQUEST vectors to OTA or somesuch)
Ideally the mailer at the mailing-list-maintaining host should know
the appropriate ...-REQUEST pseudo-mailbox for each major mailing
list, sending barfbacks there instead of to Postmaster, using
Postmaster only when the -REQUEST doesn't exist or isn't known to the
software.