Mailman 3 February 2012 - Mailman-Developers

Re: [Mailman-Developers] GSOC 12
by Florian Fuchs 20 Feb '12

20 Feb '12

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

1 0

Re: [Mailman-Developers] GSOC 12
by Jagannathan Tiruvallur Eachambadi 20 Feb '12

20 Feb '12

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

1 0

GSOC 12
by Jagannathan Tiruvallur Eachambadi 20 Feb '12

20 Feb '12

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

1 0

Feedback on draft-moonesamy-rfc2369bis-04, draft-moonesamy-rfc2919bis-04 and draft-moonesamy-list-sequence-header-00
by S Moonesamy 20 Feb '12

20 Feb '12

Hello, I would like to have some feedback on draft-moonesamy-rfc2369bis-04, draft-moonesamy-rfc2919bis-04 and draft-moonesamy-list-sequence-header-00. http://www.ietf.org/internet-drafts/draft-moonesamy-rfc2369bis-04.txt http://www.ietf.org/internet-drafts/draft-moonesamy-rfc2919bis-04.txt http://www.ietf.org/internet-drafts/draft-moonesamy-list-sequence-header-00… The changes between RFC 2369 and draft-moonesamy-rfc2369bis-04 are: o URL changed to URI o Replaced MTAs with mailing list managers in the sentence: "MTAs generating the header fields SHOULD". o Replaced MTAs with mailing list managers in the sentence: "MTAs MUST NOT insert whitespace within the brackets" in Section 2 o In Section 2, client application SHOULD ignore whitespace within brackets o Updated references o Added informative reference to RFC 5064 And between RFC 2919 and draft-moonesamy-rfc2919bis-04 are: o Removed text about the domain name system and domain ownership in Section 2 o "localhost" replaced with "invalid" o Replaced MTAs with mailing list managers in the sentence: "MTAs MUST NOT insert whitespace within the brackets" in Section 3 o Case independence in Section 6 changed to case insensitivity for ASCII o Added a paragraph in the appendix about subject tags o Updated references draft-moonesamy-list-sequence-header-00 provides a standard location for identifying the sequence position of an individual message for a mailing list. Thanks, S. Moonesamy

1 0

Re: [Mailman-Developers] Probe messages should not sent Precedenceheader
by Mark Sapiro 18 Feb '12

18 Feb '12

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

1 0

Re: [Mailman-Developers] Probe messages should not sent Precedenceheader
by Mark Sapiro 18 Feb '12

18 Feb '12

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

2 1

Re: [Mailman-Developers] Probe messages should not sent Precedenceheader
by Mark Sapiro 18 Feb '12

18 Feb '12

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. > > >Am i on correct path ? I think you are at the start of a twisted path. I'm sorry, but I'm still not completely up to speed with mm3, but here's what I can tell you from 2.1. In 2.1, cron/disabled which I think is analogous to bin/disabled.py sends warnings, but it is not the only thing which does. Warnings are actually sent by the list method sendNextNotification() which is defined in 2.1 in Mailman/Bouncer.py. The sendNextNotification() method in turn uses the UserNotification() class defined in Mailman/Message.py to actually create and send the message. The UserNotification.send() method will add a "Precedence: bulk" header to any message which doesn't have any Precedence: header. Thus, there are two possible approaches. One approach is to add a noprecedence argument to the send() method with default = False, and in the method itself skip adding the Precedence: bulk header if noprecedence is true, and add a noprecedence=True argument to the call to the send() method in sendNextNotification(). A second approach would be to add a Precedence: normal or first-class header to the message object before calling send(), but since the use of Precedence: is discouraged and there is no standard definition of its values (RFC 2076), I think and argument to supress the header entirely is preferable. I'll make that fix for 2.1. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Probe messages should not sent Precedence header
by Aamir Khan 18 Feb '12

18 Feb '12

Hi, 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. Am i on correct path ? -- Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee

1 0

Re: [Mailman-Developers] Error while setting up mailman UI
by Florian Fuchs 17 Feb '12

17 Feb '12

Hi, On Friday, February 17, 2012 17:13 CET, Aamir Khan <syst3m.w0rm(a)gmail.com> wrote: > Hi, > > I tried to create a virtualEnv in python and start the installation from > scratch. But i a still getting the errors. Screenshot is attached. I also > tried running the tests and many tests failed. One of the dominant error > was, > > "ImproperlyConfigured: Module "mailman_django.context_processors" does not > define a "lists_of_domain" callable request processor" You can find an up to date (and tested) version of the settings.py in lp:~flo-fuchs/mailmanweb/django_dev_setup If you update to the latest version it *should* work now. Cheers Florian > > > On Fri, Feb 17, 2012 at 5:48 AM, Florian Fuchs <f(a)state-of-mind.de> wrote: > > > Hi, > > > > On Friday, February 17, 2012 00:40 CET, Aamir Khan <syst3m.w0rm(a)gmail.com> > > wrote: > > > > > > REST_SERVER = 'http://localhost:8001' > > > > > > > I guess that should be, > > > > > > REST_SERVER = 'http://localhost:8000' because the django app runs on > > 8000 > > > port. > > > > Yep, the Django dev server runs on port 8000. But the REST_SERVER setting > > refers to the Mailman API which usually runs on port 8001. Did you try > > that, too? > > Also, did you start mailman by running 'bin/mailman start' from your > > mailman directory? > > > > If that doesn't work, you could try and run the wui tests: > > > > 1) stop mailman ('bin/mailman stop' from inside your mailman dir) > > 2) set MAILMAN_TEST_BINDIR in your settings.py (full path to: > > .../mailman/bin) > > 3) from the folder where the settings.py lives run: 'python manage.py test' > > > > If the tests run through you know the web ui is setup correctly and can > > talk to the mailman REST API. > > If they don't the output should give us a hint where the problem might > > be... > > > > I hope that helps... > > > > Florian > > > > > > > > > > When, changing it to above line, the URL 'http://localhost:8000' takes > > > forever to load but at least no error popped out. > > > > > > > > > > > where it probably now says: > > > > > > > > REST_SERVER = 'localhost:8001' > > > > > > > > (missing url scheme...) > > > > > > > > Sorry for not having updated the settings-branch on launchpad > > earlier... > > > > :-/ > > > > > > > > Is this solving the problem? > > > > > > > > (If you have any further questions please don't hesitate to contact me > > via > > > > mail or on irc - florianf on freenode.) > > > > > > > > Cheers > > > > Florian > > > > > > > > > > > > > > > > On Thursday, February 16, 2012 17:54 CET, Aamir Khan < > > > > syst3m.w0rm(a)gmail.com> wrote: > > > > > > > > > Hi, > > > > > > > > > > I am getting error while trying to setup mailman UI by following the > > > > guide > > > > > of setting up mailman web UI running[0]. > > > > > > > > > > I have attached the screenshot of the same. Any help will be > > appreciated. > > > > > > > > > > [0] => > > > > > > > > > > > http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI… > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > 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 > > > > > > > > > > > > > > > -- > Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee

2 1

Add the equivalent of postconf
by Aamir Khan 17 Feb '12

17 Feb '12

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 ? -- Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee

1 0