Sibling lists in Mailman3
Dear list,
after I migrated a list from Mailman21 to Mailman3 I missed the Mailman21 setting "regular_include_lists" (or something similar) in Mailman3. How are sibling lists treated in Mailman3?
Thank you in advance for your answers.
Best Markus
-- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342
On 3/27/24 08:05, Markus Grandpre wrote:
after I migrated a list from Mailman21 to Mailman3 I missed the Mailman21 setting "regular_include_lists" (or something similar) in
Mailman3. How are sibling lists treated in Mailman3?
The sibling list features do not exist in Mailman 3.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro writes:
On 3/27/24 08:05, Markus Grandpre wrote:
after I migrated a list from Mailman21 to Mailman3 I missed the Mailman21 setting "regular_include_lists" (or something similar) in Mailman3. How are sibling lists treated in Mailman3?
The sibling list features do not exist in Mailman 3.
Topics, dynamic lists, now sibling lists. All of these address a set of related problems, characterized by a large number of users who are divided into subgroups by interest, where the interests are pretty concrete and don't overlap much, each user may have several of those interests, and each subgroup considers the threads on other topics to be an interruption of their preferred workflow.
I would be interested in hearing user stories about their sites' use cases for these features (and any similar features whether or not they were implemented in Mailman 2).
Also horror stories, if any. (I can imagine that mixing rosters could leak personal information or result in annoying crosstalk.)
Please keep it in this thread, or write me personally if you prefer.
Steve
Thank you.
Am 27.03.24 um 17:26 schrieb Mark Sapiro:
On 3/27/24 08:05, Markus Grandpre wrote:
after I migrated a list from Mailman21 to Mailman3 I missed the Mailman21 setting "regular_include_lists" (or something similar) in Mailman3. How are sibling lists treated in Mailman3?
The sibling list features do not exist in Mailman 3.
-- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342
Is there an equivalent approach to implement sibling lists in Mailman3?
Best regards, Markus Grandpré
Am 3/28/24 um 16:06 schrieb Markus Grandpré:
Thank you.
Am 27.03.24 um 17:26 schrieb Mark Sapiro:
On 3/27/24 08:05, Markus Grandpre wrote:
after I migrated a list from Mailman21 to Mailman3 I missed the Mailman21 setting "regular_include_lists" (or something similar) in Mailman3. How are sibling lists treated in Mailman3?
The sibling list features do not exist in Mailman 3.
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to markus.grandpre@uni-konstanz.de
-- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342
On 4/9/24 22:25, Markus Grandpre wrote:
Is there an equivalent approach to implement sibling lists in Mailman3?
There is currently no way to provide the regular_exclude_lists function in Mailman3. For the regular_include_lists function, the closest you can come is to add the included list as a list member. See the FAQs at https://wiki.list.org/x/4030574 and https://wiki.list.org/x/4030540 for more information about what Mailman 2.1 calls umbrella lists.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (4)
-
Mark Sapiro -
Markus Grandpre -
Markus Grandpré
-
Stephen J. Turnbull