Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington odhia...@gmail.comwrote: On Wed, Mar 28, 2012 at 22:31, Florian Fuchs f...@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+running -- 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. ___ Mailman-Developers mailing list Mailman-Developers@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/mdoshayan%40gmail.com Security Policy: http://wiki.list.org/x/QIA9 ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Thu, Mar 29, 2012 at 10:33, Shayan Md mdosha...@gmail.com wrote: On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington odhia...@gmail.comwrote: On Wed, Mar 28, 2012 at 22:31, Florian Fuchs f...@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+running 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. image001.png___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Thu, Mar 29, 2012 at 1:07 PM, Odhiambo Washington odhia...@gmail.comwrote: On Thu, Mar 29, 2012 at 10:33, Shayan Md mdosha...@gmail.com wrote: On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington odhia...@gmail.com wrote: On Wed, Mar 28, 2012 at 22:31, Florian Fuchs f...@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+running 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. image001.png___ Mailman-Developers mailing list Mailman-Developers@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:
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Thu, Mar 29, 2012 at 1:07 PM, Odhiambo Washington odhia...@gmail.comwrote: On Thu, Mar 29, 2012 at 10:33, Shayan Md mdosha...@gmail.com wrote: On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington odhia...@gmail.com wrote: On Wed, Mar 28, 2012 at 22:31, Florian Fuchs f...@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+running 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. image001.png___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives:
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Thu, Mar 29, 2012 at 11:12, Shayan Md mdosha...@gmail.com wrote: On Thu, Mar 29, 2012 at 1:07 PM, Odhiambo Washington odhia...@gmail.comwrote: On Thu, Mar 29, 2012 at 10:33, Shayan Md mdosha...@gmail.com wrote: On Thu, Mar 29, 2012 at 12:28 PM, Odhiambo Washington odhia...@gmail.com wrote: On Wed, Mar 28, 2012 at 22:31, Florian Fuchs f...@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+running 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 _ _ _ _ _ _
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Thu, Mar 29, 2012 at 13:53, Florian Fuchs f...@state-of-mind.de wrote: 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. @Florian, My issue here is that I am not running Django 1.4 - unless I am missing something. I am not sure where it is coming from. I am on FreeBSD and I installed django-1.3.1 from the ports. A check on my installed apps shows just that. There is a port for py-django-devel but I did not install that at all: See this [root@jaribu] /usr/ports/www/py-django-devel# make fetch === py27-django-devel-17269,1 conflicts with installed package(s): py27-django-1.3.1 They install files into the same place. You may want to stop build with Ctrl + C. === License check disabled, port has not defined LICENSE = Django-r17269.tar.xz doesn't seem to exist in /usr/ports/distfiles/python. = Attempting to fetch http://people.cs.nctu.edu.tw/~lwhsu/ports/distfiles/Django-r17269.tar.xz Django-r17269.tar.xz 85% of 4135 kB 135 kBps 00m04s That shows I have django-1.3.1 installed. I went as far as this: `mv /usr/local/lib/python2.7/site-packages/django /usr/local/lib/python2.7/site-packages/_django-1.4` Then reinstalled django-1.3.1, but I am pretty sure that the above action wasn't necessary. So I wiped put everything - python, django, mailman, mailman.client, py-sqlite3 - and reinstalled. Mailman gave me enough grief with bin/test and I had to wipe and reinstall several times. Perhaps it wasn't getting all the files during bin/build. Now things look promising, but I still get errors about some templates I need to create - 500.html, 400.html Traceback (most recent call last): File /usr/local/lib/python2.7/site-packages/django/core/servers/basehttp.py, line 283, in run self.result = application(self.environ, self.start_response) File /usr/local/lib/python2.7/site-packages/django/core/handlers/wsgi.py, line 272, in __call__ response = self.get_response(request) File /usr/local/lib/python2.7/site-packages/django/core/handlers/base.py, line 169, in get_response response = self.handle_uncaught_exception(request, resolver, sys.exc_info()) File /usr/local/lib/python2.7/site-packages/django/core/handlers/base.py, line 218, in handle_uncaught_exception return callback(request, **param_dict) File /usr/local/lib/python2.7/site-packages/django/utils/decorators.py, line 93, in _wrapped_view response = view_func(request, *args, **kwargs) File /usr/local/lib/python2.7/site-packages/django/views/defaults.py, line 30, in server_error t = loader.get_template(template_name) # You need to create a 500.html template. File /usr/local/lib/python2.7/site-packages/django/template/loader.py, line 157, in get_template template, origin = find_template(template_name) File /usr/local/lib/python2.7/site-packages/django/template/loader.py, line 138, in find_template raise TemplateDoesNotExist(name) TemplateDoesNotExist: 500.html How do I create these and where do I place them? Where is the guide?? -- 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. image001.png___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
Hi Odhiambo, Am 29.03.12 18:12, schrieb Odhiambo Washington: My issue here is that I am not running Django 1.4 - unless I am missing something. I am not sure where it is coming from. I am on FreeBSD and I installed django-1.3.1 from the ports. A check on my installed apps shows just that. There is a port for py-django-devel but I did not install that at all: See this [root@jaribu] /usr/ports/www/py-django-devel# make fetch === py27-django-devel-17269,1 conflicts with installed package(s): py27-django-1.3.1 They install files into the same place. You may want to stop build with Ctrl + C. === License check disabled, port has not defined LICENSE = Django-r17269.tar.xz doesn't seem to exist in /usr/ports/distfiles/python. = Attempting to fetch http://people.cs.nctu.edu.tw/~lwhsu/ports/distfiles/Django-r17269.tar.xz Django-r17269.tar.xz 85% of 4135 kB 135 kBps 00m04s That shows I have django-1.3.1 installed. I went as far as this: `mv /usr/local/lib/python2.7/site-packages/django /usr/local/lib/python2.7/site-packages/_django-1.4` Then reinstalled django-1.3.1, but I am pretty sure that the above action wasn't necessary. Generally, *if* you have multiple versions installed and want to know which version is actually imported, cd to postorius/dev_setup, open up a Python shell and try the following: import django django.__file__ # prints the package path django.VERSION # prints the django version So I wiped put everything - python, django, mailman, mailman.client, py-sqlite3 - and reinstalled. Mailman gave me enough grief with bin/test and I had to wipe and reinstall several times. Perhaps it wasn't getting all the files during bin/build. Now things look promising, but I still get errors about some templates I need to create - 500.html, 400.html Traceback (most recent call last): File /usr/local/lib/python2.7/site-packages/django/core/servers/basehttp.py, line 283, in run self.result = application(self.environ, self.start_response) File /usr/local/lib/python2.7/site-packages/django/core/handlers/wsgi.py, line 272, in __call__ response = self.get_response(request) File /usr/local/lib/python2.7/site-packages/django/core/handlers/base.py, line 169, in get_response response = self.handle_uncaught_exception(request, resolver, sys.exc_info()) File /usr/local/lib/python2.7/site-packages/django/core/handlers/base.py, line 218, in handle_uncaught_exception return callback(request, **param_dict) File /usr/local/lib/python2.7/site-packages/django/utils/decorators.py, line 93, in _wrapped_view response = view_func(request, *args, **kwargs) File /usr/local/lib/python2.7/site-packages/django/views/defaults.py, line 30, in server_error t = loader.get_template(template_name) # You need to create a 500.html template. File /usr/local/lib/python2.7/site-packages/django/template/loader.py, line 157, in get_template template, origin = find_template(template_name) File /usr/local/lib/python2.7/site-packages/django/template/loader.py, line 138, in find_template raise TemplateDoesNotExist(name) TemplateDoesNotExist: 500.html Django tries to find a 500.html file to display a standard error page. It cannot find one and raises TemplateDoesNotExist. But the more important question is: What's the actual cause for the 500 internal server error? IIRC Django only looks for a 500.html in non-DEBUG mode, so my guess is that your DEBUG setting in dev_setup/settings.py is set to False. If that is the case a good next step would be to set it to True and have a look at the traceback again - it should be much more detailed than the one you're seeing right now and (hopefully) give us a clue what's actullay going wrong. If you like paste the traceback to some of the various pasters out there (like paste.ubuntu.com) and post the link to it here - it's much easier to read then. Florian How do I create these and where do I place them? Where is the guide?? ___ Mailman-Developers mailing list Mailman-Developers@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@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Wed, Mar 28, 2012 at 19:40, Odhiambo Washington odhia...@gmail.comwrote: On Wed, Mar 28, 2012 at 19:13, Florian Fuchs f...@state-of-mind.de wrote: Hi Odhiambo, Am 28.03.12 17:13, schrieb Odhiambo Washington: Hey Jeff and all, I followed the five minute guide, but I am hitting a brickwall: [root@jaribu] /usr/home/wash/Tools/Mailman/MM3/postorius/dev_setup# python manage.py syncdb Traceback (most recent call last): File manage.py, line 29, in module execute_manager(settings) File /usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/__init__.py, line 459, in execute_manager utility.execute() File /usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/__init__.py, line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File /usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/base.py, line 196, in run_from_argv self.execute(*args, **options.__dict__) File /usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/base.py, line 232, in execute output = self.handle(*args, **options) File /usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/base.py, line 371, in handle return self.handle_noargs(**options) File /usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/core/management/commands/syncdb.py, line 57, in handle_noargs cursor = connection.cursor() File /usr/local/lib/python2.7/site-packages/Django-1.4-py2.7.egg/django/db/backends/dummy/base.py, line 15, in complain raise ImproperlyConfigured(settings.DATABASES is improperly configured. django.core.exceptions.ImproperlyConfigured: settings.DATABASES is improperly configured. Please supply the ENGINE value. Check settings documentation for more details. You're doing nothing wrong! Except you're using the latest Django version (1.4) which was released only some days ago... :-) In Django 1.2 support for multiple databases has been added, so they extended the format of the db definition in settings.py. It looks like in 1.4 the old format (which we have used so far) is no longer supported which most definitely causes the above error to be thrown. Changing the DATABASE setting in dev_setup/settings.py should do the trick. Like here: https://docs.djangoproject.com/en/1.4/ref/settings/#databases I will fix that in our launchpad branch as well, so these changes will go into the next alpha (which will probably be released not too far from now... :-) Florian 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*:* root python 14108 43 tcp4 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 -- 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. image001.png___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Wed, Mar 28, 2012 at 20:03, Stephen J. Turnbull step...@xemacs.orgwrote: On Thu, Mar 29, 2012 at 1:40 AM, Odhiambo Washington odhia...@gmail.com wrote: However, I am lost as to why the argument to this procedure was named syncdb and not createdb, which is what it's doing. Can you explain that please? Sorry, I am a noob in this. It's called syncdb because it synchronizes the actual data store with the schema, by creating and updating tables and indexes as necessary. Creating a database is a special case of syncing where the database is completely empty. However, the schema in Django is dynamic; it will automatically add tables and indexes when the Django application is changed. You don't need to know about this unless you plan to dig in and develop the Django application that provides the administration interface. Thank you for the explanation. I actually accept the argument now:) -- 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. image001.png___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Wed, Mar 28, 2012 at 22:31, Florian Fuchs f...@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 Thanks. At least I have a firewall in the name of OpenBSD's PF! I am yearning for the day MM3 will be production-ready. You guys are doing a great job! BTW - Seems MM3 will only be run with Postfix, because the Exim experts have not embraced it:-( -- 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. image001.png___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On 03/24/2012 02:00 AM, Barry Warsaw wrote: Hello Mailman enthusiasts! Use the key, unlock the door See what your fate might have in store... Building on the excitement and amazing progress at our sprints at Pycon 2012, I am very happy to announce the availability of GNU Mailman 3.0 beta 1, code named The Twilight Zone. After nearly four years of design, discussion, and development, we can now see a clear path to a final release. I thank everyone who has helped us get here, by participating on the mailman-developers mailing list, the bug tracker, in private conversations, and code contributions, both to Mailman itself and all the great projects it builds on. Special thanks go to our recent sprinters, Andrea Crotti, Florian Fuchs, Toshio Kuratomi, Daniel Mizyrycki, Terri Oda, Mark Sapiro, and Stephen Turnbull. While you do want to be careful using 3.0b1 in production, I hope that you will get a copy of the code and run it through its paces. Several people are known to be running real mailing lists using the code base. At this point, the feature set is frozen, as is the database schema. We'll use the schema migration machinery to do any schema changes from here to the final release. I'm also ecstatic to announce the first alpha release of Postorius, our new official name for the Django-based Mailman 3 web user interface. The name was suggested by core developer Florian Fuchs in honor of a bass hero of both of ours, Jaco Pastorius. Postorius 1.0 alpha 1 is code named Space Farm. Postorius is in large part based on the great work of Anna Senarclens de Grancy and Benedict Stein who worked on a new Mailman web ui during their Google Summer of Code projects in 2010 and 2011. This alpha version connects to Mailman 3.0's REST API to add and edit lists and domains, as well as to moderate messages. It uses Django's auth app and Mozilla's BrowserID for authentication (a list of the current features is contained in the NEWS file of the package). Apart from the current state there are many more ideas left for the upcoming releases. There is a great team working on the web ui as well as on a new archiver, so stay tuned, and come join us! You can download GNU Mailman 3.0b1 from Launchpad or the Python Cheeseshop: https://launchpad.net/mailman http://pypi.python.org/pypi/mailman Postorius 1.0a1 is available from Launchpad and Cheeseshop as well: https://launchpad.net/postorius http://pypi.python.org/pypi/postorius The GNU Mailman documentation is available online at: http://packages.python.org/mailman/ You can submit bug reports to GNU Mailman and Postorius at: https://bugs.launchpad.net/mailman https://bugs.launchpad.net/postorius GNU Mailman and Postorius are released under the GNU General Public License version 3 or later. Enjoy! -Barry (On behalf of the entire GNU Mailman development team) Great news Barry, but just one thing, I checked now on list.org and the GNU Mailman website and there is no mention of this release.. is that on purpose? ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Mar 23, 2012, at 11:47 PM, Felipe Gasper wrote: No INSTALL file in the tarball? For folks like me who aren’t savvy with Python’s installers and were expecting to find configure/make, it would help a great deal. This may be the wrong list for this, but just in case I stumbled on the right way to install it, I got this when doing sudo python setup.py install: --- Processing dependencies for mailman==3.0.0b1 error: Installed distribution zope.interface 3.5.1 conflicts with requirement zope.interface=3.8.0 --- The online documentation is here: http://packages.python.org/mailman/README.html but I admit that the Getting Started page is a little bit out of date. It's mostly right though. You can also build mm3 in a virtualenv, which is how I actually run it in my test-production servers. This would make a nice easy bug for someone to work on. I've added two official bug tags to the tracker: 'documentation' and 'easy'. Just go to http://bugs.launchpad.net/mailman and use the advanced search to find bugs with either of these tags. If it also has a 'mailman3' official bug tag, then you'll know it's targeted for Mailman 3. Cheers, -Barry ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Mar 26, 2012, at 04:11 PM, Andrea Crotti wrote: Great news Barry, but just one thing, I checked now on list.org and the GNU Mailman website and there is no mention of this release.. is that on purpose? Not really. The server moved recently and my keys hadn't been installed. Looks like they still aren't, so let me ping the admins. -Barry signature.asc Description: PGP signature ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Mar 25, 2012, at 02:34 PM, Jeff Breidenbach wrote: Congratulations! I was able to get Postorius running by following the five minute quick start guide. I didn't see archiving settings in the user interface, how do I set that up? As Mark described, mm3 actually has a nicer architecture for archive integration. You can define multiple archivers system-wide, and there is an interface you can implement if you want to add a new one. Archivers are configured in the mailman.cfg file; i.e. they are system-wide. They cannot currently be configured per-list, although it might be interesting to someday support enabling or disabling them on a per-list basis. Maybe. ;) Note that beta2 will have a somewhat improved implementation here. Each archiver can have a clobber policy and skew interval which generalizes the old Pipermail Date: header clobbering rules, so that it can apply to any archiver. The Mail Archive is already supported in mm3, using the RFC 5064 standard and the X-Message-ID-Hash we discussed a while back. :) -Barry signature.asc Description: PGP signature ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Tue, Mar 27, 2012 at 2:38 AM, Barry Warsaw ba...@list.org wrote: On Mar 23, 2012, at 11:47 PM, Felipe Gasper wrote: No INSTALL file in the tarball? The online documentation is here: http://packages.python.org/mailman/README.html but I admit that the Getting Started page is a little bit out of date. It's mostly right though. You can also build mm3 in a virtualenv, which is how I actually run it in my test-production servers. I spent a fair amount of time on airplanes recently, which I used somewhat productively to do some updating of the docs for the beta. I haven't merged with the release code yet, so maybe there will be conflicts, but the work is at lp:~stephen-xemacs/mailman/beta1-docs Highlights: - s/alpha/beta/ as appropriate A few of the instructions have changed slightly, eg, docs are now built with setup.py build_sphinx, not bin/docs. - Add some discussion of Mailman 3 philosophy (very light) - integrate Florian's Setup the Admin UI in 5 Minutes guide cf. src/mailman/docs/WebUIin5.rst - add a slightly edited version of Toshio's Hyperkitty README cf. src/mailman/docs/ArchiveUIin5.rst This branch is branched from my sprint-2012-overview branch (recently merged, I see, thanks, Barry!) I will be doing an experimental merge in the next day or so, so I'll report on conflicts then. (Aside to Barry: my assignment agreement will go out in the afternoon mail ... uh, maybe not until tomorrow am at this rate, but RSN, anyway.) I'll add the branch URL to the bug, but I can't promise my branch really addresses any of the issues so that's all I'll do with it for now. Cheers, Steve ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
Congratulations! I was able to get Postorius running by following the five minute quick start guide. I didn't see archiving settings in the user interface, how do I set that up? Cheers, Jeff ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On 3/23/2012 9:47 PM, Felipe Gasper wrote: No INSTALL file in the tarball? For folks like me who aren’t savvy with Python’s installers and were expecting to find configure/make, it would help a great deal. This may be the wrong list for this, but just in case I stumbled on the right way to install it, I got this when doing sudo python setup.py install: The installation is python bootstrap.py bin/buildout This and the following steps are described in more detail in src/mailman/docs/START.rst -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Sat, Mar 24, 2012 at 3:00 AM, Barry Warsaw ba...@list.org wrote: Hello Mailman enthusiasts! I'm also ecstatic to announce the first alpha release of Postorius, our new official name for the Django-based Mailman 3 web user interface. The name was suggested by core developer Florian Fuchs in honor of a bass hero of both of ours, Jaco Pastorius. Postorius 1.0 alpha 1 is code named Space Farm. I can't wait for Gene Simmons and Tal Wilkenfeld! :-) ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
Hello Mailman enthusiasts! Use the key, unlock the door See what your fate might have in store... Building on the excitement and amazing progress at our sprints at Pycon 2012, I am very happy to announce the availability of GNU Mailman 3.0 beta 1, code named The Twilight Zone. After nearly four years of design, discussion, and development, we can now see a clear path to a final release. I thank everyone who has helped us get here, by participating on the mailman-developers mailing list, the bug tracker, in private conversations, and code contributions, both to Mailman itself and all the great projects it builds on. Special thanks go to our recent sprinters, Andrea Crotti, Florian Fuchs, Toshio Kuratomi, Daniel Mizyrycki, Terri Oda, Mark Sapiro, and Stephen Turnbull. While you do want to be careful using 3.0b1 in production, I hope that you will get a copy of the code and run it through its paces. Several people are known to be running real mailing lists using the code base. At this point, the feature set is frozen, as is the database schema. We'll use the schema migration machinery to do any schema changes from here to the final release. I'm also ecstatic to announce the first alpha release of Postorius, our new official name for the Django-based Mailman 3 web user interface. The name was suggested by core developer Florian Fuchs in honor of a bass hero of both of ours, Jaco Pastorius. Postorius 1.0 alpha 1 is code named Space Farm. Postorius is in large part based on the great work of Anna Senarclens de Grancy and Benedict Stein who worked on a new Mailman web ui during their Google Summer of Code projects in 2010 and 2011. This alpha version connects to Mailman 3.0's REST API to add and edit lists and domains, as well as to moderate messages. It uses Django's auth app and Mozilla's BrowserID for authentication (a list of the current features is contained in the NEWS file of the package). Apart from the current state there are many more ideas left for the upcoming releases. There is a great team working on the web ui as well as on a new archiver, so stay tuned, and come join us! You can download GNU Mailman 3.0b1 from Launchpad or the Python Cheeseshop: https://launchpad.net/mailman http://pypi.python.org/pypi/mailman Postorius 1.0a1 is available from Launchpad and Cheeseshop as well: https://launchpad.net/postorius http://pypi.python.org/pypi/postorius The GNU Mailman documentation is available online at: http://packages.python.org/mailman/ You can submit bug reports to GNU Mailman and Postorius at: https://bugs.launchpad.net/mailman https://bugs.launchpad.net/postorius GNU Mailman and Postorius are released under the GNU General Public License version 3 or later. Enjoy! -Barry (On behalf of the entire GNU Mailman development team) signature.asc Description: PGP signature ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Mar 23, 2012, at 9:00 PM, Barry Warsaw ba...@list.org wrote: Use the key, unlock the door See what your fate might have in store... Everybody walk the dinosaur! Seriously though, this is amazing news! Thanks to everyone who helped work on this. I can't wait to give it a try! Cheers, Justin ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
No INSTALL file in the tarball? For folks like me who aren’t savvy with Python’s installers and were expecting to find configure/make, it would help a great deal. This may be the wrong list for this, but just in case I stumbled on the right way to install it, I got this when doing sudo python setup.py install: --- Processing dependencies for mailman==3.0.0b1 error: Installed distribution zope.interface 3.5.1 conflicts with requirement zope.interface=3.8.0 --- -FG On 23.3.12 9:00 PM, Barry Warsaw wrote: Hello Mailman enthusiasts! Use the key, unlock the door See what your fate might have in store... Building on the excitement and amazing progress at our sprints at Pycon 2012, I am very happy to announce the availability of GNU Mailman 3.0 beta 1, code named The Twilight Zone. After nearly four years of design, discussion, and development, we can now see a clear path to a final release. I thank everyone who has helped us get here, by participating on the mailman-developers mailing list, the bug tracker, in private conversations, and code contributions, both to Mailman itself and all the great projects it builds on. Special thanks go to our recent sprinters, Andrea Crotti, Florian Fuchs, Toshio Kuratomi, Daniel Mizyrycki, Terri Oda, Mark Sapiro, and Stephen Turnbull. While you do want to be careful using 3.0b1 in production, I hope that you will get a copy of the code and run it through its paces. Several people are known to be running real mailing lists using the code base. At this point, the feature set is frozen, as is the database schema. We'll use the schema migration machinery to do any schema changes from here to the final release. I'm also ecstatic to announce the first alpha release of Postorius, our new official name for the Django-based Mailman 3 web user interface. The name was suggested by core developer Florian Fuchs in honor of a bass hero of both of ours, Jaco Pastorius. Postorius 1.0 alpha 1 is code named Space Farm. Postorius is in large part based on the great work of Anna Senarclens de Grancy and Benedict Stein who worked on a new Mailman web ui during their Google Summer of Code projects in 2010 and 2011. This alpha version connects to Mailman 3.0's REST API to add and edit lists and domains, as well as to moderate messages. It uses Django's auth app and Mozilla's BrowserID for authentication (a list of the current features is contained in the NEWS file of the package). Apart from the current state there are many more ideas left for the upcoming releases. There is a great team working on the web ui as well as on a new archiver, so stay tuned, and come join us! You can download GNU Mailman 3.0b1 from Launchpad or the Python Cheeseshop: https://launchpad.net/mailman http://pypi.python.org/pypi/mailman Postorius 1.0a1 is available from Launchpad and Cheeseshop as well: https://launchpad.net/postorius http://pypi.python.org/pypi/postorius The GNU Mailman documentation is available online at: http://packages.python.org/mailman/ You can submit bug reports to GNU Mailman and Postorius at: https://bugs.launchpad.net/mailman https://bugs.launchpad.net/postorius GNU Mailman and Postorius are released under the GNU General Public License version 3 or later. Enjoy! -Barry (On behalf of the entire GNU Mailman development team) ___ Mailman-Developers mailing list Mailman-Developers@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/felipe%40felipegasper.com Security Policy: http://wiki.list.org/x/QIA9 ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
