Just to confirm (as the probable mentor if accepted), I agree with everything Mark wrote below. Sorry for the top-post, but it seems appropriate in this case.
Steve Mark Sapiro writes: > On 3/13/26 23:56, khushal via Mailman-Developers wrote: > > > > I wanted to confirm a few implementation details > > > > - from your earlier reply it sounded like untagged or non matching posts > > should still be delivered to all subscribers. if that is the case should > > MM3 remove receive_nonmatching_topics entirely instead of keeping that > > state > > You should keep the member's receive_nonmatching_topics setting to > control this. > > > - for incoming messages if both an explicit topic header and regex/tagger > > matching apply what should take precedence? > > Just my opinion, but a message could match multiple topics, so I think > the end result should be a union of the two. > > > - for outgoing messages that match topics should mailman always include an > > X-Topics header. and if multiple topics match is there a preferred format > > or order? > > Always include as long as there are matching topics. The format in MM2.1 is > > for a single topic > > X-Topics: topic > > and for multiple topics > > X-Topics: topic1 > topic 2 > topic 3 > > which is actually wrong. There should be commas as in > > X-Topics: topic1, > topic 2, > topic 3 > > There's no preferred order. > > > - in MM2 it seems digests do not have topic filtering, should MM3 keep the > > same behavior or should topics also filter what appears in digests? > > Digests are not personalized. Every digest subscriber gets the same > digest so it is not possible to filter on topics. Digests contain all > messages. > > > - if a topic is renamed or deleted what should happen to existing member > > subscriptions to that topic. should they be automatically migrated to the > > new topic removed or be left unchanged until the user updates their > > preference? > > Good question. MM2.1 ignores this issue leaving the user's preferences > unchanged so the user is still subscribed to the old topic, but it never > matches. > > > - as suggested by Дилян to take a look, LISTSERV has a 21 topic limit, for > > MM2 parity im assuming we should not add any hard limit on the number of > > topics unless there is a specific reason. please confirm > > I don't think we need a limit. > > -- > Mark Sapiro <[email protected]> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-Developers mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/mailman-developers.python.org/ > Mailman FAQ: https://wiki.list.org/x/AgA3 > > Security Policy: https://wiki.list.org/x/QIA9 -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan _______________________________________________ Mailman-Developers mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
