Xref: utzoo comp.mail.sendmail:675 news.sysadmin:2267 news.admin:5604
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!triceratops.cis.ohio-state.edu!karl
From: karl@triceratops.cis.ohio-state.edu (Karl Kleinpaste)
Newsgroups: comp.mail.sendmail,news.sysadmin,news.admin
Subject: Re: Setting up and running an internet style mailing list
Message-ID: <KARL.89Apr13152149@triceratops.cis.ohio-state.edu>
Date: 13 Apr 89 19:21:49 GMT
References: <532@drd.UUCP>
Sender: news@tut.cis.ohio-state.edu
Followup-To: comp.mail.sendmail
Distribution: usa
Organization: OSU
Lines: 32
In-reply-to: mark@drd.UUCP's message of 12 Apr 89 20:36:06 GMT

mark@drd.UUCP (Mark Lawrence) writes:
   I know other
   people run lists without admin type messages echoing back to the
   distribution -- how is it done?

Here is my canonical large mailing list maintenance scheme.

In /usr/lib/aliases:

ListName-request:	karl
ListName:		"|/n/dinosaur/0/karl/ListName/SendScript"
owner-ListName:		ListName-request
ListName-out:		:include:/n/dinosaur/0/karl/ListName/Aliases
owner-ListName-out:	ListName-request

/n/dinosaur/0/karl is my home directory.  The Aliases file has the
actual addresses.  The SendScript looks like this:

#!/bin/sh
/bin/sed -e '/^Reply-To:/d' -e '/^Sender:/d' -e '/^From /d' | \
	(echo Reply-To: ListName@cis.ohio-state.edu; \
	 echo Errors-to: ListName-request@cis.ohio-state.edu; \
	 echo Sender: ListName-request@cis.ohio-state.edu; \
	 echo Precedence: bulk; /bin/cat -) | \
	/usr/lib/sendmail -f ListName-request@cis.ohio-state.edu \
		-F 'ListName Mailing List' ListName-out

The Precedence: header and -f ListName-request are what prevent
vacation(1) from generating responses to mail which arrives from such
lists.

--Karl