On Wed, 25 Feb 1998, Bill Houle wrote:
> At 09:10 AM 2/25/98 -0600, Robert Glover wrote:
> >
> >Is there a way to prevent an individual $ub$criber from posting to a list,
> >yet still being able to receive messages? I've noticed some NT-based
> >listservers have this ability, and was hoping there's a way to do it in
> >Majordomo.
>
> Use restrict_post, and have everyone *but* your offending users in the
> restrict_post file.
>
> Side note: why does everyone repeatedly suggest "listname.post" as a
> restrict_post name? This defeats the purpose of using Majordomo to manage
> the files, since a dotted file requires system-level access. A
> restrict_post file can be any valid listname, so make it another list that
> is noadvertised!
As a working example from my mail server ;) :
malks.config has:
restrict_post = malks-whopost
malks-whopost is a moderated list, with closed subscribe policy and
noadvertise.
Pros:
Its easy for the moderators to send a confirm unsubscribe to
malks-whopost to temporarily silence pests.
Easy for people to see 'who's been naughty or nice ;)
Cons:
Any new subscriber to malks must then be manually subscribed to
malks-whopost before they can post.
Pro of the Con:
Prevents pests from unsubscribing from malks, resubscribing and
automatically being able to post.
Its been working for nearly a month now with only one complaint (I didn't
set the password correctly ;) ), so it may work for you ;)
--==--
Bruce.
Systems Administrator
Hub Communications.
References:
|
|
