Hi all, While I was figuring out the implementation for the dynamic sublists feature across mm3 (and postorius), what I get from it is that we need to store thread opt-ins in a separate new database schema and also inject a custom (pipeline) handler which will form some kind of set intersection etc.
There are a few things that are kind of bugging me, like when a user deleted their email address permanently or unsubscribes from the (parent) mailing list, should we drop all of their rows in the new database schema that was made to store thread opt-ins immediately, or would it be better (and easier) to just do the deletions when the custom handler build encounters an address that is invalid/missing? Also for the custom handler...i am thinking of putting it right after the handler that helps form the regular delivery list/set, so the new handler just does an intersection and removes those that haven't opted into a particular thread. So do you think placing it immediately after will interfere with some steps that happen down the pipeline like archiving, moderation etc.? Thank you so much Kind regards, Archie _______________________________________________ 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
