From terri at zone12.com Mon Feb 6 22:19:23 2012 From: terri at zone12.com (Terri Oda) Date: Mon, 06 Feb 2012 14:19:23 -0700 Subject: [Mailman-Developers] GSoC 2012 Message-ID: <4F3043DB.1030707@zone12.com> So, GSoC applications have opened... so I've started a wiki page for us to capture project ideas as we get them formed: http://wiki.list.org/display/DEV/Google+Summer+of+Code+2012 One of the things I'd like to see is getting a student to move forwards with integrating BrowserID into Mailman, which some of us have discussed already. I'd like to see some more work done on the UI as well, but just saying that is nebulous. What more specific targeted projects do we have? I'd like to see integration of the search code we have from a previous GSoC into the archives, for example. What else do we have that's feasible for a student over a 4 month period? Terri From barry at list.org Fri Feb 10 03:12:33 2012 From: barry at list.org (Barry Warsaw) Date: Thu, 9 Feb 2012 21:12:33 -0500 Subject: [Mailman-Developers] GSoC 2012 In-Reply-To: <4F3043DB.1030707@zone12.com> References: <4F3043DB.1030707@zone12.com> Message-ID: <20120209211233.729086d8@resist.wooz.org> On Feb 06, 2012, at 02:19 PM, Terri Oda wrote: >So, GSoC applications have opened... so I've started a wiki page for us to >capture project ideas as we get them formed: > >http://wiki.list.org/display/DEV/Google+Summer+of+Code+2012 Thanks for taking this on Terri. >One of the things I'd like to see is getting a student to move forwards with >integrating BrowserID into Mailman, which some of us have discussed already. Yep, that would be a great project. I know there's some controversy around BrowserID (already), but it's worth investigating. OpenID is I suppose another thing to look at. >I'd like to see some more work done on the UI as well, but just saying that >is nebulous. What more specific targeted projects do we have? I'd like to >see integration of the search code we have from a previous GSoC into the >archives, for example. What else do we have that's feasible for a student >over a 4 month period? I think we'll have a much better idea about specifics after the Pycon sprint. I'd like that to be really focused on integrating the web ui with the core. Another thing to look at (added to the wiki page) is Grackle, which is an archiver framework that the Launchpad folks are working on. MHonArc is problematic for them, and clearly Pipermail is ancient. Grackle's approach again is to provide a REST API to an underlying archiver, so that the actual rendering can happen separately from storage, threading, etc. Plus, it's AGPL. -Barry From syst3m.w0rm at gmail.com Mon Feb 13 02:03:51 2012 From: syst3m.w0rm at gmail.com (Aamir Khan) Date: Mon, 13 Feb 2012 06:33:51 +0530 Subject: [Mailman-Developers] Hello Message-ID: Hi all, I am undergraduate student at IIT Roorkee. I am looking forward to contribute to Mailman project. I?ve used Git and SVN before; BZR will be new to me. I?m looking forward to contribute to the project. From barry at list.org Mon Feb 13 21:35:58 2012 From: barry at list.org (Barry Warsaw) Date: Mon, 13 Feb 2012 15:35:58 -0500 Subject: [Mailman-Developers] Hello In-Reply-To: References: Message-ID: <20120213153558.18f2b4c0@resist.wooz.org> On Feb 13, 2012, at 06:33 AM, Aamir Khan wrote: > I am undergraduate student at IIT Roorkee. I am looking forward to >contribute to Mailman project. Hi Aamir. > I?ve used Git and SVN before; BZR will be new to me. If you're familiar with git and svn, you shouldn't have too much trouble with bzr. You can always ask here or in #mailman on freenode. > I?m looking forward to contribute to the project. Me too! What are you interested in? Cheers, -Barry From syst3m.w0rm at gmail.com Thu Feb 16 17:53:04 2012 From: syst3m.w0rm at gmail.com (Aamir Khan) Date: Thu, 16 Feb 2012 22:23:04 +0530 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: References: Message-ID: Hi, 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. -- Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee From syst3m.w0rm at gmail.com Thu Feb 16 19:10:56 2012 From: syst3m.w0rm at gmail.com (Aamir Khan) Date: Thu, 16 Feb 2012 23:40:56 +0530 Subject: [Mailman-Developers] Grackle archive framework Message-ID: Hi, 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 ? -- Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee From barry at list.org Thu Feb 16 20:25:16 2012 From: barry at list.org (Barry Warsaw) Date: Thu, 16 Feb 2012 14:25:16 -0500 Subject: [Mailman-Developers] Grackle archive framework In-Reply-To: References: Message-ID: <20120216142516.69c8fbc3@resist.wooz.org> 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 From barry at list.org Thu Feb 16 20:26:08 2012 From: barry at list.org (Barry Warsaw) Date: Thu, 16 Feb 2012 14:26:08 -0500 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: References: Message-ID: <20120216142608.3449c939@resist.wooz.org> 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 From syst3m.w0rm at gmail.com Thu Feb 16 17:54:01 2012 From: syst3m.w0rm at gmail.com (Aamir Khan) Date: Thu, 16 Feb 2012 22:24:01 +0530 Subject: [Mailman-Developers] Error while setting up mailman UI In-Reply-To: References: Message-ID: 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+running -- Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee -------------- next part -------------- A non-text attachment was scrubbed... Name: mailman-error.png Type: image/png Size: 151943 bytes Desc: not available URL: From f at state-of-mind.de Fri Feb 17 00:02:03 2012 From: f at state-of-mind.de (Florian Fuchs) Date: Fri, 17 Feb 2012 00:02:03 +0100 Subject: [Mailman-Developers] Error while setting up mailman UI In-Reply-To: Message-ID: <1339-4f3d8b00-3-5fc04d00@119162885> Hi Aamir, thanks for being interested in MM3 and its web ui! A small change I recently made to the default settings seems to be the cause of the error message: In line 32 of your settings.py it should say: REST_SERVER = 'http://localhost:8001' 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 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+running > > > > > -- > Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee From syst3m.w0rm at gmail.com Fri Feb 17 00:40:03 2012 From: syst3m.w0rm at gmail.com (Aamir Khan) Date: Fri, 17 Feb 2012 05:10:03 +0530 Subject: [Mailman-Developers] Error while setting up mailman UI In-Reply-To: <1339-4f3d8b00-3-5fc04d00@119162885> References: <1339-4f3d8b00-3-5fc04d00@119162885> Message-ID: On Fri, Feb 17, 2012 at 4:32 AM, Florian Fuchs wrote: > Hi Aamir, > > thanks for being interested in MM3 and its web ui! > > A small change I recently made to the default settings seems to be the > cause of the error message: > In line 32 of your settings.py it should say: > > REST_SERVER = 'http://localhost:8001' > I guess that should be, REST_SERVER = 'http://localhost:8000' because the django app runs on 8000 port. 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 at 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+running > > > > > > > > > > -- > > Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee > > > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at 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%40gmail.com > > Security Policy: http://wiki.list.org/x/QIA9 > -- Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee From f at state-of-mind.de Fri Feb 17 01:18:56 2012 From: f at state-of-mind.de (Florian Fuchs) Date: Fri, 17 Feb 2012 01:18:56 +0100 Subject: [Mailman-Developers] Error while setting up mailman UI In-Reply-To: Message-ID: <133a-4f3d9d00-7-67165380@259298745> Hi, On Friday, February 17, 2012 00:40 CET, Aamir Khan 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 at 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+running > > > > > > > > > > > > > > > -- > > > Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee > > > > > > > > > > > > _______________________________________________ > > Mailman-Developers mailing list > > Mailman-Developers at 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%40gmail.com > > > > Security Policy: http://wiki.list.org/x/QIA9 > > > > > > -- > Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee From syst3m.w0rm at gmail.com Fri Feb 17 17:13:55 2012 From: syst3m.w0rm at gmail.com (Aamir Khan) Date: Fri, 17 Feb 2012 21:43:55 +0530 Subject: [Mailman-Developers] Error while setting up mailman UI In-Reply-To: <133a-4f3d9d00-7-67165380@259298745> References: <133a-4f3d9d00-7-67165380@259298745> Message-ID: 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" On Fri, Feb 17, 2012 at 5:48 AM, Florian Fuchs wrote: > Hi, > > On Friday, February 17, 2012 00:40 CET, Aamir Khan > 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 at 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+running > > > > > > > > > > > > > > > > > > > > -- > > > > Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Mailman-Developers mailing list > > > Mailman-Developers at 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%40gmail.com > > > > > > 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: mailman-2.png Type: image/png Size: 175363 bytes Desc: not available URL: From syst3m.w0rm at gmail.com Fri Feb 17 18:39:24 2012 From: syst3m.w0rm at gmail.com (Aamir Khan) Date: Fri, 17 Feb 2012 23:09:24 +0530 Subject: [Mailman-Developers] Add the equivalent of postconf Message-ID: 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 From f at state-of-mind.de Fri Feb 17 18:50:35 2012 From: f at state-of-mind.de (Florian Fuchs) Date: Fri, 17 Feb 2012 18:50:35 +0100 Subject: [Mailman-Developers] Error while setting up mailman UI In-Reply-To: Message-ID: <6872-4f3e9380-7-15ac3c8@155515133> Hi, On Friday, February 17, 2012 17:13 CET, Aamir Khan 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 wrote: > > > Hi, > > > > On Friday, February 17, 2012 00:40 CET, Aamir Khan > > 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 at 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+running > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Mailman-Developers mailing list > > > > Mailman-Developers at 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%40gmail.com > > > > > > > > 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 From syst3m.w0rm at gmail.com Fri Feb 17 18:58:24 2012 From: syst3m.w0rm at gmail.com (Aamir Khan) Date: Fri, 17 Feb 2012 23:28:24 +0530 Subject: [Mailman-Developers] Error while setting up mailman UI In-Reply-To: <6872-4f3e9380-7-15ac3c8@155515133> References: <6872-4f3e9380-7-15ac3c8@155515133> Message-ID: On Fri, Feb 17, 2012 at 11:20 PM, Florian Fuchs wrote: > Hi, > > On Friday, February 17, 2012 17:13 CET, Aamir Khan > 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. > Awesome, It worked!! Thanks a lot! > > Cheers > Florian > > > > > > > > On Fri, Feb 17, 2012 at 5:48 AM, Florian Fuchs > wrote: > > > > > Hi, > > > > > > On Friday, February 17, 2012 00:40 CET, Aamir Khan < > syst3m.w0rm at 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 at 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+running > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Aamir Khan | 3rd Year | Computer Science & Engineering | IIT > Roorkee > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Mailman-Developers mailing list > > > > > Mailman-Developers at 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%40gmail.com > > > > > > > > > > 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 > > > > > > -- Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee From f at state-of-mind.de Fri Feb 17 20:41:44 2012 From: f at state-of-mind.de (Florian Fuchs) Date: Fri, 17 Feb 2012 20:41:44 +0100 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <20120216142608.3449c939@resist.wooz.org> Message-ID: <6871-4f3ead80-1-12d4d3c0@103509804> Hi, > 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. I haven't had the opportunity to implement browserid on a website so far, but here are a few random thoughts on the subject: 1) Browserid is very convenient, but I wouldn't rely on it as the only means to log into the MM web ui. It relies on client-side code to be run, which has a lot of advantages usability-wise but also has some accessibility pitfalls. I don't think that's a reason *not* to implement browserid, but probably more as one of more auth-methods that site admins can choose when setting up their installation of mailman. 2) The server-side verification part of their example application [1] is done using node.js. I think creating a similar thing in python and making a django AuthBackend out of it could be a very nice task. A quick search brought up two django-browserid implementations ([2], [3]), but in both cases I'm not sure if this is how we would do it in our web ui. (Both are stand-alone reusable apps - I think we'd rather integrate something like that directly as part of our app code. But that's probably debatable...). 3) If this is too small a task for the whole summer I think it could be made part of a slightly larger login/user-related package. The wiki page for last year's GHC11 Open source day [4] describes some ideas that could fit in nicely (for example storing some additional user info, like their twitter account, ... see section "Subscriber info summary"). As I said these are random thoughts... Cheers Florian [1] https://github.com/lloyd/myfavoritebeer.org/ [2] https://github.com/mozilla/django-browserid [3] https://github.com/mozilla/django-browserid [4] http://wiki.list.org/display/DEV/Notes+from+the+GHC11+Open+Source+Day > > -Barry > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at 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.de > > Security Policy: http://wiki.list.org/x/QIA9 From f at state-of-mind.de Fri Feb 17 20:49:03 2012 From: f at state-of-mind.de (Florian Fuchs) Date: Fri, 17 Feb 2012 20:49:03 +0100 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <6871-4f3ead80-1-12d4d3c0@103509804> Message-ID: <6872-4f3eaf00-d-15ac3c8@155515136> On Friday, February 17, 2012 20:41 CET, "Florian Fuchs" wrote: > [1] https://github.com/lloyd/myfavoritebeer.org/ > [2] https://github.com/mozilla/django-browserid > [3] https://github.com/mozilla/django-browserid Sorry, I posted the second link twice. That should be: https://github.com/omab/django-social-auth Florian > > > > > > -Barry > > _______________________________________________ > > Mailman-Developers mailing list > > Mailman-Developers at 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.de > > > > Security Policy: http://wiki.list.org/x/QIA9 > > > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at 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.de > > Security Policy: http://wiki.list.org/x/QIA9 From richard at NFSNet.org Fri Feb 17 21:59:08 2012 From: richard at NFSNet.org (Richard Wackerbarth) Date: Fri, 17 Feb 2012 14:59:08 -0600 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <6871-4f3ead80-1-12d4d3c0@103509804> References: <6871-4f3ead80-1-12d4d3c0@103509804> Message-ID: <7E9E4A3A-A73E-4C99-AB5A-E206B2B71432@NFSNet.org> On Feb 17, 2012, at 1:41 PM, Florian Fuchs wrote: > 1) Browserid is very convenient, but I wouldn't rely on it as the only means to log into the MM web ui. I agree. It is a reasonable scheme to support, but we need to have "authentication" done on a "plug-in" basis. Structurally, the underlying design should be completely agnostic to the login mechanism. Since Django already has a User model with all kinds of permissions infrastructure, we should be leveraging off of that (extending the User model as needed) for our UI. MM has two kinds of authentication to perform. BrowserID "solves" both at the same time. First, it establishes that the person on the website is a particular user. But it also "proves" that the email address "belongs" to that user. Thus, with BrowserID, we can allow the user to join a mailing list without having to send the confirming email transaction. On the other hand, that confirming email transaction is basically what the browserid.org site does. Thus, with little effort, MM could also act as a secondary authority for the BrowserID protocol. > It relies on client-side code to be run, which has a lot of advantages usability-wise but also has some accessibility pitfalls. I don't think that's a reason *not* to implement browserid, but probably more as one of more auth-methods that site admins can choose when setting up their installation of mailman. > > 2) The server-side verification part of their example application [1] is done using node.js. I think creating a similar thing in python and making a django AuthBackend out of it could be a very nice task. A quick search brought up two django-browserid implementations ([2], [3]), but in both cases I'm not sure if this is how we would do it in our web ui. (Both are stand-alone reusable apps - I think we'd rather integrate something like that directly as part of our app code. But that's probably debatable...). I'll "debate" the approach. IMHO, we should be leveraging the Django user model and we should not be reimplementing it. If the existing BrowserID implementations fail to provide the necessary functionality, then we should either "fix" one of them or write another implementation which is still generic and could be reused by others. Similarly, authentication schemes such as Kerberos should be able to plug in without caring that they are being used for MM or some other application. > 3) If this is too small a task for the whole summer I think it could be made part of a slightly larger login/user-related package. The wiki page for last year's GHC11 Open source day [4] describes some ideas that could fit in nicely (for example storing some additional user info, like their twitter account, ... see section "Subscriber info summary"). In keeping with current events: > As I said these are random thoughts... Is there enough entropy? :) Richard From syst3m.w0rm at gmail.com Sat Feb 18 02:08:49 2012 From: syst3m.w0rm at gmail.com (Aamir Khan) Date: Sat, 18 Feb 2012 06:38:49 +0530 Subject: [Mailman-Developers] Probe messages should not sent Precedence header Message-ID: Hi, As suggested by Barry, I am working on this new 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 From mark at msapiro.net Sat Feb 18 02:45:07 2012 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 17 Feb 2012 17:45:07 -0800 Subject: [Mailman-Developers] Probe messages should not sent Precedenceheader In-Reply-To: Message-ID: Aamir Khan wrote: > >As suggested by Barry, I am working on this new 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 The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From syst3m.w0rm at gmail.com Sat Feb 18 11:14:23 2012 From: syst3m.w0rm at gmail.com (Aamir Khan) Date: Sat, 18 Feb 2012 15:44:23 +0530 Subject: [Mailman-Developers] Probe messages should not sent Precedenceheader In-Reply-To: References: Message-ID: On Sat, Feb 18, 2012 at 7:15 AM, Mark Sapiro wrote: > Aamir Khan wrote: > > > >As suggested by Barry, I am working on this new 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(). > > 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'. 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. 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 -- Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee From mark at msapiro.net Sat Feb 18 18:22:53 2012 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 18 Feb 2012 09:22:53 -0800 Subject: [Mailman-Developers] Probe messages should not sent Precedenceheader In-Reply-To: Message-ID: 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 says "Don't use spaces around the '=' sign when used to indicate a keyword argument or a default parameter value." -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From syst3m.w0rm at gmail.com Sat Feb 18 18:46:37 2012 From: syst3m.w0rm at gmail.com (Aamir Khan) Date: Sat, 18 Feb 2012 23:16:37 +0530 Subject: [Mailman-Developers] Probe messages should not sent Precedenceheader In-Reply-To: References: Message-ID: Mark Sapiro 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 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 From mark at msapiro.net Sat Feb 18 19:45:28 2012 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 18 Feb 2012 10:45:28 -0800 Subject: [Mailman-Developers] Probe messages should not sent Precedenceheader In-Reply-To: Message-ID: Aamir Khan wrote: > >Mark Sapiro 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 The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From sm+ietf at elandsys.com Mon Feb 20 02:15:06 2012 From: sm+ietf at elandsys.com (S Moonesamy) Date: Sun, 19 Feb 2012 17:15:06 -0800 Subject: [Mailman-Developers] Feedback on draft-moonesamy-rfc2369bis-04, draft-moonesamy-rfc2919bis-04 and draft-moonesamy-list-sequence-header-00 Message-ID: <6.2.5.6.2.20120219165817.09d2acf8@elandnews.com> 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.txt 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 From jagannathante at gmail.com Mon Feb 20 11:40:52 2012 From: jagannathante at gmail.com (Jagannathan Tiruvallur Eachambadi) Date: Mon, 20 Feb 2012 16:10:52 +0530 Subject: [Mailman-Developers] GSOC 12 Message-ID: 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, wrote: > Send Mailman-Developers mailing list submissions to > mailman-developers at 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 at python.org > > You can reach the person managing the list at > mailman-developers-owner at 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 > To: Aamir Khan > Cc: Mailman-Developers at python.org > Subject: Re: [Mailman-Developers] Probe messages should not sent > Precedenceheader > Message-ID: > 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 says "Don't > use spaces around the '=' sign when used to indicate a keyword > argument or a default parameter value." > > -- > Mark Sapiro 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 > To: Mark Sapiro > Cc: Mailman-Developers at python.org > Subject: Re: [Mailman-Developers] Probe messages should not sent > Precedenceheader > Message-ID: > > > Content-Type: text/plain; charset=ISO-8859-1 > > Mark Sapiro 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 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 > To: Aamir Khan > Cc: Mailman-Developers at python.org > Subject: Re: [Mailman-Developers] Probe messages should not sent > Precedenceheader > Message-ID: > Content-Type: text/plain; charset=iso-8859-1 > > Aamir Khan wrote: > > > >Mark Sapiro 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 The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > > ------------------------------ > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at python.org > http://mail.python.org/mailman/listinfo/mailman-developers > > > End of Mailman-Developers Digest, Vol 274, Issue 10 > *************************************************** > From jagannathante at gmail.com Mon Feb 20 11:50:11 2012 From: jagannathante at gmail.com (Jagannathan Tiruvallur Eachambadi) Date: Mon, 20 Feb 2012 16:20:11 +0530 Subject: [Mailman-Developers] GSOC 12 In-Reply-To: References: Message-ID: 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 at 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, wrote: > >> Send Mailman-Developers mailing list submissions to >> mailman-developers at 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 at python.org >> >> You can reach the person managing the list at >> mailman-developers-owner at 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 >> To: Aamir Khan >> Cc: Mailman-Developers at python.org >> Subject: Re: [Mailman-Developers] Probe messages should not sent >> Precedenceheader >> Message-ID: >> 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 says "Don't >> use spaces around the '=' sign when used to indicate a keyword >> argument or a default parameter value." >> >> -- >> Mark Sapiro 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 >> To: Mark Sapiro >> Cc: Mailman-Developers at python.org >> Subject: Re: [Mailman-Developers] Probe messages should not sent >> Precedenceheader >> Message-ID: >> < >> CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg at mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> Mark Sapiro 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 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 >> To: Aamir Khan >> Cc: Mailman-Developers at python.org >> Subject: Re: [Mailman-Developers] Probe messages should not sent >> Precedenceheader >> Message-ID: >> Content-Type: text/plain; charset=iso-8859-1 >> >> Aamir Khan wrote: >> > >> >Mark Sapiro 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 The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> >> >> >> ------------------------------ >> >> _______________________________________________ >> Mailman-Developers mailing list >> Mailman-Developers at python.org >> http://mail.python.org/mailman/listinfo/mailman-developers >> >> >> End of Mailman-Developers Digest, Vol 274, Issue 10 >> *************************************************** >> > > From f at state-of-mind.de Mon Feb 20 17:43:47 2012 From: f at state-of-mind.de (Florian Fuchs) Date: Mon, 20 Feb 2012 17:43:47 +0100 Subject: [Mailman-Developers] GSOC 12 In-Reply-To: Message-ID: <1f3e-4f427880-7-13fbcde0@263897354> 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: /mailmanweb/src/mailman_django/templates/mailman-django/lists/index.html Any luck? Florian On Monday, February 20, 2012 11:50 CET, Jagannathan Tiruvallur Eachambadi 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 at 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, wrote: > > > >> Send Mailman-Developers mailing list submissions to > >> mailman-developers at 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 at python.org > >> > >> You can reach the person managing the list at > >> mailman-developers-owner at 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 > >> To: Aamir Khan > >> Cc: Mailman-Developers at python.org > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > >> Precedenceheader > >> Message-ID: > >> 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 says "Don't > >> use spaces around the '=' sign when used to indicate a keyword > >> argument or a default parameter value." > >> > >> -- > >> Mark Sapiro 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 > >> To: Mark Sapiro > >> Cc: Mailman-Developers at python.org > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > >> Precedenceheader > >> Message-ID: > >> < > >> CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg at mail.gmail.com> > >> Content-Type: text/plain; charset=ISO-8859-1 > >> > >> Mark Sapiro 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 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 > >> To: Aamir Khan > >> Cc: Mailman-Developers at python.org > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > >> Precedenceheader > >> Message-ID: > >> Content-Type: text/plain; charset=iso-8859-1 > >> > >> Aamir Khan wrote: > >> > > >> >Mark Sapiro 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 The highway is for gamblers, > >> San Francisco Bay Area, California better use your sense - B. Dylan > >> > >> > >> > >> ------------------------------ > >> > >> _______________________________________________ > >> Mailman-Developers mailing list > >> Mailman-Developers at 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 at 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.de > > Security Policy: http://wiki.list.org/x/QIA9 From barry at list.org Mon Feb 20 19:49:55 2012 From: barry at list.org (Barry Warsaw) Date: Mon, 20 Feb 2012 13:49:55 -0500 Subject: [Mailman-Developers] Probe messages should not sent Precedence header In-Reply-To: References: Message-ID: <20120220134955.2a4f28dd@resist.wooz.org> On Feb 18, 2012, at 06:38 AM, Aamir Khan wrote: >As suggested by Barry, I am working on this new 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 From jagannathante at gmail.com Mon Feb 20 19:52:06 2012 From: jagannathante at gmail.com (Jagannathan Tiruvallur Eachambadi) Date: Tue, 21 Feb 2012 00:22:06 +0530 Subject: [Mailman-Developers] Mailman-Developers Digest, Vol 274, Issue 12 In-Reply-To: References: Message-ID: 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, wrote: > Send Mailman-Developers mailing list submissions to > mailman-developers at 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 at python.org > > You can reach the person managing the list at > mailman-developers-owner at 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 > To: mailman-developers at python.org > Subject: [Mailman-Developers] GSOC 12 > Message-ID: > > > 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, >wrote: > > > Send Mailman-Developers mailing list submissions to > > mailman-developers at 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 at python.org > > > > You can reach the person managing the list at > > mailman-developers-owner at 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 > > To: Aamir Khan > > Cc: Mailman-Developers at python.org > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > Precedenceheader > > Message-ID: > > 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 says "Don't > > use spaces around the '=' sign when used to indicate a keyword > > argument or a default parameter value." > > > > -- > > Mark Sapiro 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 > > To: Mark Sapiro > > Cc: Mailman-Developers at python.org > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > Precedenceheader > > Message-ID: > > < > CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg at mail.gmail.com > > > > > Content-Type: text/plain; charset=ISO-8859-1 > > > > Mark Sapiro 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 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 > > To: Aamir Khan > > Cc: Mailman-Developers at python.org > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > Precedenceheader > > Message-ID: > > Content-Type: text/plain; charset=iso-8859-1 > > > > Aamir Khan wrote: > > > > > >Mark Sapiro 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 The highway is for gamblers, > > San Francisco Bay Area, California better use your sense - B. Dylan > > > > > > > > ------------------------------ > > > > _______________________________________________ > > Mailman-Developers mailing list > > Mailman-Developers at 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 > To: mailman-developers at python.org > Subject: Re: [Mailman-Developers] GSOC 12 > Message-ID: > > > 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 at 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, >wrote: > > > >> Send Mailman-Developers mailing list submissions to > >> mailman-developers at 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 at python.org > >> > >> You can reach the person managing the list at > >> mailman-developers-owner at 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 > >> To: Aamir Khan > >> Cc: Mailman-Developers at python.org > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > >> Precedenceheader > >> Message-ID: > >> 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 says "Don't > >> use spaces around the '=' sign when used to indicate a keyword > >> argument or a default parameter value." > >> > >> -- > >> Mark Sapiro 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 > >> To: Mark Sapiro > >> Cc: Mailman-Developers at python.org > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > >> Precedenceheader > >> Message-ID: > >> < > >> CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg at mail.gmail.com> > >> Content-Type: text/plain; charset=ISO-8859-1 > >> > >> Mark Sapiro 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 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 > >> To: Aamir Khan > >> Cc: Mailman-Developers at python.org > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > >> Precedenceheader > >> Message-ID: > >> Content-Type: text/plain; charset=iso-8859-1 > >> > >> Aamir Khan wrote: > >> > > >> >Mark Sapiro 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 The highway is for gamblers, > >> San Francisco Bay Area, California better use your sense - B. Dylan > >> > >> > >> > >> ------------------------------ > >> > >> _______________________________________________ > >> Mailman-Developers mailing list > >> Mailman-Developers at 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" > To: "Jagannathan Tiruvallur Eachambadi" > Cc: mailman-developers at python.org > Subject: Re: [Mailman-Developers] GSOC 12 > Message-ID: <1f3e-4f427880-7-13fbcde0 at 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: > > > /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 at 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 at 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 at python.org>wrote: > > > > > >> Send Mailman-Developers mailing list submissions to > > >> mailman-developers at 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 at python.org > > >> > > >> You can reach the person managing the list at > > >> mailman-developers-owner at 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 > > >> To: Aamir Khan > > >> Cc: Mailman-Developers at python.org > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > >> Precedenceheader > > >> Message-ID: > > >> 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 says "Don't > > >> use spaces around the '=' sign when used to indicate a keyword > > >> argument or a default parameter value." > > >> > > >> -- > > >> Mark Sapiro 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 > > >> To: Mark Sapiro > > >> Cc: Mailman-Developers at python.org > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > >> Precedenceheader > > >> Message-ID: > > >> < > > >> CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg at mail.gmail.com> > > >> Content-Type: text/plain; charset=ISO-8859-1 > > >> > > >> Mark Sapiro 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 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 > > >> To: Aamir Khan > > >> Cc: Mailman-Developers at python.org > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > >> Precedenceheader > > >> Message-ID: > > >> Content-Type: text/plain; charset=iso-8859-1 > > >> > > >> Aamir Khan wrote: > > >> > > > >> >Mark Sapiro 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 The highway is for gamblers, > > >> San Francisco Bay Area, California better use your sense - B. Dylan > > >> > > >> > > >> > > >> ------------------------------ > > >> > > >> _______________________________________________ > > >> Mailman-Developers mailing list > > >> Mailman-Developers at 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 at 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.de > > > > Security Policy: http://wiki.list.org/x/QIA9 > > > > > > > > ------------------------------ > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at python.org > http://mail.python.org/mailman/listinfo/mailman-developers > > > End of Mailman-Developers Digest, Vol 274, Issue 12 > *************************************************** > From syst3m.w0rm at gmail.com Mon Feb 20 19:54:48 2012 From: syst3m.w0rm at gmail.com (Aamir Khan) Date: Tue, 21 Feb 2012 00:24:48 +0530 Subject: [Mailman-Developers] Probe messages should not sent Precedence header In-Reply-To: <20120220134955.2a4f28dd@resist.wooz.org> References: <20120220134955.2a4f28dd@resist.wooz.org> Message-ID: On Tue, Feb 21, 2012 at 12:19 AM, Barry Warsaw wrote: > On Feb 18, 2012, at 06:38 AM, Aamir Khan wrote: > > >As suggested by Barry, I am working on this new 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 at 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%40gmail.com > > Security Policy: http://wiki.list.org/x/QIA9 > -- Aamir Khan | 3rd Year | Computer Science & Engineering | IIT Roorkee From f at state-of-mind.de Mon Feb 20 23:57:20 2012 From: f at state-of-mind.de (Florian Fuchs) Date: Mon, 20 Feb 2012 23:57:20 +0100 Subject: [Mailman-Developers] Mailman-Developers Digest, Vol 274, Issue 12 In-Reply-To: Message-ID: <313a-4f42d000-1-5047fc00@93635954> 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 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, wrote: > > > Send Mailman-Developers mailing list submissions to > > mailman-developers at 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 at python.org > > > > You can reach the person managing the list at > > mailman-developers-owner at 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 > > To: mailman-developers at python.org > > Subject: [Mailman-Developers] GSOC 12 > > Message-ID: > > > > > > 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, > >wrote: > > > > > Send Mailman-Developers mailing list submissions to > > > mailman-developers at 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 at python.org > > > > > > You can reach the person managing the list at > > > mailman-developers-owner at 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 > > > To: Aamir Khan > > > Cc: Mailman-Developers at python.org > > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > > Precedenceheader > > > Message-ID: > > > 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 says "Don't > > > use spaces around the '=' sign when used to indicate a keyword > > > argument or a default parameter value." > > > > > > -- > > > Mark Sapiro 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 > > > To: Mark Sapiro > > > Cc: Mailman-Developers at python.org > > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > > Precedenceheader > > > Message-ID: > > > < > > CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg at mail.gmail.com > > > > > > > Content-Type: text/plain; charset=ISO-8859-1 > > > > > > Mark Sapiro 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 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 > > > To: Aamir Khan > > > Cc: Mailman-Developers at python.org > > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > > Precedenceheader > > > Message-ID: > > > Content-Type: text/plain; charset=iso-8859-1 > > > > > > Aamir Khan wrote: > > > > > > > >Mark Sapiro 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 The highway is for gamblers, > > > San Francisco Bay Area, California better use your sense - B. Dylan > > > > > > > > > > > > ------------------------------ > > > > > > _______________________________________________ > > > Mailman-Developers mailing list > > > Mailman-Developers at 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 > > To: mailman-developers at python.org > > Subject: Re: [Mailman-Developers] GSOC 12 > > Message-ID: > > > > > > 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 at 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, > >wrote: > > > > > >> Send Mailman-Developers mailing list submissions to > > >> mailman-developers at 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 at python.org > > >> > > >> You can reach the person managing the list at > > >> mailman-developers-owner at 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 > > >> To: Aamir Khan > > >> Cc: Mailman-Developers at python.org > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > >> Precedenceheader > > >> Message-ID: > > >> 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 says "Don't > > >> use spaces around the '=' sign when used to indicate a keyword > > >> argument or a default parameter value." > > >> > > >> -- > > >> Mark Sapiro 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 > > >> To: Mark Sapiro > > >> Cc: Mailman-Developers at python.org > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > >> Precedenceheader > > >> Message-ID: > > >> < > > >> CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg at mail.gmail.com> > > >> Content-Type: text/plain; charset=ISO-8859-1 > > >> > > >> Mark Sapiro 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 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 > > >> To: Aamir Khan > > >> Cc: Mailman-Developers at python.org > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > >> Precedenceheader > > >> Message-ID: > > >> Content-Type: text/plain; charset=iso-8859-1 > > >> > > >> Aamir Khan wrote: > > >> > > > >> >Mark Sapiro 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 The highway is for gamblers, > > >> San Francisco Bay Area, California better use your sense - B. Dylan > > >> > > >> > > >> > > >> ------------------------------ > > >> > > >> _______________________________________________ > > >> Mailman-Developers mailing list > > >> Mailman-Developers at 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" > > To: "Jagannathan Tiruvallur Eachambadi" > > Cc: mailman-developers at python.org > > Subject: Re: [Mailman-Developers] GSOC 12 > > Message-ID: <1f3e-4f427880-7-13fbcde0 at 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: > > > > > > /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 at 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 at 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 at python.org>wrote: > > > > > > > >> Send Mailman-Developers mailing list submissions to > > > >> mailman-developers at 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 at python.org > > > >> > > > >> You can reach the person managing the list at > > > >> mailman-developers-owner at 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 > > > >> To: Aamir Khan > > > >> Cc: Mailman-Developers at python.org > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > >> Precedenceheader > > > >> Message-ID: > > > >> 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 says "Don't > > > >> use spaces around the '=' sign when used to indicate a keyword > > > >> argument or a default parameter value." > > > >> > > > >> -- > > > >> Mark Sapiro 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 > > > >> To: Mark Sapiro > > > >> Cc: Mailman-Developers at python.org > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > >> Precedenceheader > > > >> Message-ID: > > > >> < > > > >> CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg at mail.gmail.com> > > > >> Content-Type: text/plain; charset=ISO-8859-1 > > > >> > > > >> Mark Sapiro 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 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 > > > >> To: Aamir Khan > > > >> Cc: Mailman-Developers at python.org > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > >> Precedenceheader > > > >> Message-ID: > > > >> Content-Type: text/plain; charset=iso-8859-1 > > > >> > > > >> Aamir Khan wrote: > > > >> > > > > >> >Mark Sapiro 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 The highway is for gamblers, > > > >> San Francisco Bay Area, California better use your sense - B. Dylan > > > >> > > > >> > > > >> > > > >> ------------------------------ > > > >> > > > >> _______________________________________________ > > > >> Mailman-Developers mailing list > > > >> Mailman-Developers at 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 at 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.de > > > > > > Security Policy: http://wiki.list.org/x/QIA9 > > > > > > > > > > > > > > > > ------------------------------ > > > > _______________________________________________ > > Mailman-Developers mailing list > > Mailman-Developers at 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 at 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.de > > Security Policy: http://wiki.list.org/x/QIA9 From f at state-of-mind.de Tue Feb 21 02:00:40 2012 From: f at state-of-mind.de (Florian Fuchs) Date: Tue, 21 Feb 2012 02:00:40 +0100 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <7E9E4A3A-A73E-4C99-AB5A-E206B2B71432@NFSNet.org> Message-ID: <34f7-4f42ec80-1-eee5a50@63575587> Hi Richard, On Friday, February 17, 2012 21:59 CET, Richard Wackerbarth wrote: > I agree. It is a reasonable scheme to support, but we need to have "authentication" done on a "plug-in" basis. Structurally, the underlying design should be completely agnostic to the login mechanism. > > Since Django already has a User model with all kinds of permissions infrastructure, we should be leveraging off of that (extending the User model as needed) for our UI. Agreed. Django's User model most definitely covers all our needs. The thing I am not sure about is: What kind of user info ends up in the core DB and what should be stored in the web ui db. In theory we don't need any kind of permanent storage in the web ui, because the core already has a pretty comprehensive user model (storing user names, email addresses, roles, memberships etc). OTOH it could make great sense to enhance this data with all kinds of crazy things that could be stored in the web ui. Or to store some user data temporarily to reduce API calls. But this means we'd have two different data sources since the web ui should not access the core db directly. > MM has two kinds of authentication to perform. BrowserID "solves" both at the same time. > First, it establishes that the person on the website is a particular user. But it also "proves" that the email address "belongs" to that user. Thus, with BrowserID, we can allow the user to join a mailing list without having to send the confirming email transaction. Yep, very convenient. The process would be initiated via the client-JS and verified server-side in the django-backend. Without ever touching the REST API. > On the other hand, that confirming email transaction is basically what the browserid.org site does. Thus, with little effort, MM could also act as a secondary authority for the BrowserID protocol. I think Barry has had some similar ideas... > > 2) The server-side verification part of their example application [1] is done using node.js. I think creating a similar thing in python and making a django AuthBackend out of it could be a very nice task. A quick search brought up two django-browserid implementations ([2], [3]), but in both cases I'm not sure if this is how we would do it in our web ui. (Both are stand-alone reusable apps - I think we'd rather integrate something like that directly as part of our app code. But that's probably debatable...). > > I'll "debate" the approach. IMHO, we should be leveraging the Django user model and we should not be reimplementing it. If the existing BrowserID implementations fail to provide the necessary functionality, then we should either "fix" one of them or write another implementation which is still generic and could be reused by others. I agree, no re-implementing the User model! In fact, I think we mean the same thing, because django's custom auth backends are simply a way to handle auth externally *and* tie that to the existing user/permissions system. Of course, if we implement such a custom backend we should do it in a generic and reusable way. I just think making a full-blown django app for what is usually just a .py file might be a bit overkill... But as I said: debatable... ;-) I guess in the end it's not a question of whether or not we make use of the Django User model. (At least to me) the question is: Do we use it to store user data permamently in the web ui or just temporarily on a request/session basis. Or a mix of both. > In keeping with current events: > > > As I said these are random thoughts... > > Is there enough entropy? :) Well, not completely random, I guess ;-) Florian From barry at list.org Tue Feb 21 02:28:14 2012 From: barry at list.org (Barry Warsaw) Date: Mon, 20 Feb 2012 20:28:14 -0500 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <34f7-4f42ec80-1-eee5a50@63575587> References: <7E9E4A3A-A73E-4C99-AB5A-E206B2B71432@NFSNet.org> <34f7-4f42ec80-1-eee5a50@63575587> Message-ID: <20120220202814.40244abb@resist.wooz.org> On Feb 21, 2012, at 02:00 AM, Florian Fuchs wrote: >Agreed. Django's User model most definitely covers all our needs. The thing I >am not sure about is: What kind of user info ends up in the core DB and what >should be stored in the web ui db. In theory we don't need any kind of >permanent storage in the web ui, because the core already has a pretty >comprehensive user model (storing user names, email addresses, roles, >memberships etc). OTOH it could make great sense to enhance this data with >all kinds of crazy things that could be stored in the web ui. Or to store >some user data temporarily to reduce API calls. But this means we'd have two >different data sources since the web ui should not access the core db >directly. Yep, it's a big question. Something could clearly make sense in the core, e.g. gpg keys for authentication or encryption. Other, specifically ui-type data might not make as much sense in the core. Even if we came up with a way to extend the core schema and store the data in the core, how would you access it? There would probably have to be a generic REST API for getting key/value data associated with the user in and out of the core. I've have a similar question when it comes to authorization. Just where to do we keep the authorization mapping users and roles to actions they can perform? I'm very close to punting on this for 3.0 beta (and thus likely for 3.0 final), though I'm also happy to revisit it during the Pycon sprint (likely for a hypothetical 3.1). Cheers, -Barry From barry at list.org Tue Feb 21 02:36:13 2012 From: barry at list.org (Barry Warsaw) Date: Mon, 20 Feb 2012 20:36:13 -0500 Subject: [Mailman-Developers] Add the equivalent of postconf In-Reply-To: References: Message-ID: <20120220203613.02bcb16f@resist.wooz.org> 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 From adam-mailman at amyl.org.uk Tue Feb 21 11:37:46 2012 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Tue, 21 Feb 2012 10:37:46 +0000 Subject: [Mailman-Developers] Add the equivalent of postconf In-Reply-To: <20120220203613.02bcb16f@resist.wooz.org> References: <20120220203613.02bcb16f@resist.wooz.org> Message-ID: <20120221103746.GJ10111@hendricks.amyl.org.uk> On Mon, Feb 20, 2012 at 08:36:13PM -0500, Barry Warsaw wrote: > (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. I'd be inclined to (consistently) use a character that's not permitted in either part -- just to make it nice and easy to say, use `awk -F` (or your tool of choice) when looking at output. I quite colons. -- "... they're not anarchists, just thugs who can't be bothered to put in the weekly commitment needed to be football hooligans." -- Nick Barlow (describing violent May Day protestors) From richard at NFSNet.org Tue Feb 21 14:59:06 2012 From: richard at NFSNet.org (Richard Wackerbarth) Date: Tue, 21 Feb 2012 07:59:06 -0600 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <34f7-4f42ec80-1-eee5a50@63575587> References: <34f7-4f42ec80-1-eee5a50@63575587> Message-ID: <015A007A-FBE2-43F6-BDD7-A3A6D49498D5@NFSNet.org> On Feb 20, 2012, at 7:00 PM, Florian Fuchs wrote: > Agreed. Django's User model > OTOH it could make great sense to enhance this data with all kinds of crazy things that could be stored in the web ui. Or to store some user data temporarily to reduce API calls. But this means we'd have two different data sources since the web ui should not access the core db directly. Let me suggest that we "step back" a bit from the implementation and look at the infrastructure architecture. The Web UI is a Django site. Therefore, (IMHO), we should build it as one. That means that we have some django apps that represent the MM functionality. They have models and views just like any other django site. The models for the users, lists, etc. just "happen" to represent the same data structure as that used by the MM core. The database access becomes a stack. The UI always accesses its data through its model. The implementation of the access could be directly as a table on a local database (as django is normally used) or it could use the REST interface to utilize the MM core as its data store. I would also introduce a transparent caching layer which would be optional. I suspect that (almost all of) the part of the MM database that is accessed by the UI could be classified as "read mostly" and that we could cache the information on a per-session basis, thus avoiding many of the accesses thru the REST interface. > Of course, if we implement such a custom backend we should do it in a generic and reusable way. I just think making a full-blown django app for what is usually just a .py file might be a bit overkill... But as I said: debatable... ;-) I'm not sure what you mean by "full-blown django app". Even though an app must have models, views, templates, etc., those can usually be empty placeholder files. > I guess in the end it's not a question of whether or not we make use of the Django User model. (At least to me) the question is: Do we use it to store user data permamently in the web ui or just temporarily on a request/session basis. Or a mix of both. We will definitely need some persistent storage that is beyond the functionality provided by the current MM core. Whether that storage is provided locally by a UI-owned database or the core database is extended to provide the backing store should be configurable at a later time. Another approach would be to migrate all of the storage to a separate module and let both the UI and the "core" interface to it. The REST interface could also be layered on top of it to provide an alternate API that could be bypassed by the core and/or the UI. This would make provide a clean place to insert "foreign" databases as might be maintained by existing enterprise infrastructures. Richard Richard From richard at NFSNet.org Tue Feb 21 15:10:54 2012 From: richard at NFSNet.org (Richard Wackerbarth) Date: Tue, 21 Feb 2012 08:10:54 -0600 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <20120220202814.40244abb@resist.wooz.org> References: <7E9E4A3A-A73E-4C99-AB5A-E206B2B71432@NFSNet.org> <34f7-4f42ec80-1-eee5a50@63575587> <20120220202814.40244abb@resist.wooz.org> Message-ID: On Feb 20, 2012, at 7:28 PM, Barry Warsaw wrote: > On Feb 21, 2012, at 02:00 AM,Florian Fuchs wrote: > >> Agreed. Django's User model > Yep, it's a big question. Something could clearly make sense in the core, > e.g. gpg keys for authentication or encryption. Other, specifically ui-type > data might not make as much sense in the core. Even if we came up with a way > to extend the core schema and store the data in the core, how would you access > it? There would probably have to be a generic REST API for getting key/value > data associated with the user in and out of the core. In general, I think that this will be needed. Consider what happens when we try to add a "plugin" optional function such as a different archiver. In general, it will need to have some database stored parameters. Do we then add yet another database? I think not. A generic key/value mechanism in the existing database would provide the capability without requiring a custom change to the API. > I've have a similar question when it comes to authorization. Just where to do > we keep the authorization mapping users and roles to actions they can perform? > I'm very close to punting on this for 3.0 beta (and thus likely for 3.0 > final), though I'm also happy to revisit it during the Pycon sprint (likely > for a hypothetical 3.1). For the short term, I would let the UI become the repository for such information. For the longer term, see my remarks in reply to Florian's message which you are referencing. Richard From matju at artengine.ca Tue Feb 21 18:49:05 2012 From: matju at artengine.ca (Mathieu Bouchard) Date: Tue, 21 Feb 2012 12:49:05 -0500 (EST) Subject: [Mailman-Developers] =?iso-8859-15?q?owner_suffix_ignored_when_in?= =?iso-8859-15?q?_Cc=A0=3F?= Message-ID: I'm using MailMan 2.1.11 and I noticed that when I send to foo-owner at example.com, MailMan takes it as if I had sent to foo at 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 From mark at msapiro.net Tue Feb 21 19:57:08 2012 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 21 Feb 2012 10:57:08 -0800 Subject: [Mailman-Developers] =?iso-8859-1?q?owner_suffix_ignored_when_in_?= =?iso-8859-1?q?Cc=A0=3F?= In-Reply-To: Message-ID: Mathieu Bouchard wrote: > >I'm using MailMan 2.1.11 and I noticed that when I send to >foo-owner at example.com, MailMan takes it as if I had sent to foo at 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)? This is not Mailman. It is something in the process that delivers mail to Mailman. Whether the address foo-owner at example.com is in a To: or a Cc: or no header at all, the envelope should be addressed to foo-owner at example.com and the message ultimately piped to /path/to/mailman/mail/mailman owner foo Somehow, your process is piping it to /path/to/mailman/mail/mailman post foo instead if foo-owner at example.com is in a Cc: -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From bob at nleaudio.com Tue Feb 21 22:16:11 2012 From: bob at nleaudio.com (Bob Puff@NLE) Date: Tue, 21 Feb 2012 16:16:11 -0500 Subject: [Mailman-Developers] OT: Need Python guru Message-ID: <4F44099B.8070606@nleaudio.com> 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 From stephen at xemacs.org Wed Feb 22 07:49:29 2012 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 22 Feb 2012 15:49:29 +0900 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <34f7-4f42ec80-1-eee5a50@63575587> References: <7E9E4A3A-A73E-4C99-AB5A-E206B2B71432@NFSNet.org> <34f7-4f42ec80-1-eee5a50@63575587> Message-ID: <87obsrmkg6.fsf@uwakimon.sk.tsukuba.ac.jp> Florian Fuchs writes: > Agreed. Django's User model most definitely covers all our > needs. What version of Django's User model are you using? The vanilla User is actually rather limited. Or do you mean as augmented by UserProfiles? If the latter, do you have a specific schema for the Profile in mind, or are you just referring to its flexibility? > The thing I am not sure about is: What kind of user info > ends up in the core DB and what should be stored in the web ui > db. In theory we don't need any kind of permanent storage in the > web ui, We do, I think. I think the core DB should be constant across Mailman installations, and restricted to fields useful in "forum" administration (ie, not restricted to mailing lists, although that will be the main purpose of Mailman 3 at its initial release). The web UI DB storage would be optional and flexible. But all fields and tables available to the web UI should be accessed by the same APIs in developing an instance of the web UI. Also, some fields of the core DB may be provided by a third party in vegetative state (eg, a personnel department). We may want to allow the web UI to augment, edit, or override some of those fields in presentation. > But this means we'd have two different data sources since the web > ui should not access the core db directly. Yes, the core DB and the web UI's persistent storage would be different. But clients of the web UI's API need not know that, or do they? From jagannathante at gmail.com Wed Feb 22 13:11:28 2012 From: jagannathante at gmail.com (Jagannathan Tiruvallur Eachambadi) Date: Wed, 22 Feb 2012 17:41:28 +0530 Subject: [Mailman-Developers] mailman web ui Message-ID: 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, wrote: > Send Mailman-Developers mailing list submissions to > mailman-developers at 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 at python.org > > You can reach the person managing the list at > mailman-developers-owner at 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 > To: Barry Warsaw > Cc: mailman-developers at python.org > Subject: Re: [Mailman-Developers] Probe messages should not sent > Precedence header > Message-ID: > > > Content-Type: text/plain; charset=ISO-8859-1 > > On Tue, Feb 21, 2012 at 12:19 AM, Barry Warsaw wrote: > > > On Feb 18, 2012, at 06:38 AM, Aamir Khan wrote: > > > > >As suggested by Barry, I am working on this new 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 at 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%40gmail.com > > > > 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" > To: "Jagannathan Tiruvallur Eachambadi" > Cc: mailman-developers at python.org > Subject: Re: [Mailman-Developers] Mailman-Developers Digest, Vol 274, > Issue 12 > Message-ID: <313a-4f42d000-1-5047fc00 at 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 at 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, >wrote: > > > > > Send Mailman-Developers mailing list submissions to > > > mailman-developers at 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 at python.org > > > > > > You can reach the person managing the list at > > > mailman-developers-owner at 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 > > > To: mailman-developers at python.org > > > Subject: [Mailman-Developers] GSOC 12 > > > Message-ID: > > > < > CABzJUX6EYs2RX7w60nHKgpRpJ33XMA3A6dLMkSjHvVr33mZvYg at 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 at python.org > > > >wrote: > > > > > > > Send Mailman-Developers mailing list submissions to > > > > mailman-developers at 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 at python.org > > > > > > > > You can reach the person managing the list at > > > > mailman-developers-owner at 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 > > > > To: Aamir Khan > > > > Cc: Mailman-Developers at python.org > > > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > > > Precedenceheader > > > > Message-ID: > > > > 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 says "Don't > > > > use spaces around the '=' sign when used to indicate a keyword > > > > argument or a default parameter value." > > > > > > > > -- > > > > Mark Sapiro 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 > > > > To: Mark Sapiro > > > > Cc: Mailman-Developers at python.org > > > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > > > Precedenceheader > > > > Message-ID: > > > > < > > > CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg at mail.gmail.com > > > > > > > > > Content-Type: text/plain; charset=ISO-8859-1 > > > > > > > > Mark Sapiro 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 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 > > > > To: Aamir Khan > > > > Cc: Mailman-Developers at python.org > > > > Subject: Re: [Mailman-Developers] Probe messages should not sent > > > > Precedenceheader > > > > Message-ID: > > > > Content-Type: text/plain; charset=iso-8859-1 > > > > > > > > Aamir Khan wrote: > > > > > > > > > >Mark Sapiro 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 The highway is for gamblers, > > > > San Francisco Bay Area, California better use your sense - B. > Dylan > > > > > > > > > > > > > > > > ------------------------------ > > > > > > > > _______________________________________________ > > > > Mailman-Developers mailing list > > > > Mailman-Developers at 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 > > > To: mailman-developers at python.org > > > Subject: Re: [Mailman-Developers] GSOC 12 > > > Message-ID: > > > < > CABzJUX4yLEAfnPg_EzCc9dQuNbYUDSLPwbG1ZT4vim1cTj3T6w at 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 at 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 at python.org > > > >wrote: > > > > > > > >> Send Mailman-Developers mailing list submissions to > > > >> mailman-developers at 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 at python.org > > > >> > > > >> You can reach the person managing the list at > > > >> mailman-developers-owner at 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 > > > >> To: Aamir Khan > > > >> Cc: Mailman-Developers at python.org > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > >> Precedenceheader > > > >> Message-ID: > > > >> 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 says "Don't > > > >> use spaces around the '=' sign when used to indicate a keyword > > > >> argument or a default parameter value." > > > >> > > > >> -- > > > >> Mark Sapiro 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 > > > >> To: Mark Sapiro > > > >> Cc: Mailman-Developers at python.org > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > >> Precedenceheader > > > >> Message-ID: > > > >> < > > > >> CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg at mail.gmail.com> > > > >> Content-Type: text/plain; charset=ISO-8859-1 > > > >> > > > >> Mark Sapiro 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 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 > > > >> To: Aamir Khan > > > >> Cc: Mailman-Developers at python.org > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > >> Precedenceheader > > > >> Message-ID: > > > >> Content-Type: text/plain; charset=iso-8859-1 > > > >> > > > >> Aamir Khan wrote: > > > >> > > > > >> >Mark Sapiro 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 The highway is for gamblers, > > > >> San Francisco Bay Area, California better use your sense - B. > Dylan > > > >> > > > >> > > > >> > > > >> ------------------------------ > > > >> > > > >> _______________________________________________ > > > >> Mailman-Developers mailing list > > > >> Mailman-Developers at 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" > > > To: "Jagannathan Tiruvallur Eachambadi" > > > Cc: mailman-developers at python.org > > > Subject: Re: [Mailman-Developers] GSOC 12 > > > Message-ID: <1f3e-4f427880-7-13fbcde0 at 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: > > > > > > > > > > /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 at 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 at 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 at python.org>wrote: > > > > > > > > > >> Send Mailman-Developers mailing list submissions to > > > > >> mailman-developers at 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 at python.org > > > > >> > > > > >> You can reach the person managing the list at > > > > >> mailman-developers-owner at 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 > > > > >> To: Aamir Khan > > > > >> Cc: Mailman-Developers at python.org > > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > > >> Precedenceheader > > > > >> Message-ID: > > > > >> 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 says > "Don't > > > > >> use spaces around the '=' sign when used to indicate a keyword > > > > >> argument or a default parameter value." > > > > >> > > > > >> -- > > > > >> Mark Sapiro 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 > > > > >> To: Mark Sapiro > > > > >> Cc: Mailman-Developers at python.org > > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > > >> Precedenceheader > > > > >> Message-ID: > > > > >> < > > > > >> > CAOb12VXRgZGMcO6W2GADwVOczHOW1zTF3xduZfoWHh_-T4BLWg at mail.gmail.com> > > > > >> Content-Type: text/plain; charset=ISO-8859-1 > > > > >> > > > > >> Mark Sapiro 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 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 > > > > >> To: Aamir Khan > > > > >> Cc: Mailman-Developers at python.org > > > > >> Subject: Re: [Mailman-Developers] Probe messages should not sent > > > > >> Precedenceheader > > > > >> Message-ID: > > > > >> Content-Type: text/plain; charset=iso-8859-1 > > > > >> > > > > >> Aamir Khan wrote: > > > > >> > > > > > >> >Mark Sapiro 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 The highway is for > gamblers, > > > > >> San Francisco Bay Area, California better use your sense - B. > Dylan > > > > >> > > > > >> > > > > >> > > > > >> ------------------------------ > > > > >> > > > > >> _______________________________________________ > > > > >> Mailman-Developers mailing list > > > > >> Mailman-Developers at 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 at 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.de > > > > > > > > Security Policy: http://wiki.list.org/x/QIA9 > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------ > > > > > > _______________________________________________ > > > Mailman-Developers mailing list > > > Mailman-Developers at 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 at 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.de > > > > Security Policy: http://wiki.list.org/x/QIA9 > > > > > > > > ------------------------------ > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at python.org > http://mail.python.org/mailman/listinfo/mailman-developers > > > End of Mailman-Developers Digest, Vol 274, Issue 14 > *************************************************** > From f at state-of-mind.de Thu Feb 23 23:04:04 2012 From: f at state-of-mind.de (Florian Fuchs) Date: Thu, 23 Feb 2012 23:04:04 +0100 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <20120220202814.40244abb@resist.wooz.org> Message-ID: <44c3-4f46b800-1-a987c90@110530851> Hi, On Tuesday, February 21, 2012 02:28 CET, Barry Warsaw wrote: > Even if we came up with a way > to extend the core schema and store the data in the core, how would you access > it? There would probably have to be a generic REST API for getting key/value > data associated with the user in and out of the core. Hmm, that doesn't sound like you particularly like that scenario. ;-) I'm not sure if it's a really good idea to use the core as a general data store. If user data (or even list data) is augmented with information the core doesn't need to operate, why not use a second data source. After all we have a system at hand (django) that's designed to do that. I kind of liked the idea of an optional "bare-bones" version web ui that doesn't need anything more than the core API to do its tasks. But of course there are many use cases beyond that. > I've have a similar question when it comes to authorization. Just where to do > we keep the authorization mapping users and roles to actions they can perform? I'm not sure if that's what you mean, but I would say that depends on who the main authority is for, say, assigning a role to a certain user for instance. What if I revoke the moderator role from a member via the command line (I don't think that's currently possible, but let's say it is...). The core would have no way of actively inform the web ui (or possibly all the many different web ui installations, apps etc...) that this privilege has been revoked. So I'd say this is some information the web ui would have to request from the core. > I'm very close to punting on this for 3.0 beta (and thus likely for 3.0 > final), though I'm also happy to revisit it during the Pycon sprint (likely > for a hypothetical 3.1). Aahhh, the Pycon sprint... :-) Cheers Florian From f at state-of-mind.de Thu Feb 23 23:46:09 2012 From: f at state-of-mind.de (Florian Fuchs) Date: Thu, 23 Feb 2012 23:46:09 +0100 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <015A007A-FBE2-43F6-BDD7-A3A6D49498D5@NFSNet.org> Message-ID: <44c6-4f46c180-9-141fdf40@268379988> Hi, On Tuesday, February 21, 2012 14:59 CET, Richard Wackerbarth wrote: > The database access becomes a stack. The UI always accesses its data through its model. The implementation of the access could be directly as a table on a local database (as django is normally used) or it could use the REST interface to utilize the MM core as its data store. Yep, it obviously makes sense to separate data from business logic. And ideally the view code doesn't look (much) different whether it accesses a model stored in a db or a rest resource. (BTW, I recently started rewriting this part of the prototype in that sense.) But I'm not sure I would see database models as exactly equivalent to REST resources. > I would also introduce a transparent caching layer which would be optional. I suspect that (almost all of) the part of the MM database that is accessed by the UI could be classified as "read mostly" and that we could cache the information on a per-session basis, thus avoiding many of the accesses thru the REST interface. Yep. But we need to decide how tolerant we are when it comes to inconsistencies between the state of the core data and a web ui session. A list of mailing lists might be stored on a per session basis - if a new list is created by a third party during a session, it's probably tolerable not to have that new list appear immediately. It's a bit trickier when it comes to privileges like moderation etc. that should probably take effect immediately (especially when revoked). > > Of course, if we implement such a custom backend we should do it in a generic and reusable way. I just think making a full-blown django app for what is usually just a .py file might be a bit overkill... But as I said: debatable... ;-) > > I'm not sure what you mean by "full-blown django app". Even though an app must have models, views, templates, etc., those can usually be empty placeholder files. By that I meant: Something people installing it have to take care of by tweaking their settings.INSTALLED_APPS tuple. If it's part of the package, that doesn't need to be done. Although having an extra app for that could make sense if the different auth methods should be strictly pluggable. Cheers Florian From f at state-of-mind.de Fri Feb 24 00:04:02 2012 From: f at state-of-mind.de (Florian Fuchs) Date: Fri, 24 Feb 2012 00:04:02 +0100 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <87obsrmkg6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <44c6-4f46c600-d-141fdf40@268379990> On Wednesday, February 22, 2012 07:49 CET, "Stephen J. Turnbull" wrote: > Florian Fuchs writes: > > > Agreed. Django's User model most definitely covers all our > > needs. > > What version of Django's User model are you using? The vanilla User > is actually rather limited. Or do you mean as augmented by > UserProfiles? If the latter, do you have a specific schema for the > Profile in mind, or are you just referring to its flexibility? By "User model" I didn't mean the actual vanilla User model (sorry for not being precise). I meant its flexibility and that it can be easily enhanced. Also how it's automatically added to the request object and accessible from the templates etc. > > > The thing I am not sure about is: What kind of user info > > ends up in the core DB and what should be stored in the web ui > > db. In theory we don't need any kind of permanent storage in the > > web ui, > > We do, I think. I think the core DB should be constant across > Mailman installations, and restricted to fields useful in "forum" > administration (ie, not restricted to mailing lists, although that > will be the main purpose of Mailman 3 at its initial release). The > web UI DB storage would be optional and flexible. But all fields and > tables available to the web UI should be accessed by the same APIs in > developing an instance of the web UI. > > Also, some fields of the core DB may be provided by a third party in > vegetative state (eg, a personnel department). We may want to allow > the web UI to augment, edit, or override some of those fields in > presentation. Good point. > > > But this means we'd have two different data sources since the web > > ui should not access the core db directly. > > Yes, the core DB and the web UI's persistent storage would be > different. But clients of the web UI's API need not know that, or do > they? If they become aware of that, something probably went wrong... ;-) Florian From richard at NFSNet.org Fri Feb 24 00:17:37 2012 From: richard at NFSNet.org (Richard Wackerbarth) Date: Thu, 23 Feb 2012 17:17:37 -0600 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <44c6-4f46c180-9-141fdf40@268379988> References: <44c6-4f46c180-9-141fdf40@268379988> Message-ID: <57D5E9FF-CC8C-44C2-80F1-3307262C96E8@NFSNet.org> On Feb 23, 2012, at 4:46 PM, Florian Fuchs wrote: >>> Of course, if we implement such a custom backend we should do it in a generic and reusable way. I just think making a full-blown django app for what is usually just a .py file might be a bit overkill... But as I said: debatable... ;-) >> >> I'm not sure what you mean by "full-blown django app". Even though an app must have models, views, templates, etc., those can usually be empty placeholder files. > > By that I meant: Something people installing it have to take care of by tweaking their settings. INSTALLED_APPS tuple. If it's part of the package, that doesn't need to be done. Although having an extra app for that could make sense if the different auth methods should be strictly pluggable. > > Cheers > Florian If I am not mistaken, the INSTALLED_APPS as defined in the django instance settings, is just a convenient way to switch on/off django apps whose code is present. I think that an enabled app can effectively override the tupe and cause other apps to behave as if they had been listed in the settings. However, I am not sure that to do so would be a good idea. The person who installs a plugin is going to have to do a number of things. In particular, he will, presumedly, have to do more than just add the code to the python path. He will modify some configuration parameter on the core side in order to have the plugin have any effect on the mail traffic. Since we have separated the mail handling from the administrative interface (UI), he will also need to both make code available and alter some configuration setting on the UI side. Just as in the django distribution, where the "admin" interface is optional, adding references to our plugins SHOULD involve adding lines to the settings files, etc. Note that we could provide a script that would automate those changes. However, as a system administrator, I prefer to be told in the installation instructions what lines I need to change, and why. I am leery of scripts that "magically" change configurations on my system. Richard From barry at list.org Fri Feb 24 00:24:30 2012 From: barry at list.org (Barry Warsaw) Date: Thu, 23 Feb 2012 18:24:30 -0500 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <44c6-4f46c180-9-141fdf40@268379988> References: <015A007A-FBE2-43F6-BDD7-A3A6D49498D5@NFSNet.org> <44c6-4f46c180-9-141fdf40@268379988> Message-ID: <20120223182430.74825346@resist.wooz.org> On Feb 23, 2012, at 11:46 PM, Florian Fuchs wrote: >Yep. But we need to decide how tolerant we are when it comes to >inconsistencies between the state of the core data and a web ui session. A >list of mailing lists might be stored on a per session basis - if a new list >is created by a third party during a session, it's probably tolerable not to >have that new list appear immediately. It's a bit trickier when it comes to >privileges like moderation etc. that should probably take effect immediately >(especially when revoked). I wonder if a push model could be used in those cases where changes to the core database need to be immediately reflected in the ui. For example, the core utilizes zope.events as a hook mechanism to notify other parts of the core when certain things happen. For the most part, I'm just using this in the test suite, but I think it would make sense to hook events to notify external systems (e.g. the web ui, or its cache, etc.) when certain things happen. Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From barry at list.org Fri Feb 24 00:36:55 2012 From: barry at list.org (Barry Warsaw) Date: Thu, 23 Feb 2012 18:36:55 -0500 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <44c3-4f46b800-1-a987c90@110530851> References: <20120220202814.40244abb@resist.wooz.org> <44c3-4f46b800-1-a987c90@110530851> Message-ID: <20120223183655.2fdccfad@resist.wooz.org> On Feb 23, 2012, at 11:04 PM, Florian Fuchs wrote: >> Even if we came up with a way to extend the core schema and store the data >> in the core, how would you access it? There would probably have to be a >> generic REST API for getting key/value data associated with the user in and >> out of the core. > >Hmm, that doesn't sound like you particularly like that scenario. ;-) Not so much. ;) >I'm not sure if it's a really good idea to use the core as a general data >store. If user data (or even list data) is augmented with information the >core doesn't need to operate, why not use a second data source. After all we >have a system at hand (django) that's designed to do that. Exactly. >> I've have a similar question when it comes to authorization. Just where to >> do we keep the authorization mapping users and roles to actions they can >> perform? > >I'm not sure if that's what you mean, but I would say that depends on who the >main authority is for, say, assigning a role to a certain user for >instance. What if I revoke the moderator role from a member via the command >line (I don't think that's currently possible, but let's say it is...). The >core would have no way of actively inform the web ui (or possibly all the >many different web ui installations, apps etc...) that this privilege has >been revoked. So I'd say this is some information the web ui would have to >request from the core. Yep. TBH, this is something I've been struggling with for a long while now. Remember I've advocated for keeping all those decisions out of the core, but there has been valid push-back on that (admittedly somewhat lazy ;) stance. Now, I think we can get notifications pushed from the core to the ui if we wanted, assuming the ui had some service to notify. See my previous message on events. But in some cases, like the one you mention above, I think it would also be fine for the ui to query the core to gather the information necessary to decide whether an action is allowed. E.g. the ui could ask the core, via REST, "is this person an owner of that mailing list?". There are upsides and downsides to this. For example, do we want to keep the logic for authorization in the web ui? That would mean if you integrate the core with your own custom web ui, then it wouldn't gain any of the benefit of the authorization logic in the Django app. OTOH, that might be just what you want, and I can imagine a site like Launchpad would prefer that, since it has its own user model. Ignoring that whole morass does keep the core lean and mean, which I rather like, especially because I want to release this beast RSN. ;) So I'm very tempted to punt on the whole authentication/authorization issue as much as possible in the core for the 3.0 release, but I'm also happy to keep the discussion open for possible changes for the future. I think the integration work going on between the web ui and the core will give us some much needed practical experience here. Right now, it's all too theoretical for me to make much headway on. >> I'm very close to punting on this for 3.0 beta (and thus likely for 3.0 >> final), though I'm also happy to revisit it during the Pycon sprint (likely >> for a hypothetical 3.1). > >Aahhh, the Pycon sprint... :-) Fun, fun! Note too that I will be giving a talk on MM3 at Pycon, but fortunately I only have to fill 30m. :) I want to be able to release MM3 very soon after the sprints. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From barry at list.org Fri Feb 24 00:43:18 2012 From: barry at list.org (Barry Warsaw) Date: Thu, 23 Feb 2012 18:43:18 -0500 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <87obsrmkg6.fsf@uwakimon.sk.tsukuba.ac.jp> References: <7E9E4A3A-A73E-4C99-AB5A-E206B2B71432@NFSNet.org> <34f7-4f42ec80-1-eee5a50@63575587> <87obsrmkg6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <20120223184318.0f0ec07e@resist.wooz.org> On Feb 22, 2012, at 03:49 PM, Stephen J. Turnbull wrote: >We do, I think. I think the core DB should be constant across >Mailman installations, and restricted to fields useful in "forum" >administration (ie, not restricted to mailing lists, although that >will be the main purpose of Mailman 3 at its initial release). The >web UI DB storage would be optional and flexible. But all fields and >tables available to the web UI should be accessed by the same APIs in >developing an instance of the web UI. > >Also, some fields of the core DB may be provided by a third party in >vegetative state (eg, a personnel department). We may want to allow >the web UI to augment, edit, or override some of those fields in >presentation. The counter argument is that the core's database should only contain the data that is needed to do its function. A leaner core schema means it will be easier to migrate and maintain as time goes on. It also reduces bloat in the REST API, even if we provided a generic key/data API (which frankly I don't like). E.g. if personnel department were central to the core's functionality, by all means, let's add it to the schema and expose it in the right places within the REST resource model. If not, then it really shouldn't be part of the core's schema. Cheers, -Barry From richard at NFSNet.org Fri Feb 24 02:55:56 2012 From: richard at NFSNet.org (Richard Wackerbarth) Date: Thu, 23 Feb 2012 19:55:56 -0600 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <20120223184318.0f0ec07e@resist.wooz.org> References: <7E9E4A3A-A73E-4C99-AB5A-E206B2B71432@NFSNet.org> <34f7-4f42ec80-1-eee5a50@63575587> <87obsrmkg6.fsf@uwakimon.sk.tsukuba.ac.jp> <20120223184318.0f0ec07e@resist.wooz.org> Message-ID: <880B8C86-79E9-4388-A19C-63EA97A271FB@NFSNet.org> On Feb 23, 2012, at 5:43 PM, Barry Warsaw wrote: > The counter argument is that the core's database should only contain the data > that is needed to do its function. Yet another argument would be: The MM suite can be partitioned logically into a message handler, an archiver, an administration-by-mail interface, a web-based interface, and a roster (et. al.) store. Perhaps the core should store only that data which it, and no other part of the suite utilizes. Upon receipt of a message, if appropriate, it would forward the message to appropriate subsystems. If it is to be distributed to a roster, it would obtain the current roster from the storage subsystem. The web UI, administration-by-mail subsystem and the corporate personnel department would interact with the data store in order to make changes to the rosters. Perhaps this concept is in keeping with the "leaner core schema" approach. It also has the advantage that the data store is isolated from the MM message handler. That would make it easier for "large corporation" to implement the store within their existing corporate database. Richard > A leaner core schema means it will be > easier to migrate and maintain as time goes on. It also reduces bloat in the > REST API, even if we provided a generic key/data API (which frankly I don't > like). > > E.g. if personnel department were central to the core's functionality, by all > means, let's add it to the schema and expose it in the right places within the > REST resource model. If not, then it really shouldn't be part of the core's > schema. > > Cheers, > -Barry > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at 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/richard%40nfsnet.org > > Security Policy: http://wiki.list.org/x/QIA9 From barry at list.org Sat Feb 25 22:37:52 2012 From: barry at list.org (Barry Warsaw) Date: Sat, 25 Feb 2012 16:37:52 -0500 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: References: <7E9E4A3A-A73E-4C99-AB5A-E206B2B71432@NFSNet.org> <34f7-4f42ec80-1-eee5a50@63575587> <20120220202814.40244abb@resist.wooz.org> Message-ID: <20120225163752.32147463@resist.wooz.org> On Feb 21, 2012, at 08:10 AM, Richard Wackerbarth wrote: >On Feb 20, 2012, at 7:28 PM, Barry Warsaw wrote: >> Yep, it's a big question. Something could clearly make sense in the core, >> e.g. gpg keys for authentication or encryption. Other, specifically >> ui-type data might not make as much sense in the core. Even if we came up >> with a way to extend the core schema and store the data in the core, how >> would you access it? There would probably have to be a generic REST API >> for getting key/value data associated with the user in and out of the core. > >In general, I think that this will be needed. Consider what happens when we >try to add a "plugin" optional function such as a different archiver. > >In general, it will need to have some database stored parameters. Do we then >add yet another database? I think not. A generic key/value mechanism in the >existing database would provide the capability without requiring a custom >change to the API. Another way to do this, now that we have (what I think is a fairly robust) schema migration, you could imagine the plugin would make available a few migrations which would add the necessary data to the existing database. There might be problems if you're adding fields to existing model objects, but adding purely new tables shouldn't be too much of a problem I'd think. >> I've have a similar question when it comes to authorization. Just where to >> do we keep the authorization mapping users and roles to actions they can >> perform? I'm very close to punting on this for 3.0 beta (and thus likely >> for 3.0 final), though I'm also happy to revisit it during the Pycon sprint >> (likely for a hypothetical 3.1). > >For the short term, I would let the UI become the repository for such >information. For the longer term, see my remarks in reply to Florian's >message which you are referencing. Yep, thanks. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From richard at NFSNet.org Sun Feb 26 14:00:40 2012 From: richard at NFSNet.org (Richard Wackerbarth) Date: Sun, 26 Feb 2012 07:00:40 -0600 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <20120225163752.32147463@resist.wooz.org> References: <7E9E4A3A-A73E-4C99-AB5A-E206B2B71432@NFSNet.org> <34f7-4f42ec80-1-eee5a50@63575587> <20120220202814.40244abb@resist.wooz.org> <20120225163752.32147463@resist.wooz.org> Message-ID: <3961BAC5-3055-4068-B58E-D85CA44D1E6A@NFSNet.org> On Feb 25, 2012, at 3:37 PM, Barry Warsaw wrote: > On Feb 21, 2012, at 08:10 AM, Richard Wackerbarth wrote: >> On Feb 20, 2012, at 7:28 PM, Barry Warsaw wrote: >>> Yep, it's a big question. Something could clearly make sense in the core, >>> e.g. gpg keys for authentication or encryption. Other, specifically >>> ui-type data might not make as much sense in the core. Even if we came up >>> with a way to extend the core schema and store the data in the core, how >>> would you access it? There would probably have to be a generic REST API >>> for getting key/value data associated with the user in and out of the core. >> >> In general, I think that this will be needed. Consider what happens when we >> try to add a "plugin" optional function such as a different archiver. >> >> In general, it will need to have some database stored parameters. Do we then >> add yet another database? I think not. A generic key/value mechanism in the >> existing database would provide the capability without requiring a custom >> change to the API. > > Another way to do this, now that we have (what I think is a fairly robust) > schema migration, you could imagine the plugin would make available a few > migrations which would add the necessary data to the existing database. There > might be problems if you're adding fields to existing model objects, but > adding purely new tables shouldn't be too much of a problem I'd think. First, I would be quite concerned if any plugins alter existing database tables. I see nothing but nightmares trying to avoid conflicting interactions, naming conventions, etc. From a maintenance point-of-view, adding auxiliary tables rather than additional columns in existing tables is much more manageable. When it comes to migrations, we need to assure that migration sequences from separate plugins remain commutative. We will have no control over the order in which a particular installation will adopt particular plugins. Where possible, I think that it is preferable to avoid add database tables if the scope of reference for those tables extends beyond the plugin itself. In order to bridge between the UI and the MM core servers, the REST interface would also have to be extended. On the other hand, implementing the parameter store for a plugin by adding rows to a common parameter database would be able to utilize an existing interface. Parameters are just key/value pairs that apply to a particular context. Generically, that context is a tuple of [user, list, ...] . If we add "plugin" to that context key, we have can have a generic store that does not need to be changed when a plugin is added. From f at state-of-mind.de Mon Feb 27 16:41:18 2012 From: f at state-of-mind.de (Florian Fuchs) Date: Mon, 27 Feb 2012 16:41:18 +0100 Subject: [Mailman-Developers] Browser ID integration with Mailman In-Reply-To: <20120223183655.2fdccfad@resist.wooz.org> Message-ID: <403-4f4ba400-9-55ee3b00@8356716> Hi, > Now, I think we can get notifications pushed from the core to the ui if we > wanted, assuming the ui had some service to notify. See my previous message > on events. Awesome! So the wui would implement a simple REST API for the core to talk to. Ideally it should be possible to "register" more than one web ui (the official ui might not be the only application using the Mailman API), so multiple parties can be notified of changes. Also, we should probably think about how fine-grained those "invalidate"-notifications can be. It's probably not necessary to invalidate the whole cache every time something changes in the core. > There are upsides and downsides to this. For example, do we want to keep the > logic for authorization in the web ui? That would mean if you integrate the > core with your own custom web ui, then it wouldn't gain any of the benefit of > the authorization logic in the Django app. OTOH, that might be just what you > want, and I can imagine a site like Launchpad would prefer that, since it has > its own user model. I wonder what the main use cases are for custom web uis. My guess is that many ui-creators might not build the whole thing anew, but create smaller applications for single tasks like (un)subscribing to lists etc. In larger integration scenarios, auth might be taken care of at some other stage (a company intranet for instance or a content management system). > Note too that I will be giving a talk on MM3 at Pycon, but fortunately I only > have to fill 30m. :) I know - I'll definitely be there! (Always wanted to know what this MM3 thing is and what it can do! ;-) Florian