Re: how to change 'restrict_post' by command

> Hi, Reference:
> > From:		Sean Casey <[email protected]> 
> > Date:		Fri, 30 Aug 2013 13:55:41 -0700 
> 
> Sean Casey wrote:
> > Bigby Findrake said on 8/30/2013 1:13 PM:
> > > On Fri, 30 Aug 2013, Joe R. Jah wrote:
> > >
> > >> On Fri, 30 Aug 2013, [email protected] wrote:
> > >>
> > >>> But, the administrator of ML can not access Mailing List server's local
> > >>> file system.
> > >>> So, he or she can not create member list files for 'restrict_post'.
> > >>>
> > >>> If you have any methods or ideas to solve it, would you help me by
> > >>> informing me your ideas ?
> > >>
> > >> You can change restrict_post, along with any other parameter by changing
> > >> the list configuration; send the following commands:
> > >
> > > So far everyone seems to be missing the OP's point: configuring the
> > > restrict_post setting is of limited use if the mailing list
> > > administrators are not able to place files on the mailing list server, a
> > > shortcoming which majordomo does nothing in itself to address.
> > 
> > The only way I've found to use restrict_post absent direct access to the 
> > server files is to set it to be the same as the list itself; that is, to 
> > restrict post to the one file that CAN be administered using majordomo's 
> > email interface. As Bigby points out, that is a "limited use" which only 
> > servers to restrict posts to the list members, but I've found it to be 
> > better than no restrictions at all.
> 
> Joe's last post is correct.
> 
> 
> Ref. Sean's "The only way I've found to use restrict_post" ...
> Here's a sample of extended use:
> 
> 	file: hike.config for list hike@
> 	  restrict_post = .hike-org-trusted-extras .trusted-extras old-committee hike-org other-org
> 	
> 	Several classes of people can write a large list "Hikers" <hike@...>
> 	(hike@ is an announcement only list, 'cos a lot of people
> 	on a number of lists I run are clueless & used to flood
> 	lists with junk )
> 	
> 	A small list of "Hike Organisers" <hike-org@...> can use
> 	their own list to discuss dates/ venues, but membership of
> 	walk-org@ also gives them permission to announce to big hike@ list.
> 	
> 	other-org@ list of organisers for a related sport
> 	are allowed to announce to hike@
> 	
> 	Members of .hike-org-trusted-extra (which is not a list just a
> 	file, so for that one I do need direct access to host) are also
> 	allowed to write to hike@ (eg trusted hikers, capable of organising,
> 	who do not want routine mail of hike-org@) (There's nothing
> 	special about file name beginning in a dot, just for my
> 	convenience)
> 	
> 	Members of file (not corresponding to a list name) .trusted-extras,
> 	I append that to almost all restrict_post lines:
> 	holiday/ emergency/ on site staff, they dont want all list mail,
> 	they do need permission to announce.
> 
> 
> BTW For anyone ramping up, supporting a growing number of hundreds
> of clueless lazy end users with majordomo@
> 	(As I do, a few lists of highly skilled people, but mostly
> 	lists of mostly self admitted clueless );...
> 	To save some re-inventing wheels as I had to, you might want
> 	to look at &/or use texts I put up to keep subscribers at bay, who
> 	regularly try to waste my time:
> 		http://berklix.org/help/
> 	
> 	( OK I also added stuff in headers & footers, & I also
> 	generate all my .configs with a Makefile, ('cos I didnt
> 	understand/ feel like trusting the majordomo.cf generic
> 	defaults in case they changed), + of course I added a lot
> 	of phrases like "please [un]sub me" both to majordomo
> 	forbidden phrases for lists & personal .procmail spam
> 	filter.)
> 
> One day i might move to Mailman, but I got bitten when I tried years back
> 	http://www.berklix.org/help/majordomo/#mailman
> + with extra time invested to get majordomo@ & lists running smoothly,
> & fearing ~600 clueless users too lazy to learn, who try to force
> sub. requests on me personaly - I'm loath to risk rocking the boat, 
> despite Mailman's attractions, so I'll probably still be running
> majordomo for some long time.
> 
> Cheers,
> Julian
> -- 
> Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com
>  Reply below not above, like a play script.  Indent old text with "> ".
>  Send plain text.  No quoted-printable, HTML, base64, multipart/alternative.


Another trick is to use parallel majordomo managed lists as access lists. 

For instance, I might have a list called 'foobar', which is comprised of three
lists in parallel. foobar, foobar-post, and foobar-purgatory. One is the 
actual list, one is additional access control for the list, and the last one
allows for reverse moderation of the list.


	foobar is the main list, with the usual list settings.



	foobar-post is a parallel list, with the same settings, except that
	foobar-post is aliased to foobar. This lets folks subscribe alternate 
	addresses to post from, without actually subscribing the second address.

	They will need to be able to receive and send mail from the alternate 
	address for subscription management, but will not receive list posts
	at that address.
	I generally don't advertise this list, but instead announce it in the
	info file.



	foobar-purgatory is another parallel list, also aliased to foobar, and
	fed from the same alias expansion as foobar. Note that it is not listed
	in restrict_post.

	It's a place where you can bounce folks whose accounts have been 
	compromised, and are spewing spam, without kicking them off the list
	entirely. They can read, but they can't post without moderator approval.

	This list is also not advertised, since normally only the list admin
	will need to manage it.

	I hacked up a copy of the 'bounce' command as 'foobar-moderate', which 
	easily bounces folks from 'foobar' to 'foobar-purgatory'. 


	The footer for foobar-purgatory proclaims that:

	'This is the foobar-purgatory list. You have been moved to this list 
	because of spam originating from your address. 
	As a result, you are no longer permitted to post to foobar.
	DO NOT attempt to resubscribe to foobar without permission from
	the list owner'
	

The configuration for foobar sets:
	restrict_post = foobar foobar-post 

The alias file has:
	foobar-post: foobar
	foobar-purgatory: foobar



I have hacked up majordomo to add a bunch of useful boilerplate to
the usual helpfile, explaining many of the common problems that I see,
such as mailers wrapping lines automatically, local policies (ie: don't
expect me to fix your problems. If you ask, I'll tell you what you are 
doing wrong, but you have to fix it at your end. No, I won't manually
push your subscription request.) as well as some boilerplate
directed at spammers (err, email marketers..). They can't say we didn't ask
them to not spam us. 

Everything feeding into majordomo, or any of our lists, is fed through demime,
which strips out all the MIME content and HTML, and mashes it to plaintext.

I take a split of the raw input to majordomo, and all of our lists, and feed
all the spam over to spamcop.

I have also added a number of common spam/phishing addresses to majordomo.cf. 
(no reason to respond to do_not_reply@, nobody@, paypal, ebay, etc, or anything 
with investment, lottery, lotto, etc in the headers.)





-- 
               -- Welcome My Son, Welcome To The Machine --
Bob Vaughan  | techie@{w6yx|tantivy}.stanford.edu 	| [email protected]
AF6RR	     | P.O. Box 19792, Stanford, Ca 94309-9792	| 1-650-469-3850
-- I am Me, I am only Me, And no one else is Me, What could be simpler? --