Mailman 3 January 2015 - Mailman-Developers

Introductory mail
by Stephen J. Turnbull 24 Jan '15

24 Jan '15

Pranjal Yadav writes: > I also learned about previous year's GSOC project and I > can see mailman core is already ported to ver 3.4 however potorius > / hyperkitty / mailman.client needs to be done. Also test suite > would be interesting work to couple with all this. I would like to > know if these 2 projects can be coupled for this year's work or > not? If you think of them as two projects, then they probably are. As a mentor, I won't touch that -- most students have enough trouble just getting started on *one* project. Also, note that projects that are just adding to a test suite are not eligible for Google support. > Apart from that I also found few bugs while setting up > env which was mainly due to (var) folder creation while running > mailman server from different locatin serving various instances. It > seems unless I do it from path/to/mailman it returns an error. I > will go through the code in over next few weeks and till then I can > expect a reply for above projects. You should go over the mailing list archives first. var folder creation was discussed extensively a couple of months ago. In general, if you're going to propose a project not on our list for *this year* (which hasn't been published yet), it is usually helpful to review the past two year's threads on the mailing lists (both mailman-developers and mailman-users) to get an idea of what the current needs are considered to be, and what things the developers are addressing already.

1 0

Re: [Mailman-Developers] Introductory mail
by Barry Warsaw 23 Jan '15

23 Jan '15

On Jan 23, 2015, at 03:15 PM, Rajeev S wrote: >I guess this is not a bug. There is a setting in the mailman.cfg that tells >mailman where to put in the var directory. This has also changed recently in bzr trunk, hopefully for the better. Cheers, -Barry

1 0

Re: [Mailman-Developers] Introductory mail
by Abhilash Raj 23 Jan '15

23 Jan '15

Hi Pranjal! On Thursday 22 January 2015 12:58 PM, Pranjal Yadav wrote: > Hello > > I'm a programming enthusiast and recently started working in > python about 6 months back, I have had experience in cryptography and many > machine learning techniques. I started reading about mailman few weeks back > and I have setup a local and server dev env successfully. > > I also learned about previous year's GSOC project and I can see > mailman core is already ported to ver 3.4 however potorius / hyperkitty / > mailman.client needs to be done. Also test suite would be interesting work > to couple with all this. I would like to know if these 2 projects can be > coupled for this year's work or not? It is not decided yet, but it is expected that postorius and hyperkitty would be ported to be bilingual by this year's pycon. I suggest you look for other project, the list on the wiki will be updated soon. > Apart from that I also found few bugs while setting up env which > was mainly due to (var) folder creation while running mailman server from > different locatin serving various instances. It seems unless I do it from > path/to/mailman it returns an error. I will go through the code in over > next few weeks and till then I can expect a reply for above projects. The var folder creation in the currect directory is a design pattern built for developers. So if mailman does not see any working instance of itself in the current directory it starts a new instance with `var` directory in the new location. You can change this behavior in mailman.cfg, look src/mailman/config/mailman.cfg for [paths.*] sections. > PS : The documentation for mailman setup is outdated I guess, reported that > to @maxking > > -- thanks, Abhilash Raj

1 0

Re: [Mailman-Developers] Introductory mail
by Rajeev S 23 Jan '15

23 Jan '15

On Thu, Jan 22, 2015 at 12:58 PM, Pranjal Yadav <godricglow(a)gmail.com> wrote: > Hello > > I'm a programming enthusiast and recently started working in > python about 6 months back, I have had experience in cryptography and many > machine learning techniques. I started reading about mailman few weeks back > and I have setup a local and server dev env successfully. > > I also learned about previous year's GSOC project and I can see > mailman core is already ported to ver 3.4 however potorius / hyperkitty / > mailman.client needs to be done. Also test suite would be interesting work > to couple with all this. I would like to know if these 2 projects can be > coupled for this year's work or not? > > Apart from that I also found few bugs while setting up env which > was mainly due to (var) folder creation while running mailman server from > different locatin serving various instances. It seems unless I do it from > path/to/mailman it returns an error. I will go through the code in over > next few weeks and till then I can expect a reply for above projects. > > I guess this is not a bug. There is a setting in the mailman.cfg that tells mailman where to put in the var directory. Look for var_dir under [paths.dev] PS : The documentation for mailman setup is outdated I guess, reported that > to @maxking > > > -- > Pranjal Yadav > Final Year Undergraduate Student > Department of Metallurgical and Materials Engineering > IIT Kharagpur > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > https://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: > https://mail.python.org/mailman/options/mailman-developers/rajeevs1992%40gm… > > Security Policy: http://wiki.list.org/x/QIA9 >

1 0

Introductory mail
by Pranjal Yadav 22 Jan '15

22 Jan '15

Hello I'm a programming enthusiast and recently started working in python about 6 months back, I have had experience in cryptography and many machine learning techniques. I started reading about mailman few weeks back and I have setup a local and server dev env successfully. I also learned about previous year's GSOC project and I can see mailman core is already ported to ver 3.4 however potorius / hyperkitty / mailman.client needs to be done. Also test suite would be interesting work to couple with all this. I would like to know if these 2 projects can be coupled for this year's work or not? Apart from that I also found few bugs while setting up env which was mainly due to (var) folder creation while running mailman server from different locatin serving various instances. It seems unless I do it from path/to/mailman it returns an error. I will go through the code in over next few weeks and till then I can expect a reply for above projects. PS : The documentation for mailman setup is outdated I guess, reported that to @maxking -- Pranjal Yadav Final Year Undergraduate Student Department of Metallurgical and Materials Engineering IIT Kharagpur

1 0

REST API first pass at Swagger spec
by Andrew Stuart 20 Jan '15

20 Jan '15

Attached is a first pass at a Swagger spec for the REST API. You can find out about Swagger at http://swagger.io The Swagger spec that I am working on is attached to this message or can be found here: http://www.mailripper.com/api-docs.json If you want to see the attached spec in action against the Mailman REST API, go to http://www.mailripper.com/swagger-ui/index.html Give it a try at http://www.mailripper.com/swagger-ui/index.html - you are welcome to change anything, it’s a test Mailman server and you can add or delete anything - nothing you do will be a problem. There’s still a fair bit to do to finalise this but most of the API queries are working - enough for you to see how it works. Any comments or feedback welcome. as

3 8

installation problems blocking a new developer
by Sumana Harihareswara 20 Jan '15

20 Jan '15

Hi all! Thank you for your IRC help and for merging several of my patches. :) I'm running into installation problems with Mailman and mailman.client . The Mailman core one, I can work around, but the client bug is stopping me from getting a running dev environment so I can fix bugs in Postorius: https://bugs.launchpad.net/mailman/+bug/1411435 after initial install, master runner crashes when config file is missing https://bugs.launchpad.net/mailman.client/+bug/1411653 Installation fails because of bdist_egg I've been improving http://wiki.mailman.psf.io/DEV/A%205%20minute%20guide%20to%20get%20the%20Ma… as I go, and have gotten help from /src/mailman/docs/START.rst and the branch https://bazaar.launchpad.net/~raj-abhilash1/mailman/docs/view/head:/src/mai… . But I am a bit at sea here, and stuck on this bdist_egg problem. Thanks, Sumana -- Sumana Harihareswara http://brainwane.net

4 3

Mailman user identification questions
by Andrew Stuart 19 Jan '15

19 Jan '15

I am working on authenticating users, just want to clarify a few things in concrete. Does every Mailman user have a single, unique userid? Is a Mailman userid secret or public information - i.e. any reason not to use the userid in, for example, a cookie that is potentially public information? Is it possible to be a Mailman user WITHOUT having a related Mailman userid i.e. somehow you can use Mailman with an email address that has no corresponding Mailman userid? Do all email addresses map back to a Mailman userid, or is it possible for email addresses to be in some sort of “orphan/floating state” in which they are not related to a userid? Is it possible for a Mailman user to log in via their email address and password, or only via their userid and password? thanks as

1 0

Re: [Mailman-Developers] MM 3: Virtual Environment Required?
by Terri Oda 19 Jan '15

19 Jan '15

On 2015-01-13, 1:35 PM, Tom Browder wrote: > I want to install, and use, MM 3. I'm on a single-user, Debian 7 > server, and control the whole thing. > > Is it important to use a virtual environment? I'm sure I will be > updating from the development branch until the stable release, and I > am prepared to have interruptions in service along the way. It *can* make your life easier if you're running multiple versions of python (which is why developers often like to use it) but it's definitely not required (even then!). As a core dev, I don't use it on some of my development machines. Terri

1 0

Re: [Mailman-Developers] MM 3: Virtual Environment Required?
by Abhilash Raj 17 Jan '15

17 Jan '15

Hi Tom, On Wednesday 14 January 2015 03:05 AM, Tom Browder wrote: > I want to install, and use, MM 3. I'm on a single-user, Debian 7 > server, and control the whole thing. > > Is it important to use a virtual environment? I'm sure I will be > updating from the development branch until the stable release, and I > am prepared to have interruptions in service along the way. I don't think you would need a virtualenv unless you are developing mailman. You can simply download the source and run `python3.4 setup.py install` to install the latest development version or the 3.0.0b5 release. > Note that I may eventually allow other users, but I will probably > remain the supreme administrator. > > Thanks. > -- thanks, Abhilash Raj

1 0