[prev in list] [next in list] [prev in thread] [next in thread] 

List:       majordomo-users
Subject:    Re: List security and config question
From:       Ed Kasky <ed () wrenkasky ! com>
Date:       2003-05-23 16:06:26
[Download RAW message or body]

At 08:36 AM Friday, 5/23/2003, Gari wrote -=>

>Good morning experts,

There's a joke here somewhere ;-)

>1. I want to make absolutely sure that nobody externally can view the
>members of one of my lists.  What is the best way via Majordomo to do this?

For each list config:

         # who_access           [enum] (open) <majordomo> /open;closed;list/
         # One of three values: open, list, closed. Open allows anyone
         # access to this command and closed completely disables the command
         # for everyone. List allows only list members access, or if
         # restrict_post is defined, only the addresses in those files are
         # allowed access.
who_access = closed

>an authorization token in the subject.  All you have to do is reply to the
>email and say 'accept' to be added to the list.  Is there a way to configure
>1.94.5 to do this?  Or is this a Majordomo 2 function?

         # subscribe_policy     [enum] (open+confirm) <majordomo> /open;closed
         # One of three values: open, closed, auto; plus an optional
         # modifier: '+confirm'.  Open allows people to subscribe themselves
         # to the list. Auto allows anybody to subscribe anybody to the list
         # without maintainer approval. Closed requires maintainer approval
         # for all subscribe requests to the list.  Adding '+confirm', ie,
         # 'open+confirm', will cause majordomo to send a reply back to the
         # subscriber which includes a authentication number which must be
         # sent back in with another subscribe command.
subscribe_policy = closed+confirm


[prev in list] [next in list] [prev in thread] [next in thread]