Mailman-Developers May 2012

mailman-developers@python.org

20 participants
55 discussions

by Stanisław Findeisen

Hi! I am running a list. available_languages is set to English (USA) and Polish, and it looks that subject lines of list subscription request (those that I need to approve) e-mails are in those 2 languages. Perhaps this depends on the language the subscribing user has selected. The body is English every time. Moreover, those Polish subject lines are distorted. It looks that they contain some Unicode/whatever but are not encoded at all; and the mail header contains: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Looks like 2 bugs? -- http://people.eisenbits.com/~stf/ http://www.eisenbits.com/ OpenPGP: E3D9 C030 88F5 D254 434C 6683 17DD 22A0 8A3B 5CC0

8 years, 11 months

Re: [Mailman-Developers] Presenting on anti-abuse developments

by Murray S. Kucherawy

> -----Original Message----- > From: mailman-developers-bounces+msk=cloudmark.com(a)python.org [mailto:mailman-developers-bounces+msk=cloudmark.com@python.org] On > Behalf Of Murray S. Kucherawy > Sent: Monday, April 02, 2012 2:59 PM > To: mailman-developers(a)python.org > Subject: [Mailman-Developers] Presenting on anti-abuse developments > > Hi all, > > One of the hats I wear these days is technical committee co-chair for > the Messaging Anti-Abuse Working Group (MAAWG). I'm looking to fill > slots for our Berlin (June) and Baltimore (October) conferences. > > If someone on the mailman development team would like to come and speak > about developments and features of Mailman (especially the new version) > that try to deal with abuse mitigation issues, please contact me off- > list. I have a request in to the executive director to find out what > support we offer to speakers in terms of expenses, etc., so I'll pass > that on once I have it to anyone that replies. I'd like to repeat this invitation. We've filled our slots for Berlin, but I have three available for Baltimore and I think any information you'd like to share on anti-abuse measures going into Mailman v3 would be of great interest. The slots are an hour long each. If you don't think you could fill that time, I can possibly pair you up with another half-session. If you'd like to make a proposal, feel free to say so here or off-list. M. S. Kucherawy MAAWG Technical Co-chair, Messaging

8 years, 11 months

Re: [Mailman-Developers] [GSoC 2012] Metrics

by George Chatzisofroniou

Hello, I'm posting some additional details of my outline for this week. For an easier reading please read it in my blog [1]. -- Following a “top-down design” methodology, i came up with additional detail of my design concept. What information is stored? As i have already mentioned the information is stored in Django models. Author This model represents an author of the mailing list. It mostly keeps track of the number of postings and number of threads started. It has the following fields: mail – CharField (Mail address of the author) totalmails – IntegerField totalthreads – IntegerField firstmsgdate – DateTimeField lastmsgdate – DateTimeField MailingList This model counts the total number of postings and threads started. totalmails – IntegerField totalthreads – IntegerField Month This model associates the author and the mailing list with each month. author – ForeignKey month – CharField postscount – IntegerField threadscount – IntegerField mailinglist – Boolean (if this is true it corresponds to the whole mailing list) Year This model is similar to month. It has a year field instead of a month field. What happens when a new email is posted to the list? - The IArchiver interface will grab the email and send it to the Metrics class. - The Metrics class will update the models: * If the author is sending to the mailing list for the first time, A new Author row will be created to the database. Otherwise, the Posts field will increase by one. - Also, the corresponding row of the two foreign fields (Month and Year) will also increase by one. * The Posts field of the Mailing List model (as well as the the related rows on the Month and Year models) will increase by one. What happens when a user requests the Metrics page? Django will generate a page based on the current models that outputs: - On top, general metrics about total authors, total mails and total threads, based on the MailingList model and below some charts (AJAX based) that represents this information - The authors of the mailing list ordered by the number of their total posts, after the general metrics. Each user will correspond to a more specific page with information like date of first and last message on top and a chart on his overall activity below. What will happen if the app is installed after an existing archive or something crashes on the system? How do the metrics are being recovered? For this case there should be a special ‘Generate’ button in the admin page. When this button is pressed, the class ‘Generate’ will be triggered and: - The Django models will be initialized (the metrics will go back to zero). A progress bar will inform the administrator that the operation is being held. - All the messages of the archive will be parsed by performing a direct Python call to the IArchiver. Another instance to the IArchiver will grab any mails sent while the parsing is going on and store them to a text file. - The metrics will be generated from scratch. - The mails stored to the text file will be added to the metrics - The administrator will be informed with a success message when the process is over. -- [1]: http://sophron.latthi.com/gsoc-mailman/?p=27 -- George Chatzisofroniou sophron.latthi.com

8 years, 11 months

Re: [Mailman-Developers] [GSoC 2012] Metrics

by Barry Warsaw

On May 03, 2012, at 02:04 AM, George Chatzisofroniou wrote: >Interface to the MM core > >The app needs to interact with the Mailman core. I think the best idea >is to implement a message bus that will send a notification every time >a message is sent (the same way an archiver works). Based on this >notification -which will carry the information about the sent message- >the app will be ready to update the counts. > >Although, in some cases (eg the app is installed after an existing >archive or there was an unexpected crash), the message bus should >deliver (triggered by a button) more than one notifications (for the >whole archive) to the app in order to initialize/recover the metrics. >In those cases, the models will be initialized and the generation of >the metrics will start over. Do you know exactly what kind of information you need? The suggestion to use the IArchiver interface is convenient, but might not tell you much other than who posted what to which list on what date. It won't tell you things like the number of recipients, how long that message took to deliver, if there were any failures, etc. The core does know this, and in fact logs it, but all you get at the IArchiver interface is the posted message. It would certainly be possible to hook in a zope.event notification with those metrics for each successfully posted message. From there, a plugin could register a subscriber that put the event data on a message bus. Or you could grep the logs. :) Anyway, I think it would be useful to improve the support for this in the core. Cheers, -Barry

8 years, 11 months

Re: [Mailman-Developers] need tutorial for setting up python development environment on Ubuntu please

by Patrick Ben Koetter

* David <dave(a)fiteyes.com>: > On Fri, May 4, 2012 at 4:22 PM, Barry Warsaw <barry(a)list.org> wrote: > > > On May 04, 2012, at 02:10 PM, David wrote: > > > > Now start up Mailman, your MTA > > > Good up to that point. What is the method for generating aliases for > Postfix in Mailman 3? This has changed im MM3. Postfix now delivers ML mails to MM3 via LMTP. -> http://wiki.list.org/display/DEV/LMTP+process -- state of mind () http://www.state-of-mind.de Franziskanerstraße 15 Telefon +49 89 3090 4664 81669 München Telefax +49 89 3090 4666 Amtsgericht München Partnerschaftsregister PR 563

8 years, 11 months

Re: [Mailman-Developers] [GSoC 2012] Metrics

by Geoff Shang

On Fri, 4 May 2012, George Chatzisofroniou wrote: >> On Thu, May 3, 2012 at 8:04 AM, George Chatzisofroniou >> <sophron(a)latthi.com> wrote: >> >> I don't know how feasible it would be to implement, but if you're >> willing to use AJAX, you could simply build up bar and line charts on >> the fly, adding "slices" of say 5 users at a time on the right side of >> the chart in progress. That might be cool. It could be set in a >> "viewport" and scrolled if it gets too big for the viewport. > > Yes, AJAX can do the job here. I will implement the AJAX bar as you > described, although i think it's better to primarily have a > non-Javascript output. I would just like to restate my plea for the ability to manage Mailman without needing javascript. Note that I'm not saying don't use any, I'm merely asking for it to be possible to use without it. I use lynx as my primary browser, and while general web surfing can be a bit tricky these days, it's very quick and useful for doing admin-type things, and I for one would like to be able to continue to do so. Certainly I have no problems using Mailman 2'.1's interface with lynx, and have been doing so for many years. If my memory serves me correctly, this was generally felt to be a reasonable request when I first mentioned it. I'm sure it's in the archives somewhere. Geoff.

8 years, 11 months

Re: [Mailman-Developers] need tutorial for setting up python development environment on Ubuntu please

by Richard Wackerbarth

> I don't have a dev_setup directory. Also, I want to start the Web GUI on > port 80 for public access via apache. > > The following page is empty: > How to get Postorius running on Apache and mod_wsgi > http://wiki.list.org/display/DEV/How+to+get+Postorius+running+on+Apache+and… David, Postorius is just a Django-based website that communicates with MM3. To deploy it, find, and follow, the directions which apply to any website powered by Django. However, I should warn you that Postorius is not as far along in its development as is the core parts that handle mail. In fact, at this time, there are so many things missing that you will be disappointed if you attempt to make the interface publicly visible. Perhaps it is premature for you to attempt to work with this early development release. Richard

8 years, 11 months

Re: [Mailman-Developers] need tutorial for setting up python development environment on Ubuntu please

by Barry Warsaw

On May 04, 2012, at 02:10 PM, David wrote: >Next Questions: >1. what are the first tests I should perform after starting mailman? Try creating a mailing list from the command line: $ mailman create -d mylist(a)example.com Subscribe some addresses to mylist. Edit a file with a list of email addresses and names using one of these formats, one entry per line: anne(a)example.com (Anne Person) Bart Person <bart(a)example.com> then run $ mailman members -a filename.txt mylist(a)example.com Now start up Mailman, your MTA and send a message to mylist(a)example.com. All the members you just added should get a copy. Check your MTA logs and Mailman's own logs for details or problems. Cheers, -Barry

8 years, 11 months

Re: [Mailman-Developers] need tutorial for setting up python development environment on Ubuntu please

by David

On Fri, May 4, 2012 at 2:10 PM, David <dave(a)fiteyes.com> wrote: > Next Questions: > 1. what are the first tests I should perform after starting mailman? > 2. a tutorial for setting up Posterious? > > Following this guide: http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI… I did these steps: wget http://www.djangoproject.com/download/1.4/tarball/ -O Django-1.4.tar.gz tar xzvf Django-1.4.tar.gz *Question*: could I have instead used # apt-get install python-django python-django-social-auth wget https://launchpad.net/postorius/trunk/1.0.0a1/+download/postorius-1.0.0a.ta… tar xf postorius-1.0.0a.tar.gz source /opt/mailman3/bin/activate /opt/mailman-3.0.0b1# mailman start cd Django-1.4 sudo python setup.py install # cd postorius/ sudo python setup.py develop *Question*: How do I test that these steps have worked so far? Next, the guide ( http://wiki.list.org/display/DEV/A+5+minute+guide+to+get+the+Mailman+web+UI…) mentions: > Start the development server > $ cd dev_setup > $ python manage.py syncdb > $ python manage.py runserver > > The last command will start the dev server on http://localhost:8000 > I don't have a dev_setup directory. Also, I want to start the Web GUI on port 80 for public access via apache. The following page is empty: How to get Postorius running on Apache and mod_wsgi http://wiki.list.org/display/DEV/How+to+get+Postorius+running+on+Apache+and…

8 years, 11 months

Re: [Mailman-Developers] need tutorial for setting up python development environment on Ubuntu please

by David

On Fri, May 4, 2012 at 2:10 PM, David <dave(a)fiteyes.com> wrote: > > I also came across this useful tutorial: > Python Ecosystem - An Introduction > http://mirnazim.org/writings/python-ecosystem-introduction/ > Now I found this too: http://wiki.list.org/display/DEV/mailman3+in+virtualenv - Added by Toshio Kuratomi<http://wiki.list.org/display/%7Etoshio@fedoraproject.org>, last edited by Toshio Kuratomi<http://wiki.list.org/display/%7Etoshio@fedoraproject.org>on Mar 12, 2012 <http://wiki.list.org/display/DEV/mailman3+in+virtualenv#page-metadata-start> * Download all sources by bzr branching:: - lp:mailman - lp:mailmanweb - lp:mailman.client - lp:django_dev_setup - http://bazaar.launchpad.net/~flo-fuchs/mailmanweb/django_dev_setup/ * Create virtualenv and install django $ virtualenv mm3 $ cd mm3 $ source bin/activate $ easy_install django * Import mailman3 sources $ cp ~/path/to/source/downloaded . * Build mailman3: $ cd mailman $ python bootstrap.py $ bin/buildout $ bin/test ## Some seems to be failing * Start Mailman: $ bin/mailman start $ cd .. # Ran into this error when running with sqlite: https://bugs.launchpad.net/mailman/+bug/246867 Changed to postgres according to docs in DATABASE.rst * Install mailman client $ cd mailman.client $ python setup.py develop $ cd .. * Install the mailman web $ cd mailmanweb $ python setup.py develop $ cd .. * Start the project $ cd django_dev_setup $ python manage.py syncdb $ python manage.py runserver

8 years, 11 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

Mailman-Developers May 2012