On Mon, Mar 18, 2019, at 9:43 AM, aaryan bhagat wrote: > Thanks for clarification abhilash, however a small query is there upon seeing > you reply. > > >a user could have multiple addresses > > > This means a user having a specific email let's say "a...@example.com" is > subscribed to multiple mailing-lists(addresses).
No, this means that a user can have multiple email addresses: User Foo: - Email: f...@example.com - Email: f...@example.com - Emai: f...@example.org > > The email will be unique of every user. Yes, one email belongs to one user. But, one user can have many email addresses. > It is not like a single user can have multiple emails subscribed to multiple > mailing-lists. Yes, one user can have multiple emails subscribed to multiple mailing lists. So from above, "User Foo" could be subscribed to - "Member of list1.example.com" with "Email: f...@example.com" - "Member of list2.example.com" with "Email: f...@example.com" - "Member of list2.example.com" with "Email: f...@example.com <mailto:f...@example.com>" - "Member of list2.example.com" with "Email: f...@example.com <mailto:f...@example.com>" So, one user can subscribe to same mailing list with more than 1 email address. > > We will treat the multiple emails as separate users right? No, addresses belong to user, but more than 1 address can belong to same user. > > Also I have begun writing the proposal. > I have a concrete idea of what should we implement. > Although it lacks multiple us-case diagrams as of now. Cool! > > On Mon, 18 Mar 2019, 22:07 Abhilash Raj, <maxk...@asynchronous.in> wrote: >> On Fri, Mar 15, 2019, at 9:52 AM, Aaryan Bhagat wrote: >> > Let's say I have an email subscribed to multiple lists and almost all >> > of them are generating bounce messages upon sending to that address. >> > It is pretty much it is confirmed that this address is now stale and >> > does not work now. >> > >> > Except from unsubscribing it from the lists I also think it would be >> > wise to remove it from client.users. >> >> When we are talking about Core, `client.users` doesn't make any >> sense. A better term to use will be just "User entry". Client is a Python >> API library, that can optionally be used to manage Core. >> >> I don't think you need to remove a user entry, you should change >> properties of the address since a user could have multiple addresses >> and we don't want to disable delivery on all of them if only one >> of them in bouncing frequently. >> >> You can always disable delivery on an address, without having >> to remove the membership or delete them. See how you can set >> preferences[1] on a address to disable delivery. >> >> [1]: >> https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/preferences.html >> >> > >> > I need some pointers regarding if this should be applied or not? >> > Am I missing some crucial info 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 >> > >> >> -- >> thanks, >> Abhilash Raj (maxking) -- thanks, Abhilash Raj (maxking) _______________________________________________ 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
