|
Content-Type: |
TEXT/PLAIN; charset=US-ASCII |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Sun, 6 Apr 1997 08:20:05 -0400 |
In-Reply-To: |
|
MIME-Version: |
1.0 |
Reply-To: |
|
-----BEGIN PGP SIGNED MESSAGE-----
On Fri, 4 Apr 1997, Jim Gerland <[log in to unmask]> wrote:
> I have a list which is a list of nested lists (follow me so far?).
> Now, they want *everyone* on *every one* of their lists to be able to
> send to *every one* of the lists (got it?).
>
> So, I setup the list headers like this:
> * Send= Prvate,(main list)
> * Send= ,(faculty-list)
> * Send= ,(department-a-faculty-list),(department-b-faculty-list)
Yup, that's the method we've used for years to mimic our campus
organizational chart. When I move to LISTSERV 1.8c, I'll also try to take
advantage of the new "Sub-lists=" list config keyword, which will allow
people to be subscribed to more than one sublist in the hierarchy but only
ever receive one copy of a posting.
I was hoping that the Sub-lists keyword would also stop the need for all
those Send=(list) and Review=(list) values -- every time a new sub-dept is
created anywhere in our campus org. chart, I have to go manually edit
every single employee list to add Send=(newlist) and Review=(newlist)
lines. Ick.
BTW, the Send= and Review= values are additive, so you don't need a
leading comma on the subsequent lines, e.g.
* Send=Private,(mainlist)
* Send=(faculty-list)
* Send=(department-a-faculty-list)
* Send=(department-b-faculty-list)
- -david
David Nessl
http://www.nerdc.ufl.edu/~david
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBM0eU9p58IU00gfAVAQEN3QP+L91rf8jhk4JQMSzim4wHj0DGLcuNXfxO
iUONB8uBTnnFLDQEp+SH8vgGcIiYuPBsC+uEWkl7pslS7/4EQPrEUUlew46OQvuc
yRI9xnRkutIbS2RqpHIx3XEFwTcCygISphkslZwElVk6cPhadXUr/PfXGJVrYy5n
hlyeHg34cBE=
=TnFf
-----END PGP SIGNATURE-----
|
|
|