Great Circle Associates Majordomo-Users
(July 2005)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: sender allowed to post but not in recipient
From: "Roger B.A. Klorese " <rogerk @ queernet . org>
Date: Mon, 11 Jul 2005 12:35:46 -0700
To: "Allan P. Magmanlac" <allan . magmanlac @ nrns . ca>
Cc: Richard Draves <draves @ bard . edu>,MAJORDOMO-USERS <majordomo-users @ greatcircle . com>
In-reply-to: <42D2B3E1.2080600@nrns.ca>
References: <42CED1FC.8040308@nrns.ca> <03b301c583f5$20023950$61acfea9@DEAN> <42D27C54.70807@nrns.ca> <42D27E17.2040006@nrns.ca> <42D282DA.8040200@bard.edu> <42D2B3E1.2080600@nrns.ca>
User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

Allan P. Magmanlac wrote:

> It would create then a totally different list and this is not what is 
> intended as there should only be one list with other people who can 
> only post to the same and one list.
>

You're thinking too narrowly.  You're thinking "list == a set of 
addresses to which mail can be sent."  We're telling you that "list == a 
set of addresses that can be managed using the Majordomo software, and, 
if proper aliases are set up, to which mail can be sent."  Note the "if" 
portion.  Don't set up the aliases (other than the -owner and owner- 
aliases), and no mail can be sent to this list -- it just becomes a file 
that can be managed remotely using the Majordomo software so you don't 
need shell access to the server.  Than you list that "list" name in the 
restrict-post line of your real list.

    restrict_post = LISTNAME:LISTNAME-posters

You're being incredibly resistant to this, and yet, it's how it's been 
done for years.


Follow-Ups:
References:
Indexed By Date Previous: Re: sender allowed to post but not in recipient list
From: "Allan P. Magmanlac" <allan.magmanlac@nrns.ca>
Next: Re: sender allowed to post but not in recipient
From: Richard Draves <draves@bard.edu>
Indexed By Thread Previous: Re: sender allowed to post but not in recipient list
From: "Allan P. Magmanlac" <allan.magmanlac@nrns.ca>
Next: Re: sender allowed to post but not in recipient
From: Richard Draves <draves@bard.edu>