Members unsubscribed still showing up in Client.Users?
I unsubscribed a couple of users from a mailing list but they are still showing up upon doing client.users. These users had joined only one mailing list.
I understand that the above question details and I deeply regret that and will not happen from now on--
My doubt is Suppose there are list of members in the mailing list like anna in test_one---test-1@example.com. Here 'anna' is in only this mailing list. If we unsubscribe anna then test_one.members does not show 'anna' as well as client.members But client.users show 'anna' . Is this behaviour expected or it should not be there?
Am I missing something here?
I followed a tutorial and *mailman start* runs just fine, but I don't know where to go from there. I do know Python, but not Django which may be a problem. If any of you could provide a road map for me - outlining what to learn, how to learn and where to learn - I would be eternally grateful!
On Tue, Mar 5, 2019 at 11:36 AM Mark Sapiro <mark@msapiro.net> wrote:
Hey Rohit, You can start by reading the contributing guide and other docs extensively, Understand the code and ask doubts
Side note: Your doubt is independent of this thread so create a new one,try avoid writing in this
Mark thanks for clarification
So currently there is a problem and I do not know the immediate solution. It is currently hindering my integration of pull request for mailmanclient.
So I have a created a new function of mass subscribing the emails but upon writing for it in 'using.rst'
I saw that the structure is rigid as the variables declared in an upper part are used below also.
Inserting my new function inbetween will cause errors as I will make new users for demonstration of function and hence new users will be recorded by client.users So my options to solve are---
Modify all the doc below Not going to happen
Delete the new users permanently---- Not just unsubscribe,permanent removal, not even client.users or any other function can see them.
Create a new client and email_list and all just for this purpose.
I need some pointers upon the method of approach (Either 2 or 3 or some new suggestion) Also need some pointers upon implementing 2 or 3.
I understand that the above question details and I deeply regret that and will not happen from now on--
My doubt is Suppose there are list of members in the mailing list like anna in test_one---test-1@example.com. Here 'anna' is in only this mailing list. If we unsubscribe anna then test_one.members does not show 'anna' as well as client.members But client.users show 'anna' . Is this behaviour expected or it should not be there?
Am I missing something here?
I followed a tutorial and *mailman start* runs just fine, but I don't know where to go from there. I do know Python, but not Django which may be a problem. If any of you could provide a road map for me - outlining what to learn, how to learn and where to learn - I would be eternally grateful!
On Tue, Mar 5, 2019 at 11:36 AM Mark Sapiro <mark@msapiro.net> wrote:
Hey Rohit, You can start by reading the contributing guide and other docs extensively, Understand the code and ask doubts
Side note: Your doubt is independent of this thread so create a new one,try avoid writing in this
Mark thanks for clarification
So currently there is a problem and I do not know the immediate solution. It is currently hindering my integration of pull request for mailmanclient.
So I have a created a new function of mass subscribing the emails but upon writing for it in 'using.rst'
I saw that the structure is rigid as the variables declared in an upper part are used below also.
Inserting my new function inbetween will cause errors as I will make new users for demonstration of function and hence new users will be recorded by client.users So my options to solve are---
Modify all the doc below Not going to happen
Delete the new users permanently---- Not just unsubscribe,permanent removal, not even client.users or any other function can see them.
Create a new client and email_list and all just for this purpose.
I need some pointers upon the method of approach (Either 2 or 3 or some new suggestion) Also need some pointers upon implementing 2 or 3.
participants (3)
-
Aaryan Bhagat -
Mark Sapiro -
Rohit Sanjay