Re: bounce vs. moderated list issue

[Chip Old <fold @ bcpl . net>]

On Wed, 14 Jun 2006 14:47 +0800, James Taylor wrote:

> [much deleted]
>
> # restrict_post        [restrict_post] (undef) <resend>
> # If defined, only addresses listed in these files (colon or space
> # separated) can post to the mailing list. By default, these files
> # are relative to the lists directory. These files are also checked
> # when get_access, index_access, info_access, intro_access,
> # which_access, or who_access is set to 'list'. This is less useful
> # than it seems it should be since there is no way to create these
> # files if you do not have access to the machine running resend.
> # This mechanism will be replaced in a future version of
> # majordomo/resend.
> restrict_post       =   enewsletter.senders
>
> while enewsletter.senders (in the lists dir with permissions -rw-rw-r-- 
> owned by majordomo:majordomo contains my email addresses in one line 
> delimited by a colon (:).

Like any other Majordomo <listname> file, the one specified in 
restrict_post should contain one e-mail address per line.  The phrase 
"only addresses listed in these files (colon or space separated) can post 
to the mailing list" is a bit ambiguous.  It actually refers to multiple 
filenames in the restrict_post directive, not to the contents of the 
file(s).  For example:

restrict_post       =   enewsletter:enewsletter.senders

would allow posting by anyone subscribed to the enewsletter list as well 
as by anyone (presumably non-subscribers) listed in the 
enewsletter.senders file.

--
Chip Old (Francis E. Old)             E-Mail:  fold @
bcpl .
net
BCPL Network Administrator            Phone:   410-887-6180
BCPL.NET Internet Services Manager    FAX:     410-887-2091
320 York Road
Towson, MD 21204-5179  US