> From majordomo-workers-owner@GreatCircle.COM Sun Apr 28 20:09:46 1996
> From: Brock Rozen <brozen@netvoyage.net>
> Reply-To: brozen@netvoyage.net
> To: Chan Wilson <cwilson@splut.neu.sgi.com>
> cc: Dave Barr <barr@math.psu.edu>, majordomo-workers@GreatCircle.COM
> Subject: Re: noadvertise in 1.94a4
> X-URL: http://www.netvoyage.net/~brozen
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> Sender: majordomo-workers-owner@GreatCircle.COM
>
> On Sun, 28 Apr 1996, Chan Wilson wrote:
>
> > Fixed. do_lists was calling access_check after checking
> > advertise/noadvertise, which meant that it would always succeed.
> >
> > Here's a question: Should list members be able to see the list via a
> > 'lists' command? Right now, [no]advertise forbids them from seeing
> > the list if they match. Thoughts?
>
> If somebody is on the list, there's no reason that it shouldn't show up
> for them when they do give a lists command. It seems silly to not let it
> show up.
>
> OTOH, the person may think the list is a "public" list and may tell others
> about it just because it shows up in the lists setting.
>
> How about this? Adding a show_lists config setting. When set to yes,
> it'll show the list to list members regardless of the
> advertise/noadvertise setting and when set to no, it'll stick solely to
> the advertise/noadvertise without regard to whether the person is a list
> member.
This would be good from the standpoint that if show_lists=yes, majordomo could
do less work by not having to check if the requestor was a member of the list.
Randall
>
> -------------------------------------------------------------------------
> | Brock Rozen | brozen@netvoyage.net | http://www.netvoyage.net/~brozen |
> | Check out my Auto-Reply System -- Send me mail with subject SEND HELP |
> -------------------------------------------------------------------------
>
>
Follow-Ups:
|
|