BERJAYA

before next release: disable backscatter in default installation
by Jo Rhett Nov. 7, 2022

Nov. 7, 2022

Hi. There's a fairly simple problem here that needs to be addressed. And it's mostly a documentation/install problem. I'm hoping we can get this resolved before the next release. PROBLEM: Mailman comes out of the box ready to backscatter spam people. Yes, it's easy enough to fix. But because it comes stock this way, and is documented to install this way, most people install it to do this. Those of us who work in abuse departments are tired of hearing "well that's how Mailman works". We also object to having to teach people how to fix their mailman installations because it's not documented in the current manual. This is *exactly* like Sendmail 14 years ago. We didn't accept it then, and Sendmail fixed the problem. RESOLUTION: Mailman default installation should not backscatter in a default configuration. 1. Don't create backscatter aliases for subscribe/unsubscribe/etc by default. Nearly everyone uses web based signup. 2. Discard or hold messages from non-subscribers by default. I would think that it would be perfectly reasonable to have documentation on how to enable the 1980s-style -request / -subscribe etc aliases. However this documentation should have a note that this is against the AUP of nearly every network provider, and enabling it will likely cause them to get listed in various blacklists as a backscatter source. FYI: I know that this goes against the instincts of many old-time mailing list advocates here. But after dealing with a 10k/hour backscatter DoS my tolerance for this problem is understandably limited. Yes, it was a sweet day back in the 1980s. I was running a mailing list server and several UUCP gateways at the time, so I remember them well. But those days are past, and we need to deal with the reality of today. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness

21 168

Re: [Mailman-Developers] Grackle archive framework
by Barry Warsaw March 17, 2012

March 17, 2012

On Feb 16, 2012, at 11:40 PM, Aamir Khan wrote: >I talked to people on #launchpad-dev, as suggested by barry to investigate >about the possibility of using grackle as new archive framework for >mailman. The project isn't functional yet. There are two parts, client and >back-end service to store the messages. Client will hopefully be completed >by end of next week. > >For backend-service implementation, i am also thinking to get involved >during its development. They are planning to have cassandra based store for >storing the messages. Any thoughts about which backend service would be >ideal to store messages for mailman installations ? On IRC, we talked about a storm + Python mailbox library based backend, with a REST+JSON wsgi based application vending the data. This would allow us to integrate fairly easily with MM3 I think, and would possibly better enable some of the archiver work being done by Terri and others. -Barry

2 1

Re: [Mailman-Developers] Browser ID integration with Mailman
by Barry Warsaw Feb. 27, 2012

Feb. 27, 2012

On Feb 16, 2012, at 10:23 PM, Aamir Khan wrote: >I was going through ideas page of mailman for GSoC 2012, and i found this >project of integrating the browser id with mailman. I guess, mailman >community members should already have some discussion about this >integration. Can you tell me some specifics, so i can do my homework as how >would i go about implementing it. Hi Aamir, I don't think much has been discussed about it, but maybe Florian has thought more about how to integrate it with the mm3 ui. -Barry

4 19

mailman web ui
by Jagannathan Tiruvallur Eachambadi Feb. 22, 2012

Feb. 22, 2012

Hi Florian, Installing postfix fixed the issue. Thanks a lot. By the way I am using Archlinux. Cheers, Jagan On Tue, Feb 21, 2012 at 4:27 AM, <mailman-developers-request(a)python.org>wrote: > Send Mailman-Developers mailing list submissions to > mailman-developers(a)python.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.python.org/mailman/listinfo/mailman-developers > or, via email, send a message with subject or body 'help' to > mailman-developers-request(a)python.org > > You can reach the person managing the list at > mailman-developers-owner(a)python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Mailman-Developers digest..." > > > Today's Topics: > > 1. Re: Probe messages should not sent Precedence header (Aamir Khan) > 2. Re: Mailman-Developers Digest, Vol 274, Issue 12 (Florian Fuchs) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 21 Feb 2012 00:24:48 +0530 > From: Aamir Khan <syst3m.w0rm(a)gmail.com> > To: Barry Warsaw <barry(a)list.org> > Cc: mailman-developers(a)python.org > Subject: Re: [Mailman-Developers] Probe messages should not sent > Precedence header > Message-ID: > <CAOb12VUryhuNYap1bCbu9y=D1kLxA_gKtLgPS4W1i70z_uvqCQ(a)mail.gmail.com > > > Content-Type: text/plain; charset=ISO-8859-1 > > On Tue, Feb 21, 2012 at 12:19 AM, Barry Warsaw <barry(a)list.org> wrote: > > > On Feb 18, 2012, at 06:38 AM, Aamir Khan wrote: > > > > >As suggested by Barry, I am working on this new bug, > > >808821<https://bugs.launchpad.net/mailman/+bug/808821>. As i browsed > > though > > >the code of mailman, i found that 'src/mailman/bin/disabled.py' is the > > script > > >which runs to send the messages to all the email addresses disabled may > be > > >because of over bouncing, by user himself, by admin, etc.. So, i just > > have > > >to find out the way, so that bouncing mail won't set the precedence > > header. > > > > This script is currently broken, but I will fix it for beta 1. I'll > leave > > the > > Precedence bug open for you to take a shot if you like. > > > > https://bugs.launchpad.net/mailman/+bug/937154 > > > sure, i will look into after you fix the bug of bin/disabled.py. > > > > > > > > > Cheers, > > -Barry > > _______________________________________________ > > Mailman-Developers mailing list > > Mailman-Developers(a)python.org > > http://mail.python.org/mailman/listinfo/mailman-developers > > Mailman FAQ: http://wiki.list.org/x/AgA3 > > Searchable Archives: > > http://www.mail-archive.com/mailman-developers%40python.org/ > > Unsubscribe: > > > http://mail.python.org/mailman/options/mailman-developers/syst3m.w0rm%40gma… > > > > Security Policy: http://wiki.list.org/x/QIA9 > > > > > > -- > Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee > > > ------------------------------ > > Message: 2 > Date: Mon, 20 Feb 2012 23:57:20 +0100 > From: "Florian Fuchs" <f(a)state-of-mind.de> > To: "Jagannathan Tiruvallur Eachambadi" <jagannathante(a)gmail.com> > Cc: mailman-developers(a)python.org > Subject: Re: [Mailman-Developers] Mailman-Developers Digest, Vol 274, > Issue 12 > Message-ID: <313a-4f42d000-1-5047fc00@93635954> > Content-Type: text/plain; charset="utf-8" > > Hi, Jagannathan, > > I noticed two things in the traceback: > > 1) mailman_django seems to be imported twice (line 4) > This is probably because you copied it inside django_dev_setup. If you > installed it correctly (python setup.py develop) it *should* really run > without putting it next to settings.py. (Having django apps living inside > the project folder is possible but somewhat discouraged with reusable apps, > because this approach doesn't really separate the app from its local > settings.) > > 2) /usr/sbin/postmap: No such file or directory (line 20) > I think this might be the actual root of the problem: Mailman cannot find > an MTA (it is looking for postfix in this case). > Depending on the system you are using, it should be pretty easy to install > postfix (`sudo apt-get install postfix` if you're running ubuntu). You > might not be able to send or receive emails just by installing it, but it > should be enough to run the web ui locally and perform all the tasks that > are currently available. > > Please tell me if this is of any help... > > Cheers > Florian > > > > On Monday, February 20, 2012 19:52 CET, Jagannathan Tiruvallur Eachambadi < > jagannathante(a)gmail.com> wrote: > > > I copied the folder mailmanweb/src/mailman-django to django_dev_setup/ > and > > the server works. But it does not go through all tests. This is snippet > of > > the errors in the test. http://pastebin.com/1CrKWpkp . > > > > On Mon, Feb 20, 2012 at 10:14 PM, <mailman-developers-request(a)python.org > >wrote: > > > > > Send Mailman-Developers mailing list submissions to > > > mailman-developers(a)python.org > > > > > > To subscribe or unsubscribe via the World Wide Web, visit > > > http://mail.python.org/mailman/listinfo/mailman-developers > > > or, via email, send a message with subject or body 'help' to > > > mailman-developers-request(a)python.org > > > > > > You can reach the person managing the list at > > > mailman-developers-owner(a)python.org > > > > > > When replying, please edit your Subject line so it is more specific > > > than "Re: Contents of Mailman-Developers digest..." > > > > > > > > > Today's Topics: > > > > > > 1. GSOC 12 (Jagannathan Tiruvallur Eachambadi) > > > 2. Re: GSOC 12 (Jagannathan Tiruvallur Eachambadi) > > > 3. Re: GSOC 12 (Florian Fuchs) > > > > > > > > > ---------------------------------------------------------------------- > > > > > > Message: 1 > > > Date: Mon, 20 Feb 2012 16:10:52 +0530 > > > From: Jagannathan Tiruvallur Eachambadi <jagannathante(a)gmail.com> > > > To: mailman-developers(a)python.org > > > Subject: [Mailman-Developers] GSOC 12 > > > Message-ID: > > > < > CABzJUX6EYs2RX7w60nHKgpRpJ33XMA3A6dLMkSjHvVr33mZvYg(a)mail.gmail.com > > > > > > > Content-Type: text/plain; charset=ISO-8859-1 > > > > > > hi all, > > > > > > I am currently doing my first year of under-graduation in > NIT-Trichy. > > > I was reading the GSOC 12 getting started page and I am unable to to > get > > > the Django server working. I get ERNO 111 , I tried shutting down > apache in > > > my computer. But that did not solve the problem. I get the following > error, > > > http://dpaste.com/705607/ . > > > > > > On Sun, Feb 19, 2012 at 4:30 PM, < > mailman-developers-request(a)python.org > > > >wrote: > > > > > > > Send Mailman-Developers mailing list submissions to > > > > mailman-developers(a)python.org > > > > > > > > To subscribe or unsubscribe via the World Wide Web, visit > > > > http://mail.python.org/mailman/listinfo/mailman-developers > > > > or, via email, send a message with subject or body 'help' to > > > > mailman-developers-request(a)python.org > > > > > > > > You can reach the person managing the list at > > > > mailman-developers-owner(a)python.org > > > > > > > > When replying, please edit your Subject line so it is more specific > > > > than "Re: Contents of Mailman-Developers digest..." > > > > > > > > > > > > Today's Topics: > > > > > > > > 1. Re: Probe messages should not sent Precedenceheader (Mark > > > > Sapiro) > > > > 2. Re: Probe messages should not sent Precedenceheader > (Aamir > > > > Khan) > > > > 3. Re: Probe messages should not sent Precedenceheader (Mark > > > > Sapiro) > > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > > > > Message: 1 > > > > Date: Sat, 18 Feb 2012 09:22:53 -0800 > > > > From: Mark Sapiro <mark(a)msapiro.net> > > > > To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > > Cc: Mailman-Developers(a)python.org > > > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > > > Precedenceheader > > > > Message-ID: <PC195201202180922530437aace67aa@MSAPIRO> > > > > Content-Type: text/plain; charset=iso-8859-1 > > > > > > > > Aamir Khan wrote: > > > > > > > > >I guess in MM3, there is no function as sendNextNotification(), > because > > > i > > > > >used command, "grep sendNextNotification() -r *" and the result was > only > > > > >file 'src/mailman/bin/disabled.py'. > > > > > > > > > > > > Which means that bin/disabled.py won't work because it hasn't been > > > > fully converted from 2.1 yet. It should be using the send_probe() > > > > function instead of sendNextNotification(). > > > > > > > > > > > > >There is a file 'src/mailman/email/messages.py', in which > > > > >UserNotification() class is defined. It has a send function, which > sets > > > > the > > > > >precedence header. > > > > > > > > > >In file 'src/mailman/app/bouces.py', I guess the probe messages are > sent > > > > >directly using send() function of UserNotification() class. I think > that > > > > >from line 211 to 228, probe message is used to send VERP probe. But > > > then, > > > > i > > > > >am not able to find out the place from where probe message is sent > after > > > > >disabling of the address because of over bouncing. > > > > > > > > > > > > There should be two places. bin/disabled.py should be calling > > > > send_probe() instead of the non-existent sendNextNotification() list > > > > method. > > > > > > > > Also, send_probe() should be called when delivery is initially > disabled > > > > as a result of a call to IBounceProcessor(), but I am unable to > follow > > > > how this works or even if it is implemented yet at least in part > > > > because I haven't yet learned anything about how things like > > > > zope.component.getUtility() work. > > > > > > > > > > > > >I have tried to make some changes to code and pushed it to my local > > > branch > > > > >[1]. Ran through all the tests, and none of them failed. Is there > any > > > way > > > > >to run through a subset of test rather than running them using > > > 'bin/test' > > > > >command. > > > > > > > > > >Comments, feedback required on patch. > > > > > > > > > > > > > > >[1] => > > > > > > > > > http://bazaar.launchpad.net/~syst3mw0rm/mailman/precedence/revision/7080 > > > > > > > > > > > > The patch itself looks good except for style. We normally don't put > > > > whitespace around the = in keyword=value arguments in definitions and > > > > calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > > > > use spaces around the '=' sign when used to indicate a keyword > > > > argument or a default parameter value." > > > > > > > > -- > > > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > > > San Francisco Bay Area, California better use your sense - B. > Dylan > > > > > > > > > > > > > > > > ------------------------------ > > > > > > > > Message: 2 > > > > Date: Sat, 18 Feb 2012 23:16:37 +0530 > > > > From: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > > To: Mark Sapiro <mark(a)msapiro.net> > > > > Cc: Mailman-Developers(a)python.org > > > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > > > Precedenceheader > > > > Message-ID: > > > > < > > > CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg(a)mail.gmail.com > > > > > > > > > Content-Type: text/plain; charset=ISO-8859-1 > > > > > > > > Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > > > > > > > > > > Which means that bin/disabled.py won't work because it hasn't been > > > > > fully converted from 2.1 yet. It should be using the send_probe() > > > > > function instead of sendNextNotification(). > > > > > > > > > > > > > Yes. I also think so. I have changed the function to send_probe() > and ran > > > > through all the test again to make sure that nothing breaks. > > > > > > > > > > > > > > > > > > There should be two places. bin/disabled.py should be calling > > > > > send_probe() instead of the non-existent sendNextNotification() > list > > > > > method. > > > > > > > > > > Also, send_probe() should be called when delivery is initially > disabled > > > > > as a result of a call to IBounceProcessor(), but I am unable to > follow > > > > > how this works or even if it is implemented yet at least in part > > > > > because I haven't yet learned anything about how things like > > > > > zope.component.getUtility() work. > > > > > > > > > > > > > I am also not able to find out the relevant code, as i am completely > new > > > to > > > > the flow of how mailman works. Maybe, barry can help me on this one. > > > > > > > > > > > > > > > > > > > The patch itself looks good except for style. We normally don't put > > > > > whitespace around the = in keyword=value arguments in definitions > and > > > > > calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says > "Don't > > > > > use spaces around the '=' sign when used to indicate a keyword > > > > > argument or a default parameter value." > > > > > > > > > > I will keep this in mind. I have created another branch with > partial > > > > changes suggested above. Here, you can find the changes, > > > > > > > > http://bazaar.launchpad.net/~syst3mw0rm/mailman/808821/revision/7080 > > > > > > > > > > > > > > > > -- > > > > Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee > > > > > > > > > > > > ------------------------------ > > > > > > > > Message: 3 > > > > Date: Sat, 18 Feb 2012 10:45:28 -0800 > > > > From: Mark Sapiro <mark(a)msapiro.net> > > > > To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > > Cc: Mailman-Developers(a)python.org > > > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > > > Precedenceheader > > > > Message-ID: <PC195201202181045280109fb8c76c9@MSAPIRO> > > > > Content-Type: text/plain; charset=iso-8859-1 > > > > > > > > Aamir Khan wrote: > > > > > > > > > >Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > > > > > >> > > > > >> Which means that bin/disabled.py won't work because it hasn't been > > > > >> fully converted from 2.1 yet. It should be using the send_probe() > > > > >> function instead of sendNextNotification(). > > > > >> > > > > > > > > > >Yes. I also think so. I have changed the function to send_probe() > and > > > ran > > > > >through all the test again to make sure that nothing breaks. > > > > > > > > > > > > I don't think you can simply change > mlist.sendNextNotification(member) > > > > to mlist.send_probe(member) because send_probe() is not a list > method, > > > > plus it requires a message argument in addition to the member > argument. > > > > > > > > Also, it is apparent that the test suite is not testing > bin/disabled.py > > > > or it would have been failing all along. > > > > > > > > -- > > > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > > > San Francisco Bay Area, California better use your sense - B. > Dylan > > > > > > > > > > > > > > > > ------------------------------ > > > > > > > > _______________________________________________ > > > > Mailman-Developers mailing list > > > > Mailman-Developers(a)python.org > > > > http://mail.python.org/mailman/listinfo/mailman-developers > > > > > > > > > > > > End of Mailman-Developers Digest, Vol 274, Issue 10 > > > > *************************************************** > > > > > > > > > > > > > ------------------------------ > > > > > > Message: 2 > > > Date: Mon, 20 Feb 2012 16:20:11 +0530 > > > From: Jagannathan Tiruvallur Eachambadi <jagannathante(a)gmail.com> > > > To: mailman-developers(a)python.org > > > Subject: Re: [Mailman-Developers] GSOC 12 > > > Message-ID: > > > < > CABzJUX4yLEAfnPg_EzCc9dQuNbYUDSLPwbG1ZT4vim1cTj3T6w(a)mail.gmail.com > > > > > > > Content-Type: text/plain; charset=ISO-8859-1 > > > > > > Sorry, the error is TemplateDoesNotExist. I forgot to start the mailman > > > runner. This is the error I am getting : http://dpaste.com/705614/ > > > > > > On Mon, Feb 20, 2012 at 4:10 PM, Jagannathan Tiruvallur Eachambadi < > > > jagannathante(a)gmail.com> wrote: > > > > > > > > > > > hi all, > > > > > > > > I am currently doing my first year of under-graduation in > > > NIT-Trichy. > > > > I was reading the GSOC 12 getting started page and I am unable to to > get > > > > the Django server working. I get ERNO 111 , I tried shutting down > apache > > > in > > > > my computer. But that did not solve the problem. I get the following > > > error, > > > > http://dpaste.com/705607/ . > > > > > > > > On Sun, Feb 19, 2012 at 4:30 PM, < > mailman-developers-request(a)python.org > > > >wrote: > > > > > > > >> Send Mailman-Developers mailing list submissions to > > > >> mailman-developers(a)python.org > > > >> > > > >> To subscribe or unsubscribe via the World Wide Web, visit > > > >> http://mail.python.org/mailman/listinfo/mailman-developers > > > >> or, via email, send a message with subject or body 'help' to > > > >> mailman-developers-request(a)python.org > > > >> > > > >> You can reach the person managing the list at > > > >> mailman-developers-owner(a)python.org > > > >> > > > >> When replying, please edit your Subject line so it is more specific > > > >> than "Re: Contents of Mailman-Developers digest..." > > > >> > > > >> > > > >> Today's Topics: > > > >> > > > >> 1. Re: Probe messages should not sent Precedenceheader > (Mark > > > >> Sapiro) > > > >> 2. Re: Probe messages should not sent Precedenceheader > (Aamir > > > >> Khan) > > > >> 3. Re: Probe messages should not sent Precedenceheader > (Mark > > > >> Sapiro) > > > >> > > > >> > > > >> > ---------------------------------------------------------------------- > > > >> > > > >> Message: 1 > > > >> Date: Sat, 18 Feb 2012 09:22:53 -0800 > > > >> From: Mark Sapiro <mark(a)msapiro.net> > > > >> To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > >> Cc: Mailman-Developers(a)python.org > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > >> Precedenceheader > > > >> Message-ID: <PC195201202180922530437aace67aa@MSAPIRO> > > > >> Content-Type: text/plain; charset=iso-8859-1 > > > >> > > > >> Aamir Khan wrote: > > > >> > > > >> >I guess in MM3, there is no function as sendNextNotification(), > > > because i > > > >> >used command, "grep sendNextNotification() -r *" and the result was > > > only > > > >> >file 'src/mailman/bin/disabled.py'. > > > >> > > > >> > > > >> Which means that bin/disabled.py won't work because it hasn't been > > > >> fully converted from 2.1 yet. It should be using the send_probe() > > > >> function instead of sendNextNotification(). > > > >> > > > >> > > > >> >There is a file 'src/mailman/email/messages.py', in which > > > >> >UserNotification() class is defined. It has a send function, which > sets > > > >> the > > > >> >precedence header. > > > >> > > > > >> >In file 'src/mailman/app/bouces.py', I guess the probe messages are > > > sent > > > >> >directly using send() function of UserNotification() class. I think > > > that > > > >> >from line 211 to 228, probe message is used to send VERP probe. But > > > >> then, i > > > >> >am not able to find out the place from where probe message is sent > > > after > > > >> >disabling of the address because of over bouncing. > > > >> > > > >> > > > >> There should be two places. bin/disabled.py should be calling > > > >> send_probe() instead of the non-existent sendNextNotification() list > > > >> method. > > > >> > > > >> Also, send_probe() should be called when delivery is initially > disabled > > > >> as a result of a call to IBounceProcessor(), but I am unable to > follow > > > >> how this works or even if it is implemented yet at least in part > > > >> because I haven't yet learned anything about how things like > > > >> zope.component.getUtility() work. > > > >> > > > >> > > > >> >I have tried to make some changes to code and pushed it to my local > > > >> branch > > > >> >[1]. Ran through all the tests, and none of them failed. Is there > any > > > way > > > >> >to run through a subset of test rather than running them using > > > 'bin/test' > > > >> >command. > > > >> > > > > >> >Comments, feedback required on patch. > > > >> > > > > >> > > > > >> >[1] => > > > >> > > > > > http://bazaar.launchpad.net/~syst3mw0rm/mailman/precedence/revision/7080 > > > >> > > > >> > > > >> The patch itself looks good except for style. We normally don't put > > > >> whitespace around the = in keyword=value arguments in definitions > and > > > >> calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > > > >> use spaces around the '=' sign when used to indicate a keyword > > > >> argument or a default parameter value." > > > >> > > > >> -- > > > >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > > >> San Francisco Bay Area, California better use your sense - B. > Dylan > > > >> > > > >> > > > >> > > > >> ------------------------------ > > > >> > > > >> Message: 2 > > > >> Date: Sat, 18 Feb 2012 23:16:37 +0530 > > > >> From: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > >> To: Mark Sapiro <mark(a)msapiro.net> > > > >> Cc: Mailman-Developers(a)python.org > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > >> Precedenceheader > > > >> Message-ID: > > > >> < > > > >> CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg(a)mail.gmail.com> > > > >> Content-Type: text/plain; charset=ISO-8859-1 > > > >> > > > >> Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> > > > >> > > > > >> > Which means that bin/disabled.py won't work because it hasn't been > > > >> > fully converted from 2.1 yet. It should be using the send_probe() > > > >> > function instead of sendNextNotification(). > > > >> > > > > >> > > > >> Yes. I also think so. I have changed the function to send_probe() > and > > > ran > > > >> through all the test again to make sure that nothing breaks. > > > >> > > > >> > > > >> > > > > >> > There should be two places. bin/disabled.py should be calling > > > >> > send_probe() instead of the non-existent sendNextNotification() > list > > > >> > method. > > > >> > > > > >> > Also, send_probe() should be called when delivery is initially > > > disabled > > > >> > as a result of a call to IBounceProcessor(), but I am unable to > follow > > > >> > how this works or even if it is implemented yet at least in part > > > >> > because I haven't yet learned anything about how things like > > > >> > zope.component.getUtility() work. > > > >> > > > > >> > > > >> I am also not able to find out the relevant code, as i am > completely new > > > >> to > > > >> the flow of how mailman works. Maybe, barry can help me on this one. > > > >> > > > >> > > > > >> > > > > >> > The patch itself looks good except for style. We normally don't > put > > > >> > whitespace around the = in keyword=value arguments in definitions > and > > > >> > calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says > "Don't > > > >> > use spaces around the '=' sign when used to indicate a keyword > > > >> > argument or a default parameter value." > > > >> > > > > >> > I will keep this in mind. I have created another branch with > partial > > > >> changes suggested above. Here, you can find the changes, > > > >> > > > >> > http://bazaar.launchpad.net/~syst3mw0rm/mailman/808821/revision/7080 > > > >> > > > >> > > > >> > > > >> -- > > > >> Aamir Khan | 3rd Year | Computer Science & Engineering | IIT > Roorkee > > > >> > > > >> > > > >> ------------------------------ > > > >> > > > >> Message: 3 > > > >> Date: Sat, 18 Feb 2012 10:45:28 -0800 > > > >> From: Mark Sapiro <mark(a)msapiro.net> > > > >> To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > >> Cc: Mailman-Developers(a)python.org > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > >> Precedenceheader > > > >> Message-ID: <PC195201202181045280109fb8c76c9@MSAPIRO> > > > >> Content-Type: text/plain; charset=iso-8859-1 > > > >> > > > >> Aamir Khan wrote: > > > >> > > > > >> >Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> > > > > >> >> > > > >> >> Which means that bin/disabled.py won't work because it hasn't > been > > > >> >> fully converted from 2.1 yet. It should be using the send_probe() > > > >> >> function instead of sendNextNotification(). > > > >> >> > > > >> > > > > >> >Yes. I also think so. I have changed the function to send_probe() > and > > > ran > > > >> >through all the test again to make sure that nothing breaks. > > > >> > > > >> > > > >> I don't think you can simply change > mlist.sendNextNotification(member) > > > >> to mlist.send_probe(member) because send_probe() is not a list > method, > > > >> plus it requires a message argument in addition to the member > argument. > > > >> > > > >> Also, it is apparent that the test suite is not testing > bin/disabled.py > > > >> or it would have been failing all along. > > > >> > > > >> -- > > > >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > > >> San Francisco Bay Area, California better use your sense - B. > Dylan > > > >> > > > >> > > > >> > > > >> ------------------------------ > > > >> > > > >> _______________________________________________ > > > >> Mailman-Developers mailing list > > > >> Mailman-Developers(a)python.org > > > >> http://mail.python.org/mailman/listinfo/mailman-developers > > > >> > > > >> > > > >> End of Mailman-Developers Digest, Vol 274, Issue 10 > > > >> *************************************************** > > > >> > > > > > > > > > > > > > > > > > ------------------------------ > > > > > > Message: 3 > > > Date: Mon, 20 Feb 2012 17:43:47 +0100 > > > From: "Florian Fuchs" <f(a)state-of-mind.de> > > > To: "Jagannathan Tiruvallur Eachambadi" <jagannathante(a)gmail.com> > > > Cc: mailman-developers(a)python.org > > > Subject: Re: [Mailman-Developers] GSOC 12 > > > Message-ID: <1f3e-4f427880-7-13fbcde0@263897354> > > > Content-Type: text/plain; charset="utf-8" > > > > > > Hi Jagannathan, > > > > > > if the Error is TemplateDoesNotExist, the first thing to check would > be: > > > Does the relevant file exist and does the user starting the server > have the > > > necessary rights to access it? > > > > > > In your case that would be the following file: > > > > > > > > > > <folder-where-mailmanweb-lives>/mailmanweb/src/mailman_django/templates/mailman-django/lists/index.html > > > > > > Any luck? > > > > > > Florian > > > > > > > > > > > > On Monday, February 20, 2012 11:50 CET, Jagannathan Tiruvallur > Eachambadi < > > > jagannathante(a)gmail.com> wrote: > > > > > > > Sorry, the error is TemplateDoesNotExist. I forgot to start the > mailman > > > > runner. This is the error I am getting : http://dpaste.com/705614/ > > > > > > > > On Mon, Feb 20, 2012 at 4:10 PM, Jagannathan Tiruvallur Eachambadi < > > > > jagannathante(a)gmail.com> wrote: > > > > > > > > > > > > > > hi all, > > > > > > > > > > I am currently doing my first year of under-graduation in > > > NIT-Trichy. > > > > > I was reading the GSOC 12 getting started page and I am unable to > to > > > get > > > > > the Django server working. I get ERNO 111 , I tried shutting down > > > apache in > > > > > my computer. But that did not solve the problem. I get the > following > > > error, > > > > > http://dpaste.com/705607/ . > > > > > > > > > > On Sun, Feb 19, 2012 at 4:30 PM, < > > > mailman-developers-request(a)python.org>wrote: > > > > > > > > > >> Send Mailman-Developers mailing list submissions to > > > > >> mailman-developers(a)python.org > > > > >> > > > > >> To subscribe or unsubscribe via the World Wide Web, visit > > > > >> http://mail.python.org/mailman/listinfo/mailman-developers > > > > >> or, via email, send a message with subject or body 'help' to > > > > >> mailman-developers-request(a)python.org > > > > >> > > > > >> You can reach the person managing the list at > > > > >> mailman-developers-owner(a)python.org > > > > >> > > > > >> When replying, please edit your Subject line so it is more > specific > > > > >> than "Re: Contents of Mailman-Developers digest..." > > > > >> > > > > >> > > > > >> Today's Topics: > > > > >> > > > > >> 1. Re: Probe messages should not sent Precedenceheader > (Mark > > > > >> Sapiro) > > > > >> 2. Re: Probe messages should not sent Precedenceheader > (Aamir > > > > >> Khan) > > > > >> 3. Re: Probe messages should not sent Precedenceheader > (Mark > > > > >> Sapiro) > > > > >> > > > > >> > > > > >> > ---------------------------------------------------------------------- > > > > >> > > > > >> Message: 1 > > > > >> Date: Sat, 18 Feb 2012 09:22:53 -0800 > > > > >> From: Mark Sapiro <mark(a)msapiro.net> > > > > >> To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > > >> Cc: Mailman-Developers(a)python.org > > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > > >> Precedenceheader > > > > >> Message-ID: <PC195201202180922530437aace67aa@MSAPIRO> > > > > >> Content-Type: text/plain; charset=iso-8859-1 > > > > >> > > > > >> Aamir Khan wrote: > > > > >> > > > > >> >I guess in MM3, there is no function as sendNextNotification(), > > > because i > > > > >> >used command, "grep sendNextNotification() -r *" and the result > was > > > only > > > > >> >file 'src/mailman/bin/disabled.py'. > > > > >> > > > > >> > > > > >> Which means that bin/disabled.py won't work because it hasn't been > > > > >> fully converted from 2.1 yet. It should be using the send_probe() > > > > >> function instead of sendNextNotification(). > > > > >> > > > > >> > > > > >> >There is a file 'src/mailman/email/messages.py', in which > > > > >> >UserNotification() class is defined. It has a send function, > which > > > sets > > > > >> the > > > > >> >precedence header. > > > > >> > > > > > >> >In file 'src/mailman/app/bouces.py', I guess the probe messages > are > > > sent > > > > >> >directly using send() function of UserNotification() class. I > think > > > that > > > > >> >from line 211 to 228, probe message is used to send VERP probe. > But > > > > >> then, i > > > > >> >am not able to find out the place from where probe message is > sent > > > after > > > > >> >disabling of the address because of over bouncing. > > > > >> > > > > >> > > > > >> There should be two places. bin/disabled.py should be calling > > > > >> send_probe() instead of the non-existent sendNextNotification() > list > > > > >> method. > > > > >> > > > > >> Also, send_probe() should be called when delivery is initially > > > disabled > > > > >> as a result of a call to IBounceProcessor(), but I am unable to > follow > > > > >> how this works or even if it is implemented yet at least in part > > > > >> because I haven't yet learned anything about how things like > > > > >> zope.component.getUtility() work. > > > > >> > > > > >> > > > > >> >I have tried to make some changes to code and pushed it to my > local > > > > >> branch > > > > >> >[1]. Ran through all the tests, and none of them failed. Is there > > > any way > > > > >> >to run through a subset of test rather than running them using > > > 'bin/test' > > > > >> >command. > > > > >> > > > > > >> >Comments, feedback required on patch. > > > > >> > > > > > >> > > > > > >> >[1] => > > > > >> > > > > > http://bazaar.launchpad.net/~syst3mw0rm/mailman/precedence/revision/7080 > > > > >> > > > > >> > > > > >> The patch itself looks good except for style. We normally don't > put > > > > >> whitespace around the = in keyword=value arguments in definitions > and > > > > >> calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says > "Don't > > > > >> use spaces around the '=' sign when used to indicate a keyword > > > > >> argument or a default parameter value." > > > > >> > > > > >> -- > > > > >> Mark Sapiro <mark(a)msapiro.net> The highway is for > gamblers, > > > > >> San Francisco Bay Area, California better use your sense - B. > Dylan > > > > >> > > > > >> > > > > >> > > > > >> ------------------------------ > > > > >> > > > > >> Message: 2 > > > > >> Date: Sat, 18 Feb 2012 23:16:37 +0530 > > > > >> From: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > > >> To: Mark Sapiro <mark(a)msapiro.net> > > > > >> Cc: Mailman-Developers(a)python.org > > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > > >> Precedenceheader > > > > >> Message-ID: > > > > >> < > > > > >> > CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg(a)mail.gmail.com> > > > > >> Content-Type: text/plain; charset=ISO-8859-1 > > > > >> > > > > >> Mark Sapiro <mark(a)msapiro.net> wrote: > > > > >> > > > > >> > > > > > >> > Which means that bin/disabled.py won't work because it hasn't > been > > > > >> > fully converted from 2.1 yet. It should be using the > send_probe() > > > > >> > function instead of sendNextNotification(). > > > > >> > > > > > >> > > > > >> Yes. I also think so. I have changed the function to send_probe() > and > > > ran > > > > >> through all the test again to make sure that nothing breaks. > > > > >> > > > > >> > > > > >> > > > > > >> > There should be two places. bin/disabled.py should be calling > > > > >> > send_probe() instead of the non-existent sendNextNotification() > list > > > > >> > method. > > > > >> > > > > > >> > Also, send_probe() should be called when delivery is initially > > > disabled > > > > >> > as a result of a call to IBounceProcessor(), but I am unable to > > > follow > > > > >> > how this works or even if it is implemented yet at least in part > > > > >> > because I haven't yet learned anything about how things like > > > > >> > zope.component.getUtility() work. > > > > >> > > > > > >> > > > > >> I am also not able to find out the relevant code, as i am > completely > > > new > > > > >> to > > > > >> the flow of how mailman works. Maybe, barry can help me on this > one. > > > > >> > > > > >> > > > > > >> > > > > > >> > The patch itself looks good except for style. We normally don't > put > > > > >> > whitespace around the = in keyword=value arguments in > definitions > > > and > > > > >> > calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says > "Don't > > > > >> > use spaces around the '=' sign when used to indicate a keyword > > > > >> > argument or a default parameter value." > > > > >> > > > > > >> > I will keep this in mind. I have created another branch with > partial > > > > >> changes suggested above. Here, you can find the changes, > > > > >> > > > > >> > http://bazaar.launchpad.net/~syst3mw0rm/mailman/808821/revision/7080 > > > > >> > > > > >> > > > > >> > > > > >> -- > > > > >> Aamir Khan | 3rd Year | Computer Science & Engineering | IIT > Roorkee > > > > >> > > > > >> > > > > >> ------------------------------ > > > > >> > > > > >> Message: 3 > > > > >> Date: Sat, 18 Feb 2012 10:45:28 -0800 > > > > >> From: Mark Sapiro <mark(a)msapiro.net> > > > > >> To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > > >> Cc: Mailman-Developers(a)python.org > > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > > >> Precedenceheader > > > > >> Message-ID: <PC195201202181045280109fb8c76c9@MSAPIRO> > > > > >> Content-Type: text/plain; charset=iso-8859-1 > > > > >> > > > > >> Aamir Khan wrote: > > > > >> > > > > > >> >Mark Sapiro <mark(a)msapiro.net> wrote: > > > > >> > > > > > >> >> > > > > >> >> Which means that bin/disabled.py won't work because it hasn't > been > > > > >> >> fully converted from 2.1 yet. It should be using the > send_probe() > > > > >> >> function instead of sendNextNotification(). > > > > >> >> > > > > >> > > > > > >> >Yes. I also think so. I have changed the function to send_probe() > > > and ran > > > > >> >through all the test again to make sure that nothing breaks. > > > > >> > > > > >> > > > > >> I don't think you can simply change > mlist.sendNextNotification(member) > > > > >> to mlist.send_probe(member) because send_probe() is not a list > method, > > > > >> plus it requires a message argument in addition to the member > > > argument. > > > > >> > > > > >> Also, it is apparent that the test suite is not testing > > > bin/disabled.py > > > > >> or it would have been failing all along. > > > > >> > > > > >> -- > > > > >> Mark Sapiro <mark(a)msapiro.net> The highway is for > gamblers, > > > > >> San Francisco Bay Area, California better use your sense - B. > Dylan > > > > >> > > > > >> > > > > >> > > > > >> ------------------------------ > > > > >> > > > > >> _______________________________________________ > > > > >> Mailman-Developers mailing list > > > > >> Mailman-Developers(a)python.org > > > > >> http://mail.python.org/mailman/listinfo/mailman-developers > > > > >> > > > > >> > > > > >> End of Mailman-Developers Digest, Vol 274, Issue 10 > > > > >> *************************************************** > > > > >> > > > > > > > > > > > > > > _______________________________________________ > > > > Mailman-Developers mailing list > > > > Mailman-Developers(a)python.org > > > > http://mail.python.org/mailman/listinfo/mailman-developers > > > > Mailman FAQ: http://wiki.list.org/x/AgA3 > > > > Searchable Archives: > > > http://www.mail-archive.com/mailman-developers%40python.org/ > > > > Unsubscribe: > > > > http://mail.python.org/mailman/options/mailman-developers/f%40state-of-mind… > > > > > > > > Security Policy: http://wiki.list.org/x/QIA9 > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------ > > > > > > _______________________________________________ > > > Mailman-Developers mailing list > > > Mailman-Developers(a)python.org > > > http://mail.python.org/mailman/listinfo/mailman-developers > > > > > > > > > End of Mailman-Developers Digest, Vol 274, Issue 12 > > > *************************************************** > > > > > _______________________________________________ > > Mailman-Developers mailing list > > Mailman-Developers(a)python.org > > http://mail.python.org/mailman/listinfo/mailman-developers > > Mailman FAQ: http://wiki.list.org/x/AgA3 > > Searchable Archives: > http://www.mail-archive.com/mailman-developers%40python.org/ > > Unsubscribe: > http://mail.python.org/mailman/options/mailman-developers/f%40state-of-mind… > > > > Security Policy: http://wiki.list.org/x/QIA9 > > > > > > > > ------------------------------ > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > http://mail.python.org/mailman/listinfo/mailman-developers > > > End of Mailman-Developers Digest, Vol 274, Issue 14 > *************************************************** >

1 0

OT: Need Python guru
by Bob Puff＠NLE Feb. 21, 2012

Feb. 21, 2012

HI guys, Pardon the OT request, but I have a Python app that is generating an occasional error, and I need someone fluent in Python to help me fix it. Its probably some simple error trapping that is needed. My Python skills are limited to some MM 2.x hacking, and that's about it! Please contact me off-list if you might be able to spare 10 minutes to "help a brotha out" :) Bob

1 0

owner suffix ignored when in Cc ?
by Mathieu Bouchard Feb. 21, 2012

Feb. 21, 2012

I'm using MailMan 2.1.11 and I noticed that when I send to foo-owner(a)example.com, MailMan takes it as if I had sent to foo(a)example.com instead, if the address is in Cc, whereas it works correctly when the address is in To. Is this a bug in MailMan, or is it a bug in MailMan's default config, or would it be a bug in another config (PostFix routing tables or ProcMail rules) ? ______________________________________________________________________ | Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC

2 1

Re: [Mailman-Developers] Add the equivalent of postconf
by Barry Warsaw Feb. 21, 2012

Feb. 21, 2012

On Feb 17, 2012, at 11:09 PM, Aamir Khan wrote: >Referring to this bug, https://bugs.launchpad.net/mailman/+bug/518517 > >I am planning to implement the command 'mailconf' analogous to 'postconf'. >As mentioned in bug description, the idea is to dump all or one variable of >the mailman configuration variables. > >How can i find the configuration variables of mailman to be dumped using >this command ? My thought is that this command would dump configuration sections and values from the mailman.config.config object. These are built via the lazr.config library and are driven by src/mailman/config/schema.cfg and src/mailman/config/mailman.cfg in the source tree, and overridden by any values the admin has added via /etc/mailman.cfg (and others, see START.rst for details). Specifically, this would *not* dump values from the database. To start with, `bin/mailman mailconf` seems like a reasonable choice. A thought on syntax. Parameters would have a syntax like section:key e.g. paths:var_dir Maybe both the section and variable name would be optional. In the former case, mailconf could print all the key/values in the section. In the latter, it could print all keys that match the variable name. In both cases, it should probably print the full path to the variable. (The colon separate might not be the best choice, since you'll probably use that to separate keys from values. OTOH, dot may not be the best choice either, since it's possible that some sections may have dot names in them. You could use the syntax [section]key: value too.) Cheers, -Barry

2 1

Re: [Mailman-Developers] Mailman-Developers Digest, Vol 274, Issue 12
by Florian Fuchs Feb. 20, 2012

Feb. 20, 2012

Hi, Jagannathan, I noticed two things in the traceback: 1) mailman_django seems to be imported twice (line 4) This is probably because you copied it inside django_dev_setup. If you installed it correctly (python setup.py develop) it *should* really run without putting it next to settings.py. (Having django apps living inside the project folder is possible but somewhat discouraged with reusable apps, because this approach doesn't really separate the app from its local settings.) 2) /usr/sbin/postmap: No such file or directory (line 20) I think this might be the actual root of the problem: Mailman cannot find an MTA (it is looking for postfix in this case). Depending on the system you are using, it should be pretty easy to install postfix (`sudo apt-get install postfix` if you're running ubuntu). You might not be able to send or receive emails just by installing it, but it should be enough to run the web ui locally and perform all the tasks that are currently available. Please tell me if this is of any help... Cheers Florian On Monday, February 20, 2012 19:52 CET, Jagannathan Tiruvallur Eachambadi <jagannathante(a)gmail.com> wrote: > I copied the folder mailmanweb/src/mailman-django to django_dev_setup/ and > the server works. But it does not go through all tests. This is snippet of > the errors in the test. http://pastebin.com/1CrKWpkp . > > On Mon, Feb 20, 2012 at 10:14 PM, <mailman-developers-request(a)python.org>wrote: > > > Send Mailman-Developers mailing list submissions to > > mailman-developers(a)python.org > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://mail.python.org/mailman/listinfo/mailman-developers > > or, via email, send a message with subject or body 'help' to > > mailman-developers-request(a)python.org > > > > You can reach the person managing the list at > > mailman-developers-owner(a)python.org > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Mailman-Developers digest..." > > > > > > Today's Topics: > > > > 1. GSOC 12 (Jagannathan Tiruvallur Eachambadi) > > 2. Re: GSOC 12 (Jagannathan Tiruvallur Eachambadi) > > 3. Re: GSOC 12 (Florian Fuchs) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Mon, 20 Feb 2012 16:10:52 +0530 > > From: Jagannathan Tiruvallur Eachambadi <jagannathante(a)gmail.com> > > To: mailman-developers(a)python.org > > Subject: [Mailman-Developers] GSOC 12 > > Message-ID: > > <CABzJUX6EYs2RX7w60nHKgpRpJ33XMA3A6dLMkSjHvVr33mZvYg(a)mail.gmail.com > > > > > Content-Type: text/plain; charset=ISO-8859-1 > > > > hi all, > > > > I am currently doing my first year of under-graduation in NIT-Trichy. > > I was reading the GSOC 12 getting started page and I am unable to to get > > the Django server working. I get ERNO 111 , I tried shutting down apache in > > my computer. But that did not solve the problem. I get the following error, > > http://dpaste.com/705607/ . > > > > On Sun, Feb 19, 2012 at 4:30 PM, <mailman-developers-request(a)python.org > > >wrote: > > > > > Send Mailman-Developers mailing list submissions to > > > mailman-developers(a)python.org > > > > > > To subscribe or unsubscribe via the World Wide Web, visit > > > http://mail.python.org/mailman/listinfo/mailman-developers > > > or, via email, send a message with subject or body 'help' to > > > mailman-developers-request(a)python.org > > > > > > You can reach the person managing the list at > > > mailman-developers-owner(a)python.org > > > > > > When replying, please edit your Subject line so it is more specific > > > than "Re: Contents of Mailman-Developers digest..." > > > > > > > > > Today's Topics: > > > > > > 1. Re: Probe messages should not sent Precedenceheader (Mark > > > Sapiro) > > > 2. Re: Probe messages should not sent Precedenceheader (Aamir > > > Khan) > > > 3. Re: Probe messages should not sent Precedenceheader (Mark > > > Sapiro) > > > > > > > > > ---------------------------------------------------------------------- > > > > > > Message: 1 > > > Date: Sat, 18 Feb 2012 09:22:53 -0800 > > > From: Mark Sapiro <mark(a)msapiro.net> > > > To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > Cc: Mailman-Developers(a)python.org > > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > > Precedenceheader > > > Message-ID: <PC195201202180922530437aace67aa@MSAPIRO> > > > Content-Type: text/plain; charset=iso-8859-1 > > > > > > Aamir Khan wrote: > > > > > > >I guess in MM3, there is no function as sendNextNotification(), because > > i > > > >used command, "grep sendNextNotification() -r *" and the result was only > > > >file 'src/mailman/bin/disabled.py'. > > > > > > > > > Which means that bin/disabled.py won't work because it hasn't been > > > fully converted from 2.1 yet. It should be using the send_probe() > > > function instead of sendNextNotification(). > > > > > > > > > >There is a file 'src/mailman/email/messages.py', in which > > > >UserNotification() class is defined. It has a send function, which sets > > > the > > > >precedence header. > > > > > > > >In file 'src/mailman/app/bouces.py', I guess the probe messages are sent > > > >directly using send() function of UserNotification() class. I think that > > > >from line 211 to 228, probe message is used to send VERP probe. But > > then, > > > i > > > >am not able to find out the place from where probe message is sent after > > > >disabling of the address because of over bouncing. > > > > > > > > > There should be two places. bin/disabled.py should be calling > > > send_probe() instead of the non-existent sendNextNotification() list > > > method. > > > > > > Also, send_probe() should be called when delivery is initially disabled > > > as a result of a call to IBounceProcessor(), but I am unable to follow > > > how this works or even if it is implemented yet at least in part > > > because I haven't yet learned anything about how things like > > > zope.component.getUtility() work. > > > > > > > > > >I have tried to make some changes to code and pushed it to my local > > branch > > > >[1]. Ran through all the tests, and none of them failed. Is there any > > way > > > >to run through a subset of test rather than running them using > > 'bin/test' > > > >command. > > > > > > > >Comments, feedback required on patch. > > > > > > > > > > > >[1] => > > > > > > http://bazaar.launchpad.net/~syst3mw0rm/mailman/precedence/revision/7080 > > > > > > > > > The patch itself looks good except for style. We normally don't put > > > whitespace around the = in keyword=value arguments in definitions and > > > calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > > > use spaces around the '=' sign when used to indicate a keyword > > > argument or a default parameter value." > > > > > > -- > > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > > San Francisco Bay Area, California better use your sense - B. Dylan > > > > > > > > > > > > ------------------------------ > > > > > > Message: 2 > > > Date: Sat, 18 Feb 2012 23:16:37 +0530 > > > From: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > To: Mark Sapiro <mark(a)msapiro.net> > > > Cc: Mailman-Developers(a)python.org > > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > > Precedenceheader > > > Message-ID: > > > < > > CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg(a)mail.gmail.com > > > > > > > Content-Type: text/plain; charset=ISO-8859-1 > > > > > > Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > > > > > > > Which means that bin/disabled.py won't work because it hasn't been > > > > fully converted from 2.1 yet. It should be using the send_probe() > > > > function instead of sendNextNotification(). > > > > > > > > > > Yes. I also think so. I have changed the function to send_probe() and ran > > > through all the test again to make sure that nothing breaks. > > > > > > > > > > > > > > There should be two places. bin/disabled.py should be calling > > > > send_probe() instead of the non-existent sendNextNotification() list > > > > method. > > > > > > > > Also, send_probe() should be called when delivery is initially disabled > > > > as a result of a call to IBounceProcessor(), but I am unable to follow > > > > how this works or even if it is implemented yet at least in part > > > > because I haven't yet learned anything about how things like > > > > zope.component.getUtility() work. > > > > > > > > > > I am also not able to find out the relevant code, as i am completely new > > to > > > the flow of how mailman works. Maybe, barry can help me on this one. > > > > > > > > > > > > > > > The patch itself looks good except for style. We normally don't put > > > > whitespace around the = in keyword=value arguments in definitions and > > > > calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > > > > use spaces around the '=' sign when used to indicate a keyword > > > > argument or a default parameter value." > > > > > > > > I will keep this in mind. I have created another branch with partial > > > changes suggested above. Here, you can find the changes, > > > > > > http://bazaar.launchpad.net/~syst3mw0rm/mailman/808821/revision/7080 > > > > > > > > > > > > -- > > > Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee > > > > > > > > > ------------------------------ > > > > > > Message: 3 > > > Date: Sat, 18 Feb 2012 10:45:28 -0800 > > > From: Mark Sapiro <mark(a)msapiro.net> > > > To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > Cc: Mailman-Developers(a)python.org > > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > > Precedenceheader > > > Message-ID: <PC195201202181045280109fb8c76c9@MSAPIRO> > > > Content-Type: text/plain; charset=iso-8859-1 > > > > > > Aamir Khan wrote: > > > > > > > >Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > > > >> > > > >> Which means that bin/disabled.py won't work because it hasn't been > > > >> fully converted from 2.1 yet. It should be using the send_probe() > > > >> function instead of sendNextNotification(). > > > >> > > > > > > > >Yes. I also think so. I have changed the function to send_probe() and > > ran > > > >through all the test again to make sure that nothing breaks. > > > > > > > > > I don't think you can simply change mlist.sendNextNotification(member) > > > to mlist.send_probe(member) because send_probe() is not a list method, > > > plus it requires a message argument in addition to the member argument. > > > > > > Also, it is apparent that the test suite is not testing bin/disabled.py > > > or it would have been failing all along. > > > > > > -- > > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > > San Francisco Bay Area, California better use your sense - B. Dylan > > > > > > > > > > > > ------------------------------ > > > > > > _______________________________________________ > > > Mailman-Developers mailing list > > > Mailman-Developers(a)python.org > > > http://mail.python.org/mailman/listinfo/mailman-developers > > > > > > > > > End of Mailman-Developers Digest, Vol 274, Issue 10 > > > *************************************************** > > > > > > > > > ------------------------------ > > > > Message: 2 > > Date: Mon, 20 Feb 2012 16:20:11 +0530 > > From: Jagannathan Tiruvallur Eachambadi <jagannathante(a)gmail.com> > > To: mailman-developers(a)python.org > > Subject: Re: [Mailman-Developers] GSOC 12 > > Message-ID: > > <CABzJUX4yLEAfnPg_EzCc9dQuNbYUDSLPwbG1ZT4vim1cTj3T6w(a)mail.gmail.com > > > > > Content-Type: text/plain; charset=ISO-8859-1 > > > > Sorry, the error is TemplateDoesNotExist. I forgot to start the mailman > > runner. This is the error I am getting : http://dpaste.com/705614/ > > > > On Mon, Feb 20, 2012 at 4:10 PM, Jagannathan Tiruvallur Eachambadi < > > jagannathante(a)gmail.com> wrote: > > > > > > > > hi all, > > > > > > I am currently doing my first year of under-graduation in > > NIT-Trichy. > > > I was reading the GSOC 12 getting started page and I am unable to to get > > > the Django server working. I get ERNO 111 , I tried shutting down apache > > in > > > my computer. But that did not solve the problem. I get the following > > error, > > > http://dpaste.com/705607/ . > > > > > > On Sun, Feb 19, 2012 at 4:30 PM, <mailman-developers-request(a)python.org > > >wrote: > > > > > >> Send Mailman-Developers mailing list submissions to > > >> mailman-developers(a)python.org > > >> > > >> To subscribe or unsubscribe via the World Wide Web, visit > > >> http://mail.python.org/mailman/listinfo/mailman-developers > > >> or, via email, send a message with subject or body 'help' to > > >> mailman-developers-request(a)python.org > > >> > > >> You can reach the person managing the list at > > >> mailman-developers-owner(a)python.org > > >> > > >> When replying, please edit your Subject line so it is more specific > > >> than "Re: Contents of Mailman-Developers digest..." > > >> > > >> > > >> Today's Topics: > > >> > > >> 1. Re: Probe messages should not sent Precedenceheader (Mark > > >> Sapiro) > > >> 2. Re: Probe messages should not sent Precedenceheader (Aamir > > >> Khan) > > >> 3. Re: Probe messages should not sent Precedenceheader (Mark > > >> Sapiro) > > >> > > >> > > >> ---------------------------------------------------------------------- > > >> > > >> Message: 1 > > >> Date: Sat, 18 Feb 2012 09:22:53 -0800 > > >> From: Mark Sapiro <mark(a)msapiro.net> > > >> To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > >> Cc: Mailman-Developers(a)python.org > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > >> Precedenceheader > > >> Message-ID: <PC195201202180922530437aace67aa@MSAPIRO> > > >> Content-Type: text/plain; charset=iso-8859-1 > > >> > > >> Aamir Khan wrote: > > >> > > >> >I guess in MM3, there is no function as sendNextNotification(), > > because i > > >> >used command, "grep sendNextNotification() -r *" and the result was > > only > > >> >file 'src/mailman/bin/disabled.py'. > > >> > > >> > > >> Which means that bin/disabled.py won't work because it hasn't been > > >> fully converted from 2.1 yet. It should be using the send_probe() > > >> function instead of sendNextNotification(). > > >> > > >> > > >> >There is a file 'src/mailman/email/messages.py', in which > > >> >UserNotification() class is defined. It has a send function, which sets > > >> the > > >> >precedence header. > > >> > > > >> >In file 'src/mailman/app/bouces.py', I guess the probe messages are > > sent > > >> >directly using send() function of UserNotification() class. I think > > that > > >> >from line 211 to 228, probe message is used to send VERP probe. But > > >> then, i > > >> >am not able to find out the place from where probe message is sent > > after > > >> >disabling of the address because of over bouncing. > > >> > > >> > > >> There should be two places. bin/disabled.py should be calling > > >> send_probe() instead of the non-existent sendNextNotification() list > > >> method. > > >> > > >> Also, send_probe() should be called when delivery is initially disabled > > >> as a result of a call to IBounceProcessor(), but I am unable to follow > > >> how this works or even if it is implemented yet at least in part > > >> because I haven't yet learned anything about how things like > > >> zope.component.getUtility() work. > > >> > > >> > > >> >I have tried to make some changes to code and pushed it to my local > > >> branch > > >> >[1]. Ran through all the tests, and none of them failed. Is there any > > way > > >> >to run through a subset of test rather than running them using > > 'bin/test' > > >> >command. > > >> > > > >> >Comments, feedback required on patch. > > >> > > > >> > > > >> >[1] => > > >> > > > http://bazaar.launchpad.net/~syst3mw0rm/mailman/precedence/revision/7080 > > >> > > >> > > >> The patch itself looks good except for style. We normally don't put > > >> whitespace around the = in keyword=value arguments in definitions and > > >> calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > > >> use spaces around the '=' sign when used to indicate a keyword > > >> argument or a default parameter value." > > >> > > >> -- > > >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > >> San Francisco Bay Area, California better use your sense - B. Dylan > > >> > > >> > > >> > > >> ------------------------------ > > >> > > >> Message: 2 > > >> Date: Sat, 18 Feb 2012 23:16:37 +0530 > > >> From: Aamir Khan <syst3m.w0rm(a)gmail.com> > > >> To: Mark Sapiro <mark(a)msapiro.net> > > >> Cc: Mailman-Developers(a)python.org > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > >> Precedenceheader > > >> Message-ID: > > >> < > > >> CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg(a)mail.gmail.com> > > >> Content-Type: text/plain; charset=ISO-8859-1 > > >> > > >> Mark Sapiro <mark(a)msapiro.net> wrote: > > >> > > >> > > > >> > Which means that bin/disabled.py won't work because it hasn't been > > >> > fully converted from 2.1 yet. It should be using the send_probe() > > >> > function instead of sendNextNotification(). > > >> > > > >> > > >> Yes. I also think so. I have changed the function to send_probe() and > > ran > > >> through all the test again to make sure that nothing breaks. > > >> > > >> > > >> > > > >> > There should be two places. bin/disabled.py should be calling > > >> > send_probe() instead of the non-existent sendNextNotification() list > > >> > method. > > >> > > > >> > Also, send_probe() should be called when delivery is initially > > disabled > > >> > as a result of a call to IBounceProcessor(), but I am unable to follow > > >> > how this works or even if it is implemented yet at least in part > > >> > because I haven't yet learned anything about how things like > > >> > zope.component.getUtility() work. > > >> > > > >> > > >> I am also not able to find out the relevant code, as i am completely new > > >> to > > >> the flow of how mailman works. Maybe, barry can help me on this one. > > >> > > >> > > > >> > > > >> > The patch itself looks good except for style. We normally don't put > > >> > whitespace around the = in keyword=value arguments in definitions and > > >> > calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > > >> > use spaces around the '=' sign when used to indicate a keyword > > >> > argument or a default parameter value." > > >> > > > >> > I will keep this in mind. I have created another branch with partial > > >> changes suggested above. Here, you can find the changes, > > >> > > >> http://bazaar.launchpad.net/~syst3mw0rm/mailman/808821/revision/7080 > > >> > > >> > > >> > > >> -- > > >> Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee > > >> > > >> > > >> ------------------------------ > > >> > > >> Message: 3 > > >> Date: Sat, 18 Feb 2012 10:45:28 -0800 > > >> From: Mark Sapiro <mark(a)msapiro.net> > > >> To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > >> Cc: Mailman-Developers(a)python.org > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > >> Precedenceheader > > >> Message-ID: <PC195201202181045280109fb8c76c9@MSAPIRO> > > >> Content-Type: text/plain; charset=iso-8859-1 > > >> > > >> Aamir Khan wrote: > > >> > > > >> >Mark Sapiro <mark(a)msapiro.net> wrote: > > >> > > > >> >> > > >> >> Which means that bin/disabled.py won't work because it hasn't been > > >> >> fully converted from 2.1 yet. It should be using the send_probe() > > >> >> function instead of sendNextNotification(). > > >> >> > > >> > > > >> >Yes. I also think so. I have changed the function to send_probe() and > > ran > > >> >through all the test again to make sure that nothing breaks. > > >> > > >> > > >> I don't think you can simply change mlist.sendNextNotification(member) > > >> to mlist.send_probe(member) because send_probe() is not a list method, > > >> plus it requires a message argument in addition to the member argument. > > >> > > >> Also, it is apparent that the test suite is not testing bin/disabled.py > > >> or it would have been failing all along. > > >> > > >> -- > > >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > >> San Francisco Bay Area, California better use your sense - B. Dylan > > >> > > >> > > >> > > >> ------------------------------ > > >> > > >> _______________________________________________ > > >> Mailman-Developers mailing list > > >> Mailman-Developers(a)python.org > > >> http://mail.python.org/mailman/listinfo/mailman-developers > > >> > > >> > > >> End of Mailman-Developers Digest, Vol 274, Issue 10 > > >> *************************************************** > > >> > > > > > > > > > > > > ------------------------------ > > > > Message: 3 > > Date: Mon, 20 Feb 2012 17:43:47 +0100 > > From: "Florian Fuchs" <f(a)state-of-mind.de> > > To: "Jagannathan Tiruvallur Eachambadi" <jagannathante(a)gmail.com> > > Cc: mailman-developers(a)python.org > > Subject: Re: [Mailman-Developers] GSOC 12 > > Message-ID: <1f3e-4f427880-7-13fbcde0@263897354> > > Content-Type: text/plain; charset="utf-8" > > > > Hi Jagannathan, > > > > if the Error is TemplateDoesNotExist, the first thing to check would be: > > Does the relevant file exist and does the user starting the server have the > > necessary rights to access it? > > > > In your case that would be the following file: > > > > > > <folder-where-mailmanweb-lives>/mailmanweb/src/mailman_django/templates/mailman-django/lists/index.html > > > > Any luck? > > > > Florian > > > > > > > > On Monday, February 20, 2012 11:50 CET, Jagannathan Tiruvallur Eachambadi < > > jagannathante(a)gmail.com> wrote: > > > > > Sorry, the error is TemplateDoesNotExist. I forgot to start the mailman > > > runner. This is the error I am getting : http://dpaste.com/705614/ > > > > > > On Mon, Feb 20, 2012 at 4:10 PM, Jagannathan Tiruvallur Eachambadi < > > > jagannathante(a)gmail.com> wrote: > > > > > > > > > > > hi all, > > > > > > > > I am currently doing my first year of under-graduation in > > NIT-Trichy. > > > > I was reading the GSOC 12 getting started page and I am unable to to > > get > > > > the Django server working. I get ERNO 111 , I tried shutting down > > apache in > > > > my computer. But that did not solve the problem. I get the following > > error, > > > > http://dpaste.com/705607/ . > > > > > > > > On Sun, Feb 19, 2012 at 4:30 PM, < > > mailman-developers-request(a)python.org>wrote: > > > > > > > >> Send Mailman-Developers mailing list submissions to > > > >> mailman-developers(a)python.org > > > >> > > > >> To subscribe or unsubscribe via the World Wide Web, visit > > > >> http://mail.python.org/mailman/listinfo/mailman-developers > > > >> or, via email, send a message with subject or body 'help' to > > > >> mailman-developers-request(a)python.org > > > >> > > > >> You can reach the person managing the list at > > > >> mailman-developers-owner(a)python.org > > > >> > > > >> When replying, please edit your Subject line so it is more specific > > > >> than "Re: Contents of Mailman-Developers digest..." > > > >> > > > >> > > > >> Today's Topics: > > > >> > > > >> 1. Re: Probe messages should not sent Precedenceheader (Mark > > > >> Sapiro) > > > >> 2. Re: Probe messages should not sent Precedenceheader (Aamir > > > >> Khan) > > > >> 3. Re: Probe messages should not sent Precedenceheader (Mark > > > >> Sapiro) > > > >> > > > >> > > > >> ---------------------------------------------------------------------- > > > >> > > > >> Message: 1 > > > >> Date: Sat, 18 Feb 2012 09:22:53 -0800 > > > >> From: Mark Sapiro <mark(a)msapiro.net> > > > >> To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > >> Cc: Mailman-Developers(a)python.org > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > >> Precedenceheader > > > >> Message-ID: <PC195201202180922530437aace67aa@MSAPIRO> > > > >> Content-Type: text/plain; charset=iso-8859-1 > > > >> > > > >> Aamir Khan wrote: > > > >> > > > >> >I guess in MM3, there is no function as sendNextNotification(), > > because i > > > >> >used command, "grep sendNextNotification() -r *" and the result was > > only > > > >> >file 'src/mailman/bin/disabled.py'. > > > >> > > > >> > > > >> Which means that bin/disabled.py won't work because it hasn't been > > > >> fully converted from 2.1 yet. It should be using the send_probe() > > > >> function instead of sendNextNotification(). > > > >> > > > >> > > > >> >There is a file 'src/mailman/email/messages.py', in which > > > >> >UserNotification() class is defined. It has a send function, which > > sets > > > >> the > > > >> >precedence header. > > > >> > > > > >> >In file 'src/mailman/app/bouces.py', I guess the probe messages are > > sent > > > >> >directly using send() function of UserNotification() class. I think > > that > > > >> >from line 211 to 228, probe message is used to send VERP probe. But > > > >> then, i > > > >> >am not able to find out the place from where probe message is sent > > after > > > >> >disabling of the address because of over bouncing. > > > >> > > > >> > > > >> There should be two places. bin/disabled.py should be calling > > > >> send_probe() instead of the non-existent sendNextNotification() list > > > >> method. > > > >> > > > >> Also, send_probe() should be called when delivery is initially > > disabled > > > >> as a result of a call to IBounceProcessor(), but I am unable to follow > > > >> how this works or even if it is implemented yet at least in part > > > >> because I haven't yet learned anything about how things like > > > >> zope.component.getUtility() work. > > > >> > > > >> > > > >> >I have tried to make some changes to code and pushed it to my local > > > >> branch > > > >> >[1]. Ran through all the tests, and none of them failed. Is there > > any way > > > >> >to run through a subset of test rather than running them using > > 'bin/test' > > > >> >command. > > > >> > > > > >> >Comments, feedback required on patch. > > > >> > > > > >> > > > > >> >[1] => > > > >> > > > http://bazaar.launchpad.net/~syst3mw0rm/mailman/precedence/revision/7080 > > > >> > > > >> > > > >> The patch itself looks good except for style. We normally don't put > > > >> whitespace around the = in keyword=value arguments in definitions and > > > >> calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > > > >> use spaces around the '=' sign when used to indicate a keyword > > > >> argument or a default parameter value." > > > >> > > > >> -- > > > >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > > >> San Francisco Bay Area, California better use your sense - B. Dylan > > > >> > > > >> > > > >> > > > >> ------------------------------ > > > >> > > > >> Message: 2 > > > >> Date: Sat, 18 Feb 2012 23:16:37 +0530 > > > >> From: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > >> To: Mark Sapiro <mark(a)msapiro.net> > > > >> Cc: Mailman-Developers(a)python.org > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > >> Precedenceheader > > > >> Message-ID: > > > >> < > > > >> CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg(a)mail.gmail.com> > > > >> Content-Type: text/plain; charset=ISO-8859-1 > > > >> > > > >> Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> > > > >> > > > > >> > Which means that bin/disabled.py won't work because it hasn't been > > > >> > fully converted from 2.1 yet. It should be using the send_probe() > > > >> > function instead of sendNextNotification(). > > > >> > > > > >> > > > >> Yes. I also think so. I have changed the function to send_probe() and > > ran > > > >> through all the test again to make sure that nothing breaks. > > > >> > > > >> > > > >> > > > > >> > There should be two places. bin/disabled.py should be calling > > > >> > send_probe() instead of the non-existent sendNextNotification() list > > > >> > method. > > > >> > > > > >> > Also, send_probe() should be called when delivery is initially > > disabled > > > >> > as a result of a call to IBounceProcessor(), but I am unable to > > follow > > > >> > how this works or even if it is implemented yet at least in part > > > >> > because I haven't yet learned anything about how things like > > > >> > zope.component.getUtility() work. > > > >> > > > > >> > > > >> I am also not able to find out the relevant code, as i am completely > > new > > > >> to > > > >> the flow of how mailman works. Maybe, barry can help me on this one. > > > >> > > > >> > > > > >> > > > > >> > The patch itself looks good except for style. We normally don't put > > > >> > whitespace around the = in keyword=value arguments in definitions > > and > > > >> > calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > > > >> > use spaces around the '=' sign when used to indicate a keyword > > > >> > argument or a default parameter value." > > > >> > > > > >> > I will keep this in mind. I have created another branch with partial > > > >> changes suggested above. Here, you can find the changes, > > > >> > > > >> http://bazaar.launchpad.net/~syst3mw0rm/mailman/808821/revision/7080 > > > >> > > > >> > > > >> > > > >> -- > > > >> Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee > > > >> > > > >> > > > >> ------------------------------ > > > >> > > > >> Message: 3 > > > >> Date: Sat, 18 Feb 2012 10:45:28 -0800 > > > >> From: Mark Sapiro <mark(a)msapiro.net> > > > >> To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > > >> Cc: Mailman-Developers(a)python.org > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > >> Precedenceheader > > > >> Message-ID: <PC195201202181045280109fb8c76c9@MSAPIRO> > > > >> Content-Type: text/plain; charset=iso-8859-1 > > > >> > > > >> Aamir Khan wrote: > > > >> > > > > >> >Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> > > > > >> >> > > > >> >> Which means that bin/disabled.py won't work because it hasn't been > > > >> >> fully converted from 2.1 yet. It should be using the send_probe() > > > >> >> function instead of sendNextNotification(). > > > >> >> > > > >> > > > > >> >Yes. I also think so. I have changed the function to send_probe() > > and ran > > > >> >through all the test again to make sure that nothing breaks. > > > >> > > > >> > > > >> I don't think you can simply change mlist.sendNextNotification(member) > > > >> to mlist.send_probe(member) because send_probe() is not a list method, > > > >> plus it requires a message argument in addition to the member > > argument. > > > >> > > > >> Also, it is apparent that the test suite is not testing > > bin/disabled.py > > > >> or it would have been failing all along. > > > >> > > > >> -- > > > >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > > >> San Francisco Bay Area, California better use your sense - B. Dylan > > > >> > > > >> > > > >> > > > >> ------------------------------ > > > >> > > > >> _______________________________________________ > > > >> Mailman-Developers mailing list > > > >> Mailman-Developers(a)python.org > > > >> http://mail.python.org/mailman/listinfo/mailman-developers > > > >> > > > >> > > > >> End of Mailman-Developers Digest, Vol 274, Issue 10 > > > >> *************************************************** > > > >> > > > > > > > > > > > _______________________________________________ > > > Mailman-Developers mailing list > > > Mailman-Developers(a)python.org > > > http://mail.python.org/mailman/listinfo/mailman-developers > > > Mailman FAQ: http://wiki.list.org/x/AgA3 > > > Searchable Archives: > > http://www.mail-archive.com/mailman-developers%40python.org/ > > > Unsubscribe: > > http://mail.python.org/mailman/options/mailman-developers/f%40state-of-mind… > > > > > > Security Policy: http://wiki.list.org/x/QIA9 > > > > > > > > > > > > > > > > ------------------------------ > > > > _______________________________________________ > > Mailman-Developers mailing list > > Mailman-Developers(a)python.org > > http://mail.python.org/mailman/listinfo/mailman-developers > > > > > > End of Mailman-Developers Digest, Vol 274, Issue 12 > > *************************************************** > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > http://mail.python.org/mailman/listinfo/mailman-developers > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ > Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/f%40state-of-mind… > > Security Policy: http://wiki.list.org/x/QIA9

1 0

Re: [Mailman-Developers] Probe messages should not sent Precedence header
by Barry Warsaw Feb. 20, 2012

Feb. 20, 2012

On Feb 18, 2012, at 06:38 AM, Aamir Khan wrote: >As suggested by Barry, I am working on this new bug, >808821<https://bugs.launchpad.net/mailman/+bug/808821>. As i browsed though >the code of mailman, i found that 'src/mailman/bin/disabled.py' is the script >which runs to send the messages to all the email addresses disabled may be >because of over bouncing, by user himself, by admin, etc.. So, i just have >to find out the way, so that bouncing mail won't set the precedence header. This script is currently broken, but I will fix it for beta 1. I'll leave the Precedence bug open for you to take a shot if you like. https://bugs.launchpad.net/mailman/+bug/937154 Cheers, -Barry

2 1

Re: [Mailman-Developers] Mailman-Developers Digest, Vol 274, Issue 12
by Jagannathan Tiruvallur Eachambadi Feb. 20, 2012

Feb. 20, 2012

I copied the folder mailmanweb/src/mailman-django to django_dev_setup/ and the server works. But it does not go through all tests. This is snippet of the errors in the test. http://pastebin.com/1CrKWpkp . On Mon, Feb 20, 2012 at 10:14 PM, <mailman-developers-request(a)python.org>wrote: > Send Mailman-Developers mailing list submissions to > mailman-developers(a)python.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.python.org/mailman/listinfo/mailman-developers > or, via email, send a message with subject or body 'help' to > mailman-developers-request(a)python.org > > You can reach the person managing the list at > mailman-developers-owner(a)python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Mailman-Developers digest..." > > > Today's Topics: > > 1. GSOC 12 (Jagannathan Tiruvallur Eachambadi) > 2. Re: GSOC 12 (Jagannathan Tiruvallur Eachambadi) > 3. Re: GSOC 12 (Florian Fuchs) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 20 Feb 2012 16:10:52 +0530 > From: Jagannathan Tiruvallur Eachambadi <jagannathante(a)gmail.com> > To: mailman-developers(a)python.org > Subject: [Mailman-Developers] GSOC 12 > Message-ID: > <CABzJUX6EYs2RX7w60nHKgpRpJ33XMA3A6dLMkSjHvVr33mZvYg(a)mail.gmail.com > > > Content-Type: text/plain; charset=ISO-8859-1 > > hi all, > > I am currently doing my first year of under-graduation in NIT-Trichy. > I was reading the GSOC 12 getting started page and I am unable to to get > the Django server working. I get ERNO 111 , I tried shutting down apache in > my computer. But that did not solve the problem. I get the following error, > http://dpaste.com/705607/ . > > On Sun, Feb 19, 2012 at 4:30 PM, <mailman-developers-request(a)python.org > >wrote: > > > Send Mailman-Developers mailing list submissions to > > mailman-developers(a)python.org > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://mail.python.org/mailman/listinfo/mailman-developers > > or, via email, send a message with subject or body 'help' to > > mailman-developers-request(a)python.org > > > > You can reach the person managing the list at > > mailman-developers-owner(a)python.org > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Mailman-Developers digest..." > > > > > > Today's Topics: > > > > 1. Re: Probe messages should not sent Precedenceheader (Mark > > Sapiro) > > 2. Re: Probe messages should not sent Precedenceheader (Aamir > > Khan) > > 3. Re: Probe messages should not sent Precedenceheader (Mark > > Sapiro) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Sat, 18 Feb 2012 09:22:53 -0800 > > From: Mark Sapiro <mark(a)msapiro.net> > > To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > Cc: Mailman-Developers(a)python.org > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > Precedenceheader > > Message-ID: <PC195201202180922530437aace67aa@MSAPIRO> > > Content-Type: text/plain; charset=iso-8859-1 > > > > Aamir Khan wrote: > > > > >I guess in MM3, there is no function as sendNextNotification(), because > i > > >used command, "grep sendNextNotification() -r *" and the result was only > > >file 'src/mailman/bin/disabled.py'. > > > > > > Which means that bin/disabled.py won't work because it hasn't been > > fully converted from 2.1 yet. It should be using the send_probe() > > function instead of sendNextNotification(). > > > > > > >There is a file 'src/mailman/email/messages.py', in which > > >UserNotification() class is defined. It has a send function, which sets > > the > > >precedence header. > > > > > >In file 'src/mailman/app/bouces.py', I guess the probe messages are sent > > >directly using send() function of UserNotification() class. I think that > > >from line 211 to 228, probe message is used to send VERP probe. But > then, > > i > > >am not able to find out the place from where probe message is sent after > > >disabling of the address because of over bouncing. > > > > > > There should be two places. bin/disabled.py should be calling > > send_probe() instead of the non-existent sendNextNotification() list > > method. > > > > Also, send_probe() should be called when delivery is initially disabled > > as a result of a call to IBounceProcessor(), but I am unable to follow > > how this works or even if it is implemented yet at least in part > > because I haven't yet learned anything about how things like > > zope.component.getUtility() work. > > > > > > >I have tried to make some changes to code and pushed it to my local > branch > > >[1]. Ran through all the tests, and none of them failed. Is there any > way > > >to run through a subset of test rather than running them using > 'bin/test' > > >command. > > > > > >Comments, feedback required on patch. > > > > > > > > >[1] => > > > > http://bazaar.launchpad.net/~syst3mw0rm/mailman/precedence/revision/7080 > > > > > > The patch itself looks good except for style. We normally don't put > > whitespace around the = in keyword=value arguments in definitions and > > calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > > use spaces around the '=' sign when used to indicate a keyword > > argument or a default parameter value." > > > > -- > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > San Francisco Bay Area, California better use your sense - B. Dylan > > > > > > > > ------------------------------ > > > > Message: 2 > > Date: Sat, 18 Feb 2012 23:16:37 +0530 > > From: Aamir Khan <syst3m.w0rm(a)gmail.com> > > To: Mark Sapiro <mark(a)msapiro.net> > > Cc: Mailman-Developers(a)python.org > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > Precedenceheader > > Message-ID: > > < > CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg(a)mail.gmail.com > > > > > Content-Type: text/plain; charset=ISO-8859-1 > > > > Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > > > > Which means that bin/disabled.py won't work because it hasn't been > > > fully converted from 2.1 yet. It should be using the send_probe() > > > function instead of sendNextNotification(). > > > > > > > Yes. I also think so. I have changed the function to send_probe() and ran > > through all the test again to make sure that nothing breaks. > > > > > > > > > > There should be two places. bin/disabled.py should be calling > > > send_probe() instead of the non-existent sendNextNotification() list > > > method. > > > > > > Also, send_probe() should be called when delivery is initially disabled > > > as a result of a call to IBounceProcessor(), but I am unable to follow > > > how this works or even if it is implemented yet at least in part > > > because I haven't yet learned anything about how things like > > > zope.component.getUtility() work. > > > > > > > I am also not able to find out the relevant code, as i am completely new > to > > the flow of how mailman works. Maybe, barry can help me on this one. > > > > > > > > > > > The patch itself looks good except for style. We normally don't put > > > whitespace around the = in keyword=value arguments in definitions and > > > calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > > > use spaces around the '=' sign when used to indicate a keyword > > > argument or a default parameter value." > > > > > > I will keep this in mind. I have created another branch with partial > > changes suggested above. Here, you can find the changes, > > > > http://bazaar.launchpad.net/~syst3mw0rm/mailman/808821/revision/7080 > > > > > > > > -- > > Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee > > > > > > ------------------------------ > > > > Message: 3 > > Date: Sat, 18 Feb 2012 10:45:28 -0800 > > From: Mark Sapiro <mark(a)msapiro.net> > > To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > Cc: Mailman-Developers(a)python.org > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > Precedenceheader > > Message-ID: <PC195201202181045280109fb8c76c9@MSAPIRO> > > Content-Type: text/plain; charset=iso-8859-1 > > > > Aamir Khan wrote: > > > > > >Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > >> > > >> Which means that bin/disabled.py won't work because it hasn't been > > >> fully converted from 2.1 yet. It should be using the send_probe() > > >> function instead of sendNextNotification(). > > >> > > > > > >Yes. I also think so. I have changed the function to send_probe() and > ran > > >through all the test again to make sure that nothing breaks. > > > > > > I don't think you can simply change mlist.sendNextNotification(member) > > to mlist.send_probe(member) because send_probe() is not a list method, > > plus it requires a message argument in addition to the member argument. > > > > Also, it is apparent that the test suite is not testing bin/disabled.py > > or it would have been failing all along. > > > > -- > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > San Francisco Bay Area, California better use your sense - B. Dylan > > > > > > > > ------------------------------ > > > > _______________________________________________ > > Mailman-Developers mailing list > > Mailman-Developers(a)python.org > > http://mail.python.org/mailman/listinfo/mailman-developers > > > > > > End of Mailman-Developers Digest, Vol 274, Issue 10 > > *************************************************** > > > > > ------------------------------ > > Message: 2 > Date: Mon, 20 Feb 2012 16:20:11 +0530 > From: Jagannathan Tiruvallur Eachambadi <jagannathante(a)gmail.com> > To: mailman-developers(a)python.org > Subject: Re: [Mailman-Developers] GSOC 12 > Message-ID: > <CABzJUX4yLEAfnPg_EzCc9dQuNbYUDSLPwbG1ZT4vim1cTj3T6w(a)mail.gmail.com > > > Content-Type: text/plain; charset=ISO-8859-1 > > Sorry, the error is TemplateDoesNotExist. I forgot to start the mailman > runner. This is the error I am getting : http://dpaste.com/705614/ > > On Mon, Feb 20, 2012 at 4:10 PM, Jagannathan Tiruvallur Eachambadi < > jagannathante(a)gmail.com> wrote: > > > > > hi all, > > > > I am currently doing my first year of under-graduation in > NIT-Trichy. > > I was reading the GSOC 12 getting started page and I am unable to to get > > the Django server working. I get ERNO 111 , I tried shutting down apache > in > > my computer. But that did not solve the problem. I get the following > error, > > http://dpaste.com/705607/ . > > > > On Sun, Feb 19, 2012 at 4:30 PM, <mailman-developers-request(a)python.org > >wrote: > > > >> Send Mailman-Developers mailing list submissions to > >> mailman-developers(a)python.org > >> > >> To subscribe or unsubscribe via the World Wide Web, visit > >> http://mail.python.org/mailman/listinfo/mailman-developers > >> or, via email, send a message with subject or body 'help' to > >> mailman-developers-request(a)python.org > >> > >> You can reach the person managing the list at > >> mailman-developers-owner(a)python.org > >> > >> When replying, please edit your Subject line so it is more specific > >> than "Re: Contents of Mailman-Developers digest..." > >> > >> > >> Today's Topics: > >> > >> 1. Re: Probe messages should not sent Precedenceheader (Mark > >> Sapiro) > >> 2. Re: Probe messages should not sent Precedenceheader (Aamir > >> Khan) > >> 3. Re: Probe messages should not sent Precedenceheader (Mark > >> Sapiro) > >> > >> > >> ---------------------------------------------------------------------- > >> > >> Message: 1 > >> Date: Sat, 18 Feb 2012 09:22:53 -0800 > >> From: Mark Sapiro <mark(a)msapiro.net> > >> To: Aamir Khan <syst3m.w0rm(a)gmail.com> > >> Cc: Mailman-Developers(a)python.org > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > >> Precedenceheader > >> Message-ID: <PC195201202180922530437aace67aa@MSAPIRO> > >> Content-Type: text/plain; charset=iso-8859-1 > >> > >> Aamir Khan wrote: > >> > >> >I guess in MM3, there is no function as sendNextNotification(), > because i > >> >used command, "grep sendNextNotification() -r *" and the result was > only > >> >file 'src/mailman/bin/disabled.py'. > >> > >> > >> Which means that bin/disabled.py won't work because it hasn't been > >> fully converted from 2.1 yet. It should be using the send_probe() > >> function instead of sendNextNotification(). > >> > >> > >> >There is a file 'src/mailman/email/messages.py', in which > >> >UserNotification() class is defined. It has a send function, which sets > >> the > >> >precedence header. > >> > > >> >In file 'src/mailman/app/bouces.py', I guess the probe messages are > sent > >> >directly using send() function of UserNotification() class. I think > that > >> >from line 211 to 228, probe message is used to send VERP probe. But > >> then, i > >> >am not able to find out the place from where probe message is sent > after > >> >disabling of the address because of over bouncing. > >> > >> > >> There should be two places. bin/disabled.py should be calling > >> send_probe() instead of the non-existent sendNextNotification() list > >> method. > >> > >> Also, send_probe() should be called when delivery is initially disabled > >> as a result of a call to IBounceProcessor(), but I am unable to follow > >> how this works or even if it is implemented yet at least in part > >> because I haven't yet learned anything about how things like > >> zope.component.getUtility() work. > >> > >> > >> >I have tried to make some changes to code and pushed it to my local > >> branch > >> >[1]. Ran through all the tests, and none of them failed. Is there any > way > >> >to run through a subset of test rather than running them using > 'bin/test' > >> >command. > >> > > >> >Comments, feedback required on patch. > >> > > >> > > >> >[1] => > >> > > http://bazaar.launchpad.net/~syst3mw0rm/mailman/precedence/revision/7080 > >> > >> > >> The patch itself looks good except for style. We normally don't put > >> whitespace around the = in keyword=value arguments in definitions and > >> calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > >> use spaces around the '=' sign when used to indicate a keyword > >> argument or a default parameter value." > >> > >> -- > >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > >> San Francisco Bay Area, California better use your sense - B. Dylan > >> > >> > >> > >> ------------------------------ > >> > >> Message: 2 > >> Date: Sat, 18 Feb 2012 23:16:37 +0530 > >> From: Aamir Khan <syst3m.w0rm(a)gmail.com> > >> To: Mark Sapiro <mark(a)msapiro.net> > >> Cc: Mailman-Developers(a)python.org > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > >> Precedenceheader > >> Message-ID: > >> < > >> CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg(a)mail.gmail.com> > >> Content-Type: text/plain; charset=ISO-8859-1 > >> > >> Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> > > >> > Which means that bin/disabled.py won't work because it hasn't been > >> > fully converted from 2.1 yet. It should be using the send_probe() > >> > function instead of sendNextNotification(). > >> > > >> > >> Yes. I also think so. I have changed the function to send_probe() and > ran > >> through all the test again to make sure that nothing breaks. > >> > >> > >> > > >> > There should be two places. bin/disabled.py should be calling > >> > send_probe() instead of the non-existent sendNextNotification() list > >> > method. > >> > > >> > Also, send_probe() should be called when delivery is initially > disabled > >> > as a result of a call to IBounceProcessor(), but I am unable to follow > >> > how this works or even if it is implemented yet at least in part > >> > because I haven't yet learned anything about how things like > >> > zope.component.getUtility() work. > >> > > >> > >> I am also not able to find out the relevant code, as i am completely new > >> to > >> the flow of how mailman works. Maybe, barry can help me on this one. > >> > >> > > >> > > >> > The patch itself looks good except for style. We normally don't put > >> > whitespace around the = in keyword=value arguments in definitions and > >> > calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > >> > use spaces around the '=' sign when used to indicate a keyword > >> > argument or a default parameter value." > >> > > >> > I will keep this in mind. I have created another branch with partial > >> changes suggested above. Here, you can find the changes, > >> > >> http://bazaar.launchpad.net/~syst3mw0rm/mailman/808821/revision/7080 > >> > >> > >> > >> -- > >> Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee > >> > >> > >> ------------------------------ > >> > >> Message: 3 > >> Date: Sat, 18 Feb 2012 10:45:28 -0800 > >> From: Mark Sapiro <mark(a)msapiro.net> > >> To: Aamir Khan <syst3m.w0rm(a)gmail.com> > >> Cc: Mailman-Developers(a)python.org > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > >> Precedenceheader > >> Message-ID: <PC195201202181045280109fb8c76c9@MSAPIRO> > >> Content-Type: text/plain; charset=iso-8859-1 > >> > >> Aamir Khan wrote: > >> > > >> >Mark Sapiro <mark(a)msapiro.net> wrote: > >> > > >> >> > >> >> Which means that bin/disabled.py won't work because it hasn't been > >> >> fully converted from 2.1 yet. It should be using the send_probe() > >> >> function instead of sendNextNotification(). > >> >> > >> > > >> >Yes. I also think so. I have changed the function to send_probe() and > ran > >> >through all the test again to make sure that nothing breaks. > >> > >> > >> I don't think you can simply change mlist.sendNextNotification(member) > >> to mlist.send_probe(member) because send_probe() is not a list method, > >> plus it requires a message argument in addition to the member argument. > >> > >> Also, it is apparent that the test suite is not testing bin/disabled.py > >> or it would have been failing all along. > >> > >> -- > >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > >> San Francisco Bay Area, California better use your sense - B. Dylan > >> > >> > >> > >> ------------------------------ > >> > >> _______________________________________________ > >> Mailman-Developers mailing list > >> Mailman-Developers(a)python.org > >> http://mail.python.org/mailman/listinfo/mailman-developers > >> > >> > >> End of Mailman-Developers Digest, Vol 274, Issue 10 > >> *************************************************** > >> > > > > > > > ------------------------------ > > Message: 3 > Date: Mon, 20 Feb 2012 17:43:47 +0100 > From: "Florian Fuchs" <f(a)state-of-mind.de> > To: "Jagannathan Tiruvallur Eachambadi" <jagannathante(a)gmail.com> > Cc: mailman-developers(a)python.org > Subject: Re: [Mailman-Developers] GSOC 12 > Message-ID: <1f3e-4f427880-7-13fbcde0@263897354> > Content-Type: text/plain; charset="utf-8" > > Hi Jagannathan, > > if the Error is TemplateDoesNotExist, the first thing to check would be: > Does the relevant file exist and does the user starting the server have the > necessary rights to access it? > > In your case that would be the following file: > > > <folder-where-mailmanweb-lives>/mailmanweb/src/mailman_django/templates/mailman-django/lists/index.html > > Any luck? > > Florian > > > > On Monday, February 20, 2012 11:50 CET, Jagannathan Tiruvallur Eachambadi < > jagannathante(a)gmail.com> wrote: > > > Sorry, the error is TemplateDoesNotExist. I forgot to start the mailman > > runner. This is the error I am getting : http://dpaste.com/705614/ > > > > On Mon, Feb 20, 2012 at 4:10 PM, Jagannathan Tiruvallur Eachambadi < > > jagannathante(a)gmail.com> wrote: > > > > > > > > hi all, > > > > > > I am currently doing my first year of under-graduation in > NIT-Trichy. > > > I was reading the GSOC 12 getting started page and I am unable to to > get > > > the Django server working. I get ERNO 111 , I tried shutting down > apache in > > > my computer. But that did not solve the problem. I get the following > error, > > > http://dpaste.com/705607/ . > > > > > > On Sun, Feb 19, 2012 at 4:30 PM, < > mailman-developers-request(a)python.org>wrote: > > > > > >> Send Mailman-Developers mailing list submissions to > > >> mailman-developers(a)python.org > > >> > > >> To subscribe or unsubscribe via the World Wide Web, visit > > >> http://mail.python.org/mailman/listinfo/mailman-developers > > >> or, via email, send a message with subject or body 'help' to > > >> mailman-developers-request(a)python.org > > >> > > >> You can reach the person managing the list at > > >> mailman-developers-owner(a)python.org > > >> > > >> When replying, please edit your Subject line so it is more specific > > >> than "Re: Contents of Mailman-Developers digest..." > > >> > > >> > > >> Today's Topics: > > >> > > >> 1. Re: Probe messages should not sent Precedenceheader (Mark > > >> Sapiro) > > >> 2. Re: Probe messages should not sent Precedenceheader (Aamir > > >> Khan) > > >> 3. Re: Probe messages should not sent Precedenceheader (Mark > > >> Sapiro) > > >> > > >> > > >> ---------------------------------------------------------------------- > > >> > > >> Message: 1 > > >> Date: Sat, 18 Feb 2012 09:22:53 -0800 > > >> From: Mark Sapiro <mark(a)msapiro.net> > > >> To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > >> Cc: Mailman-Developers(a)python.org > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > >> Precedenceheader > > >> Message-ID: <PC195201202180922530437aace67aa@MSAPIRO> > > >> Content-Type: text/plain; charset=iso-8859-1 > > >> > > >> Aamir Khan wrote: > > >> > > >> >I guess in MM3, there is no function as sendNextNotification(), > because i > > >> >used command, "grep sendNextNotification() -r *" and the result was > only > > >> >file 'src/mailman/bin/disabled.py'. > > >> > > >> > > >> Which means that bin/disabled.py won't work because it hasn't been > > >> fully converted from 2.1 yet. It should be using the send_probe() > > >> function instead of sendNextNotification(). > > >> > > >> > > >> >There is a file 'src/mailman/email/messages.py', in which > > >> >UserNotification() class is defined. It has a send function, which > sets > > >> the > > >> >precedence header. > > >> > > > >> >In file 'src/mailman/app/bouces.py', I guess the probe messages are > sent > > >> >directly using send() function of UserNotification() class. I think > that > > >> >from line 211 to 228, probe message is used to send VERP probe. But > > >> then, i > > >> >am not able to find out the place from where probe message is sent > after > > >> >disabling of the address because of over bouncing. > > >> > > >> > > >> There should be two places. bin/disabled.py should be calling > > >> send_probe() instead of the non-existent sendNextNotification() list > > >> method. > > >> > > >> Also, send_probe() should be called when delivery is initially > disabled > > >> as a result of a call to IBounceProcessor(), but I am unable to follow > > >> how this works or even if it is implemented yet at least in part > > >> because I haven't yet learned anything about how things like > > >> zope.component.getUtility() work. > > >> > > >> > > >> >I have tried to make some changes to code and pushed it to my local > > >> branch > > >> >[1]. Ran through all the tests, and none of them failed. Is there > any way > > >> >to run through a subset of test rather than running them using > 'bin/test' > > >> >command. > > >> > > > >> >Comments, feedback required on patch. > > >> > > > >> > > > >> >[1] => > > >> > > http://bazaar.launchpad.net/~syst3mw0rm/mailman/precedence/revision/7080 > > >> > > >> > > >> The patch itself looks good except for style. We normally don't put > > >> whitespace around the = in keyword=value arguments in definitions and > > >> calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > > >> use spaces around the '=' sign when used to indicate a keyword > > >> argument or a default parameter value." > > >> > > >> -- > > >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > >> San Francisco Bay Area, California better use your sense - B. Dylan > > >> > > >> > > >> > > >> ------------------------------ > > >> > > >> Message: 2 > > >> Date: Sat, 18 Feb 2012 23:16:37 +0530 > > >> From: Aamir Khan <syst3m.w0rm(a)gmail.com> > > >> To: Mark Sapiro <mark(a)msapiro.net> > > >> Cc: Mailman-Developers(a)python.org > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > >> Precedenceheader > > >> Message-ID: > > >> < > > >> CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg(a)mail.gmail.com> > > >> Content-Type: text/plain; charset=ISO-8859-1 > > >> > > >> Mark Sapiro <mark(a)msapiro.net> wrote: > > >> > > >> > > > >> > Which means that bin/disabled.py won't work because it hasn't been > > >> > fully converted from 2.1 yet. It should be using the send_probe() > > >> > function instead of sendNextNotification(). > > >> > > > >> > > >> Yes. I also think so. I have changed the function to send_probe() and > ran > > >> through all the test again to make sure that nothing breaks. > > >> > > >> > > >> > > > >> > There should be two places. bin/disabled.py should be calling > > >> > send_probe() instead of the non-existent sendNextNotification() list > > >> > method. > > >> > > > >> > Also, send_probe() should be called when delivery is initially > disabled > > >> > as a result of a call to IBounceProcessor(), but I am unable to > follow > > >> > how this works or even if it is implemented yet at least in part > > >> > because I haven't yet learned anything about how things like > > >> > zope.component.getUtility() work. > > >> > > > >> > > >> I am also not able to find out the relevant code, as i am completely > new > > >> to > > >> the flow of how mailman works. Maybe, barry can help me on this one. > > >> > > >> > > > >> > > > >> > The patch itself looks good except for style. We normally don't put > > >> > whitespace around the = in keyword=value arguments in definitions > and > > >> > calls. PEP 8 <http://www.python.org/dev/peps/pep-0008/> says "Don't > > >> > use spaces around the '=' sign when used to indicate a keyword > > >> > argument or a default parameter value." > > >> > > > >> > I will keep this in mind. I have created another branch with partial > > >> changes suggested above. Here, you can find the changes, > > >> > > >> http://bazaar.launchpad.net/~syst3mw0rm/mailman/808821/revision/7080 > > >> > > >> > > >> > > >> -- > > >> Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee > > >> > > >> > > >> ------------------------------ > > >> > > >> Message: 3 > > >> Date: Sat, 18 Feb 2012 10:45:28 -0800 > > >> From: Mark Sapiro <mark(a)msapiro.net> > > >> To: Aamir Khan <syst3m.w0rm(a)gmail.com> > > >> Cc: Mailman-Developers(a)python.org > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > >> Precedenceheader > > >> Message-ID: <PC195201202181045280109fb8c76c9@MSAPIRO> > > >> Content-Type: text/plain; charset=iso-8859-1 > > >> > > >> Aamir Khan wrote: > > >> > > > >> >Mark Sapiro <mark(a)msapiro.net> wrote: > > >> > > > >> >> > > >> >> Which means that bin/disabled.py won't work because it hasn't been > > >> >> fully converted from 2.1 yet. It should be using the send_probe() > > >> >> function instead of sendNextNotification(). > > >> >> > > >> > > > >> >Yes. I also think so. I have changed the function to send_probe() > and ran > > >> >through all the test again to make sure that nothing breaks. > > >> > > >> > > >> I don't think you can simply change mlist.sendNextNotification(member) > > >> to mlist.send_probe(member) because send_probe() is not a list method, > > >> plus it requires a message argument in addition to the member > argument. > > >> > > >> Also, it is apparent that the test suite is not testing > bin/disabled.py > > >> or it would have been failing all along. > > >> > > >> -- > > >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > >> San Francisco Bay Area, California better use your sense - B. Dylan > > >> > > >> > > >> > > >> ------------------------------ > > >> > > >> _______________________________________________ > > >> Mailman-Developers mailing list > > >> Mailman-Developers(a)python.org > > >> http://mail.python.org/mailman/listinfo/mailman-developers > > >> > > >> > > >> End of Mailman-Developers Digest, Vol 274, Issue 10 > > >> *************************************************** > > >> > > > > > > > > _______________________________________________ > > Mailman-Developers mailing list > > Mailman-Developers(a)python.org > > http://mail.python.org/mailman/listinfo/mailman-developers > > Mailman FAQ: http://wiki.list.org/x/AgA3 > > Searchable Archives: > http://www.mail-archive.com/mailman-developers%40python.org/ > > Unsubscribe: > http://mail.python.org/mailman/options/mailman-developers/f%40state-of-mind… > > > > Security Policy: http://wiki.list.org/x/QIA9 > > > > > > > > ------------------------------ > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > http://mail.python.org/mailman/listinfo/mailman-developers > > > End of Mailman-Developers Digest, Vol 274, Issue 12 > *************************************************** >

1 0

Mailman-Developers

February 2012