It sounds like this is a proposal to somehow use information from one
list to affect the behavior of another list. If the two lists are
operating in different security/administrative domains then it means
information is leaking from one domain into another. I can see some
interesting
On Wed, Jun 19, 2019, at 9:28 AM, Mark Sapiro wrote:
> On 6/19/19 9:11 AM, Abhilash Raj wrote:
> >
> > Storing list of tuples in database might be inefficient for reads. I don't
> > think
> > there is an accurate column type one could use for this purpose unless
> > we convert them to string
On 6/19/19 9:11 AM, Abhilash Raj wrote:
>
> Storing list of tuples in database might be inefficient for reads. I don't
> think
> there is an accurate column type one could use for this purpose unless
> we convert them to string back and forth.
If we use PickleType, SQLAlchemy does the
On Wed, Jun 19, 2019, at 7:09 AM, Mark Sapiro wrote:
> 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
Ok, understood, currently,
[this](https://gitlab.com/mailman/mailman/merge_requests/528) is the pr for
which the discussion is happening, I will make the necessary changes.
Thanks,
Cheers!
___
Mailman-Developers mailing list --
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
Yes, definitely you are right on this, but since my mentor (Abbhilahs) focused
on the easy implementation first and Mark also focused on the complexity being
increased along with the bugs in the code. I am going for the easier
implementation as of now. Reason being I am not just contributing to
On 6/19/19 1:56 AM, Aaryan Bhagat wrote:
>> 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
