<html>
<font size=3>At 01:39 PM 8/30/00 -0700, Dan Mick wrote:<br>
<br>
<blockquote type=cite cite>>
> - I'd be *most useful* to
have a another subscriber option<br>
> > which indicated that
the subscriber wasn't really a person<br>
> > but was, in reality,
a sublist. For those subscribers<br>
> > monthly notices
(which should also be a per-subscriber thing<br>
> > IMO) and other
administrativia would be sent to owner-<subscriber><br>
> > (or
<subscriber>-owner, or <subscriber>-admin).<br>
> <br>
> <br>
> Umm, that's what the entire "umbrella list" concept is
for; it's switches <br>
explicitly<br>
> do that. Or were you wanting to mix people and lists?<br>
<br>
Speaking personally, I've yet to understand what "umbrella
list"<br>
means, or how it changes Mailman's operation. Anyone who
understands<br>
this want to take a shot at explaining it?</font></blockquote><br>
It's a list that consists of just other lists. I use it locally to
consolidate some lists that<br>
have similar types of users; like two clubs that often co-sponsor events,
with<br>
overlapping memberships. There's a combined list that gets
both. If mailman knows<br>
it's an umbrella list, it won't do silly things like send the password
reminders to<br>
the member lists, because it knows they're not people.<br>
<br>
<br>
</html>