Simon wrote: > >My question basically is, what happens if I add a list in the >'accept_these_nonmembers' list, but that list contains another list as >well as individual subscribers? > > From what I can tell, it *looks* like it won't hurt anything, but the >members of that nested lists will still have to added individually in >order to be accepted. Is this right?
Yes. See remarks below. >Hmmm.. that sounded a little twisted... here's a semi-graphical explanation: > >Currently, this site uses nested lists, like so (I *will* be changing >the current nested list structure to use the new 'Umbrella' structure, >but I still want an answer to this question): > >Lists: >accounting >administration >everyone >sales >teamleaders > etc... > >teamleaders list members: > [EMAIL PROTECTED] > [EMAIL PROTECTED] > >sales list members: > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > etc... > >everyone list members: > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > etc... > >Now, currently, each list has the individual ([EMAIL PROTECTED], etc) >users that aren't actual members added in the 'accept_these_nonmembers' >filter. > >Now, if I add @sales to 'accept_these_nonmembers' for the everyone list >and remove all of the individual @sales members, then user3 and user4 >will be able to send to everyone, but user3 and user4 will not, even >though they are members of teamleaders and [EMAIL PROTECTED] is a >member of sales, I would have to also add @teamleaders to allow user1 >and user2 to be able to send to everyone - correct? Given that I think you mean 'but user1 and user2 will not', that is correct. >My main concern is that having a nested list inside a list that is added >to the 'accept_these_nonmembers' field of another list won't *break* >anything, especially in some way that is not readily apparent... No. It won't break anything. Putting @sales in any *_these_nonmembers field of the everyone list is just the same as individually listing all the member addresses of the sales list including the address '[EMAIL PROTECTED]'. At the point of processing the nonmember post, [EMAIL PROTECTED] is just another address which may or may not be the sender of the post. It probably won't match, and it won't be expanded in any way. Note that Mailman doesn't do well with lists that have a mixture of real users and other lists as members. If you declare the list as an umbrella list, then e.g. member [EMAIL PROTECTED] may not be able to get a password reminder as it will be sent to [EMAIL PROTECTED] If it's not an umbrella list, then anyone can go to the options login page for e.g. [EMAIL PROTECTED] and request a reminder which will be posted to the teamleaders list. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
