On 6/18/19 10:56 PM, Aaryan Bhagat wrote: > > 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?
I would do this differently. The bounce_info attribute of the address is a possibly empty list of tuples. Each tuple contains things like the list_id, the current score and last_bounce_received. In MM 2.1 the bounce_info for a list also contained the remaining number of notices and the time of the last notice sent to control the sending of notices and eventual removal of an address with delivery disabled by bounce. This way, you keep track of bounces by list and ultimately may disable delivery to the address from only the one list on which the score reaches threshold. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ 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
