hi steve, I set up MM2 locally and tried the topics feature like list config, member preferences, injected posts, and checking recipients through logs. that helped me understand most of the behavior.
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 - for incoming messages if both an explicit topic header and regex/tagger matching apply what should take precedence? - 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? - 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? - 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? - 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 thanks, Khushal(a-khushal) _______________________________________________ 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
