confusing post requirements policy
Recently i added an option to mailman to make it so that the list of posters that are allowed to post sans approval would or would not include the list members automatically.
I have several lists using this option, and just discovered that a good deal of confusion was created over the fact that there are 3 interrelated questions on the admin cgi (and corresponding variables) that could be summed up in 2:
- variable member_posting_only.
- variable posters
- posters_includes_members
currently, there is not only confusion, but a problem. specifically, if member_posting_only is set, posters has some addresses in it, and posters_includes_members is set to yes, then it doesn't allow posting from non members in the posters list.
It seems like it would be much more clear if there were 2 variables:
member_posting (in place of member_posting_only and posters_includes_members) posters
if member_posting is set to true, the addresses in posters gets added to the subscriber list to form the list of all approved posts. if member_posting is set to false, the addresses in posters are the only ones that can post without approval.
this seems much simpler and more clear to me.
how do people feel about this?
scott
Can you clear up how I would say: "everyone can post execpt viega@list.org"?
John
On Thu, Oct 22, 1998 at 03:56:22PM -0400, Scott wrote: Recently i
added an option to mailman to make it so that the list of posters that are allowed to post sans approval would or would not include the list members automatically. I have several lists using this option, and just discovered that a good deal of confusion was created over the fact that there are 3 interrelated questions on the admin cgi (and corresponding variables) that could be summed up in 2: 1) variable member_posting_only. 2) variable posters 3) posters_includes_members currently, there is not only confusion, but a problem. specifically, if member_posting_only is set, posters has some addresses in it, and posters_includes_members is set to yes, then it doesn't allow posting from non members in the posters list. It seems like it would be much more clear if there were 2 variables: member_posting (in place of member_posting_only and posters_includes_members) posters if member_posting is set to true, the addresses in posters gets added to the subscriber list to form the list of all approved posts. if member_posting is set to false, the addresses in posters are the only ones that can post without approval. this seems much simpler and more clear to me. how do people feel about this? scott _______________________________________________ Mailman-Developers maillist - Mailman-Developers@python.org http://www.python.org/mailman/listinfo/mailman-developers
do you mean everyone or all subscribers? lets do both, as an exercise ;)
to allow all people, subscribers or not, to post to a list except viega@list.org:
set member_posting to no set moderated to no add viega@list.org to forbidden_posters
to allow all subscribers to post to a list except viega@list.org set member_posting to yes set moderated to no add viega@list.org to forbidden_posters
perhaps member_posting could be more aptly named something else, but the current suffix "_only" implies that the variable posters is ignored when in fact it is not.
scott
On Thu, Oct 22, 1998 at 01:06:28PM -0700, John Viega wrote: | Can you clear up how I would say: "everyone can post execpt viega@list.org"? | | | John | | On Thu, Oct 22, 1998 at 03:56:22PM -0400, Scott wrote: Recently i | > added an option to mailman to make it so that the list of posters | > that are allowed to post sans approval would or would not include | > the list members automatically. I have several lists using this | > option, and just discovered that a good deal of confusion was | > created over the fact that there are 3 interrelated questions on the | > admin cgi (and corresponding variables) that could be summed up in | > 2: 1) variable member_posting_only. 2) variable posters 3) | > posters_includes_members currently, there is not only confusion, but | > a problem. specifically, if member_posting_only is set, posters has | > some addresses in it, and posters_includes_members is set to yes, | > then it doesn't allow posting from non members in the posters list. | > It seems like it would be much more clear if there were 2 variables: | > member_posting (in place of member_posting_only and | > posters_includes_members) posters if member_posting is set to true, | > the addresses in posters gets added to the subscriber list to form | > the list of all approved posts. if member_posting is set to false, | > the addresses in posters are the only ones that can post without | > approval. this seems much simpler and more clear to me. how do | > people feel about this? scott | > _______________________________________________ Mailman-Developers | > maillist - Mailman-Developers@python.org | > http://www.python.org/mailman/listinfo/mailman-developers
for an example of how this would work, go to http://chronis.icgroup.com/mailman/admin/test
password is testme
and play with it. there is one less question to answer, it seems much more clear, and all the possibilities of the poster_includes_members setting are there.
for those of you who aren't running code from the cvs sources, you can compare it to
http://mailman.pobox.com/cgi-bin/admin/testdrive password testme
it seems much cleaner to me, and i'll make the appropriate changes if people seem to agree.
scott
On Thu, Oct 22, 1998 at 04:10:35PM -0400, Scott wrote:
| do you mean everyone or all subscribers? lets do both, as an exercise ;)
|
| to allow all people, subscribers or not, to post to a list except
| viega@list.org:
|
| set member_posting to no
| set moderated to no
| add viega@list.org to forbidden_posters
|
| to allow all subscribers to post to a list except viega@list.org
| set member_posting to yes
| set moderated to no
| add viega@list.org to forbidden_posters
|
| perhaps member_posting could be more aptly named something else, but
| the current suffix "_only" implies that the variable posters is
| ignored when in fact it is not.
|
| scott
|
|
|
| On Thu, Oct 22, 1998 at 01:06:28PM -0700, John Viega wrote:
| | Can you clear up how I would say: "everyone can post execpt viega@list.org"?
| |
| |
| | John
| |
| | On Thu, Oct 22, 1998 at 03:56:22PM -0400, Scott wrote: Recently i
| | > added an option to mailman to make it so that the list of posters
| | > that are allowed to post sans approval would or would not include
| | > the list members automatically. I have several lists using this
| | > option, and just discovered that a good deal of confusion was
| | > created over the fact that there are 3 interrelated questions on the
| | > admin cgi (and corresponding variables) that could be summed up in
| | > 2: 1) variable member_posting_only. 2) variable posters 3)
| | > posters_includes_members currently, there is not only confusion, but
| | > a problem. specifically, if member_posting_only is set, posters has
| | > some addresses in it, and posters_includes_members is set to yes,
| | > then it doesn't allow posting from non members in the posters list.
| | > It seems like it would be much more clear if there were 2 variables:
| | > member_posting (in place of member_posting_only and
| | > posters_includes_members) posters if member_posting is set to true,
| | > the addresses in posters gets added to the subscriber list to form
| | > the list of all approved posts. if member_posting is set to false,
| | > the addresses in posters are the only ones that can post without
| | > approval. this seems much simpler and more clear to me. how do
| | > people feel about this? scott
| | > _______________________________________________ Mailman-Developers
| | > maillist - Mailman-Developers@python.org
| | > http://www.python.org/mailman/listinfo/mailman-developers
|
| _______________________________________________
| Mailman-Developers maillist - Mailman-Developers@python.org
| http://www.python.org/mailman/listinfo/mailman-developers
|
participants (2)
-
John Viega -
Scott