On Mon, 11 Apr 2011, Mark Sapiro wrote:
Lucio Chiappetti wrote:

The help text for accept_these_nonmembers says
[...]
I cannot manage to have the @ notation working though.

The first syntax without the space after the @ is the correct one. It is being rejected because a list cannot reference itself in *_these_nonmembers. You must put only '@pseudoastro' in accept_these_nonmembers of the pseudotecno list and vice versa.

Thanks, I was trying to copy a common configurations for ALL lists from the first one with /usr/lib/mailman/bin/config_list -o and -i, so I thought to include all the lists in accept_these_nonmembers

Now (listing all sibling lists EXCEPT "itself") I can achieve what I want.

I tried this in conjunction with sibling lists as defined in
regular_include_lists. Of course in this case I use the full list
name [email protected] ...

Only I noticed that nesting of sibling lists is not allowed (it does not work as expected).

I created the following cases :

 list     members siblings         accept non members
 ----------------------------------------------------------------
 pseudoa  A       none             pseudot pseudop              *
 pseudot  B       none             pseudoa pseudop              *
 pseudos  none    pseudoa pseudot  pseudoa pseudot pseudop
 pseudop  A+x(,C) none             pseudoa pseudot              *
 pseudoi  none    pseudos pseudop  pseudoa pseudot pseudop

The three lists marked with * contain members (in the regime they will contain several members and they will be disjoinct, and there will be six such lists).

The other two lists (no *) are umbrella lists. They have no members but only sibling lists.

All the lists will be closed. Members of all real lists (and only they) can post to any of the lists.

However with the configuration given above, list "pseudoi", which is a 2-level umbrella list (one of the sibling has siblings) does not work.
Message sent to it are never dispatched to pseudot.

The SOLUTION is to avoid nesting. "pseudoi" siblings are all three level-0 lists pseudoa pseudot pseudop.

This way it works.

And it is also smart. Originally in pseudop I defined as member myself with a subaddress (A+x). This is not realistic but I did not want to annoy another colleague for the tests.

Mailman is so smart that when sending to pseudoi send just to A,B and C and removes the duplicate to A+x. Great !

While when receiving, a subaddress is honoured (so if I post from e.g.
lucio+fakenonmember, this triggers moderation). As it should be !

Maybe part of this information could go in a FAQ.
------------------------------------------------------
Mailman-Users mailing list [email protected]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Reply via email to