>As far as I can tell, all the relevant list attributes are already >defined in mailman/model/mailinglist.py. As noted there, they should >probably be added to mailman/interfaces/mailinglist.py.
Yes, and I have done that (WIP actually) in the latest [pr](https://gitlab.com/mailman/mailman/merge_requests/528). >I'm not sure about creating the attributes like bounce score in the >member model. Granted this has the advantage of there already being >separate, per list member records, but my concern is that it's an >address that is bouncing, not a member so it may be more appropriate to >keep bounce info with the address rather than the member. Ok, so from what I get I will explain by taking an `example` address subscribed to 2 mailing list. - Create a bounce_score attribute in the address model. - Bounces generate from both the lists will add up the bounce_score attribute. - If `bounce_score >= bounce_score_threshold of list1` disable membership of list 1. - If `bounce_score>=bounce_score_threshold of list2` disable membership of list2. Is the above inference correct? Or, am I missing something inc context here? _______________________________________________ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org 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
