On 09/15/2016 05:13 PM, Mark Sapiro wrote:
It works like this. The recipient list for the master list post are all
the members of the master list plus all the members of those
regular_include_lists not also directly addressed in To: or Cc:, but
that recipient list is built as a set so there are no duplicates in it.

Actually, that works fine. Posters to the lists will be BoD members and educated volunteers who will have instructions. All other posters will have their posts silently sent to the cosmic bit bucket.

I understand that unsubscribe instructions on posts distributed via
(addressed to) the Master List will be relevant to the Master List,
although the address to be "unsubscribed" may exist on one or more
sibling lists. Since at least one of the sibling lists will contain the
email addresses of dues-paying members, it's necessary that the
unsubscribe request be processed on the Master List as an instruction
to _not_ distribute to the unsubscribing address rather than as an
instruction to unsubscribe the address from any or all sibling lists.

This is not possible for sibling lists. If an address is a member of
both the 'master' and one of the regular_include_lists, and it is
unsubscribed from the master, it will still be sent copies of posts to
the master because of its membership in the included list. There's no
way for the master to know that any member of an included list should
not be included.

This is turning into a relational database exercise :) There are creative ways to deal with it outside of Mailman and I can figure it out. withlist may be my friend here.

Can Mailman do these things?


It could probably be enhanced to do the things it currently doesn't do,
but there are no plans to do so.

Mailman very kindly provides most of the hooks necessary to do a lot of processing outside of the Mailman environment.

One thing that would be useful would be an option in Mailman to execute an arbitrary program or callback each time an action is taken, such as every time a name is subscribed or unsubscribed. This would could be used to trigger any external processing scripts.

Thanks for your response.

--
Lindsay Haisley       | "We have met the enemy and he is us."
FMP Computer Services |
512-259-1190          |          -- Pogo
http://www.fmp.com    |
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Reply via email to