# @(#) $Id: README,v 1.1 1991/10/26 23:17:34 tron Exp $

Path: veritas!amdcad!sun!newstop!sun-barr!cs.utexas.edu!swrinde!mips!atha!aupair.cs.athabascau.ca!lyndon
From: lyndon@aupair.cs.athabascau.ca (Lyndon Nerenberg)
Newsgroups: comp.mail.misc
Subject: Re: Smail3, mailing lists, and remote bounce messages
Message-ID: <lyndon.686548573@aupair.cs.athabascau.ca>
Date: 4 Oct 91 03:56:13 GMT
References: <1991Oct2.143758.11575@tssi.com>
Sender: news@cs.athabascau.ca
Lines: 123

nolan@tssi.com (Michael Nolan) writes:

>The problem is this: if there is a bad address on the list the
>bounce message is passed on to the entire list, not just to the owner.
>LOCAL delivery problems go to the owner, but not remote ones.

Here's how I handle the problem on the smail3-users mailing list.

owner-smail3-users-redist:	postmaster
owner-smail3-users:		postmaster
owner-smail3-users-request:	postmaster
smail3-users-request:		postmaster
smail3-users:	"|/etc/local/smail/stripheaders|/usr/local/bin/smail -odq -oi -fsmail3-users-request smail3-users-redist daryl"
smail3-users-redist:	:include:/etc/local/smail/LISTS/smail3-users


Messages sent to smail3-users gets it's envelope return address changed
to <smail3-users-request> before being sent out to the list. Most mailers
use the envelope from address to send bounce notifications to. Local errors
in processing list messages go to postmaster via the owner-* entries. I
can't recall a bounce message ever getting past this system in two years
of use. It's also the system used by Brian Kantor at UCSD for several
*very* large mailing lists (i.e. I stole the idea from him :-)
--
           atha!cs.athabascau.ca!lyndon || lyndon@cs.athabascau.ca
                    Packet: ve6bbm@ve6mc.ab.can.noam
        As a math atheist, I should be excused from this.   --Calvin
