[Mailman-Developers] Re: Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

Stephen writes: >If we receive a bounce that indicates that the address does not exist, >we should stop sending warnings there. Somebody has screwed up pretty >badly, and it wasn't us. That is the main hurdle, bounce extraction cannot determine the exact cause so we cannot ever say with surety

[Mailman-Developers] Re: Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

Stephen writes: >You wrote some posts that indicated you were specifically worried >about the timing of the warning mails. When the conversation >continued without much explanation of your concerns, I assumed that >you were still thinking about the concurrency issues that arise in an

[Mailman-Developers] Re: Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

Stephen writes: >What "threshold"? The disabled_warning_interval? Yes, exactly. I apologise for being informal. Stephen writes: >Incrementing the warning counter should always happen if the mail is >successfully sent. Yes, I meant that only, I apologise for not explaining correctly. Stephen

[Mailman-Developers] Re: Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

Stephen writes: >I don't understand why you believe there are conditions under which >Mailman will do something undesirable, such as create a very long >delay from the time "something" (such as mailing a disabled warning) >should happen until it does happen. I am sorry but I do not understand

[Mailman-Developers] Re: Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

So it has taken me a couple of days regarding the right implementation. According to me, I think a new command which takes all the `Address` instances and in each instances checks which tuple of `bounce_info` have `disabled` attribute true ( more regarding these attribute in

[Mailman-Developers] Re: Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

Thanks for the reply, Stephen! Stephen writes: >I don't understand why there's any problem here. In what scenario is >the database corrupted relative to what is desired? What variables >are set differently from desired, and how? What are the user >consequences of the incorrect database?

[Mailman-Developers] Re: Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

Stephen Writes: >The odds that this happens is quite small unless you have a humongous >list. Furthermore, the probability that the mail will go through this >time if the account has disabled due to bouncing is presumably way >less than 1. So my first-order response is this is a non-problem. >

[Mailman-Developers] Implementing `bounce_you_are_disabled_warnings_interval` in `Send_Warnings` function.

I am developing the processing of bounce messages as my GSoC project. Currently the `Bounce Functions` are being developed in [this](https://gitlab.com/mailman/mailman/merge_requests/538) pr on GitLab. There is one `bool` attribute called `bounce_you_are_disabled_warnings_interval` in the

[Mailman-Developers] Re: flufl.lock._lockfile.NotLockedError: Already unlocked

>This seems to be because you removed the var/ directory without stopping >Mailman Core. Note that var/ directory is continuously needed by Mailman >Core when running since it stores it's runtime information there. If you >remove the var/ directory without stopping Mailman Core, you'll end >up in

[Mailman-Developers] Re: Cannnot find the processing of bounces as `hard` and `soft`

I understand, thanks for the reply, Mark. So that means I can set the `bounce_score_threshold` as Integer instead of Float reason being that the score will always be increased by one. Is the above inference correct? Am I missing something here? ___

[Mailman-Developers] flufl.lock._lockfile.NotLockedError: Already unlocked

I have started working on [this](https://gitlab.com/mailman/mailman/merge_requests/538) pr. It is regarding various bounce_process functions. Strange behaviour is observed which I am not so sure what or why is happening. Unexpected Traceback error pops up in my terminal. >File

[Mailman-Developers] Cannnot find the processing of bounces as `hard` and `soft`

Somewhat details regarding this can be found in [this](https://mail.python.org/archives/list/mailman-developers@python.org/thread/N7LB2VQN5MC7INXTP3N2CF7MJYSZQI3W/#5ELFHHN4FDLXHXLDVBYKLX36GQTWJTWV) thread also. Currently, in the `mailman/src/mailman/runners/bounce.py` I do not see whether the

[Mailman-Developers] Re: Alembic not going back to previous migration?

I will explain a little bit more what I exactly did, I downgraded alembic to `2d2d0ef0828f` version, made changes to `58858f75303c` migration file and then tried to upgrade again but alembic is recognising duplicating columns which means it has not downgraded properly, can we somehow erase all

[Mailman-Developers] Alembic not going back to previous migration?

Currently, I am working on [this](https://gitlab.com/mailman/mailman/merge_requests/528) PR. A problem arose with some SQLite tests and I made changes to the latest migration file. This is my output of `alembic -c src/mailman/config/alembic.cfg history` command >2d2d0ef0828f -> 58858f75303c

[Mailman-Developers] Mailman still sending mails when `DEVMODE` is on?

Currently, I have been trying to run a working instance of Mailman up and running. I have edited the `mailman.cfg` file enabling devmode. The current output of `mailman info` command is the following >GNU Mailman 3.2.3 (La Villa Strangiato) >Python 3.7.1 (default, Dec 14 2018, 19:28:38)

[Mailman-Developers] Re: Rich Text support in Hyperkitty

>Headers with # aren't supported, mostly due to their widespread use as >comments in code shared on mailing lists. I do not understand this, if you write a code snippet, it will not recognize the `#` a markdown syntax. So there should be no problem. >The supported syntax is limited Markdown Why

[Mailman-Developers] Re: Bounce processing should be done to only USER entities?

This is a really thoughtful insight, while I was thinking about implementing this feature of obtaining bounce data from other mailing lists, I did not realize that `shared servers` can also be there and then much hassle will be in obtaining data, so you can only take data from the same

[Mailman-Developers] Re: Bounce processing should be done to only USER entities?

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 --

[Mailman-Developers] Re: [SPAM?] Re: Bounce processing should be done to only USER entities?

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

[Mailman-Developers] Re: Bounce processing should be done to only USER entities?

>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

[Mailman-Developers] Re: Bounce processing should be done to only USER entities?

>Looking at the suggestion from Mark, how about you continue working on >the simplified implementation for now., and then once we have completed >that and we still have time left in your GSoC period, we can talk about the >enhanced proposal? Ok, I understand. >I think the only >relevant thing

[Mailman-Developers] Re: [SPAM?] Re: Bounce processing should be done to only USER entities?

>List 1 is a monthly newsletter. An email is sent early in the month, >every month, and no other traffic. If we want to allow subscribers to >bounce once and only on the second bounce (because it was just a >transitory issue) you need a second bounce, then at least for email from >this list, you

[Mailman-Developers] Re: Bounce processing should be done to only USER entities?

>I think your approach is probably valid, but it adds complexity to the >process. Complexity is not necessarily bad, but unnecessary complexity >is bad because it makes things more fragile and bug prone and more >difficult to maintain. > >So the bottom line question is whether this additional

[Mailman-Developers] Re: Bounce processing should be done to only USER entities?

>However, I have been a Mailman developer for 15 years and am commenting >from that perspective. I fully understand and respect that and in no state to question that ever. >Even though Mailman 3 has a concept of a user and understands things >like an address may be receiving mail from more than

[Mailman-Developers] Re: Bounce processing should be done to only USER entities?

>Mark would know more about this, but I wonder if there is a need to keep >the bounce score separate for each MailingList and keep the association >with a Member Object, as compared to an Address object Keeping it as separate has definitely its own perks, this is the basis for my proposal and I

[Mailman-Developers] Re: Bounce processing should be done to only USER entities?

>Why? Your proposal indicates you understand that a bounce is associated >with a particular address and list and should not affect that address on >other lists. So why are you interested in all the lists associated with >that address? You are right, but my proposal also indicates that I want to

[Mailman-Developers] Re: Bounce processing should be done to only USER entities?

The title to this inappropriate I accidentally copy-pasted something else at the end. Pardon my inappropriate title. I actually mean "Creation of bounce variables under which models?" ___ Mailman-Developers mailing list -- mailman-developers@python.org

[Mailman-Developers] Bounce processing should be done to only USER entities?

This is with reference to a discussion in a thread [1] here: I need two requirements : - I need an object of a user which has an attribute which tells us what are all the emails of the following user. - I need an object of an email having an attribute which tells us what mailing-lists that

[Mailman-Developers] Re: Subscribing members to list through 2 different methods?

I understood it, thanks for explaining >It is not *required* to create a "User" object associated with a Django user >until that user actually subscribes to a list. For my current aim of processing bounces, I think my target people are only those who are subscribed to some list right? Because

[Mailman-Developers] Re: Subscribing members to list through 2 different methods?

I actually am trying to understand the model architecture as a whole, I admit the pace is slow due to my machine had hardware problems recently ( I notified this as soon as possible to Abhilash and it is fixed now ), As mentioned in my proposal [1] I actually need an entity ( any model, class

[Mailman-Developers] Re: Subscribing members to list through 2 different methods?

>This used to be the case before Django-Mailman3 exited. With move to >django-allauth, we now sync _most_ of the changes in Postorius down >to Core. So you are implying if we create an account using Postorious, a User/Address object is created automatically in the Core but this is not important,

[Mailman-Developers] Re: Subscribing members to list through 2 different methods?

>mailmanclient is completely separate from Mailman core. It provides a >set of Python bindings that are used by Postorius and HyperKitty to >communicate with core via core's REST API. Its mailing list subscribe >method is not core's subscribe method and its arguments are those >appropriate for

[Mailman-Developers] Re: Possible Bug in the Docs of GNU Mailman?

Well I generally obtained the URL from search which somehow landed me to a previous release, although this problem is not reproducible now in my browser and I am at the latest release always ___ Mailman-Developers mailing list --

[Mailman-Developers] Re: Possible Bug in the Docs of GNU Mailman?

Yes, you are right this problem is not there in release 3.1 although I wonder why the previous release of ReadTheDocs was used by my browser as default. Thanks for helping ___ Mailman-Developers mailing list -- mailman-developers@python.org To

[Mailman-Developers] Subscribing members to list through 2 different methods?

Upon searching more regarding various models in the Gnu Mailman, I learned that technically first a "User" entity is created and then a "Member" entity can be created in correspondence to a "Mailing-List" entity. For example >harry_member = mlist.subscribe(harry_user) This, however, is totally

[Mailman-Developers] Possible Bug in the Docs of GNU Mailman?

Upon searching for various models in the docs of GNU Mailman ( One which is on ReadTheDocs ), I entered a query "Users" which gave me the result [1]. The problem is that the links to the pages which the search yielded, gave 404. This behaviour is rather peculiar and if it is reproducible in

[Mailman-Developers] Creation of blog posts documenting various valuable experiences during GSoC.

Hello everyone, I am a fellow GSoC contributor here and as part of my process to write blog posts. I have written 2 blog posts until now in my blog[1]. Since not much has been started for the organization's work, I have mostly focused on the GSoC period, what GSoC is, the how-tos and the tips

[Mailman-Developers] Re: Season of docs' 19 Doubts

Hello Aditi!, I am a fellow contributor in this organization under GSoC programme. Great to have you onboard with us. >1) Is there any user guide/support page on how to use the mailing list >explaining all the features of Postorius and Hyperkitty? For example, how >to manage subscription, how to

[Mailman-Developers] Re: Related to Google Season of Docs'19

Hello Saurabh!, I am a fellow GSoC contributor here, its good that you are reading the organization's GSoD page You can also see these threads as they contain valuable information. https://mail.python.org/archives/list/mailman-developers@python.org/thread/GSOUKG5DC4YGY5IKAFMHX6AHZOK6QXLS/

[Mailman-Developers] Re: Google Season of Docs 2019 Technical Writer

Hello Ali, I am a fellow GSoC contributor in this organization, welcome to have you onboard with us! You can check these mailing threads, they will help you in detail on how to start. https://mail.python.org/archives/list/mailman-developers@python.org/thread/GSOUKG5DC4YGY5IKAFMHX6AHZOK6QXLS/

[Mailman-Developers] Re: Mailman documentation for Google Season of Docs

Hello Shajia! I am a fellow contributor here under the GSoC program. >I'd love this opportunity to contribute as a technical writer at Mailman. As a front-end focused developer, I would love to work on Postorius, the Mailman’s web frontend. It's great to have you onboard. For GSoD I would

[Mailman-Developers] Re: Link in the webpage---"DEV/SeasonOfDocs2019-MailmanWiki" giving 404

>It's all in the first paragraph at Creating the account will help us to modify this wiki, but what happens to the doc at ReadtheDoc? Also, I am having trouble in sign up as the TextCha is always giving me the wrong answer! I have tried various answers to this which I

[Mailman-Developers] Re: Link in the webpage---"DEV/SeasonOfDocs2019-MailmanWiki" giving 404

Thanks, Mark for clearing that up I also want to know that is there a hierarchy or some other method of controlling power regarding changes in the wiki. What I mean is how the wiki is controlled/modified, who governs that? I just am inquisitive in this case and want to know the workflow. Any

[Mailman-Developers] Link in the webpage---"DEV/SeasonOfDocs2019-MailmanWiki" giving 404

So I was scrolling down the GSoD page of the org and found out that a major link important for GSoD folks under the "Writing Your Application" section is giving 404. I am copy pasting the line here >The [[https://developers.google.com/season-of-docs/docs/|Introduction to >Season of Docs page]

[Mailman-Developers] Re: Mailman Google Season of Docs

Hello Omar! I am a fellow GSoC contributor to this organization. Welcome to have you onboard with us for contributions. It looks like your doc is still in the newbie stage as of now. I would suggest you to read this link for help.

[Mailman-Developers] Re: Creating new Variables in the Database

>This is basic use on how fields look like in SQLAlchemy[1]. After you have >added a field, you can use Alembic to autogenerate migrations for your >changes in database schema. See [2] on how to write alembic migration >from scratch. > >You can (and should) just use alembic to autogenerate it

[Mailman-Developers] Re: Creating new Variables in the Database

Apparently, I think there is a minor bug in hyperkitty/postorious I suppose When I created the message to post into the list I accidentally clicked the "Send" button twice and then the page loaded so there were two copies of the exact same message, the URL is also different so I think it

[Mailman-Developers] Creating new Variables in the Database

As mentioned in my proposal[1] I will create new variables and modify the schema of how we save things in the database. Here I am facing issues (most probably because I am a newbie in SQL Alchemy). I am not able to understand how to exactly implement this. Relevant searches in the docs provided

[Mailman-Developers] Creating new Variables in the Database

As mentioned in my proposal[1] I will create new variables and modify the schema of how we save things in the database. Here I am facing issues (most probably because I am a newbie in SQL Alchemy). I am not able to understand how to exactly implement this. Relevant searches in the docs provided

[Mailman-Developers] Re: Google Season of Docs 2019 - GNU Mailman

Hello Raghav!, I am Aaryan a fellow GSoC contributor in this Organization. Mailman community would love to accept contributions from a guy having a skill like yours! Posting the important links This is the org's link for GSoD https://wiki.list.org/DEV/SeasonOfDocs2019 This the google's guide

[Mailman-Developers] Re: Interested for Google Season Of Docs

Hello Ayon!, I am Aaryan a fellow GSoC student in this organizationI. This the google's guide for GSoD https://developers.google.com/season-of-docs/ https://developers.google.com/season-of-docs/docs/participants/ https://developers.google.com/season-of-docs/docs/timeline Go through them. >How

[Mailman-Developers] Re: Season of Docs 2019

Yo Ovuoba!, I am Aaryan a fellow GSoC student here in this Org. I would suggest you go through these links This is the org's link for GSoD https://wiki.list.org/DEV/SeasonOfDocs2019 This the google's guide for GSoD https://developers.google.com/season-of-docs/

[Mailman-Developers] Re: Regarding Google Season of Docs

Hey Piyush, Mailman looks forward towards your contributions This is the org's link for GSoD https://wiki.list.org/DEV/SeasonOfDocs2019 This the google's guide for GSoD https://developers.google.com/season-of-docs/ https://developers.google.com/season-of-docs/docs/participants/

[Mailman-Developers] Re: GSoC Selections

Hey Arun!, >Congratulations to Aaryan Bhagat Thanks! Means a lot. Stick with the org if you find some time in the summers, it will help us a lot. You have learned a lot here and it will surely help for next time. >I would be thankful if you could tell me whether or not the detailed p

[Mailman-Developers] Re: Interested in Working on the Mailman Documentation for GSOD

Hello Ariessa! I am also a contributor here and have applied under the GSoC program. I have mentioned some pointers in your proposal. Try to give more time and discuss more here. This part of writing documents for mailman2 to 3 migration is very important and aside from the main mentors other

[Mailman-Developers] GSoC full proposal regarding "Add support for bounce processing in Core"

First of all, I apologize for not being active in the Gitlab codebase and only on the mailing-lists. This is because my semester is ending and had a lot of tests, moreover I was focusing only on my proposal and its related work. Fornutaley, that is not a problem anymore. I do not have any other

[Mailman-Developers] Re: Introduction

It mostly depends on the proposal and the quality of the work. If you submit good quality pr and a nice proposal before the deadline then you have a good chance. On Mon, 1 Apr 2019, 06:02 Rushang Gajjal, wrote: > I wanted the confirmation at the earliest regarding whether they are any > chances

[Mailman-Developers] Re: Mailman Core start error

>Please don't use sudo. Figure out what is the permission that you need and use only those. Sudo will get the `mailman start` to work and change a lot of other things that will break your installation. Abhilash is right! do not do that and assume the software is okay. First of all, I guess

[Mailman-Developers] Re: Loss of data when unsubscribed?

/YVNHTVAZEMRZ4EKBBVGMB25SPWX7Y63C/ On Thu, 28 Mar 2019, 21:58 Mark Sapiro, wrote: > On 3/27/19 11:01 PM, aaryan bhagat wrote: > > I understand you point Steve. > > What I want to ask mainly is that-- > > It is obvious that posts will not be deleted even if the user > unsubscribed. > > But t

[Mailman-Developers] (no subject)

I understand you point Steve. What I want to ask mainly is that-- It is obvious that posts will not be deleted even if the user unsubscribed. But there is a "Discussion you have commented" section. It is linked with each user. If a user resubscribes will this section appear or it will start

[Mailman-Developers] Re: Loss of data when unsubscribed?

Thanks for the reply, Steve! What I am trying to ask is hyperkitty preserves the archives even if the user unsubscribed or not since the data is important for the discussion in the thread. But there is a field there "Discussions you have posted to". If a user resubscribes, will the field

[Mailman-Developers] Re: Loss of data when unsubscribed?

Thanks Mark for the clarification! On Thu, 28 Mar 2019, 01:56 Mark Sapiro, wrote: > On 3/27/19 12:47 PM, Aaryan Bhagat wrote: > > Well in a crux when the user will resubscribe he will see its previous > posts. > > We have an implementation for that already right? >

[Mailman-Developers] Re: Loss of data when unsubscribed?

Well in a crux when the user will resubscribe he will see its previous posts. We have an implementation for that already right? ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to

[Mailman-Developers] Loss of data when unsubscribed?

When we unsubscribed a user after sending a probe. We currently remove it from the list's roster. Let's suppose the email is resubscribed. Will the discussion the email has posted earlier will remain there or the account will start fresh as any other new account?

[Mailman-Developers] Re: GSoC Proposal

I need it needs to be elaborated more. Read the gsoc proposal guide and the mailman format of proposal here https://wiki.list.org/DEV/GSoC-Application-Template On Mon, 25 Mar 2019, 20:38 Arun H, wrote: > Is this proposal OK? The link is below: > >

[Mailman-Developers] Re: Draft of GSoC Proposal on project "Add support for bounce processing in Core"

I am going to follow this methodology as of now as no reply has been received yet and the timeline for proposal submission has started. If anyone has some suggestions, please comment on this thread. ___ Mailman-Developers mailing list --

[Mailman-Developers] Re: Introduction to community

Hello Shivangi! I think you have already gone through the code base and seen a few issues. Well, the most important thing I would say to you right now is, according to the timeline the proposal submission starts today ( 25th March ) and ends on April 9th. Please start working now on any one of

[Mailman-Developers] Re: Draft of GSoC Proposal on project "Add support for bounce processing in Core"

Is my approach feasible and correct? Should I go on with this and start writing the timeline and execution of the work or some changes are still required? ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email

[Mailman-Developers] Re: Removing of bounce address from client.users?

>I'm really just an outside observer here, but it seems to me that in this >thread you (aaryan) are getting way ahead of yourself. I know you are >interested in this as a GSOC project, but it seems to me you should be >focusing on your GSOC proposal and getting accepted before you start

[Mailman-Developers] Re: Removing of bounce address from client.users?

ams as of now. On Mon, 18 Mar 2019, 22:07 Abhilash Raj, 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. > >

[Mailman-Developers] Re: Regarding GsOC proposal submission.

Ok thanks for suggestion. On Sun, 17 Mar 2019, 16:03 Abhilash Raj, wrote: > On March 16, 2019 10:21:56 AM PDT, Aaryan Bhagat < > aaryanbhagat...@gmail.com> wrote: > >For the project idea "Add support for bounce processing in Core" which > >I men

[Mailman-Developers] Regarding GsOC proposal submission.

For the project idea "Add support for bounce processing in Core" which I mentioned in the threads

[Mailman-Developers] Removing of bounce address from client.users?

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

[Mailman-Developers] Re: What is the processing time of bounce events?

I beleive I have understood. We can process the events registered and call for the necessary action (unsubscribing , send warning mail etc) it will not affect the other runners. Am I missing something? Provide some pointers on this please. On Thu, 14 Mar 2019, 11:45 aaryan bhagat, wrote: >

[Mailman-Developers] Re: What is the processing time of bounce events?

Ok, thanks for the clarification On Thu, 14 Mar 2019, 11:44 Mark Sapiro, wrote: > On 3/13/19 10:41 PM, aaryan bhagat wrote: > > The events when stored. I do not think their processing for removing an > > address effects the other runners so we can focus on a detailed handling &g

[Mailman-Developers] Re: What is the processing time of bounce events?

The events when stored. I do not think their processing for removing an address effects the other runners so we can focus on a detailed handling of registered msg. On Thu, 14 Mar 2019, 11:08 aaryan bhagat, wrote: > I want to ask whether they are independent or not we can define the > comp

[Mailman-Developers] Re: What is the processing time of bounce events?

I want to ask whether they are independent or not we can define the complexity of our processing upon its dependence on other processes. On Thu, 14 Mar 2019, 11:06 Mark Sapiro, wrote: > On 3/13/19 12:36 PM, Aaryan Bhagat wrote: > > > > Given a list of registered bounce

[Mailman-Developers] Re: Doubt regarding definition of "temporary and permanent failures"

Much appreciated Steve! I have a idea of what is there to work on and will post new doubt on threads soon!. ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org

[Mailman-Developers] Re: Doubt regarding definition of "temporary and permanent failures"

/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_aft

[Mailman-Developers] Re: Doubt regarding definition of "temporary and permanent failures"

Of course I will focus on what you explained me earlier. I just wanted to get a detailed understanding og what it is doing already. Thanks for help! On Tue, 12 Mar 2019, 22:47 Mark Sapiro, wrote: > On 3/12/19 4:17 AM, Aaryan Bhagat wrote: > > In "bounce.py" in "mai

[Mailman-Developers] Re: Doubt regarding definition of "temporary and permanent failures"

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

[Mailman-Developers] Re: Doubt regarding definition of "temporary and permanent failures"

In "bounce.py" in "mailman/src/mailman/runners" There is a comment in line 75 of this file states- The addresses will come back from flufl.bounce as bytes/8-bit strings, but we must store them as unicodes in the database. Assume utf-8 encoding, but be cautious. Reply by Mark Sapiro

[Mailman-Developers] Re: Doubt regarding definition of "temporary and permanent failures"

>The other kind are DSNs of some type returned to a LIST-bounces address. These >are processed by flufl.bounce which >determines whether the failure is temporary or permanent and reports that to >the bounce runner. In the end the bounce runner gets

[Mailman-Developers] Re: Indentation Issue

Xiaoxing, I think maybe dependencies are updated so running setup.py should solve the problem as it is with other module `readme_renderer` On Tue, 12 Mar 2019, 15:02 Xiaoxing Ye, wrote: > Hi Saswat, > > As you haven't supplied enough error information, please try to > pip install

[Mailman-Developers] Re: Doubt regarding definition of "temporary and permanent failures"

>There is some doc at > I have have gone through this earlier, here there is only mention about the registration of bounce events in a queue for processing. No mention of the type of errors discussed above. >If the

[Mailman-Developers] Re: Doubt regarding definition of "temporary and permanent failures"

Is this in the mailman3 doc? Like for what failure should we retry or discard the mail etc. On Tue, 12 Mar 2019, 04:02 Mark Sapiro, wrote: > On 3/11/19 1:45 PM, Aaryan Bhagat wrote: > > Are "temporary and permanent failures" mentioned in "bounce.py" in &

[Mailman-Developers] Doubt regarding definition of "temporary and permanent failures"

Are "temporary and permanent failures" mentioned in "bounce.py" in "mailman/src/mailman/runners/" the same as "soft and hard bounces" respectively? ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to

[Mailman-Developers] GSoC Intro and Project

I have started contributing in GNU Mailman for quite some time now and a some Introduction is required so. My name is Aaryan Bhagat a 2nd Year Computer Science Undergraduate studying in Indian Institute of Technology Kharagur. github-link---"https://github.com/berserker1; gitlab-link&

[Mailman-Developers] Re: Reason for file in mailman/src/mailman/model?

A follow up question I do not get what "bounces.py" in "mailman/src/mailman" is trying to achieve? >From what I understand we have a func to send the bounce back (this happens in >MTA so nothing unusual) Since Verp does not work effectively with every MTA so we parse the Verp message and send

[Mailman-Developers] Re: Reason for file in mailman/src/mailman/model?

Thanks Mark for clarification I have thought of working on "Implementing bounce features in mailman 3 " as my gsoc project I will create a new thread soon regarding the current status and will ask for inputs there. On Sat, 9 Mar 2019, 08:21 Mark Sapiro, wrote: > On 3/8/19 4:56 PM,

[Mailman-Developers] Reason for file in mailman/src/mailman/model?

There is some basic problem that has been tinkering me. In the codebase we have a MODELS folder in MAILMAN REPO We are forming classes using implementer from zope.interface although we have created interface already in INTERFACE folder. I read the doc on implementer but not much is given. Any

[Mailman-Developers] Re: Introduction

Hi Kanav I believe you should start reading The Contributing Guide http://docs.mailman3.org/en/latest/devsetup.html and the GSoC Ideas--- https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202019 to start with. ___ Mailman-Developers mailing

[Mailman-Developers] Re: Facing problem in setting up environment

r 7, 2019 at 12:04 AM aaryan bhagat > wrote: > >> Like should we create a issue for this. >> (I am asking to everyone who has replied to this thread atleast and to >> the administrators also) >> >> On Thu, 7 Mar 2019, 00:02 Krishna Kumar Dey, < >> k

[Mailman-Developers] Re: Facing problem in setting up environment

e from Installed apps works for now. > @aaryan It's not yet updated . We need to find an alternative for it. > > On Wed, Mar 6, 2019 at 11:43 PM aaryan bhagat > wrote: > >> Hi Xiaoxing, >> If you are saying 'painstore' >> is not required as of feb 22 canbot we ju

[Mailman-Developers] Re: Facing problem in setting up environment

Hi Xiaoxing, If you are saying 'painstore' is not required as of feb 22 canbot we just update the repo to latest version with paintstore not there? Is it done? On Wed, 6 Mar 2019, 23:35 Xiaoxing Ye, wrote: > Hi Dinesh, > > Your error message is not completed. I am guessing there are two >

[Mailman-Developers] Re: Confusing definition of "subscribers"

Thanks Richard for clarification ___ 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:

[Mailman-Developers] Re: Confusing definition of "subscribers"

Help me out in this line. You said that you are not a member of that list but you are able to send a mail? Any pointers or references on how this is possible? ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an

[Mailman-Developers] Re: Members unsubscribed still showing up in Client.Users?

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

[Mailman-Developers] Re: Members unsubscribed still showing up in Client.Users?

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 ___ Mailman-Developers mailing

[Mailman-Developers] 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. ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email

  1   2   >