khushal via Mailman-Developers writes: > from what I understand, the idea is that list admins can define > topic tags, and members can subscribe only to the topics they care > about. If a message has a topic assigned then it will only go to > members subscribed to that topic.
Correct. > the direction in which i'm thinking, > - the topics are defined per mailing list by admins > - members can subscribe/unsubscribe from topics > - messages can be tagged with a topic > - during delivery, Mailman checks the message topic and only sends > it to members subscribed to that topic > - untagged messages treated as the special "not a topic" I believe that is correct. However, the point of this task is to reproduce the Mailman 2 feature for sites that use it. So you should refer to the Mailman 2 sources (launchpad.net/mailman, just download the tarball). > Questions: > i. does "not a topic" mean messages that don’t have any topic > assigned? Yes. > ii. if a member is not subscribed to any topics (including "not a > topic"), should they receive no messages at all? IIUC, "not a topic" is a bad name. It should be "no topic" or "untagged", and it should be visible only internally. You subscribe to the list, you should receive messages if tagged with any of your subscribed topics or not tagged. > iii. fro the scope of the project, is Core + Postorius support main > expectation, and wiht email commands as an additional goal? That would be acceptable since we're moving away from mail commands in any case. However, the preferred design is an exact replication of the Mailman 2 feature set, perhaps with additional features that are more in line with current Mailman 3 practice. HyperKitty is out of scope. > iv. for adding topics to messages does this happen only though > Postorius or should topic headers in incoming mail must be also > supported? I don't understand the question. Topics can only be created by admins, so that needs to be managed via Postorius. Subscribing to topics could be handled either by Postorius or email headers, but replication of Mailman 2 features is the most important criterion. Assembling the list of recipients must be based on a topic tag in the message header, as posters have no other way to indicate the topic. Does that answer your question? Steve -- 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
