Mailman 3 March 2012 - Mailman-Developers

Re: [Mailman-Developers] any interest in a new built-in web-archive? (i.e. pipermail replacement)
by Stephen J. Turnbull 29 Mar '12

29 Mar '12

On Thu, Mar 29, 2012 at 4:04 PM, David Jeske <davidj(a)gmail.com> wrote: >> - Merging of forums, archives, newsgroups, and IMAP. > > You like to bite off the big ones eh? NNTP, then IMAP. > > Does anyone even use fat-mail-clients anymore? Yes, and yes. But I don't think anybody has really thought carefully about these desiderata yet, they're just frequently suggested on mailman-users and sometimes mailman-developers.

1 0

Re: [Mailman-Developers] mailman / archive-ui / licensing questions
by Stephen J. Turnbull 29 Mar '12

29 Mar '12

On Thu, Mar 29, 2012 at 1:00 PM, David Jeske <davidj(a)gmail.com> wrote: > I started to talk to one of them about installing CSLA (or MHonArc, or > anything really), and realized I should see if you folks are interested in > a great bundled archiver, I'm personally interested, but that's not going to be the main focus until the core gets a little less alpha, I would guess. > I admit that even with a pretty good knowledge of these many licenses, I'm > not familiar with the intracacies of FSF copyright assignment and non-GPL > free licenses. The bottom line is that if you assign it to the FSF, they can change the license of future copies to something you don't like without your permission, or even consulting you. This has been done in the past (eg, libreadline). I don't know whether they would bother with a non-GNU project, though. However, copies of the version you originally released under a different license remain under that license, and there's always a grant-back clause in the assignment contract that allows you to make derivatives of your contributions available under any license you like. > The ClearsilverArchiver code (written by me and two others) is released > under the "Simplified BSD" license and "totally free". It's important to me > that any code I release be similarly free-and-unrestricted > (i.e. BSD/Python/Artistic/PublicDomain), not free under certain conditions > (i.e. GPL/LGPL). It's not possible to assert GPL restrictions on > totally-free code, because it's already totally free. That's not the way copyright works, though. It certainly is possible to assert GPL (or any other) restrictions on given *copies* of permissively-licensed code. If you've got a copy of the old (say, early '90s) O'Reilly "X Window System" series kicking around, check out the copyright notice in those books. (Preventing that is precisely why copyleft advocates advocate copyleft.) Even on a verbatim copy, lawyerly FUD means that even if there is no actual legal issue, practically it may be infeasible for just plain folks to redistribute. Cf. the DMCA takedowns. > FSF says S-BSD is GPL-Compatible, which I believe means they are saying > they have no problem with GPL code depending on and being combined with > (i.e. linked with) S-BSD code, because the S-BSD code is fully open-source > and does not put restrictions on the use of the GPL code. No. What they mean is that it is Borg-able. You can assimilate S-BSD code into a GPL project, and that copy is distributed under the GPL. Perhaps in legal theory they cannot prevent you from making copies of the S-BSD portions and doing anything the S-BSD permits, but the S-BSD (like other permissive licenses) does not require them to tell you what parts are S-BSD, only that some parts are, and who wrote those (unspecified) parts. (The wording is generally to the effect of "This file is part of the FOO Program, which is licensed to you under the GPL. It contains software by J. Random Hacker, with the following permissions notice...".) The burden will be on the user to determine which parts can and cannot be copied, and if it comes to a court case, the user will have to prove that the parts they've copied are not actually GPL. I would say you should try to retain copyright, and have the Mailman project distribute it with the S-BSD license under the "mere aggregation" clause of the GPL. This would entail certain restrictions on interface. Eg, you can't put the whole thing in a pipeline Handler, and you would need to have a separate webapp for summarizing/indexing/searching/retrieving the archived posts. I advocate those restrictions anyway. :-) Some small glue parts that need to be tightly integrated with core Mailman might need to be done under GPL. > It's also my understanding that the primary reason for FSF copyright > assignment is to provide a coherent entity to enforce the terms of the GPL > by challenging violators who don't redistribute source.... something which > is not necessary for S-BSD. (Though I suppose they could enforce that folks > include the S-BSD copyright notices.) The FSF's reason is so that they have control over the license, which allows them to make it GPL if that seems like a good idea to them. (Mostly they are way too busy to go looking for opportunities, though, and it's a labor-intensive process for a project of any size.) In return, they will enforce license provisions. Projects may also wish to do this so that they have the legal right to offer other licenses (the FSF is not a good assignee for this purpose!), or change the primary license. If no single entity owns the whole copyright, then you have to get agreement of all owners, some of whom may be in retreat in a Tibetan monastery or the heirs to someone who lost an argument with a bus, etc. (MIT specifically allows sublicensing, as does Larry Rosen's AFT; but S-BSD does not.) > Is Mailman-team is interested in having a better built-in archiver that is > included in the distribution, but licensed under the less-restrictive S-BSD > terms? I certainly would be interested! (I believe that freedom can only be preserved by the blood and legal fees of patriots, while GPL isn't much help any more, and increasingly frequently a PITA. :-) Other folks prefer to license their work under copyleft, specifically the GPL. But there's explicit permission in the GPL for such distribution (the "mere aggregation" clause), as long as communication between the archiver and core Mailman is done by open protocols such as *MTP and maildir. (Ie, the included Handler and IArchive integration code will probably be GPL, but there's no need for anything in a separate process, including indexing and web UI, to be GPL.)

1 0

Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
by Florian Fuchs 29 Mar '12

29 Mar '12

Hi, there seems to be a general problem running postorius with Django 1.4. Postorius alpha1 was released the same day Django 1.4 was, so we haven't had anyone on the team so far who was running 1.4 while working on postorius. @Shayan, could you file a bug on https://launchpad.net/postorius and paste your traceback into the description field? I will try to get into it as soon as possible. Thanks! Florian Am 29.03.12 10:51, schrieb Odhiambo Washington: > On Thu, Mar 29, 2012 at 11:12, Shayan Md <mdoshayan(a)gmail.com> wrote: > >> >> >> On Thu, Mar 29, 2012 at 1:07 PM, Odhiambo Washington <odhiambo(a)gmail.com>wrote: >> >>> >>> >>> On Thu, Mar 29, 2012 at 10:33, Shayan Md <mdoshayan(a)gmail.com> wrote: >>> >>>> >>>> >>>> On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington < >>>> odhiambo(a)gmail.com> wrote: >>>> >>>>> On Wed, Mar 28, 2012 at 22:31, Florian Fuchs <f(a)state-of-mind.de> >>>>> wrote: >>>>> >>>>>> Hi Odhiambo, >>>>>> >>>>>> Am 28.03.12 18:47, schrieb Odhiambo Washington: >>>>>>> One more thing: >>>>>>> >>>>>>> In settings.py, I have this: >>>>>>> >>>>>>> REST_SERVER = 'http://192.168.40.252:8001' >>>>>>> >>>>>>> However, this doesn't seem to be respected when I do runserver: >>>>>>> >>>>>>> [root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup# >>>>>>> python manage.py runserver >>>>>>> Validating models... >>>>>>> >>>>>>> 0 errors found >>>>>>> Django version 1.4, using settings 'dev_setup.settings' >>>>>>> Development server is running at http://127.0.0.1:8000/ >>>>>>> Quit the server with CONTROL-C. >>>>>>> >>>>>>> >>>>>>> [root@jaribu] /usr/home/wash# sockstat -l | grep 800 >>>>>>> root python 77906 3 tcp4 127.0.0.1:8000 >>>>>>> <http://127.0.0.1:8000> *:* >>>>>>> root python 14108 43 tcp4 127.0.0.1:8001 >>>>>>> <http://127.0.0.1:8001> *:* >>>>>>> >>>>>>> Since I am not using the server as a Desktop, I need a way to >>>>> access it >>>>>>> remotely, not via 127.0.0.1 >>>>>> >>>>>> The REST_SERVER setting defines the location of Mailman's rest API >>>>>> (which is frequently accessed by postorius), *not* the address of >>>>>> postorius itself. The API can only be accessed from localhost, so the >>>>>> setting has to be 'http://localhost:8001'. >>>>>> >>>>>> If you'd like to access postorius from a different machine as the one >>>>>> you're running it on, that's no problem: >>>>>> >>>>>> Just run the development server like this and you're good to go: >>>>>> >>>>>> python manage.py runserver 192.168.x.xxx:8000 >>>>>> >>>>>> (Don't do that on a machine that is exposed to the web though, since >>>>>> Django's dev server is not meant to be run in a production >>>>> environment.) >>>>>> >>>>>> Hope that helps! >>>>>> >>>>>> Florian >>>>>> >>>>>> >>>>> >>>>> My current quest is to see what MM3 web UI looks like, but it appears I >>>>> am >>>>> still way behind. >>>>> I get these errors in the backend when I run posturious and try to >>>>> access >>>>> it: >>>>> >>>>> http://bit.ly/H2rDuW >>>>> >>>> Looks like you didn't start mailman server. Go through this[1] page to >>>> setup mailman3. >>>> >>>> [1] >>>> http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI… >>>> >>>> >>> Maybe and maybe not, as I was following this very guide! >>> >>> [wash@jaribu ~/public_html]$ ps ax | grep mailman >>> 70295 ?? Is 0:00.40 /usr/local/bin/python >>> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/master >>> 70298 ?? S 0:01.52 /usr/local/bin/python >>> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >>> --runner=news:0:1 >>> 70299 ?? S 0:01.57 /usr/local/bin/python >>> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=in:0:1 >>> 70300 ?? S 0:01.46 /usr/local/bin/python >>> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >>> --runner=digest:0:1 >>> 70301 ?? S 0:01.49 /usr/local/bin/python >>> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >>> --runner=pipeline:0:1 >>> 70302 ?? S 0:01.45 /usr/local/bin/python >>> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >>> --runner=archive:0:1 >>> 70303 ?? S 0:01.46 /usr/local/bin/python >>> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=out:0:1 >>> 70304 ?? I 0:00.41 /usr/local/bin/python >>> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >>> --runner=retry:0:1 >>> 70305 ?? S 0:01.17 /usr/local/bin/python >>> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >>> --runner=rest:0:1 >>> 70306 ?? S 0:01.46 /usr/local/bin/python >>> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >>> --runner=bounces:0:1 >>> 70307 ?? S 0:00.43 /usr/local/bin/python >>> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >>> --runner=lmtp:0:1 >>> 70308 ?? S 0:01.45 /usr/local/bin/python >>> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >>> --runner=command:0:1 >>> 70309 ?? S 0:01.50 /usr/local/bin/python >>> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >>> --runner=virgin:0:1 >>> 78850 1 S+ 0:00.01 grep mailman >>> >>> Is there something amiss? >>> >>> >>> [root@jaribu] /usr/home/wash# sockstat -l | grep 800 >>> root python 70442 3 tcp4 192.168.40.252:8000 *:* >>> root python 70305 43 tcp4 127.0.0.1:8001 *:* >>> >>> >>> I suppose the 8001 is mailman and 8000 is posturious. >> >> Downgrading to django 1.3 might do the trick. Same error here >> https://answers.launchpad.net/graphite/+question/191549 >> >>> >>> >>> > Okay. I have to figure out why the consensus is that I am running django > 1.4 while I actually installed 1.3.1: > > [root@jaribu] /usr/ports/www/py-django# ls -al /var/db/pkg/ | grep django > drwxr-xr-x 2 root wheel 512 Mar 26 18:20 py27-django-1.3.1 > drwxr-xr-x 2 root wheel 512 Mar 26 18:20 > py27-django-extensions-0.8 > > > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > http://mail.python.org/mailman/listinfo/mailman-developers > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ > Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/f%40state-of-mind… > > Security Policy: http://wiki.list.org/x/QIA9

2 1

Re: [Mailman-Developers] Google Summer of Code: Integration of Search Code
by Barry Warsaw 29 Mar '12

29 Mar '12

On Mar 28, 2012, at 10:29 AM, Stephen J. Turnbull wrote: >The only tricky issue is that we *do* have to worry about message-ID >collisions of truly different messages and about messages without message >IDs, especially for converted historical archives. So the API needs to be >able to deal with these issues, probably by returning a set or sequence of >messages. Mailman 3 itself requires unique Message-IDs. IIRC, the Mail Archive guys found a very very low collision rate over millions of messages, and I think all such cases were basically spam. The LMTP runner doesn't yet reject duplicates, but it should (LP: #967951). s>I would guess she'll probably store messages in YY-MM/MSGID, or as git does >in "unpacked" XX/YYYYYYYY... format, where XX are the first two digits of the >hash ID, and YY... are the remaining ones). But it could easily be backed by >an IMAP store or something more specialized; we don't really care as long as >it's object-ID-addressable. Don't forget too that the LMTP runner automatically adds the X-Message-ID-Hash header, which is a Base32 encoding of the SHA1 hash of the Message-ID contents (without the angle brackets). This hash could be used as well. -Barry

2 1

Re: [Mailman-Developers] GSoC
by Florian Fuchs 29 Mar '12

29 Mar '12

Am 29.03.12 03:49, schrieb Stephen J. Turnbull: > To be honest, I don't see how it would be related to Postorius, except > perhaps as some sort of plug-in (but we don't have a plug-in > architecture for Postorius, yet). Adding such features to Postorius > would be bloat, IMO. I also worry about the performance hit; I think > it should probably maintain its own database, etc for the data-mining > end, and sparingly access the REST client API to update profiles. It could go into a separate application, but preferably one that could be hooked into by Postorius. Django already has some kind of plugin-architecture. It's generally pretty easy to "plug" different apps together if they follow some simple guidelines for re-usability (postorius is already using django.contrib.auth and django-social-auth for instance). Also, Django allows using multiple databases (even different db-types) within the same project, so there would be no need to use one database for everything. (Of course if your db needs are more exotic or beyond the SQL realm, you're not obliged to use Django's ORM at all.) Without strongly suggesting any architecture here: I think the relation to Postorius would be that it currently takes care of authentication and already holds some user information. So displaying this kind of extended information within postorius only seemed natural. No matter where this data is generated from. I'm not advocating to bloat Postorius, but to use Django. :-) > >> Yes, those would all be very interesting pieces of data. > > To stalkers and Tom Clancy's favorite folks, as well as to nicer > people. Make sure there are opt-outs for users. We talked about that at the PyCon sprint a little. If Postorius displays more detailed user information the privacy defaults should be pretty strict. Rather an opt-in than an opt-out. And possibly even more fine-grained, something like: "Show this piece of information only to: me - other list members - everyone"... or similar. Florian

1 0

Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
by Odhiambo Washington 29 Mar '12

29 Mar '12

On Thu, Mar 29, 2012 at 11:12, Shayan Md <mdoshayan(a)gmail.com> wrote: > > > On Thu, Mar 29, 2012 at 1:07 PM, Odhiambo Washington <odhiambo(a)gmail.com>wrote: > >> >> >> On Thu, Mar 29, 2012 at 10:33, Shayan Md <mdoshayan(a)gmail.com> wrote: >> >>> >>> >>> On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington < >>> odhiambo(a)gmail.com> wrote: >>> >>>> On Wed, Mar 28, 2012 at 22:31, Florian Fuchs <f(a)state-of-mind.de> >>>> wrote: >>>> >>>> > Hi Odhiambo, >>>> > >>>> > Am 28.03.12 18:47, schrieb Odhiambo Washington: >>>> > > One more thing: >>>> > > >>>> > > In settings.py, I have this: >>>> > > >>>> > > REST_SERVER = 'http://192.168.40.252:8001' >>>> > > >>>> > > However, this doesn't seem to be respected when I do runserver: >>>> > > >>>> > > [root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup# >>>> > > python manage.py runserver >>>> > > Validating models... >>>> > > >>>> > > 0 errors found >>>> > > Django version 1.4, using settings 'dev_setup.settings' >>>> > > Development server is running at http://127.0.0.1:8000/ >>>> > > Quit the server with CONTROL-C. >>>> > > >>>> > > >>>> > > [root@jaribu] /usr/home/wash# sockstat -l | grep 800 >>>> > > root python 77906 3 tcp4 127.0.0.1:8000 >>>> > > <http://127.0.0.1:8000> *:* >>>> > > root python 14108 43 tcp4 127.0.0.1:8001 >>>> > > <http://127.0.0.1:8001> *:* >>>> > > >>>> > > Since I am not using the server as a Desktop, I need a way to >>>> access it >>>> > > remotely, not via 127.0.0.1 >>>> > >>>> > The REST_SERVER setting defines the location of Mailman's rest API >>>> > (which is frequently accessed by postorius), *not* the address of >>>> > postorius itself. The API can only be accessed from localhost, so the >>>> > setting has to be 'http://localhost:8001'. >>>> > >>>> > If you'd like to access postorius from a different machine as the one >>>> > you're running it on, that's no problem: >>>> > >>>> > Just run the development server like this and you're good to go: >>>> > >>>> > python manage.py runserver 192.168.x.xxx:8000 >>>> > >>>> > (Don't do that on a machine that is exposed to the web though, since >>>> > Django's dev server is not meant to be run in a production >>>> environment.) >>>> > >>>> > Hope that helps! >>>> > >>>> > Florian >>>> > >>>> > >>>> >>>> My current quest is to see what MM3 web UI looks like, but it appears I >>>> am >>>> still way behind. >>>> I get these errors in the backend when I run posturious and try to >>>> access >>>> it: >>>> >>>> http://bit.ly/H2rDuW >>>> >>> Looks like you didn't start mailman server. Go through this[1] page to >>> setup mailman3. >>> >>> [1] >>> http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI… >>> >>> >> Maybe and maybe not, as I was following this very guide! >> >> [wash@jaribu ~/public_html]$ ps ax | grep mailman >> 70295 ?? Is 0:00.40 /usr/local/bin/python >> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/master >> 70298 ?? S 0:01.52 /usr/local/bin/python >> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >> --runner=news:0:1 >> 70299 ?? S 0:01.57 /usr/local/bin/python >> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=in:0:1 >> 70300 ?? S 0:01.46 /usr/local/bin/python >> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >> --runner=digest:0:1 >> 70301 ?? S 0:01.49 /usr/local/bin/python >> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >> --runner=pipeline:0:1 >> 70302 ?? S 0:01.45 /usr/local/bin/python >> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >> --runner=archive:0:1 >> 70303 ?? S 0:01.46 /usr/local/bin/python >> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=out:0:1 >> 70304 ?? I 0:00.41 /usr/local/bin/python >> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >> --runner=retry:0:1 >> 70305 ?? S 0:01.17 /usr/local/bin/python >> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >> --runner=rest:0:1 >> 70306 ?? S 0:01.46 /usr/local/bin/python >> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >> --runner=bounces:0:1 >> 70307 ?? S 0:00.43 /usr/local/bin/python >> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >> --runner=lmtp:0:1 >> 70308 ?? S 0:01.45 /usr/local/bin/python >> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >> --runner=command:0:1 >> 70309 ?? S 0:01.50 /usr/local/bin/python >> /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner >> --runner=virgin:0:1 >> 78850 1 S+ 0:00.01 grep mailman >> >> Is there something amiss? >> >> >> [root@jaribu] /usr/home/wash# sockstat -l | grep 800 >> root python 70442 3 tcp4 192.168.40.252:8000 *:* >> root python 70305 43 tcp4 127.0.0.1:8001 *:* >> >> >> I suppose the 8001 is mailman and 8000 is posturious. > > Downgrading to django 1.3 might do the trick. Same error here > https://answers.launchpad.net/graphite/+question/191549 > >> >> >> Okay. I have to figure out why the consensus is that I am running django 1.4 while I actually installed 1.3.1: [root@jaribu] /usr/ports/www/py-django# ls -al /var/db/pkg/ | grep django drwxr-xr-x 2 root wheel 512 Mar 26 18:20 py27-django-1.3.1 drwxr-xr-x 2 root wheel 512 Mar 26 18:20 py27-django-extensions-0.8 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email.

1 0

Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
by Shayan Md 29 Mar '12

29 Mar '12

On Thu, Mar 29, 2012 at 1:07 PM, Odhiambo Washington <odhiambo(a)gmail.com>wrote: > > > On Thu, Mar 29, 2012 at 10:33, Shayan Md <mdoshayan(a)gmail.com> wrote: > >> >> >> On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington <odhiambo(a)gmail.com >> > wrote: >> >>> On Wed, Mar 28, 2012 at 22:31, Florian Fuchs <f(a)state-of-mind.de> wrote: >>> >>> > Hi Odhiambo, >>> > >>> > Am 28.03.12 18:47, schrieb Odhiambo Washington: >>> > > One more thing: >>> > > >>> > > In settings.py, I have this: >>> > > >>> > > REST_SERVER = 'http://192.168.40.252:8001' >>> > > >>> > > However, this doesn't seem to be respected when I do runserver: >>> > > >>> > > [root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup# >>> > > python manage.py runserver >>> > > Validating models... >>> > > >>> > > 0 errors found >>> > > Django version 1.4, using settings 'dev_setup.settings' >>> > > Development server is running at http://127.0.0.1:8000/ >>> > > Quit the server with CONTROL-C. >>> > > >>> > > >>> > > [root@jaribu] /usr/home/wash# sockstat -l | grep 800 >>> > > root python 77906 3 tcp4 127.0.0.1:8000 >>> > > <http://127.0.0.1:8000> *:* >>> > > root python 14108 43 tcp4 127.0.0.1:8001 >>> > > <http://127.0.0.1:8001> *:* >>> > > >>> > > Since I am not using the server as a Desktop, I need a way to access >>> it >>> > > remotely, not via 127.0.0.1 >>> > >>> > The REST_SERVER setting defines the location of Mailman's rest API >>> > (which is frequently accessed by postorius), *not* the address of >>> > postorius itself. The API can only be accessed from localhost, so the >>> > setting has to be 'http://localhost:8001'. >>> > >>> > If you'd like to access postorius from a different machine as the one >>> > you're running it on, that's no problem: >>> > >>> > Just run the development server like this and you're good to go: >>> > >>> > python manage.py runserver 192.168.x.xxx:8000 >>> > >>> > (Don't do that on a machine that is exposed to the web though, since >>> > Django's dev server is not meant to be run in a production >>> environment.) >>> > >>> > Hope that helps! >>> > >>> > Florian >>> > >>> > >>> >>> My current quest is to see what MM3 web UI looks like, but it appears I >>> am >>> still way behind. >>> I get these errors in the backend when I run posturious and try to access >>> it: >>> >>> http://bit.ly/H2rDuW >>> >> Looks like you didn't start mailman server. Go through this[1] page to >> setup mailman3. >> >> [1] >> http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI… >> >> > Maybe and maybe not, as I was following this very guide! > > [wash@jaribu ~/public_html]$ ps ax | grep mailman > 70295 ?? Is 0:00.40 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/master > 70298 ?? S 0:01.52 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=news:0:1 > 70299 ?? S 0:01.57 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=in:0:1 > 70300 ?? S 0:01.46 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=digest:0:1 > 70301 ?? S 0:01.49 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=pipeline:0:1 > 70302 ?? S 0:01.45 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=archive:0:1 > 70303 ?? S 0:01.46 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=out:0:1 > 70304 ?? I 0:00.41 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=retry:0:1 > 70305 ?? S 0:01.17 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=rest:0:1 > 70306 ?? S 0:01.46 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=bounces:0:1 > 70307 ?? S 0:00.43 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=lmtp:0:1 > 70308 ?? S 0:01.45 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=command:0:1 > 70309 ?? S 0:01.50 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=virgin:0:1 > 78850 1 S+ 0:00.01 grep mailman > > Is there something amiss? > > > [root@jaribu] /usr/home/wash# sockstat -l | grep 800 > root python 70442 3 tcp4 192.168.40.252:8000 *:* > root python 70305 43 tcp4 127.0.0.1:8001 *:* > > > I suppose the 8001 is mailman and 8000 is posturious. Downgrading to django 1.3 might do the trick. Same error here https://answers.launchpad.net/graphite/+question/191549 > > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254733744121/+254722743223 > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > I can't hear you -- I'm using the scrambler. > Please consider the environment before printing this email. > >

1 0

Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
by Terri Oda 29 Mar '12

29 Mar '12

On 12-03-29 12:58 AM, Odhiambo Washington wrote: > My current quest is to see what MM3 web UI looks like, but it appears > I am still way behind. I get these errors in the backend when I run > posturious and try to access it: http://bit.ly/H2rDuW > I'm very fuzzy on this, but I think I got a similar problem during one of my many updates and it was due to updating code without restarting Mailman and re-running syncdb. But I'm pretty sure you don't have an out-of-sync error between mailman.client and postorius like I had then. You might also want to try Django 1.3.1 just in case it's a 1.4 issue. Florian might know more; I haven't upgraded django yet myself. Terri

1 0

Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
by Shayan Md 29 Mar '12

29 Mar '12

On Thu, Mar 29, 2012 at 1:07 PM, Odhiambo Washington <odhiambo(a)gmail.com>wrote: > > > On Thu, Mar 29, 2012 at 10:33, Shayan Md <mdoshayan(a)gmail.com> wrote: > >> >> >> On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington <odhiambo(a)gmail.com >> > wrote: >> >>> On Wed, Mar 28, 2012 at 22:31, Florian Fuchs <f(a)state-of-mind.de> wrote: >>> >>> > Hi Odhiambo, >>> > >>> > Am 28.03.12 18:47, schrieb Odhiambo Washington: >>> > > One more thing: >>> > > >>> > > In settings.py, I have this: >>> > > >>> > > REST_SERVER = 'http://192.168.40.252:8001' >>> > > >>> > > However, this doesn't seem to be respected when I do runserver: >>> > > >>> > > [root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup# >>> > > python manage.py runserver >>> > > Validating models... >>> > > >>> > > 0 errors found >>> > > Django version 1.4, using settings 'dev_setup.settings' >>> > > Development server is running at http://127.0.0.1:8000/ >>> > > Quit the server with CONTROL-C. >>> > > >>> > > >>> > > [root@jaribu] /usr/home/wash# sockstat -l | grep 800 >>> > > root python 77906 3 tcp4 127.0.0.1:8000 >>> > > <http://127.0.0.1:8000> *:* >>> > > root python 14108 43 tcp4 127.0.0.1:8001 >>> > > <http://127.0.0.1:8001> *:* >>> > > >>> > > Since I am not using the server as a Desktop, I need a way to access >>> it >>> > > remotely, not via 127.0.0.1 >>> > >>> > The REST_SERVER setting defines the location of Mailman's rest API >>> > (which is frequently accessed by postorius), *not* the address of >>> > postorius itself. The API can only be accessed from localhost, so the >>> > setting has to be 'http://localhost:8001'. >>> > >>> > If you'd like to access postorius from a different machine as the one >>> > you're running it on, that's no problem: >>> > >>> > Just run the development server like this and you're good to go: >>> > >>> > python manage.py runserver 192.168.x.xxx:8000 >>> > >>> > (Don't do that on a machine that is exposed to the web though, since >>> > Django's dev server is not meant to be run in a production >>> environment.) >>> > >>> > Hope that helps! >>> > >>> > Florian >>> > >>> > >>> >>> My current quest is to see what MM3 web UI looks like, but it appears I >>> am >>> still way behind. >>> I get these errors in the backend when I run posturious and try to access >>> it: >>> >>> http://bit.ly/H2rDuW >>> >> Looks like you didn't start mailman server. Go through this[1] page to >> setup mailman3. >> >> [1] >> http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI… >> >> > Maybe and maybe not, as I was following this very guide! > > [wash@jaribu ~/public_html]$ ps ax | grep mailman > 70295 ?? Is 0:00.40 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/master > 70298 ?? S 0:01.52 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=news:0:1 > 70299 ?? S 0:01.57 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=in:0:1 > 70300 ?? S 0:01.46 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=digest:0:1 > 70301 ?? S 0:01.49 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=pipeline:0:1 > 70302 ?? S 0:01.45 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=archive:0:1 > 70303 ?? S 0:01.46 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=out:0:1 > 70304 ?? I 0:00.41 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=retry:0:1 > 70305 ?? S 0:01.17 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=rest:0:1 > 70306 ?? S 0:01.46 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=bounces:0:1 > 70307 ?? S 0:00.43 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=lmtp:0:1 > 70308 ?? S 0:01.45 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=command:0:1 > 70309 ?? S 0:01.50 /usr/local/bin/python > /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner > --runner=virgin:0:1 > 78850 1 S+ 0:00.01 grep mailman > > Is there something amiss? > > > [root@jaribu] /usr/home/wash# sockstat -l | grep 800 > root python 70442 3 tcp4 192.168.40.252:8000 *:* > root python 70305 43 tcp4 127.0.0.1:8001 *:* > > > I suppose the 8001 is mailman and 8000 is posturious. > > Err.. I was wrong. It must be something else, which I don't know. > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254733744121/+254722743223 > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > I can't hear you -- I'm using the scrambler. > Please consider the environment before printing this email. > >

1 0

Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
by Odhiambo Washington 29 Mar '12

29 Mar '12

On Thu, Mar 29, 2012 at 10:33, Shayan Md <mdoshayan(a)gmail.com> wrote: > > > On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington <odhiambo(a)gmail.com>wrote: > >> On Wed, Mar 28, 2012 at 22:31, Florian Fuchs <f(a)state-of-mind.de> wrote: >> >> > Hi Odhiambo, >> > >> > Am 28.03.12 18:47, schrieb Odhiambo Washington: >> > > One more thing: >> > > >> > > In settings.py, I have this: >> > > >> > > REST_SERVER = 'http://192.168.40.252:8001' >> > > >> > > However, this doesn't seem to be respected when I do runserver: >> > > >> > > [root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup# >> > > python manage.py runserver >> > > Validating models... >> > > >> > > 0 errors found >> > > Django version 1.4, using settings 'dev_setup.settings' >> > > Development server is running at http://127.0.0.1:8000/ >> > > Quit the server with CONTROL-C. >> > > >> > > >> > > [root@jaribu] /usr/home/wash# sockstat -l | grep 800 >> > > root python 77906 3 tcp4 127.0.0.1:8000 >> > > <http://127.0.0.1:8000> *:* >> > > root python 14108 43 tcp4 127.0.0.1:8001 >> > > <http://127.0.0.1:8001> *:* >> > > >> > > Since I am not using the server as a Desktop, I need a way to access >> it >> > > remotely, not via 127.0.0.1 >> > >> > The REST_SERVER setting defines the location of Mailman's rest API >> > (which is frequently accessed by postorius), *not* the address of >> > postorius itself. The API can only be accessed from localhost, so the >> > setting has to be 'http://localhost:8001'. >> > >> > If you'd like to access postorius from a different machine as the one >> > you're running it on, that's no problem: >> > >> > Just run the development server like this and you're good to go: >> > >> > python manage.py runserver 192.168.x.xxx:8000 >> > >> > (Don't do that on a machine that is exposed to the web though, since >> > Django's dev server is not meant to be run in a production environment.) >> > >> > Hope that helps! >> > >> > Florian >> > >> > >> >> My current quest is to see what MM3 web UI looks like, but it appears I am >> still way behind. >> I get these errors in the backend when I run posturious and try to access >> it: >> >> http://bit.ly/H2rDuW >> > Looks like you didn't start mailman server. Go through this[1] page to > setup mailman3. > > [1] > http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI… > > Maybe and maybe not, as I was following this very guide! [wash@jaribu ~/public_html]$ ps ax | grep mailman 70295 ?? Is 0:00.40 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/master 70298 ?? S 0:01.52 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=news:0:1 70299 ?? S 0:01.57 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=in:0:1 70300 ?? S 0:01.46 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=digest:0:1 70301 ?? S 0:01.49 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=pipeline:0:1 70302 ?? S 0:01.45 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=archive:0:1 70303 ?? S 0:01.46 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=out:0:1 70304 ?? I 0:00.41 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=retry:0:1 70305 ?? S 0:01.17 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=rest:0:1 70306 ?? S 0:01.46 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=bounces:0:1 70307 ?? S 0:00.43 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=lmtp:0:1 70308 ?? S 0:01.45 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=command:0:1 70309 ?? S 0:01.50 /usr/local/bin/python /usr/home/wash/Tools/Mailman/MM3/mailman-3.0.0b1/bin/runner --runner=virgin:0:1 78850 1 S+ 0:00.01 grep mailman Is there something amiss? [root@jaribu] /usr/home/wash# sockstat -l | grep 800 root python 70442 3 tcp4 192.168.40.252:8000 *:* root python 70305 43 tcp4 127.0.0.1:8001 *:* I suppose the 8001 is mailman and 8000 is posturious. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email.

1 0