On 3/12/19 10:01 AM, Aaryan Bhagat wrote: > Thanks for the guidance mark! > > Also >> The additional complexity is because an address may be subscribed to more >> than one list and optimum values for settings such as bounce_score_threshold >> and bounce_info_stale_after depend on list traffic patterns. Compromises >> will need to be made. > > > Cannot we have separate variables managed by specific list owners/moderators > for this type of user.
We can but how does it all fit together and make sense? In a MM 3 installation we only have one address record for an address regardless of how many lists it is a member of, and if that address is bouncing on one list, presumably it will bounce on all lists. So do we want to keep track of bounces per address per list and disable delivery per list, or does it make more sense to keep track of bounces per address and disable all delivery to the address? -- 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
