From sumanah at panix.com Thu Apr 2 05:03:13 2015 From: sumanah at panix.com (Sumana Harihareswara) Date: Wed, 01 Apr 2015 23:03:13 -0400 Subject: [Mailman-Developers] LWN article about the upcoming Mailman suite's 3.0 release Message-ID: <551CB171.6060801@panix.com> I wrote this article for LWN about what's new in the upcoming release and implications for the larger open source ecosystem: http://lwn.net/SubscriberLink/638090/0229275ea355532b/ I took screenshots of HyperKitty and Postorius, in case you want to see! The comments have some interesting thoughts as well. Thanks to the Mailman development team for answering my questions via IRC and email as I was writing this! -- Sumana Harihareswara http://brainwane.net From andrew.stuart at supercoders.com.au Sat Apr 4 05:30:45 2015 From: andrew.stuart at supercoders.com.au (Andrew Stuart) Date: Sat, 4 Apr 2015 14:30:45 +1100 Subject: [Mailman-Developers] How to validate mailing list-id? Message-ID: <28CE5CCB-E718-4684-BBAF-A0767C8B6DE2@supercoders.com.au> I?ve read RFC2919 https://www.ietf.org/rfc/rfc2919.txt which says: "The list header fields are subject to the encoding and character restrictions for mail headers as described in [RFC822]." RFC822 http://www.w3.org/Protocols/rfc822/ says: "The field-body may be composed of any ASCII characters, except CR or LF. (While CR and/or LF may be present in the actual text, they are removed by the action of unfolding the field.)" Am I correct in understanding then that a mailing list-id may be composed of any ASCII characters? Thus this is a valid mailing list-id: ///*/etc/pw.txt Is this function an accurate validator for a mailing list-id? def is_valid_list_id(list_id): try: list_id.decode('ASCII') except UnicodeDecodeError: return False else: return True From mark at msapiro.net Sat Apr 4 07:26:37 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 03 Apr 2015 22:26:37 -0700 Subject: [Mailman-Developers] How to validate mailing list-id? In-Reply-To: <28CE5CCB-E718-4684-BBAF-A0767C8B6DE2@supercoders.com.au> References: <28CE5CCB-E718-4684-BBAF-A0767C8B6DE2@supercoders.com.au> Message-ID: <551F760D.70400@msapiro.net> On 04/03/2015 08:30 PM, Andrew Stuart wrote: > > Am I correct in understanding then that a mailing list-id may be composed of any ASCII characters? No. > Thus this is a valid mailing list-id: ///*/etc/pw.txt No. It is a valid 'list-label', but a list-id is a list label followed by a dot followed by 'localhost' or a domain name and the characters that can appear in a domain name are much more restricted, i.e. only dot separated strings of letters, digits and hyphens, not beginning with hyphen. And even a list-label can't contain any ascii character or even any ascii printable character. >From RFC2919 Sec 2 The syntax for a list identifier in ABNF [RFC2234] follows: list-id = list-label "." list-id-namespace list-label = dot-atom-text list-id-namespace = domain-name / unmanaged-list-id-namespace unmanaged-list-id-namespace = "localhost" domain-name = dot-atom-text Where: dot-atom-text is defined in [DRUMS] "localhost" is a reserved domain name is defined in [RFC2606] Unfortunately, the [DRUMS] reference is missing in this RFC, but dot-atom-text is defined in RFCs 2822 and 5322 as dot-atom-text = 1*atext *("." 1*atext) and atext atext = ALPHA / DIGIT / ; Printable US-ASCII "!" / "#" / ; characters not including "$" / "%" / ; specials. Used for atoms. "&" / "'" / "*" / "+" / "-" / "/" / "=" / "?" / "^" / "_" / "`" / "{" / "|" / "}" / "~" > Is this function an accurate validator for a mailing list-id? > > def is_valid_list_id(list_id): > try: > list_id.decode('ASCII') > except UnicodeDecodeError: > return False > else: > return True No. not only will it accept specials;, it will accept controls 0x00 - 0x1f and 0x7f, so it's not even a good validator for list-label. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From sumanah at panix.com Tue Apr 7 22:03:28 2015 From: sumanah at panix.com (Sumana Harihareswara) Date: Tue, 07 Apr 2015 16:03:28 -0400 Subject: [Mailman-Developers] prepping TODO list for PyCon sprints next week Message-ID: <55243810.7030800@panix.com> The PyCon sprints are Monday, April 13th 2015 -- Thursday, April 16th 2015 in Montr?al and are free to attend. http://wiki.list.org/DEV/PyCon%202015%20Sprint Please add yourself to that page if you're coming (if you're not going to be there all 4 days, it would be cool if you could say that so people know when they can find you). The main thing people seem to want to do: release the 3.0 version of the suite. The blockers to release: http://wiki.list.org/DEV/Mailman%203.0 Please do go ahead and update that page and/or the relevant bugs if they're already fixed. best, Sumana -- Sumana Harihareswara http://brainwane.net From andrew.stuart at supercoders.com.au Wed Apr 8 00:52:58 2015 From: andrew.stuart at supercoders.com.au (Andrew Stuart) Date: Wed, 8 Apr 2015 08:52:58 +1000 Subject: [Mailman-Developers] Currently on HN front page Message-ID: https://news.ycombinator.com/item?id=9336291 From ankush.sharma.ece12 at iitbhu.ac.in Mon Apr 13 11:48:12 2015 From: ankush.sharma.ece12 at iitbhu.ac.in (Ankush Sharma) Date: Mon, 13 Apr 2015 15:18:12 +0530 Subject: [Mailman-Developers] Approach for making Editable fields in user profile Message-ID: Hello everyone, I need to discuss in context with the feature request https://bugs.launchpad.net/postorius/+bug/1432383. The point is to make the fields like irc handle, first-name, last-name etc. editable in the user profile. User registration is currently done using *django-browserid *with the default *User Model. *There are no schema rules for these *extra *fields in the *auth_user *table of the underlying Postorius database due to the use of the default *User Model*. I am thinking of using a CustomBackend class overriding the BrowserIdBackend class for adding customisation *[1]*. Also, I think it would be required to have a *new *User model for these extra fields which can be used by django-browserid for the initial user registration. Initially, these *extra *fields can be set to *empty*. Later on, with the help of an update view users can be asked to update their profiles when they login. This would require the use of database migrations. Other option is to use to create an extra table for these fields and for it the default *User model *would be suffice. In this case, an extra form would do the job. I want to ask whether my approach is correct ? Or it would be more meaningful to take input for these fields during the first time when the user registers by using Persona ? ( I guess it would require some ugly tweaks ) Waiting for your opinion on it ! Thanks, Ankush Sharma IIT-BHU, Varanasi India *github.com/black-perl * [1] : http://django-browserid.readthedocs.org/en/latest/user/customization.html#automatic-user-creation From ankush.sharma.ece12 at iitbhu.ac.in Mon Apr 13 15:31:23 2015 From: ankush.sharma.ece12 at iitbhu.ac.in (Ankush Sharma) Date: Mon, 13 Apr 2015 19:01:23 +0530 Subject: [Mailman-Developers] [ Query ] Some bugs in postorius that needs to be addressed Message-ID: Hello everyone, I have found a good some bugs in postorius. Needs your review before fixing them. *1.* The *list_moderator* is not able to access the list of held messages as visiting at /postorius/lists/*/held_messages *gives a *403 *i.e *Forbidden* Status code because it is simply not allowed to access it. I have discussed the cause and fix for this issue here https://bugs.launchpad.net/postorius/+bug/1443433 . I am assuming the *list_owner* to be a *list_moderator* in my fix as indicated by http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/postorius/auth/decorators.py#L88 *2. *At http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/postorius/templates/postorius/menu/list_nav.html#L18 ; why a *list_moderator *is allowed to view the `*Mass Subscribe`* link on the list navigation bar ? Though clicking it will give a *403* again as he has not permission for it. I think it should be *list_owner. * *3. *The *list_navigation menu *containing the links to Info, Settings, Mass Subscribe, Delete etc. options for a list are only visible to the *super_user. *Though, a *list_owner *should be able to see these for his *owned lists *and similarly a *list_moderator *should be able to see the *held messages *option in his navigation menu. This can be fixed by replacing the line: http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/postorius/templates/postorius/lists/summary.html#L10 by % if user.is_superuser or user.is_list_owner or user.is_moderator %} As we have a second level permission check before rendering the respective options implemented in the file : http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/postorius/templates/postorius/menu/list_nav.html . Doing this will cause proper person to see the options that he is allowed to do in his navigation menu. More on this here : https://bugs.launchpad.net/postorius/+bug/1443400 Thanks, Ankush Sharma IIT-BHU,Varanasi India github.com/black-perl From ankush.sharma.ece12 at iitbhu.ac.in Mon Apr 13 15:35:25 2015 From: ankush.sharma.ece12 at iitbhu.ac.in (Ankush Sharma) Date: Mon, 13 Apr 2015 19:05:25 +0530 Subject: [Mailman-Developers] [ Query ] Some bugs in postorius that needs to be addressed In-Reply-To: References: Message-ID: Sorry for the typo `good` is not required in the first line. On Mon, Apr 13, 2015 at 7:01 PM, Ankush Sharma < ankush.sharma.ece12 at iitbhu.ac.in> wrote: > Hello everyone, > > I have found a good some bugs in postorius. Needs your review before > fixing them. > > *1.* The *list_moderator* is not able to access the list of held messages > as visiting at /postorius/lists/*/held_messages *gives > a *403 *i.e *Forbidden* Status code because it is simply not allowed to > access it. I have discussed the cause and fix for this issue here > https://bugs.launchpad.net/postorius/+bug/1443433 . > I am assuming the *list_owner* to be a *list_moderator* in my fix as > indicated by > http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/postorius/auth/decorators.py#L88 > > *2. *At > http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/postorius/templates/postorius/menu/list_nav.html#L18 ; why > a *list_moderator *is allowed to view the `*Mass Subscribe`* link on the > list navigation bar ? Though clicking it will give a *403* again as he > has not permission for it. I think it should be *list_owner. * > > *3. *The *list_navigation menu *containing the links to Info, Settings, > Mass Subscribe, Delete etc. options for a list are only visible to the *super_user. > *Though, a *list_owner *should be able to see these for his *owned lists *and > similarly a *list_moderator *should be able to see the *held messages *option > in his navigation menu. This can be fixed by replacing the line: http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/postorius/templates/postorius/lists/summary.html#L10 > by > > % if user.is_superuser or user.is_list_owner or user.is_moderator %} > > As we have a second level permission check before rendering the respective > options implemented in the file : > http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/postorius/templates/postorius/menu/list_nav.html > . > Doing this will cause proper person to see the options that he is allowed > to do in his navigation menu. More on this here : > https://bugs.launchpad.net/postorius/+bug/1443400 > > Thanks, > > Ankush Sharma > IIT-BHU,Varanasi > India > github.com/black-perl > > From sumanah at panix.com Mon Apr 13 21:38:56 2015 From: sumanah at panix.com (Sumana Harihareswara) Date: Mon, 13 Apr 2015 15:38:56 -0400 Subject: [Mailman-Developers] Update from Day 1 of the PyCon sprints Message-ID: <552C1B50.8040403@panix.com> Hi all! Eight of us have started on our first day of the PyCon sprints and have started our push towards the Mailman suite 3.0 release, which will also include Postorius 1.0 and HyperKitty 1.0 releases. http://wiki.list.org/DEV/PyCon%202015%20Sprint lists what we are trying to finish up this week; we've moved some nice-to-have stuff to the "3.1" section in http://wiki.list.org/DEV/Mailman%203.0 (probably the 3.1 version of the Mailman Suite will include HyperKitty 1.1 and Postorius 1.1; mailman-bundler will help enforce this sort of component version alignment). Our goal for the 3.0 release is: We're blessing this as working, we encourage people to install it fresh, and we think new installations will work well. You might be able to upgrade existing lists, but if you're upgrading from 2.x, test and make backups first. We do not promise feature parity with 2.x. Also, probably not this week, but soon, we're going to move the HyperKitty bug tracker and wiki content from fedorahosted to a new Launchpad project and to wiki.list.org, to reduce the number of different places we do bugtracking and documentation. I'll be leading that, probably in May. -- Sumana Harihareswara http://brainwane.net From ankush.sharma.ece12 at iitbhu.ac.in Mon Apr 13 21:49:46 2015 From: ankush.sharma.ece12 at iitbhu.ac.in (Ankush Sharma) Date: Tue, 14 Apr 2015 01:19:46 +0530 Subject: [Mailman-Developers] [ Query ] Some bugs in postorius that needs to be addressed In-Reply-To: References: Message-ID: The above bugs have been discussed in detail with Bhavesh Goyal with involvement of Terri. I think fixing https://code.launchpad.net/~bhavesh-goyal093/postorius/fixed-nav-role-identification would work ! On Mon, Apr 13, 2015 at 7:05 PM, Ankush Sharma < ankush.sharma.ece12 at iitbhu.ac.in> wrote: > Sorry for the typo `good` is not required in the first line. > > On Mon, Apr 13, 2015 at 7:01 PM, Ankush Sharma < > ankush.sharma.ece12 at iitbhu.ac.in> wrote: > >> Hello everyone, >> >> I have found a good some bugs in postorius. Needs your review before >> fixing them. >> >> *1.* The *list_moderator* is not able to access the list of held >> messages as visiting at /postorius/lists/*/held_messages >> *gives a *403 *i.e *Forbidden* Status code because it is simply not >> allowed to access it. I have discussed the cause and fix for this issue >> here https://bugs.launchpad.net/postorius/+bug/1443433 . >> I am assuming the *list_owner* to be a *list_moderator* in my fix as >> indicated by >> http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/postorius/auth/decorators.py#L88 >> >> *2. *At >> http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/postorius/templates/postorius/menu/list_nav.html#L18 ; why >> a *list_moderator *is allowed to view the `*Mass Subscribe`* link on the >> list navigation bar ? Though clicking it will give a *403* again as he >> has not permission for it. I think it should be *list_owner. * >> >> *3. *The *list_navigation menu *containing the links to Info, Settings, >> Mass Subscribe, Delete etc. options for a list are only visible to the *super_user. >> *Though, a *list_owner *should be able to see these for his *owned >> lists *and similarly a *list_moderator *should be able to see the *held >> messages *option in his navigation menu. This can be fixed by replacing >> the line: http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/postorius/templates/postorius/lists/summary.html#L10 >> by >> >> % if user.is_superuser or user.is_list_owner or user.is_moderator %} >> >> As we have a second level permission check before rendering the >> respective options implemented in the file : >> http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/view/head:/src/postorius/templates/postorius/menu/list_nav.html >> . >> Doing this will cause proper person to see the options that he is allowed >> to do in his navigation menu. More on this here : >> https://bugs.launchpad.net/postorius/+bug/1443400 >> >> Thanks, >> >> Ankush Sharma >> IIT-BHU,Varanasi >> India >> github.com/black-perl >> >> > > From terri at toybox.ca Wed Apr 15 00:44:18 2015 From: terri at toybox.ca (Terri Oda) Date: Tue, 14 Apr 2015 18:44:18 -0400 Subject: [Mailman-Developers] Outstanding postorius merge requests (was Re: [ Query ] Some bugs in postorius that needs to be addressed) In-Reply-To: References: Message-ID: <552D9842.1090401@toybox.ca> On 2015-04-13 3:49 PM, Ankush Sharma wrote: > The above bugs have been discussed in detail with Bhavesh Goyal with > involvement of Terri. I think fixing > https://code.launchpad.net/~bhavesh-goyal093/postorius/fixed-nav-role-identification > would > work ! This has been merged, thanks all! Incidentally, I spent most of yesterday and some of today reviewing outstanding postorius merge proposals. You can see the list of ones that I got in here: http://bazaar.launchpad.net/~mailman-coders/postorius/trunk/changes And I've sent out fix required notes to a few folk because I couldn't get things running easily. There's still a few I haven't looked at as well. I'm switching over to doing some work on a docker image for mailman so I won't be doing as many merge requests tomorrow, but if any of you are hoping to have a merge happen while I'm at PyCon, I'd totally appreciate it if you could check your merge against the latest updates (as you can see, there's been a few commits) and make sure to run the tox tests. Once you've got it all working, hit me up on IRC and I'll see what I can do! And, of course, helping try out other people's merge proposals and do any initial debugging is always awesome. As is adding more tests! :) Terri From sumanah at panix.com Thu Apr 16 04:53:02 2015 From: sumanah at panix.com (Sumana Harihareswara) Date: Wed, 15 Apr 2015 22:53:02 -0400 Subject: [Mailman-Developers] Help us release Mailman suite 3.0 tomorrow Message-ID: <552F240E.7070908@panix.com> Hello from Montreal (PyCon sprints, day 3). You've probably seen a flurry of updates to Mailman core, Postorius, HyperKitty, and even the client and bundler. We've finished all the must-have changes in HyperKitty, we've improved subscriber address options in Postorius, and we're nearly done with the new subscription policy. But we still have to test the installation more -- and we'd love your help doing that. And we're not 100% done with the subscription policy work, and we need to write release notes and update installation HOWTOs. You can help! Try to reproduce: * https://bugs.launchpad.net/postorius/+bug/1036207 mailman.client hangs accessing moderation queue * https://bugs.launchpad.net/postorius/+bug/1062963 Admin notification not received Write some nice-to-have bugfixes: * https://fedorahosted.org/hyperkitty/ticket/90 display of poster's email address overlaps with message excerpt * https://fedorahosted.org/hyperkitty/ticket/91 search result page should include name of list * https://fedorahosted.org/hyperkitty/ticket/96 When displaying a post, include a link to parent post * https://bugs.launchpad.net/postorius/+bug/1443643 Test for invalid email addresses in mass subscribe * https://bugs.launchpad.net/postorius/+bug/1444699 I can't add a single member (non-owner, non-moderator) from the Members page. * https://bugs.launchpad.net/postorius/+bug/1443995 Need tests for list moderator views -- Sumana Harihareswara http://brainwane.net From terri at toybox.ca Thu Apr 16 05:14:40 2015 From: terri at toybox.ca (Terri Oda) Date: Wed, 15 Apr 2015 23:14:40 -0400 Subject: [Mailman-Developers] Mailman3 Suite in Docker! (Also: probably decent recipe for ubuntu 14.04) Message-ID: <552F2920.5000805@toybox.ca> Hey all, I've got a Dockerfile up here for those of you who might want to try dumping Mailman3 suite into a container and watching it go: http://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile This gets everything running with some default configs, and I can tell that it at least gets the websites up inside the container. (If you do a little mental translation, you can use those same instructions to set up on a fresh Ubuntu 14.04 install, I presume.) The problem is that I'm both very tired after PyCon+sprints and very new to Docker, and I don't know what instructions I need for people to run that and wire the ports up so you can connect to postorius and hyperkitty on your local machine. Can anyone help with that? Terri From terri at toybox.ca Thu Apr 16 15:07:51 2015 From: terri at toybox.ca (Terri Oda) Date: Thu, 16 Apr 2015 09:07:51 -0400 Subject: [Mailman-Developers] Mailman3 Suite in Docker! (Also: probably decent recipe for ubuntu 14.04) In-Reply-To: References: <552F2920.5000805@toybox.ca> Message-ID: Oh, right. Change 'source' to '.' I did that last night but apparently didn't update the wiki. And it's a wiki, you can update it without needing pull requests :) On April 16, 2015 1:35:41 AM EDT, Pranjal Mittal wrote: >Hi Terri, > >There seems to be an issue in the step that activates the venv in the >Dockerfile i.e.: >RUN source venv/bin/activate > >Here is the last part of from my docker build logs which shows the >error: >http://dpaste.com/2PG8THT > >The error happens because while building the docker image the default >shell >used is not bash. /bin/sh need not be bash which makes the source >command >fail (because it will only work in bash). > >I have updated the docker file which should fix this issue: >http://dpaste.com/0ZGFR51 > >I can help with docker integration but keeping a little busy with >catching >up on academics after Pycon; will work on it from next week. Can we add >this file to some github repo to be able to send PR's, etc >conveniently? > > >Thanks, >- Pranjal > >On Wed, Apr 15, 2015 at 8:14 PM, Terri Oda wrote: > >> Hey all, >> >> I've got a Dockerfile up here for those of you who might want to try >> dumping Mailman3 suite into a container and watching it go: >> >> >http://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile >> >> This gets everything running with some default configs, and I can >tell >> that it at least gets the websites up inside the container. >> >> (If you do a little mental translation, you can use those same >> instructions to set up on a fresh Ubuntu 14.04 install, I presume.) >> >> The problem is that I'm both very tired after PyCon+sprints and very >new >> to Docker, and I don't know what instructions I need for people to >run that >> and wire the ports up so you can connect to postorius and hyperkitty >on >> your local machine. >> >> Can anyone help with that? >> >> Terri >> >> _______________________________________________ >> Mailman-Developers mailing list >> Mailman-Developers at 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/mittal.pranjal%40gmail.com >> >> Security Policy: http://wiki.list.org/x/QIA9 >> From coolyashish at gmail.com Thu Apr 16 20:45:32 2015 From: coolyashish at gmail.com (Ashish Kumar) Date: Fri, 17 Apr 2015 00:15:32 +0530 Subject: [Mailman-Developers] Regarding Csv Export for list owner in postorius Message-ID: Hi Everyone, Recently My branch for feature request of csv export option for list owner to get the members of a list got merged. I was thinking of extending this feature request to pdf and sharing the list of members on drive, as It will be very helpful for communities which have a lot of volunteers, organizers. Scenario: Suppose a team of volunteers working in a country/state like bloodconnect in india. For an activity like camps [in case of blood connect], Owner need to send a pdf of all the volunteers working in a specific area to the area head either by drive or mail. It would be very convenient if we provide these option as a UI in postorius itself. Thanks Ashish Kumar From tom.browder at gmail.com Fri Apr 17 15:58:52 2015 From: tom.browder at gmail.com (Tom Browder) Date: Fri, 17 Apr 2015 08:58:52 -0500 Subject: [Mailman-Developers] [Mailman-Users] 3.0 testing... In-Reply-To: <5530E301.2020008@mcfsoftware.com> References: <55270CFC.3080308@mcfsoftware.com> <5530E301.2020008@mcfsoftware.com> Message-ID: On Fri, Apr 17, 2015 at 5:40 AM, Farokh Irani wrote: > Hi everyone. > > I posted the message below a while back, but never saw a reply. Did I miss > it? ? ? >> Farokh Irani >> April 9, 2015 at 19:36 >> >> If I set up a machine to test 3.0, will I be able to simply install the >> official 3.0 release over it, or should I plan on doing a completely clean >> install?? ?Probably have better luck with dev list for MM 3. Best, -Tom? From tom.browder at gmail.com Fri Apr 17 16:01:58 2015 From: tom.browder at gmail.com (Tom Browder) Date: Fri, 17 Apr 2015 09:01:58 -0500 Subject: [Mailman-Developers] Regarding Csv Export for list owner in postorius In-Reply-To: References: Message-ID: On Thu, Apr 16, 2015 at 1:45 PM, Ashish Kumar wrote: > Hi Everyone, > > Recently My branch for feature request of csv export option for list owner > to get the members of a list got merged. I was thinking of extending this > feature request to pdf and sharing the list of members on drive, as It will A plain text file would be good also (easier to handle programmatically than csv IMHO). Best, -Tom From danil at smirnov.la Fri Apr 17 18:04:58 2015 From: danil at smirnov.la (Danil Smirnov) Date: Fri, 17 Apr 2015 19:04:58 +0300 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 Message-ID: I'm trying to install Mailman 3 using this manual: http://mailman-bundler.readthedocs.org/en/latest/ After step (venv)[root at host src]# pip install zc.buildout (venv)[root at host src]# buildout I've got an error ---- Installing mailman. The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) does not exist /tmp/tmpuGe9kP/run: line 2: /usr/local/src/mailman-bundler/venv-3.4/bin/pip: File or directory not found While: Installing mailman. ---- I have Python 3.4. in /usr/local/bin directory, not /usr/bin. Please help. Danil From godricglow at gmail.com Fri Apr 17 18:59:11 2015 From: godricglow at gmail.com (Pranjal Yadav) Date: Fri, 17 Apr 2015 22:29:11 +0530 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: References: Message-ID: Can you check with "where python3" and post the output. On Fri, Apr 17, 2015 at 9:34 PM, Danil Smirnov wrote: > I'm trying to install Mailman 3 using this manual: > http://mailman-bundler.readthedocs.org/en/latest/ > > After step > (venv)[root at host src]# pip install zc.buildout > (venv)[root at host src]# buildout > > I've got an error > ---- > Installing mailman. > The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) does > not exist > /tmp/tmpuGe9kP/run: line 2: > /usr/local/src/mailman-bundler/venv-3.4/bin/pip: File or directory not > found > While: > Installing mailman. > ---- > > I have Python 3.4. in /usr/local/bin directory, not /usr/bin. > > Please help. > > Danil > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at 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/godricglow%40gmail.com > > Security Policy: http://wiki.list.org/x/QIA9 > -- *Pranjal Yadav* *IIT Kharagpur* From danil at smirnov.la Fri Apr 17 19:38:37 2015 From: danil at smirnov.la (Danil Smirnov) Date: Fri, 17 Apr 2015 20:38:37 +0300 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: References: Message-ID: Have you meant [root at host ~]# which python3 /usr/bin/which: no python3 in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) ? 2015-04-17 19:59 GMT+03:00 Pranjal Yadav : > Can you check with "where python3" and post the output. > > On Fri, Apr 17, 2015 at 9:34 PM, Danil Smirnov wrote: > >> I'm trying to install Mailman 3 using this manual: >> http://mailman-bundler.readthedocs.org/en/latest/ >> >> After step >> (venv)[root at host src]# pip install zc.buildout >> (venv)[root at host src]# buildout >> >> I've got an error >> ---- >> Installing mailman. >> The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) does >> not exist >> /tmp/tmpuGe9kP/run: line 2: >> /usr/local/src/mailman-bundler/venv-3.4/bin/pip: File or directory not >> found >> While: >> Installing mailman. >> ---- >> >> I have Python 3.4. in /usr/local/bin directory, not /usr/bin. >> >> Please help. >> >> Danil >> _______________________________________________ >> Mailman-Developers mailing list >> Mailman-Developers at 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/godricglow%40gmail.com >> >> Security Policy: http://wiki.list.org/x/QIA9 >> > > > > -- > > *Pranjal Yadav* > > *IIT Kharagpur* > From danil at smirnov.la Fri Apr 17 19:54:06 2015 From: danil at smirnov.la (Danil Smirnov) Date: Fri, 17 Apr 2015 20:54:06 +0300 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: References: Message-ID: But [root at host ~]# which python3.4 /usr/local/bin/python3.4 2015-04-17 20:38 GMT+03:00 Danil Smirnov : > Have you meant > [root at host ~]# which python3 > /usr/bin/which: no python3 in > (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) > ? > > 2015-04-17 19:59 GMT+03:00 Pranjal Yadav : > >> Can you check with "where python3" and post the output. >> >> On Fri, Apr 17, 2015 at 9:34 PM, Danil Smirnov wrote: >> >>> I'm trying to install Mailman 3 using this manual: >>> http://mailman-bundler.readthedocs.org/en/latest/ >>> >>> After step >>> (venv)[root at host src]# pip install zc.buildout >>> (venv)[root at host src]# buildout >>> >>> I've got an error >>> ---- >>> Installing mailman. >>> The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) does >>> not exist >>> /tmp/tmpuGe9kP/run: line 2: >>> /usr/local/src/mailman-bundler/venv-3.4/bin/pip: File or directory not >>> found >>> While: >>> Installing mailman. >>> ---- >>> >>> I have Python 3.4. in /usr/local/bin directory, not /usr/bin. >>> >>> Please help. >>> >>> Danil >>> _______________________________________________ >>> Mailman-Developers mailing list >>> Mailman-Developers at 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/godricglow%40gmail.com >>> >>> Security Policy: http://wiki.list.org/x/QIA9 >>> >> >> >> >> -- >> >> *Pranjal Yadav* >> >> *IIT Kharagpur* >> > > From godricglow at gmail.com Fri Apr 17 20:00:20 2015 From: godricglow at gmail.com (Pranjal Yadav) Date: Fri, 17 Apr 2015 23:30:20 +0530 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: References: Message-ID: Add the following to your ~/.bashrc file: export PATH=/usr/local/bin:$PATH Alternatively, you can simply rename /usr/bin/python to /usr/bin/python3.4 and create a symlink pointing to the new version, e.g. ln -s /usr/local/bin/python /usr/bin/python On Fri, Apr 17, 2015 at 11:24 PM, Danil Smirnov wrote: > But > [root at host ~]# which python3.4 > /usr/local/bin/python3.4 > > > 2015-04-17 20:38 GMT+03:00 Danil Smirnov : > > > Have you meant > > [root at host ~]# which python3 > > /usr/bin/which: no python3 in > > (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) > > ? > > > > 2015-04-17 19:59 GMT+03:00 Pranjal Yadav : > > > >> Can you check with "where python3" and post the output. > >> > >> On Fri, Apr 17, 2015 at 9:34 PM, Danil Smirnov > wrote: > >> > >>> I'm trying to install Mailman 3 using this manual: > >>> http://mailman-bundler.readthedocs.org/en/latest/ > >>> > >>> After step > >>> (venv)[root at host src]# pip install zc.buildout > >>> (venv)[root at host src]# buildout > >>> > >>> I've got an error > >>> ---- > >>> Installing mailman. > >>> The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) > does > >>> not exist > >>> /tmp/tmpuGe9kP/run: line 2: > >>> /usr/local/src/mailman-bundler/venv-3.4/bin/pip: File or directory not > >>> found > >>> While: > >>> Installing mailman. > >>> ---- > >>> > >>> I have Python 3.4. in /usr/local/bin directory, not /usr/bin. > >>> > >>> Please help. > >>> > >>> Danil > >>> _______________________________________________ > >>> Mailman-Developers mailing list > >>> Mailman-Developers at 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/godricglow%40gmail.com > >>> > >>> Security Policy: http://wiki.list.org/x/QIA9 > >>> > >> > >> > >> > >> -- > >> > >> *Pranjal Yadav* > >> > >> *IIT Kharagpur* > >> > > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at 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/godricglow%40gmail.com > > Security Policy: http://wiki.list.org/x/QIA9 > -- *Pranjal Yadav* *IIT Kharagpur* From danil at smirnov.la Fri Apr 17 20:03:31 2015 From: danil at smirnov.la (Danil Smirnov) Date: Fri, 17 Apr 2015 21:03:31 +0300 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: References: Message-ID: Are you absolutely sure about renaming? As I understand I need both Python 2.7 which is /usr/bin/python and 3.4 which is /usr/local/bin/python3.4 for the Mailman installation. 2015-04-17 21:00 GMT+03:00 Pranjal Yadav : > Add the following to your ~/.bashrc file: > > export PATH=/usr/local/bin:$PATH > > Alternatively, you can simply rename /usr/bin/python to /usr/bin/python3.4 > and create a symlink pointing to the new version, e.g. > ln -s /usr/local/bin/python /usr/bin/python > > > > On Fri, Apr 17, 2015 at 11:24 PM, Danil Smirnov wrote: > >> But >> [root at host ~]# which python3.4 >> /usr/local/bin/python3.4 >> >> >> 2015-04-17 20:38 GMT+03:00 Danil Smirnov : >> >> > Have you meant >> > [root at host ~]# which python3 >> > /usr/bin/which: no python3 in >> > (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) >> > ? >> > >> > 2015-04-17 19:59 GMT+03:00 Pranjal Yadav : >> > >> >> Can you check with "where python3" and post the output. >> >> >> >> On Fri, Apr 17, 2015 at 9:34 PM, Danil Smirnov >> wrote: >> >> >> >>> I'm trying to install Mailman 3 using this manual: >> >>> http://mailman-bundler.readthedocs.org/en/latest/ >> >>> >> >>> After step >> >>> (venv)[root at host src]# pip install zc.buildout >> >>> (venv)[root at host src]# buildout >> >>> >> >>> I've got an error >> >>> ---- >> >>> Installing mailman. >> >>> The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) >> does >> >>> not exist >> >>> /tmp/tmpuGe9kP/run: line 2: >> >>> /usr/local/src/mailman-bundler/venv-3.4/bin/pip: File or directory not >> >>> found >> >>> While: >> >>> Installing mailman. >> >>> ---- >> >>> >> >>> I have Python 3.4. in /usr/local/bin directory, not /usr/bin. >> >>> >> >>> Please help. >> >>> >> >>> Danil >> >>> _______________________________________________ >> >>> Mailman-Developers mailing list >> >>> Mailman-Developers at 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/godricglow%40gmail.com >> >>> >> >>> Security Policy: http://wiki.list.org/x/QIA9 >> >>> >> >> >> >> >> >> >> >> -- >> >> >> >> *Pranjal Yadav* >> >> >> >> *IIT Kharagpur* >> >> >> > >> > >> _______________________________________________ >> Mailman-Developers mailing list >> Mailman-Developers at 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/godricglow%40gmail.com >> >> Security Policy: http://wiki.list.org/x/QIA9 >> > > > > -- > > *Pranjal Yadav* > > *IIT Kharagpur* > From danil at smirnov.la Fri Apr 17 20:06:55 2015 From: danil at smirnov.la (Danil Smirnov) Date: Fri, 17 Apr 2015 21:06:55 +0300 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: References: Message-ID: Tried export PATH=/usr/local/bin:$PATH, does not help - the error is same: Installing mailman. The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) does not exist /tmp/tmpePyrQ3/run: line 2: /usr/local/src/mailman-bundler/venv-3.4/bin/pip: ??? ?????? ????? ??? ???????? While: Installing mailman. 2015-04-17 21:00 GMT+03:00 Pranjal Yadav : > Add the following to your ~/.bashrc file: > > export PATH=/usr/local/bin:$PATH > > Alternatively, you can simply rename /usr/bin/python to /usr/bin/python3.4 > and create a symlink pointing to the new version, e.g. > > ln -s /usr/local/bin/python /usr/bin/python > > > > On Fri, Apr 17, 2015 at 11:24 PM, Danil Smirnov wrote: >> >> But >> [root at host ~]# which python3.4 >> /usr/local/bin/python3.4 >> >> >> 2015-04-17 20:38 GMT+03:00 Danil Smirnov : >> >> > Have you meant >> > [root at host ~]# which python3 >> > /usr/bin/which: no python3 in >> > (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) >> > ? >> > >> > 2015-04-17 19:59 GMT+03:00 Pranjal Yadav : >> > >> >> Can you check with "where python3" and post the output. >> >> >> >> On Fri, Apr 17, 2015 at 9:34 PM, Danil Smirnov >> >> wrote: >> >> >> >>> I'm trying to install Mailman 3 using this manual: >> >>> http://mailman-bundler.readthedocs.org/en/latest/ >> >>> >> >>> After step >> >>> (venv)[root at host src]# pip install zc.buildout >> >>> (venv)[root at host src]# buildout >> >>> >> >>> I've got an error >> >>> ---- >> >>> Installing mailman. >> >>> The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) >> >>> does >> >>> not exist >> >>> /tmp/tmpuGe9kP/run: line 2: >> >>> /usr/local/src/mailman-bundler/venv-3.4/bin/pip: File or directory not >> >>> found >> >>> While: >> >>> Installing mailman. >> >>> ---- >> >>> >> >>> I have Python 3.4. in /usr/local/bin directory, not /usr/bin. >> >>> >> >>> Please help. >> >>> >> >>> Danil >> >>> _______________________________________________ >> >>> Mailman-Developers mailing list >> >>> Mailman-Developers at 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/godricglow%40gmail.com >> >>> >> >>> Security Policy: http://wiki.list.org/x/QIA9 >> >>> >> >> >> >> >> >> >> >> -- >> >> >> >> *Pranjal Yadav* >> >> >> >> *IIT Kharagpur* >> >> >> > >> > >> _______________________________________________ >> Mailman-Developers mailing list >> Mailman-Developers at 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/godricglow%40gmail.com >> >> Security Policy: http://wiki.list.org/x/QIA9 > > > > > -- > Pranjal Yadav > IIT Kharagpur From mark at msapiro.net Fri Apr 17 20:18:02 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 17 Apr 2015 11:18:02 -0700 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: References: Message-ID: <55314E5A.1030707@msapiro.net> On 04/17/2015 10:54 AM, Danil Smirnov wrote: > But > [root at host ~]# which python3.4 > /usr/local/bin/python3.4 > > > 2015-04-17 20:38 GMT+03:00 Danil Smirnov : > >> Have you meant >> [root at host ~]# which python3 >> /usr/bin/which: no python3 in >> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) >> ? You only need ln -s /usr/local/bin/python3.4 /usr/local/bin/python3 You don't need to rename anything. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From danil at smirnov.la Fri Apr 17 20:24:02 2015 From: danil at smirnov.la (Danil Smirnov) Date: Fri, 17 Apr 2015 21:24:02 +0300 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: <55314E5A.1030707@msapiro.net> References: <55314E5A.1030707@msapiro.net> Message-ID: 2015-04-17 21:18 GMT+03:00 Mark Sapiro : > You only need > > ln -s /usr/local/bin/python3.4 /usr/local/bin/python3 > > You don't need to rename anything. Thanks Mark! I did this: # ls -l /usr/local/bin/ ????? 68 -rwxr-xr-x 1 root root 101 apr 17 18:28 2to3-3.4 -rwxr-xr-x 1 root root 241 apr 17 18:28 easy_install-3.4 -rwxr-xr-x 1 root root 99 apr 17 18:28 idle3.4 -rwxr-xr-x 1 root root 213 apr 17 18:28 pip3.4 -rwxr-xr-x 1 root root 84 apr 17 18:28 pydoc3.4 lrwxrwxrwx 1 root root 24 apr 17 21:19 python3 -> /usr/local/bin/python3.4 -rwxr-xr-x 2 root root 17544 apr 17 18:28 python3.4 -rwxr-xr-x 2 root root 17544 apr 17 18:28 python3.4m -rwxr-xr-x 1 root root 3030 apr 17 18:28 python3.4m-config -rwxr-xr-x 1 root root 236 apr 17 18:28 pyvenv-3.4 But I've got the same error again: Installing mailman. The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) does not exist /tmp/tmplM1FLA/run: line 2: /usr/local/src/mailman-bundler/venv-3.4/bin/pip: ??? ?????? ????? ??? ???????? While: Installing mailman. I wonder don't I need to do ln -s /usr/local/bin/python3.4 /usr/bin/python3.4 as the error says? Danil From mark at msapiro.net Fri Apr 17 21:00:53 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 17 Apr 2015 12:00:53 -0700 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: References: <55314E5A.1030707@msapiro.net> Message-ID: <55315865.8040106@msapiro.net> On 04/17/2015 11:24 AM, Danil Smirnov wrote: > But I've got the same error again: > > Installing mailman. > The executable /usr/bin/python3.4 (from --python=/usr/bin/python3.4) > does not exist > /tmp/tmplM1FLA/run: line 2: > /usr/local/src/mailman-bundler/venv-3.4/bin/pip: ??? ?????? ????? ??? > ???????? > While: > Installing mailman. > > I wonder don't I need to do > > ln -s /usr/local/bin/python3.4 /usr/bin/python3.4 > > as the error says? That will probably get around this, but I don't think it should be necessary. At this point, I suspect you haven't activated the venv that you had active when you started. (Every time you start a new shell, you have to activate the venv for that shell.) Note also that the document at is NOT the latest. I suggest you remove your mailman-bundler branch and get the latest with 'bzr branch lp:mailman-bundler' (or maybe just update yours with 'bzr pull' and remove the venv and venv-3.4 directories), and follow the README.rst in the latest rev. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From danil at smirnov.la Fri Apr 17 21:20:48 2015 From: danil at smirnov.la (Danil Smirnov) Date: Fri, 17 Apr 2015 22:20:48 +0300 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: <55315865.8040106@msapiro.net> References: <55314E5A.1030707@msapiro.net> <55315865.8040106@msapiro.net> Message-ID: 2015-04-17 22:00 GMT+03:00 Mark Sapiro : > At this point, I suspect you haven't activated the venv that you had > active when you started. (Every time you start a new shell, you have to > activate the venv for that shell.) I am still on the same shell that when I started. My prompt looks like: (venv)[root at host mailman-bundler]# > I suggest you remove your mailman-bundler branch and get the latest with > 'bzr branch lp:mailman-bundler' I've got this branch TODAY so I think it's latest. So, does it mean that there is no way to install Mailman 3 using manual mentioned? Danil From danil at smirnov.la Fri Apr 17 21:25:22 2015 From: danil at smirnov.la (Danil Smirnov) Date: Fri, 17 Apr 2015 22:25:22 +0300 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: References: <55314E5A.1030707@msapiro.net> Message-ID: 2015-04-17 21:24 GMT+03:00 Danil Smirnov : > I wonder don't I need to do > > ln -s /usr/local/bin/python3.4 /usr/bin/python3.4 > > as the error says? I've created this symlink and that's what I've got now: (venv)[root at host mailman-bundler]# ln -s /usr/local/bin/python3.4 /usr/bin/python3.4 (venv)[root at host mailman-bundler]# buildout Develop: '/usr/local/src/mailman-bundler/.' warning: no files found matching '*.in' under directory 'mailman_bundler' warning: no files found matching '*.in' under directory 'deployment' warning: no files found matching 'deployment/mailman-web.logrotate.conf' Updating mailman-web. Updating main. Installing mailman. Running virtualenv with interpreter /usr/bin/python3.4 Using base prefix '/usr/local' New python executable in /usr/local/src/mailman-bundler/venv-3.4/bin/python3.4 Also creating executable in /usr/local/src/mailman-bundler/venv-3.4/bin/python Failed to import the site module Traceback (most recent call last): File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/site.py", line 67, in import os File "/usr/local/src/mailman-bundler/venv-3.4/lib/python3.4/os.py", line 616, in from _collections_abc import MutableMapping ImportError: No module named '_collections_abc' ERROR: The executable /usr/local/src/mailman-bundler/venv-3.4/bin/python3.4 is not functioning ERROR: It thinks sys.prefix is '/usr/local/src/mailman-bundler' (should be '/usr/local/src/mailman-bundler/venv-3.4') ERROR: virtualenv is not compatible with this system or executable /tmp/tmpTl6JgC/run: line 2: /usr/local/src/mailman-bundler/venv-3.4/bin/pip: ??? ?????? ????? ??? ???????? While: Installing mailman. An internal error occurred due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "/usr/local/src/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", line 1946, in main getattr(buildout, command)(args) File "/usr/local/src/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", line 626, in install installed_files = self[part]._call(recipe.install) File "/usr/local/src/venv/lib/python2.7/site-packages/zc/buildout/buildout.py", line 1370, in _call return f() File "/usr/local/src/mailman-bundler/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py", line 56, in install self.execute() File "/usr/local/src/mailman-bundler/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py", line 69, in execute run_commands(cmds, self.shell) File "/usr/local/src/mailman-bundler/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py", line 39, in run_commands check_call('%s %s' % (shell, tmpfile), shell=True) File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call raise CalledProcessError(retcode, cmd) CalledProcessError: Command 'sh /tmp/tmpTl6JgC/run' returned non-zero exit status 127 Danil From danil at smirnov.la Fri Apr 17 21:29:22 2015 From: danil at smirnov.la (Danil Smirnov) Date: Fri, 17 Apr 2015 22:29:22 +0300 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: <55315865.8040106@msapiro.net> References: <55314E5A.1030707@msapiro.net> <55315865.8040106@msapiro.net> Message-ID: 2015-04-17 22:00 GMT+03:00 Mark Sapiro : > pull' and remove the venv and venv-3.4 directories), and follow the > README.rst in the latest rev. I've checked the file and found that it offers the same installation instructions before my error stop than http://mailman-bundler.readthedocs.org/en/latest/ D. From mark at msapiro.net Fri Apr 17 21:39:45 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 17 Apr 2015 12:39:45 -0700 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: References: <55314E5A.1030707@msapiro.net> <55315865.8040106@msapiro.net> Message-ID: <8906E8AD-EB1B-4EEF-AF7A-003386799669@msapiro.net> On April 17, 2015 12:20:48 PM PDT, Danil Smirnov wrote: > >I've got this branch TODAY so I think it's latest. > >So, does it mean that there is no way to install Mailman 3 using >manual mentioned? There have been at least 13 revs to that branch since Monday. The README.rst in the branch is the latest and differs in some details from the one you referenced. Something is wrong because it should have installed Python 3.4 in venv-3.4. -- Mark Sapiro Sent from my Android phone with K-9 Mail. [Unpaid endorsement] From danil at smirnov.la Fri Apr 17 21:48:42 2015 From: danil at smirnov.la (Danil Smirnov) Date: Fri, 17 Apr 2015 22:48:42 +0300 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: <8906E8AD-EB1B-4EEF-AF7A-003386799669@msapiro.net> References: <55314E5A.1030707@msapiro.net> <55315865.8040106@msapiro.net> <8906E8AD-EB1B-4EEF-AF7A-003386799669@msapiro.net> Message-ID: 2015-04-17 22:39 GMT+03:00 Mark Sapiro : > On April 17, 2015 12:20:48 PM PDT, Danil Smirnov wrote: >> >>I've got this branch TODAY so I think it's latest. >> >>So, does it mean that there is no way to install Mailman 3 using >>manual mentioned? > > > There have been at least 13 revs to that branch since Monday. Mark, I don't understand you: # bzr pull Using saved parent location: http://bazaar.launchpad.net/~abompard/mailman-bundler/mailman-bundler/ No revisions or tags to pull. > The README.rst in the branch is the latest and differs in some details from the one you referenced. I've checked it and don't see any differences before buildout command. > Something is wrong because it should have installed Python 3.4 in venv-3.4. Definitely! That's why I'm writing. I think it's important for the developers to test what you're going to release on my new Centos 7 box, isn't it? I can fill bug report if it is more appropriate. Danil From mark at msapiro.net Sat Apr 18 00:06:24 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 17 Apr 2015 15:06:24 -0700 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: References: <55314E5A.1030707@msapiro.net> <55315865.8040106@msapiro.net> <8906E8AD-EB1B-4EEF-AF7A-003386799669@msapiro.net> Message-ID: <553183E0.9010504@msapiro.net> On 04/17/2015 12:48 PM, Danil Smirnov wrote: > > Mark, I don't understand you: > # bzr pull > Using saved parent location: > http://bazaar.launchpad.net/~abompard/mailman-bundler/mailman-bundler/ > No revisions or tags to pull. OK, it seems your branch is up to date. I was only concerned because we were sprinting on Mailman 3 at PyCon Monday through Thursday and there have been many changes to mailman-bundler and the packages it pulls in. postorius, mailman.client and mailman3 have all had multiple commits in this time. >> The README.rst in the branch is the latest and differs in some details from the one you referenced. > > I've checked it and don't see any differences before buildout command. I was mistaken. That document is up to date with the branch. >> Something is wrong because it should have installed Python 3.4 in venv-3.4. > > Definitely! > > That's why I'm writing. > > I think it's important for the developers to test what you're going to > release on my new Centos 7 box, > isn't it? Absolutely, and we appreciate your doing so. > I can fill bug report if it is more appropriate. Yes, that would be appropriate. File the bug at and include the full OS version, what Python software you installed prior to running buildout, what steps you followed to install that software and what steps you took before running buildout. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Apr 18 02:52:43 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 17 Apr 2015 17:52:43 -0700 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: References: Message-ID: <5531AADB.6060205@msapiro.net> Please see this wiki page . It addresses Ubuntu, not CentOS, but talks about prerequisite things applicable to both although the apt-get package names may be different for Yum. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From danil at smirnov.la Sat Apr 18 14:21:00 2015 From: danil at smirnov.la (Danil Smirnov) Date: Sat, 18 Apr 2015 15:21:00 +0300 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: <5531AADB.6060205@msapiro.net> References: <5531AADB.6060205@msapiro.net> Message-ID: 2015-04-18 3:52 GMT+03:00 Mark Sapiro : > Please see this wiki page . It > addresses Ubuntu, not CentOS, but talks about prerequisite things > applicable to both although the apt-get package names may be different > for Yum. This does not help. The error is the same. Filled a bug: https://bugs.launchpad.net/mailman/+bug/1445764 Danil From danil at smirnov.la Sat Apr 18 21:18:12 2015 From: danil at smirnov.la (Danil Smirnov) Date: Sat, 18 Apr 2015 22:18:12 +0300 Subject: [Mailman-Developers] wrong path to python 3.4 while installing mailman 3 In-Reply-To: References: <5531AADB.6060205@msapiro.net> Message-ID: And fixing the main problem with Python 3.4 path did not help to make "buildout" command successful. I've posted the error message as a comment of my bug report: https://bugs.launchpad.net/mailman/+bug/1445764 2015-04-18 15:21 GMT+03:00 Danil Smirnov : > 2015-04-18 3:52 GMT+03:00 Mark Sapiro : >> Please see this wiki page . It >> addresses Ubuntu, not CentOS, but talks about prerequisite things >> applicable to both although the apt-get package names may be different >> for Yum. > > This does not help. The error is the same. > > Filled a bug: > https://bugs.launchpad.net/mailman/+bug/1445764 > > Danil From brian at emwd.com Mon Apr 20 15:06:31 2015 From: brian at emwd.com (Brian Carpenter) Date: Mon, 20 Apr 2015 09:06:31 -0400 Subject: [Mailman-Developers] Mailman 3 discussion Message-ID: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> Hello Everyone, I have a working installation of Mailman 3 on a CentOS 6 server. I have a number of questions regarding the use of it. Is this the right forum to ask those questions? Thanks! Brian Carpenter Owner Providing Cloud Services and more for over 15 years. T: 336.755.0685 E: brian at emwd.com www.emwd.com -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 29057 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 991 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 1191 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 90 bytes Desc: not available URL: From mark at msapiro.net Mon Apr 20 16:51:17 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 20 Apr 2015 07:51:17 -0700 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> Message-ID: <55351265.9030102@msapiro.net> On 04/20/2015 06:06 AM, Brian Carpenter wrote: > > I have a working installation of Mailman 3 on a CentOS 6 server. I have a > number of questions regarding the use of it. Is this the right forum to ask > those questions? Yes. We would also be interested in your feedback regarding the installation process. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From sumanah at panix.com Mon Apr 20 16:53:09 2015 From: sumanah at panix.com (Sumana Harihareswara) Date: Mon, 20 Apr 2015 10:53:09 -0400 Subject: [Mailman-Developers] Mailman Suite 3.0rc1 awaiting an upstream fix Message-ID: <553512D5.5040105@panix.com> At the PyCon sprint last week, we made a lot of progress towards a 3.0 release and we discussed next steps. I'm very glad so many of us could make it and pitch in. The 3.0rc1 depends on a new Falcon release because there's a bugfix awaiting release in Falcon that fixes a blocker bug for us: https://bugs.launchpad.net/postorius/+bug/1444504 Once that's out, we can put out a release candidate. In order to release 3.0.0 final, we need core native releases for all 5 components of the Mailman suite, with tested installation instructions and with all the components tagged, tested, and on PyPI. We'd also like some infrastructure and workflow improvements before we do that -- for one thing, we ought to set up continuous integration to run our automated tests on every merge. We will probably request a CI server/VM from the Python Software Foundation. We could actually set up CI for HyperKitty (and probably our other components as well) right away using the (no guarantee of uptime/service level) Jenkins installation at http://jenkins.cloud.fedoraproject.org/ if someone followed the instructions at https://fedoraproject.org/wiki/Jenkins at infra#Can_I_add_my_project_to_Jenkins.3F and add ticket to https://fedorahosted.org/fedora-infrastructure/ . We need to have an i18n setup and I've agreed to take lead on that. And there's further potential wrangling around Launchpad, branches, Bazaar, Git, etc. that I'll write up tomorrow. Hope this helps keep everyone up to date. -- Sumana Harihareswara http://brainwane.net From danil at smirnov.la Mon Apr 20 20:13:25 2015 From: danil at smirnov.la (Danil Smirnov) Date: Mon, 20 Apr 2015 21:13:25 +0300 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: <55351265.9030102@msapiro.net> References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> Message-ID: I would like to ask too. After successful fight with 'virtualenv' buggy version bug (https://bugs.launchpad.net/mailman/+bug/1445764) I've proceeded to initial setup through the Postorius web inteface. I opened the link http://127.0.0.1:8000/mailman3 in the 'links' browser and try to add new domain through 'Manage lists' - 'Domains' - 'Create domain' form. When I submit the form, I get the error: --- [root at host ~]# links http://127.0.0.1:8000/mailman3 TypeError at /mailman3/domains/new/ (p1 of 18) TypeError at /mailman3/domains/new/ create_domain() got an unexpected keyword argument 'owner' Request Method: POST Request URL: http://127.0.0.1:8000/mailman3/domains/new/ Django Version: 1.7.7 Exception Type: TypeError Exception Value: create_domain() got an unexpected keyword argument 'owner' Exception Location: /usr/local/src/mailman-bundler/eggs/postorius-1.0.0-py2.7.egg/postorius/models.py in create, line 117 Python Executable: /usr/local/src/venv/bin/python Python Version: 2.7.5 ['/usr/local/src/mailman-bundler/eggs/Django-1.7.7-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/postorius-1.0.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/HyperKitty-0.9.7-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/Whoosh-2.7.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/mock-1.0.1-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/beautifulsoup4-4.3.2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/djangorecipe-1.11-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/zc.recipe.egg-2.0.1-py2.7.egg', '/usr/local/src/venv/lib/python2.7/site-packages', '/usr/local/src/mailman-bundler/eggs/numpy-1.9.2-py2.7-linux-x86_64.egg', '/usr/local/src/mailman-bundler/eggs/lockfile-0.10.2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_extensions-1.5.2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_haystack-2.3.1-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/enum34-1.0.4-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/networkx-1.9.1-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/python_dateutil-1.5-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/mailmanclient-1.0.0b2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_browserid-0.11.1-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_compressor-1.5-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_paintstore-0.2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/pytz-2015.2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/robot_detection-0.3-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/cssmin-0.2.0-py2.7.egg', Python Path: '/usr/local/src/mailman-bundler/eggs/rjsmin-1.0.10-py2.7-linux-x86_64.egg', '/usr/local/src/mailman-bundler/eggs/django_crispy_forms-1.4.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/djangorestframework-3.1.1-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/python_social_auth-0.2.7-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_gravatar2-1.3.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/six-1.9.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/decorator-3.4.2-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/httplib2-0.9.1-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/fancy_tag-0.2.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/requests-2.6.0-py2.7.egg', '/usr/local/src/mailman-bundler/eggs/django_appconf-1.0.1-py2.7.egg', OK --- I wonder are there any way to connect to the Postorius through outer-accessible domain like http://mydomain.tld:8000/mailman3/ ? Danil 2015-04-20 17:51 GMT+03:00 Mark Sapiro : > On 04/20/2015 06:06 AM, Brian Carpenter wrote: >> >> I have a working installation of Mailman 3 on a CentOS 6 server. I have a >> number of questions regarding the use of it. Is this the right forum to ask >> those questions? > > > Yes. > > We would also be interested in your feedback regarding the installation > process. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at python.org > 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/danil%40smirnov.la > > Security Policy: http://wiki.list.org/x/QIA9 From f at florianfuchs.com Mon Apr 20 21:22:26 2015 From: f at florianfuchs.com (Florian Fuchs) Date: Mon, 20 Apr 2015 21:22:26 +0200 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> Message-ID: <553551F2.1040509@florianfuchs.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 20.04.2015 um 20:13 schrieb Danil Smirnov: > I would like to ask too. > > After successful fight with 'virtualenv' buggy version bug > (https://bugs.launchpad.net/mailman/+bug/1445764) I've proceeded to > initial setup through the Postorius web inteface. > > I opened the link http://127.0.0.1:8000/mailman3 in the 'links' > browser and try to add new domain through 'Manage lists' - > 'Domains' - 'Create domain' form. > > When I submit the form, I get the error: > > --- [root at host ~]# links http://127.0.0.1:8000/mailman3 > > > TypeError at /mailman3/domains/new/ (p1 of 18) > > TypeError at /mailman3/domains/new/ That looks like incompatible versions of Postorius and mailman.client to me. The currently available ones on pypi and launchpad (released on Friday) should be working. Did you download them before Friday evening (EST) by any chance? Florian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVNVHyAAoJEEceGbPdavl74bwIAKOAkO6zAIkTbhFNY4P9VFF0 o3TkeFpf2VVdmiQihQczk7ToTprfnGvu5PFo5jX77AaFyF4gaEOaFSfQ6/wwomwL nPb4XayVolceaa5oJbXmPE5XtVUJwVrUrIz9MXreoPDNS9QldUc1c95VVBPQSwQM 7vY1Bc/i2iMRONyTO2ZLWuvVXQwQrSKLlL4P2A1NR7eStE7z+9D17X8jE14Pq8sA uv9Fxy8KMHilXxmGLPePZ6483a415vy9lNCqde6iXbLLk3Tj4FZRgCmBSbw+m+RB Zgt8rJoqn/lLSpN9W/oKDZI4bn2svHK0gmotwspq8qGM+ZDWDJaVmiGNS3Dql/4= =rko1 -----END PGP SIGNATURE----- From danil at smirnov.la Mon Apr 20 21:36:14 2015 From: danil at smirnov.la (Danil Smirnov) Date: Mon, 20 Apr 2015 22:36:14 +0300 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: <553551F2.1040509@florianfuchs.com> References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> <553551F2.1040509@florianfuchs.com> Message-ID: 2015-04-20 22:22 GMT+03:00 Florian Fuchs : > That looks like incompatible versions of Postorius and mailman.client > to me. The currently available ones on pypi and launchpad (released > on Friday) should be working. Did you download them before Friday > evening (EST) by any chance? Nope. I've downloaded very last revision couple of hours ago. Danil From danil at smirnov.la Mon Apr 20 21:41:19 2015 From: danil at smirnov.la (Danil Smirnov) Date: Mon, 20 Apr 2015 22:41:19 +0300 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> <553551F2.1040509@florianfuchs.com> Message-ID: Look at this please: http://dpaste.com/3N8ABXY From abompard at fedoraproject.org Mon Apr 20 20:19:29 2015 From: abompard at fedoraproject.org (Aurelien Bompard) Date: Mon, 20 Apr 2015 20:19:29 +0200 Subject: [Mailman-Developers] [hyperkitty-devel] Mailman Suite 3.0rc1 awaiting an upstream fix In-Reply-To: <20150420150842.GD4969@carmine.pingoured.fr> References: <553512D5.5040105@panix.com> <20150420150842.GD4969@carmine.pingoured.fr> Message-ID: > We are (as in Patrick is) currently working on getting a Fedora 22 builder added > to the jenkins instance so that we have a python 3.4 available for you folks if > you so desire :) Fedora 21 has Python 3.4, so that would be enough. A. From pingou at pingoured.fr Mon Apr 20 17:08:42 2015 From: pingou at pingoured.fr (Pierre-Yves Chibon) Date: Mon, 20 Apr 2015 17:08:42 +0200 Subject: [Mailman-Developers] Mailman Suite 3.0rc1 awaiting an upstream fix In-Reply-To: <553512D5.5040105@panix.com> References: <553512D5.5040105@panix.com> Message-ID: <20150420150842.GD4969@carmine.pingoured.fr> On Mon, Apr 20, 2015 at 10:53:09AM -0400, Sumana Harihareswara wrote: > At the PyCon sprint last week, we made a lot of progress towards a 3.0 > release and we discussed next steps. I'm very glad so many of us could > make it and pitch in. > > The 3.0rc1 depends on a new Falcon release because there's a bugfix > awaiting release in Falcon that fixes a blocker bug for us: > https://bugs.launchpad.net/postorius/+bug/1444504 Once that's out, we > can put out a release candidate. > > In order to release 3.0.0 final, we need core native releases for all 5 > components of the Mailman suite, with tested installation instructions > and with all the components tagged, tested, and on PyPI. We'd also like > some infrastructure and workflow improvements before we do that -- for > one thing, we ought to set up continuous integration to run our > automated tests on every merge. We will probably request a CI server/VM > from the Python Software Foundation. We could actually set up CI for > HyperKitty (and probably our other components as well) right away using > the (no guarantee of uptime/service level) Jenkins installation at > http://jenkins.cloud.fedoraproject.org/ if someone followed the > instructions at > https://fedoraproject.org/wiki/Jenkins at infra#Can_I_add_my_project_to_Jenkins.3F > and add ticket to https://fedorahosted.org/fedora-infrastructure/ . We > need to have an i18n setup and I've agreed to take lead on that. And > there's further potential wrangling around Launchpad, branches, Bazaar, > Git, etc. that I'll write up tomorrow. We are (as in Patrick is) currently working on getting a Fedora 22 builder added to the jenkins instance so that we have a python 3.4 available for you folks if you so desire :) Pierre From f at florianfuchs.com Mon Apr 20 23:34:59 2015 From: f at florianfuchs.com (Florian Fuchs) Date: Mon, 20 Apr 2015 23:34:59 +0200 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> <553551F2.1040509@florianfuchs.com> Message-ID: <20150420213458.GA9251@soc2> On Mon, Apr 20, 2015 at 22:36:14PM +0300, Danil Smirnov wrote: >2015-04-20 22:22 GMT+03:00 Florian Fuchs : >> That looks like incompatible versions of Postorius and mailman.client >> to me. The currently available ones on pypi and launchpad (released >> on Friday) should be working. Did you download them before Friday >> evening (EST) by any chance? > >Nope. I've downloaded very last revision couple of hours ago. OK, the problem was a file name conflict on the Python package index (due to an erroneously omitted pre-release suffix while parsing the version string of a previous beta-release), which eventually led to pypi delivering the previous release's tarball. I've associated a new file with the latest release on pypi so the correct tarball gets installed. Sorry for that... Florian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: From brian at emwd.com Mon Apr 20 23:38:26 2015 From: brian at emwd.com (Brian Carpenter) Date: Mon, 20 Apr 2015 17:38:26 -0400 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: <55351265.9030102@msapiro.net> References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> Message-ID: <195901d07bb2$55e39e00$01aada00$@emwd.com> > > I have a working installation of Mailman 3 on a CentOS 6 server. I have a > > number of questions regarding the use of it. Is this the right forum to ask > > those questions? > > > Yes. > > We would also be interested in your feedback regarding the installation > process. > > -- > Mark Sapiro The highway is for gamblers, According to my linux admin, the installation process was straightforward. We used the mailman3 bundler to install all 3 packages of Mailman 3. We are running Mailman 3 using Nginx and Postgres. We have one troubleshooting issue we are looking into. When I try to use the mass subscribe function, I got an Server Error (500) message. Has anyone else run into that? Also what user levels does Mailman 3 support at this time? Brian Carpenter Owner Providing Cloud Services and more for over 15 years. E: brian at emwd.com www.emwd.com From pingou at pingoured.fr Mon Apr 20 20:51:08 2015 From: pingou at pingoured.fr (Pierre-Yves Chibon) Date: Mon, 20 Apr 2015 20:51:08 +0200 Subject: [Mailman-Developers] [hyperkitty-devel] Mailman Suite 3.0rc1 awaiting an upstream fix In-Reply-To: References: <553512D5.5040105@panix.com> <20150420150842.GD4969@carmine.pingoured.fr> Message-ID: <20150420185108.GB13513@carmine.pingoured.fr> On Mon, Apr 20, 2015 at 08:19:29PM +0200, Aurelien Bompard wrote: > > We are (as in Patrick is) currently working on getting a Fedora 22 builder added > > to the jenkins instance so that we have a python 3.4 available for you folks if > > you so desire :) > > > Fedora 21 has Python 3.4, so that would be enough. That is true, but currently we only have a F20 builder, but good to know that if we do not manage to get the F22 one running, we can also try getting a F21 one up. Thanks, Pierre From danil at smirnov.la Tue Apr 21 08:40:52 2015 From: danil at smirnov.la (Danil Smirnov) Date: Tue, 21 Apr 2015 09:40:52 +0300 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: <20150420213458.GA9251@soc2> References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> <553551F2.1040509@florianfuchs.com> <20150420213458.GA9251@soc2> Message-ID: 2015-04-21 0:34 GMT+03:00 Florian Fuchs : > OK, the problem was a file name conflict on the Python package index (due to > an erroneously omitted pre-release suffix while parsing the version string > of > a previous beta-release), which eventually led to pypi delivering the > previous release's tarball. I've associated a new file with the latest > release on pypi so the correct tarball gets installed. > > Sorry for that... Okay, but what is workaround right now? I don't see any new revisions in the mailman-bundler... Danil From f at florianfuchs.com Tue Apr 21 14:41:49 2015 From: f at florianfuchs.com (Florian Fuchs) Date: Tue, 21 Apr 2015 14:41:49 +0200 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> <553551F2.1040509@florianfuchs.com> <20150420213458.GA9251@soc2> Message-ID: <20150421124149.GA5425@soc2> On Di, Apr 21, 2015 at 09:40:52 +0300, Danil Smirnov wrote: >2015-04-21 0:34 GMT+03:00 Florian Fuchs : >> OK, the problem was a file name conflict on the Python package index (due to >> an erroneously omitted pre-release suffix while parsing the version string >> of >> a previous beta-release), which eventually led to pypi delivering the >> previous release's tarball. I've associated a new file with the latest >> release on pypi so the correct tarball gets installed. >> >> Sorry for that... > >Okay, but what is workaround right now? >I don't see any new revisions in the mailman-bundler... The change is not directly reflected in mailman-bundler. But running `buildout` again should install the newest version of mailman.client. Florian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: From danil at smirnov.la Tue Apr 21 15:15:06 2015 From: danil at smirnov.la (Danil Smirnov) Date: Tue, 21 Apr 2015 16:15:06 +0300 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: <20150421124149.GA5425@soc2> References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> <553551F2.1040509@florianfuchs.com> <20150420213458.GA9251@soc2> <20150421124149.GA5425@soc2> Message-ID: 2015-04-21 15:41 GMT+03:00 Florian Fuchs : > The change is not directly reflected in mailman-bundler. But running > `buildout` again should install the newest version of mailman.client. > Florian Now there is no response from http://127.0.0.1:8000/mailman3 at all... :( Just blank screen of links and 'Request sent' status. Danil From aurelien at bompard.org Tue Apr 21 17:26:01 2015 From: aurelien at bompard.org (Aurelien Bompard) Date: Tue, 21 Apr 2015 17:26:01 +0200 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> <553551F2.1040509@florianfuchs.com> <20150420213458.GA9251@soc2> <20150421124149.GA5425@soc2> Message-ID: > Now there is no response from http://127.0.0.1:8000/mailman3 > at all... :( > > Just blank screen of links and 'Request sent' status. Make sure you started the "runserver" command again. Does it output something when you connect to the page? A. From danil at smirnov.la Tue Apr 21 17:56:51 2015 From: danil at smirnov.la (Danil Smirnov) Date: Tue, 21 Apr 2015 18:56:51 +0300 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> <553551F2.1040509@florianfuchs.com> <20150420213458.GA9251@soc2> <20150421124149.GA5425@soc2> Message-ID: 2015-04-21 18:26 GMT+03:00 Aurelien Bompard : > Make sure you started the "runserver" command again. Does it output > something when you connect to the page? Yes I've checked it already - if it is not started I get 'Connection refused' error. If started, I get 'Received 0 B,...' or 'Request sent' in bottom status line and blank/black screen. update. Hm, somehow it returned to the working state. Domain has been successfully created. Thank you! Danil From brian at emwd.com Tue Apr 21 20:30:14 2015 From: brian at emwd.com (Brian Carpenter) Date: Tue, 21 Apr 2015 14:30:14 -0400 Subject: [Mailman-Developers] List Info Page Message-ID: <282401d07c61$35f49e00$a1ddda00$@emwd.com> Is the concept of the listinfo page being carried over to Mailman 3 and if yes, is it part of Mailman 3's current distribution or is it yet to be added? Brian Carpenter Owner Providing Cloud Services and more for over 15 years. T: 336.755.0685 E: brian at emwd.com www.emwd.com -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 29057 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 991 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 1191 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 90 bytes Desc: not available URL: From mark at msapiro.net Tue Apr 21 22:46:02 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 21 Apr 2015 13:46:02 -0700 Subject: [Mailman-Developers] List Info Page In-Reply-To: <282401d07c61$35f49e00$a1ddda00$@emwd.com> References: <282401d07c61$35f49e00$a1ddda00$@emwd.com> Message-ID: <5536B70A.7080207@msapiro.net> On 04/21/2015 11:30 AM, Brian Carpenter wrote: > Is the concept of the listinfo page being carried over to Mailman 3 and if > yes, is it part of Mailman 3's current distribution or is it yet to be > added? The postorius home page (also the /lists page) is the overview of lists. Or do you mean the listinfo page for a specific list? There isn't a lot there now. First, you have to be logged in to see it. This is different from 2.1 where a 'user' is an email address/password for a list and the same person is a separate 'user' for each list of which she is a member. In MM 3 she is a user of that Mailman installation. She may have several email addresses and various roles with respect to specific lists, so she can be a user before joining any lists. At some point, the list's 'info' tab will have more of the current listinfo type information. It's still a work in progress, and I'm also still learning as my primary role is, and will be for some time, 2.1 maintenance and support. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From barry at list.org Wed Apr 22 00:41:07 2015 From: barry at list.org (Barry Warsaw) Date: Tue, 21 Apr 2015 18:41:07 -0400 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: <195901d07bb2$55e39e00$01aada00$@emwd.com> References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> <195901d07bb2$55e39e00$01aada00$@emwd.com> Message-ID: <20150421184107.2de3f68e@limelight.wooz.org> On Apr 20, 2015, at 05:38 PM, Brian Carpenter wrote: >According to my linux admin, the installation process was straightforward. >We used the mailman3 bundler to install all 3 packages of Mailman 3. We are >running Mailman 3 using Nginx and Postgres. We have one troubleshooting >issue we are looking into. When I try to use the mass subscribe function, I >got an Server Error (500) message. Has anyone else run into that? Postorius currently implements mass subscribe as N number of individual subscription requests. In the future, we might add a real mass subscribe end point to the REST API. In any case, a 500 error always indicates a REST server bug. There should be a traceback in the mailman error log. If you find it and can reproduce the problem please do open a bug on Launchpad. We're very very close to a final release so if this can be fixed before then, we'll try to do so. >Also what user levels does Mailman 3 support at this time? I'm not quite sure what you mean. In the model, members link users/addresses to mailing lists. For a member linking a user, the user must have a verified, preferred address. Each member has a role, which can be member, nonmember, owner, or moderator. So a mailing list's owner is a member record with role owner. Domains can also have owners, but these aren't members. Domains directly link to a list of user records, each of which is the domain owner. User records have a flag which if true, indicate that that user is a server owner. All of these various things can be set through the REST API, though I'm not sure if Postorius supports each. Does that help? Cheers, -Barry From barry at list.org Wed Apr 22 00:41:51 2015 From: barry at list.org (Barry Warsaw) Date: Tue, 21 Apr 2015 18:41:51 -0400 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> <553551F2.1040509@florianfuchs.com> Message-ID: <20150421184151.51f97f40@limelight.wooz.org> On Apr 20, 2015, at 10:41 PM, Danil Smirnov wrote: >Look at this please: >http://dpaste.com/3N8ABXY Darn, that expired. Cheers, -Barry From mark at msapiro.net Wed Apr 22 00:57:06 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 21 Apr 2015 15:57:06 -0700 Subject: [Mailman-Developers] Mailman 3 discussion In-Reply-To: <20150421184151.51f97f40@limelight.wooz.org> References: <130301d07b6a$d1f10d90$75d328b0$@emwd.com> <55351265.9030102@msapiro.net> <553551F2.1040509@florianfuchs.com> <20150421184151.51f97f40@limelight.wooz.org> Message-ID: <5536D5C2.3060502@msapiro.net> On 04/21/2015 03:41 PM, Barry Warsaw wrote: > On Apr 20, 2015, at 10:41 PM, Danil Smirnov wrote: > >> Look at this please: >> http://dpaste.com/3N8ABXY > > Darn, that expired. I think Florian addressed that one at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Sun Apr 19 17:08:01 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Mon, 20 Apr 2015 00:08:01 +0900 Subject: [Mailman-Developers] Regarding Csv Export for list owner in postorius In-Reply-To: References: Message-ID: <87sibwma0e.fsf@uwakimon.sk.tsukuba.ac.jp> Ashish Kumar writes: > of extending this feature request to pdf I don't understand the motivation for this. I guess it will look a tiny bit nicer when printed on paper, but it's basically an opaque, uneditable format which can surely be trivially produced by anyone who has space and power to run a printer. > and sharing the list of members on drive, What's "drive"? > as It will be very helpful for communities which have a lot of > volunteers, organizers. How is it helpful? > Scenario: > Suppose a team of volunteers working in a country/state like > bloodconnect in india. For an activity like camps [in case of blood > connect], Owner need to send a pdf Why does the owner need to do that? I think that plain text (as Tom Browder suggests) is almost surely more useful in every way. CSV, on the other hand, has the advantage that it can be accurately read into a spreadsheet which is "the" way non-geeky people manage tables. > of all the volunteers working in a specific area to the area head > either by drive or mail. It would be very convenient if we provide > these option as a UI in postorius itself. Looks like a YAGNI to me, so it would just clutter the UI. From sumanah at panix.com Wed Apr 22 16:36:57 2015 From: sumanah at panix.com (Sumana Harihareswara) Date: Wed, 22 Apr 2015 10:36:57 -0400 Subject: [Mailman-Developers] Regarding Csv Export for list owner in postorius In-Reply-To: <87sibwma0e.fsf@uwakimon.sk.tsukuba.ac.jp> References: <87sibwma0e.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <5537B209.5050705@panix.com> On 19/04/15 11:08, Stephen J. Turnbull wrote: > Ashish Kumar writes: > > > of extending this feature request to pdf > > I don't understand the motivation for this. I guess it will look a > tiny bit nicer when printed on paper, but it's basically an opaque, > uneditable format which can surely be trivially produced by anyone who > has space and power to run a printer. Stephen, I suspect you are overestimating the technical skill of some members of communities that want to use Mailman. But let's find out... Ashish, can you talk a little bit more about the current workflow that these folks are using (the ones in the scenario you suggested)? I'm used to seeing word processing and spreadsheet applications that can easily export to PDF. But maybe you know of a ton of people who need to create PDFs from list membership rosters, and right now that's a 10-step process for them (including "import into a Google doc, fiddle with headers, hit Export and tweak options x and y and z"), and you have an idea for how we can make that a 4-step process. > > and sharing the list of members on drive, > > What's "drive"? Probably Google Drive? > > as It will be very helpful for communities which have a lot of > > volunteers, organizers. > > How is it helpful? Here's a use case I ran into in December: I was editing a private document in Google Drive and wanted to share it with about 40 people, all of whom were on the same email thread as me. I ended up spending many tedious minutes copying and pasting email addresses into the "Share" dialog box in Google Drive. If I were a list owner for a community that used Google Drive, I bet this sort of need would crop up several times per year, and I'd wish there were an easy way for me to import that membership roster into a Google Drive permissions list. > > Scenario: > > Suppose a team of volunteers working in a country/state like > > bloodconnect in india. For an activity like camps [in case of blood > > connect], Owner need to send a pdf > > Why does the owner need to do that? I think that plain text (as Tom > Browder suggests) is almost surely more useful in every way. CSV, on > the other hand, has the advantage that it can be accurately read into > a spreadsheet which is "the" way non-geeky people manage tables. I have, as an event organizer, seen situations where venue managers, school administrators, and similar bureaucrats demanded PDFs. > > of all the volunteers working in a specific area to the area head > > either by drive or mail. It would be very convenient if we provide > > these option as a UI in postorius itself. > > Looks like a YAGNI to me, so it would just clutter the UI. Ashish, here's my opinion, for the use cases I've dealt with: CSV export is super helpful, plain text export is also very helpful, and PDF export is somewhat helpful. Answering my question will definitely help. :) -- Sumana Harihareswara http://brainwane.net From adam-mailman at amyl.org.uk Wed Apr 22 16:48:53 2015 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Wed, 22 Apr 2015 15:48:53 +0100 Subject: [Mailman-Developers] Regarding Csv Export for list owner in postorius In-Reply-To: <5537B209.5050705@panix.com> References: <87sibwma0e.fsf@uwakimon.sk.tsukuba.ac.jp> <5537B209.5050705@panix.com> Message-ID: <20150422144853.GA21372@hendricks.amyl.org.uk> On Wed, Apr 22, 2015 at 10:36:57AM -0400, Sumana Harihareswara wrote: > Ashish, can you talk a little bit more about the current workflow that > these folks are using (the ones in the scenario you suggested)? I'm used > to seeing word processing and spreadsheet applications that can easily > export to PDF. But maybe you know of a ton of people who need to create > PDFs from list membership rosters, and right now that's a 10-step > process for them (including "import into a Google doc, fiddle with > headers, hit Export and tweak options x and y and z"), and you have an > idea for how we can make that a 4-step process. Google Sheets (or whatever they're called this week) support a couple of functions that could hit the relevant API: IMPORTDATA [for (c|t)sv]: https://support.google.com/docs/answer/3093335?hl=en IMPORTHTML [for tables/lists]: https://support.google.com/docs/answer/3093339?hl=en Could either of those be an option (steer: user interface has PRODUCE A SPREADSHEET/EXPORT TO GDOCS)? > Here's a use case I ran into in December: I was editing a private > document in Google Drive and wanted to share it with about 40 people, > all of whom were on the same email thread as me. I ended up spending > many tedious minutes copying and pasting email addresses into the > "Share" dialog box in Google Drive. If I were a list owner for a > community that used Google Drive, I bet this sort of need would crop up > several times per year, and I'd wish there were an easy way for me to > import that membership roster into a Google Drive permissions list. Google Drive works extremely well with Google Groups? funny that. Part of that is why for one of the things I do, we've migrated over to Google Apps; for better integration / easier sharing. -- "what was asked of the Director in this case was not a statement of prosecuting policy but a proleptic grant of immunity from prosecution. That, I am quite satisfied, the Director had no power to give.? -- Bingham of Cornhill, R (Pretty) v DPP [2002] 1 AC 800 From adam-mailman at amyl.org.uk Wed Apr 22 17:11:05 2015 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Wed, 22 Apr 2015 16:11:05 +0100 Subject: [Mailman-Developers] Regarding Csv Export for list owner in postorius In-Reply-To: <5537B209.5050705@panix.com> References: <87sibwma0e.fsf@uwakimon.sk.tsukuba.ac.jp> <5537B209.5050705@panix.com> Message-ID: <20150422151105.GB21372@hendricks.amyl.org.uk> On Wed, Apr 22, 2015 at 10:36:57AM -0400, Sumana Harihareswara wrote: > Here's a use case I ran into in December: I was editing a private > document in Google Drive and wanted to share it with about 40 people, > all of whom were on the same email thread as me. I ended up spending > many tedious minutes copying and pasting email addresses into the > "Share" dialog box in Google Drive. My workflow for that is open the mail, copy all the recipients, paste in to the (advance) share dialog. But that is an annoyance. Particularly if I need to revoke 187 other users first? > If I were a list owner for a > community that used Google Drive, I bet this sort of need would crop up > several times per year, and I'd wish there were an easy way for me to > import that membership roster into a Google Drive permissions list. I'd suggest (at a later stage / as an extra plugin) something that uses the G-docs permissions:insert api function might be useful: https://developers.google.com/drive/v2/reference/permissions/insert something that delivers to the user something to copy/paste and run in their browser ("give list-members access to this Google Drive Folder/Document"). -- The University of California Department of Statistics... where mean is normal, and deviation standard From stephen at xemacs.org Wed Apr 22 18:51:48 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Thu, 23 Apr 2015 01:51:48 +0900 Subject: [Mailman-Developers] Regarding Csv Export for list owner in postorius In-Reply-To: <5537B209.5050705@panix.com> References: <87sibwma0e.fsf@uwakimon.sk.tsukuba.ac.jp> <5537B209.5050705@panix.com> Message-ID: <87618ot8bf.fsf@uwakimon.sk.tsukuba.ac.jp> Sumana Harihareswara writes: > Stephen, I suspect you are overestimating the technical skill of > some members of communities that want to use Mailman. I doubt it. My point is that we're talking about the PDF proposal, not the CSV feature. I may be underestimating the ability of programs other than printer drivers to do useful things with PDF, but in my experience printing is about all you can do unless you have a full suite of Adobe tools. Note that if you download CSV on most modern desktops, you will automatically be dropped into a spreadsheet program. So I would suppose that the workflow is 1. Click on "output member list" button in Mailman 2. Button down on File in Excel 3. Drag to print, release 4. Click on "output PDF" button 5. Type in file name (these programs, or the mail authors, usually have horribly bad suggestions for the file names). 6. Click Save button. > > How is it helpful? > Here's a use case I ran into in December: I was editing a private > document in Google Drive and wanted to share it with about 40 > people, all of whom were on the same email thread as me. I ended up > spending many tedious minutes copying and pasting email addresses > into the "Share" dialog box in Google Drive. If I were a list owner > for a community that used Google Drive, I bet this sort of need > would crop up several times per year, and I'd wish there were an > easy way for me to import that membership roster into a Google > Drive permissions list. I do not for one second doubt the utility of file output of membership rosters in a convenient, Microsoft-compatible format. But with CSV, we already have that. It's the utility of *PDF* that I'm questioning. > I have, as an event organizer, seen situations where venue > managers, school administrators, and similar bureaucrats demanded > PDFs. Me, too, in fact I do it myself in preference to working with .doc. But are list managers really likely to be so untechnical as to be unable to produce PDF from CSV? Also, are these PDFs going to be *just* "Display Name ", or are they going to contain other information? Generating CSV makes it easy to delete columns and rows as appropriate, or add them by hand. PDF, OTOH, is basically an uneditable blob. From stephen at xemacs.org Wed Apr 22 18:54:18 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Thu, 23 Apr 2015 01:54:18 +0900 Subject: [Mailman-Developers] Regarding Csv Export for list owner in postorius In-Reply-To: <20150422144853.GA21372@hendricks.amyl.org.uk> References: <87sibwma0e.fsf@uwakimon.sk.tsukuba.ac.jp> <5537B209.5050705@panix.com> <20150422144853.GA21372@hendricks.amyl.org.uk> Message-ID: <874mo8t879.fsf@uwakimon.sk.tsukuba.ac.jp> Adam McGreggor writes: > IMPORTDATA [for (c|t)sv]: https://support.google.com/docs/answer/3093335?hl=en > > IMPORTHTML [for tables/lists]: https://support.google.com/docs/answer/3093339?hl=en > > Could either of those be an option (steer: user interface has PRODUCE > A SPREADSHEET/EXPORT TO GDOCS)? Both of those look a lot more like it for my taste. Steve From coolyashish at gmail.com Wed Apr 22 19:42:27 2015 From: coolyashish at gmail.com (Ashish Kumar) Date: Wed, 22 Apr 2015 23:12:27 +0530 Subject: [Mailman-Developers] Regarding Csv Export for list owner in postorius In-Reply-To: <874mo8t879.fsf@uwakimon.sk.tsukuba.ac.jp> References: <87sibwma0e.fsf@uwakimon.sk.tsukuba.ac.jp> <5537B209.5050705@panix.com> <20150422144853.GA21372@hendricks.amyl.org.uk> <874mo8t879.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: Hi All, I was talking about a case where user needs to directly sends the member lists[info about the members like name, email ids, etc.] to some other email id's But yes stephen made it clear that It would be trivial to use excel like application for exporting csv into pdf's . So we can use the csv export which is already there or make a generic export view like a dropdown having some options like pdf, csv, txt etc. Thank You Ashish Kumar From stephen at xemacs.org Thu Apr 23 01:40:50 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Thu, 23 Apr 2015 08:40:50 +0900 Subject: [Mailman-Developers] Regarding Csv Export for list owner in postorius In-Reply-To: References: <87sibwma0e.fsf@uwakimon.sk.tsukuba.ac.jp> <5537B209.5050705@panix.com> <20150422144853.GA21372@hendricks.amyl.org.uk> <874mo8t879.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <87383ru3y5.fsf@uwakimon.sk.tsukuba.ac.jp> Ashish Kumar writes: > I was talking about a case where user needs to directly sends the > member lists[info about the members like name, email ids, etc.] to > some other email id's Yes, I understand that. There's a context for all this though. Mailman is an *open source* project. Some of us are free software advocates, who do this because we're trying to change the rules by which our world manages its software assets. Some of us are open source advocates, who see the question as a purely economic one of "faster, better, cheaper: we should not need to choose". For those of you still in college or graduate school, there's some bitter history here that I hope you never have a need to relive. But one thing we all agree on is that our software should empower our users to address their own needs. PDF is a proprietary format; it is owned, lock, stock and most popular implementation by the same company that had a visiting programmer arrested in the U.S. for publications outside U.S. More important for the current application, Adobe has also released buggy versions of its popular Acrobat Reader that crashed a supposedly advanced operating system (Windows NT) on documents that they acknowledged to conform to their own PDF standard. However, they WONTFIXed that bug because Adobe's products never used that particular idiom (and perhaps because Ghostscript, then the most popular alternative to Adobe Postscript products, did use it). So, in the end, supplying a PDF option helps to lock our users in to dependency on proprietary software and standards that they cannot change and which do not empower them to work faster, better, and cheaper. It's a difficult judgment whether the convenience of supplying output in this extremely popular format outweighs the effect of encouraging dependency. Sumana made an important point that perhaps I was overestimating the technical skills of the users being targeted by the feature. Perhaps, but if so, they'll tell us about it. What I advocate is that we not *underestimate* their potential for growth, nor close off the avenue to making the software and its output do what *they* want, rather than what *we* guess they want. Wearing my mentor hat: BTW, once again you haven't specified your case carefully enough for others to judge whether PDF is needed. Really, what purpose would not be well-served with a restructured text table directly insertend in the email, or a csv attachment, or an HTML table in HTML mail? Why PDF? Your "send the list" use case is no help in judging: those other three formats I just mentioned also present the list to an arbitrary group of recipients via email. Sumana presented a well-specified use case: formatting a list so that it can easily be presented to Google Docs to create a permission for a large group. That allows me to decide, "no PDF!" because I'm sure Google Docs would cough a hairball if she fed it PDF! Steve From adam-mailman at amyl.org.uk Thu Apr 23 13:22:14 2015 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Thu, 23 Apr 2015 12:22:14 +0100 Subject: [Mailman-Developers] Regarding Csv Export for list owner in postorius In-Reply-To: <87383ru3y5.fsf@uwakimon.sk.tsukuba.ac.jp> References: <87sibwma0e.fsf@uwakimon.sk.tsukuba.ac.jp> <5537B209.5050705@panix.com> <20150422144853.GA21372@hendricks.amyl.org.uk> <874mo8t879.fsf@uwakimon.sk.tsukuba.ac.jp> <87383ru3y5.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <20150423112214.GA5658@hendricks.amyl.org.uk> On Thu, Apr 23, 2015 at 08:40:50AM +0900, Stephen J. Turnbull wrote: > But one thing we all agree on is that our software should empower our > users to address their own needs. PDF is a proprietary format PDF has been an open standard (as much as 'open standards' are) since July 2008. While Adobe Systems made the PDF specification available free of charge in 1993, PDF was a proprietary format, controlled by Adobe, until it was officially released as an open standard on July 1, 2008, and published by the International Organization for Standardization as ISO 32000-1:2008,[4][5] at which time control of the specification passed to an ISO Committee of volunteer industry experts. In 2008, Adobe published a Public Patent License to ISO 32000-1 granting royalty-free rights for all patents owned by Adobe that are necessary to make, use, sell and distribute PDF compliant implementations -- http://en.wikipedia.org/wiki/Portable_Document_Format (The recent MS Office formats are also open standardized: Office Open XML etc) > More important for the current application, Adobe has > also released buggy versions of its popular Acrobat Reader that > crashed a supposedly advanced operating system (Windows NT) Hasn't NT been End of Life-d now for over 10 years? -- "[These atrocities] -- they all happened, and they did not happen any the less because the Daily Telegraph has suddenly found out about them when it is five years too late." -- George Orwell (Looking Back on the Spanish War, 1942) From barry at python.org Thu Apr 23 22:04:17 2015 From: barry at python.org (Barry Warsaw) Date: Thu, 23 Apr 2015 16:04:17 -0400 Subject: [Mailman-Developers] [Bug 1414154] Re: switch to external translation system In-Reply-To: <20150410194251.26637.20807.malone@gac.canonical.com> References: <20150123203254.612.75563.malonedeb@chaenomeles.canonical.com> <20150410194251.26637.20807.malone@gac.canonical.com> Message-ID: <20150423160417.49d99a03@limelight.wooz.org> On Apr 10, 2015, at 07:42 PM, Aur?lien Bompard wrote: >I would like to mention the existence of Zanata >which is 100% Free software. Could we use that? At least the license looks pretty decent, being GPL'd. I've just signed up and will try to create a Mailman project once I get the confirmation email. Then we can at least play with it and see if it'll do the trick for us. From stephen at xemacs.org Fri Apr 24 04:36:11 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Fri, 24 Apr 2015 11:36:11 +0900 Subject: [Mailman-Developers] Regarding Csv Export for list owner in postorius In-Reply-To: <20150423112214.GA5658@hendricks.amyl.org.uk> References: <87sibwma0e.fsf@uwakimon.sk.tsukuba.ac.jp> <5537B209.5050705@panix.com> <20150422144853.GA21372@hendricks.amyl.org.uk> <874mo8t879.fsf@uwakimon.sk.tsukuba.ac.jp> <87383ru3y5.fsf@uwakimon.sk.tsukuba.ac.jp> <20150423112214.GA5658@hendricks.amyl.org.uk> Message-ID: <87wq12qmlg.fsf@uwakimon.sk.tsukuba.ac.jp> Adam McGreggor writes: > PDF has been an open standard (as much as 'open standards' are) Some open standards (specifically, IETF standards) really are. However, ISO standards rarely come up to that level, since all ISO standards must be vetted by national or regional organizations (and ECMA is about as bad as they come when it comes to kowtowing to corporate interests). > since July 2008. I stand corrected (I've been out of Ghostscript development as long as Peter Deutsch has been out of it, so haven't paid attention to the ins and outs of PDF). Be that as it may, all of the open source PDF tools I know of are pretty much crap compared to Adobe's tools. For practical purposes it's a binary blob. If you know better, I'd love to hear about it. > Hasn't NT been End of Life-d now for over 10 years? Not the point. The point is that Adobe used its market power to refuse to fix a bug that took the whole system down, and it wasn't a MS-DOG-based system, it was a system that cleared the DoD's "Orange Book" standard for security. I see nothing in Adobe's current behavior to indicate that it has become more open since. (The opening of PDF is consistent with cost-cutting in the face of an "innovator's dilemma" in the PDF market and Adobe's move into dynamic presentation like its acquisition of Macromedia.) > "[These atrocities] -- they all happened, and they did not happen > any the less because the Daily Telegraph has suddenly found out > about them when it is five years too late." > -- George Orwell (Looking Back on the Spanish War, 1942) What an apropros quote for a discussion of Adobe's "openness"! Steve From f at florianfuchs.com Mon Apr 27 21:05:45 2015 From: f at florianfuchs.com (Florian Fuchs) Date: Mon, 27 Apr 2015 21:05:45 +0200 Subject: [Mailman-Developers] Welcome to GSoC 2015 Message-ID: <20150427190542.GA25538@soc2> Fellow friends of Mailman, dear students, welcome to GSoC 2015 (the Mailman edition)! First of all: We were overwhelmed by the amount of interest in Mailman during this year's application phase. We got far more applications than expected, and in the process many bug fixes (and new reports) and merge proposals. Thanks to all the applicants who asked questions on IRC, posted thoughts and ideas to this mailings list and submitted an unexpected number of great proposals. You rock! Google gave us 3 slots (which is a really good number, given we're in as a separate org for the first time in years). But having to pick 3 out of 25 left us with some really hard choices. So for those who couldn't get in this year: Please don't feel discouraged to keep contributing to Mailman or to try again next year! But now, without further ado, let's welcome our three GSoC students: Ankush Sharma - Mailman client written in JavaScript Mentors: Florian Fuchs, Abhilash Raj Bhavesh Goyal - A Dashboard for Admins/Owners/Moderators Mentors: Abhilash Raj, Sneha Priscilla Makini Pranjal Yadav - Dynamic Sublists Mentors: Stephen Turnbull, Terri Oda Congratulations to you all -- we are looking forward to working with you! Let's have a great summer! Florian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: From barry at list.org Mon Apr 27 21:11:09 2015 From: barry at list.org (Barry Warsaw) Date: Mon, 27 Apr 2015 15:11:09 -0400 Subject: [Mailman-Developers] Welcome to GSoC 2015 In-Reply-To: <20150427190542.GA25538@soc2> References: <20150427190542.GA25538@soc2> Message-ID: <20150427151109.2b8354d8@anarchist.wooz.org> On Apr 27, 2015, at 09:05 PM, Florian Fuchs wrote: >Ankush Sharma - Mailman client written in JavaScript >Mentors: Florian Fuchs, Abhilash Raj > >Bhavesh Goyal - A Dashboard for Admins/Owners/Moderators >Mentors: Abhilash Raj, Sneha Priscilla Makini > >Pranjal Yadav - Dynamic Sublists >Mentors: Stephen Turnbull, Terri Oda > >Congratulations to you all -- we are looking forward to working with you! L >et's have a great summer! Indeed congratulations to all students and a warm thank you to all mentors! Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From godricglow at gmail.com Mon Apr 27 23:09:17 2015 From: godricglow at gmail.com (Pranjal Yadav) Date: Tue, 28 Apr 2015 02:39:17 +0530 Subject: [Mailman-Developers] Welcome to GSoC 2015 In-Reply-To: <20150427190542.GA25538@soc2> References: <20150427190542.GA25538@soc2> Message-ID: Congratulations everybody and cheers (_)3 I'm thankful to all the mentors for their help and support throughout and for considering my proposal. Looking forward for a great summer! On Tue, Apr 28, 2015 at 12:35 AM, Florian Fuchs wrote: > Fellow friends of Mailman, dear students, > welcome to GSoC 2015 (the Mailman edition)! > > First of all: We were overwhelmed by the amount of interest in Mailman > during this year's application phase. We got far more applications than > expected, and in the process many bug fixes (and new reports) and merge > proposals. Thanks to all the applicants who asked questions on IRC, posted > thoughts and ideas to this mailings list and submitted an unexpected number > of great proposals. You rock! > > Google gave us 3 slots (which is a really good number, given we're in as a > separate org for the first time in years). But having to pick 3 out of 25 > left us with some really hard choices. So for those who couldn't get in > this year: Please don't feel discouraged to keep contributing to Mailman or > to try again next year! > > But now, without further ado, let's welcome our three GSoC students: > > Ankush Sharma - Mailman client written in JavaScript > Mentors: Florian Fuchs, Abhilash Raj > > Bhavesh Goyal - A Dashboard for Admins/Owners/Moderators > Mentors: Abhilash Raj, Sneha Priscilla Makini > > Pranjal Yadav - Dynamic Sublists > Mentors: Stephen Turnbull, Terri Oda > > Congratulations to you all -- we are looking forward to working with you! > Let's have a great summer! > > Florian > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at 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/godricglow%40gmail.com > > Security Policy: http://wiki.list.org/x/QIA9 > -- *Pranjal Yadav* *IIT Kharagpur* From stephen at xemacs.org Tue Apr 28 03:36:41 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 28 Apr 2015 10:36:41 +0900 Subject: [Mailman-Developers] Welcome to GSoC 2015 In-Reply-To: <20150427190542.GA25538@soc2> References: <20150427190542.GA25538@soc2> Message-ID: <87383lqbiu.fsf@uwakimon.sk.tsukuba.ac.jp> Florian Fuchs writes: > Fellow friends of Mailman, dear students, > > welcome to GSoC 2015 (the Mailman edition)! Congratulations to all of the applicants on the high quality of applications! For those who were not selected, I'd be happy to discuss your applications off-list (and by mail, not IRC, I'm still catching up on $DAYJOB so replies may take a few days). > But now, without further ado, let's welcome our three GSoC > students: Congratulations to the selected students! And a personal note: > Bhavesh Goyal - A Dashboard for Admins/Owners/Moderators > Mentors: Abhilash Raj, Sneha Priscilla Makini I've mentored a similar project in the past (Shanu Salunke's "Mailman Interface" for Systers), so feel free to include me in discussions. That said, speaking as an individual mentor, I would really like to see most technical discussions take place on this list, or at least be summarized here. I hope folks not participating in GSoC will bear with us (hi, Andrew! some of your older posts are in my queue, someday soon...). Besides wanting to see what students I'm *not* mentoring are up to, we've had issues in the past where a project went off in an unprofitable (ie, hard to integrate) direction when the mentor and student were communicating almost exclusively in personal mail and IRC direct messages. Although your mentor has a *responsibility* to answer you, the rest of us care and want to contribute, and that's easiest if you post to this list. Here's to a fun and productive summer for everyone! Steve From ankush.sharma.ece12 at iitbhu.ac.in Tue Apr 28 14:35:37 2015 From: ankush.sharma.ece12 at iitbhu.ac.in (Ankush Sharma) Date: Tue, 28 Apr 2015 18:05:37 +0530 Subject: [Mailman-Developers] Welcome to GSoC 2015 In-Reply-To: <87383lqbiu.fsf@uwakimon.sk.tsukuba.ac.jp> References: <20150427190542.GA25538@soc2> <87383lqbiu.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: Congratulations everybody and thanks to all Mailman mentors for their constant support. Thanks, Ankush Sharma http://github.com/black-perl On Tue, Apr 28, 2015 at 7:06 AM, Stephen J. Turnbull wrote: > Florian Fuchs writes: > > Fellow friends of Mailman, dear students, > > > > welcome to GSoC 2015 (the Mailman edition)! > > Congratulations to all of the applicants on the high quality of > applications! > > For those who were not selected, I'd be happy to discuss your > applications off-list (and by mail, not IRC, I'm still catching up on > $DAYJOB so replies may take a few days). > > > But now, without further ado, let's welcome our three GSoC > > students: > > Congratulations to the selected students! > > And a personal note: > > > Bhavesh Goyal - A Dashboard for Admins/Owners/Moderators > > Mentors: Abhilash Raj, Sneha Priscilla Makini > > I've mentored a similar project in the past (Shanu Salunke's "Mailman > Interface" for Systers), so feel free to include me in discussions. > > That said, speaking as an individual mentor, I would really like to > see most technical discussions take place on this list, or at least be > summarized here. I hope folks not participating in GSoC will bear > with us (hi, Andrew! some of your older posts are in my queue, someday > soon...). Besides wanting to see what students I'm *not* mentoring > are up to, we've had issues in the past where a project went off in an > unprofitable (ie, hard to integrate) direction when the mentor and > student were communicating almost exclusively in personal mail and IRC > direct messages. > > Although your mentor has a *responsibility* to answer you, the rest of > us care and want to contribute, and that's easiest if you post to this > list. > > Here's to a fun and productive summer for everyone! > > Steve > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at 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/ankush.sharma.ece12%40itbhu.ac.in > > Security Policy: http://wiki.list.org/x/QIA9 > From danil at smirnov.la Tue Apr 28 18:33:50 2015 From: danil at smirnov.la (Danil Smirnov) Date: Tue, 28 Apr 2015 19:33:50 +0300 Subject: [Mailman-Developers] web-interface for site owner for mm 2.1.x Message-ID: 2015-04-28 19:17 GMT+03:00 Mark Sapiro : > If you set > > OWNERS_CAN_DELETE_THEIR_OWN_LISTS = Yes > > in mm_cfg.py, every page in Mailman's admin GUI will have a "Delete this > mailing list (requires confirmation)" link under "Other Administrative > Activities". Without this setting, the link is not there and attempts to > remove a list via the http(s)://example.com/mailman/rmlist/LISTNAME CGI > will fail. Hi everybody! How do you think, should site owner have an ability to remove lists from web interface also? We have separate password for list creation which can be set different from site owner password. We have special email alias "mailman-owner at domain.tld" which belongs to whole installation admin. So we already have credentials for site owner to let him/her log in. Probably we also need full administration web interface for all mm_cfg.py amendments to avoid using console for the administration of Mailman installation at all. I wonder if nobody interested in this? Danil From mark at msapiro.net Tue Apr 28 18:42:09 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 28 Apr 2015 09:42:09 -0700 Subject: [Mailman-Developers] web-interface for site owner for mm 2.1.x In-Reply-To: References: Message-ID: <553FB861.4080309@msapiro.net> On 04/28/2015 09:33 AM, Danil Smirnov wrote: > > How do you think, should site owner have an ability to remove lists > from web interface also? This will be available in MM 3. If you are asking if a site admin can remove a list via the web UI if the OWNERS_CAN_DELETE_THEIR_OWN_LISTS setting is the default No, the answer for MM 2.1 is no and there is no plan to change that. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From danil at smirnov.la Tue Apr 28 18:59:41 2015 From: danil at smirnov.la (Danil Smirnov) Date: Tue, 28 Apr 2015 19:59:41 +0300 Subject: [Mailman-Developers] web-interface for site owner for mm 2.1.x In-Reply-To: <553FB861.4080309@msapiro.net> References: <553FB861.4080309@msapiro.net> Message-ID: 2015-04-28 19:42 GMT+03:00 Mark Sapiro : > If you are asking if a site admin can remove a list via the web UI if > the OWNERS_CAN_DELETE_THEIR_OWN_LISTS setting is the default No, the > answer for MM 2.1 is no and there is no plan to change that. Personally I'm okay with the command line. But I have the client who asked me to install Mailman for her and intend to administer the installation by herself. She is not familiar with ssh/Linux console and uses cPanel-based hosting. Right now everything seems smooth for her besides lists removal - it can't be done without console access. Of course, we have workaround with OWNERS_CAN_DELETE_THEIR_OWN_LISTS setting, but in this case she cannot delegate list creation/administration to untrusted person. I understand the reasons why list removal is not available by default, but it would be great if we can somehow add special site owner permission to get her ability to remove lists (and to her only). (I'm asking about 2.1.x branch only, as I mentioned in the subject line.) Danil From mark at msapiro.net Tue Apr 28 19:39:42 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 28 Apr 2015 10:39:42 -0700 Subject: [Mailman-Developers] web-interface for site owner for mm 2.1.x In-Reply-To: References: <553FB861.4080309@msapiro.net> Message-ID: <553FC5DE.9010908@msapiro.net> On 04/28/2015 09:59 AM, Danil Smirnov wrote: > > But I have the client who asked me to install Mailman for her and > intend to administer the installation by herself. > She is not familiar with ssh/Linux console and uses cPanel-based hosting. cPanel provides a version of Mailman and has it's own list creation and deletion cPanel interface outside of the Mailman web UI. It seems if you used that, it would solve your problem. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From danil at smirnov.la Tue Apr 28 20:02:11 2015 From: danil at smirnov.la (Danil Smirnov) Date: Tue, 28 Apr 2015 21:02:11 +0300 Subject: [Mailman-Developers] web-interface for site owner for mm 2.1.x In-Reply-To: <553FC5DE.9010908@msapiro.net> References: <553FB861.4080309@msapiro.net> <553FC5DE.9010908@msapiro.net> Message-ID: 2015-04-28 20:39 GMT+03:00 Mark Sapiro : > cPanel provides a version of Mailman and has it's own list creation and > deletion cPanel interface outside of the Mailman web UI. > > It seems if you used that, it would solve your problem. Nope. She has serious reasons to avoid using cPanel's Mailman. So it was disabled in favor of standard Mailman installation. I can give more details but webpanel talk is irrelevant to the topic of this discussion. Danil From mark at msapiro.net Tue Apr 28 20:39:39 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 28 Apr 2015 11:39:39 -0700 Subject: [Mailman-Developers] web-interface for site owner for mm 2.1.x In-Reply-To: References: <553FB861.4080309@msapiro.net> <553FC5DE.9010908@msapiro.net> Message-ID: <553FD3EB.1080800@msapiro.net> On 04/28/2015 11:02 AM, Danil Smirnov wrote: > > Nope. She has serious reasons to avoid using cPanel's Mailman. > So it was disabled in favor of standard Mailman installation. > I can give more details but webpanel talk is irrelevant > to the topic of this discussion. Then if she is going to create lists and turn them over to others to admin and the others are going to change the admin password so she doesn't know it, there are two choices for removing the list short of writing your own CGI or WSGI process to do it: - there is the command line bin/rmlist tool - you could modify Mailman/Cgi/rmlist.py and remove the 10 lines of code starting with # Be sure the list owners are not sneaking around! if not mm_cfg.OWNERS_CAN_DELETE_THEIR_OWN_LISTS: and ending with return which would then allow anyone who knows the site admin, site list creator or list admin password to go to a URL like http://example.com/mailman/rmlist/LISTNAME and remove the list. If you wanted to limit it to only the site admin or site list creator passwords, further down in the code, find if mlist.Authenticate((mm_cfg.AuthCreator, mm_cfg.AuthListAdmin, mm_cfg.AuthSiteAdmin), password) == mm_cfg.UnAuthorized: and remove the mm_cfg.AuthListAdmin, line. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From shirish at hamaralinux.org Tue Apr 28 21:47:11 2015 From: shirish at hamaralinux.org (shirish) Date: Wed, 29 Apr 2015 01:17:11 +0530 Subject: [Mailman-Developers] mailman 3.0 roadmap, feature-parity with mailman 2.x and documentation Message-ID: <553FE3BF.10203@hamaralinux.org> Hi all, Thank you for the unblemished service by Mailman. It is due to you that many FOSS projects continue to see the light of the day as email continues to hold its sway on developers rather than forums and mail management continues to be easier due to Mailman. Newbie here. I have been reading the Mailman wiki page specifically http://wiki.list.org/DEV/Mailman%203.0 Now from the wiki page :- "We aim to release Mailman 3.0rc1 in late April, 2015." - wiki entry While RC1 is hopefully round the corner there doesn't seem to be a roadmap at least within mailman. The launchpad series gives the following :- https://launchpad.net/mailman/+series What would be nice is if there is some ETA as to when 3.0 will be released to the general public. Are there going to be another 2-3-4 RC releases before 3.0 is ready ? Another query :- " It is not yet at full feature parity with Mailman 2.x, but we're working on that for 3.1. " - wiki entry on the same page. While this is good to know, is there a matrix of features somewhere which shows features of mailman 2.x vs mailman 3.0 . I am unable to find such a page in the wiki or perhaps I didn't search enough. In any case if there is a listing of features of both mailman 3.x and mailman 2.x would be helpful for both newbies as well as experienced users as it will look like a snapshot of the features integrated or used in the new release. It doesn't have to be finished today but if there is even some information about the existence of such a page with differences between 2.x and 3.x would be immensely helpful. Lastly, the documentation for 3.0.x seems to be a good way at http://gnu-mailman.readthedocs.org/en/latest/ would be nicer if there was a way to generate .pdf from the content therein. Look forward to trying out Mailman 3 soonish. -- Regards, Shirish Agarwal, Community Lead, Hamaralinux.org From barry at list.org Wed Apr 29 00:00:05 2015 From: barry at list.org (Barry Warsaw) Date: Tue, 28 Apr 2015 18:00:05 -0400 Subject: [Mailman-Developers] ANNOUNCING: GNU Mailman 3.0 Message-ID: <20150428180005.6337c2a1@limelight.wooz.org> Twenty years ago, I attended the first Python Workshop at NIST with about 20 other old school Pythonistas. Earlier this month I attended PyCon 2015 in Montreal. PyCon is always exhilarating, but this one was incredibly special for me personally, because my son was on spring break and joined me for the first half of the conference. Both the Python language and its community have grown a little bit in the intervening years, but what hasn't changed is our love of the language, and the truly amazing people we share that love with. The Python community really is one of the very best open source communities on the planet. The best community inside that great Python family has to be the GNU Mailman team. They're all smart and cool, fun to hang out with, and fun to hack with. With diverse backgrounds, each and every one are good friends and valued technical peers. As has been the case for the last few years, we've sprinted on Mailman 3, getting lots of great work done, but never quite getting something we were satisfied enough with to release. The first alpha of Mailman 3 was released a little over 7 years ago. And so I'm here --and on behalf of Abhilash, Aur?lien, Florian, John, Mark, Stephen, Sumana, Terri, our GSoC students, and all the great people who have contributed over the years-- to proudly announce the official release of GNU Mailman 3.0, code named "Show Don't Tell". Mailman 3 is really a suite of 5 tools: * The core, which provides the mail delivery engine, the unified user model, moderation and modification of email messages, and interfaces to external archivers; * Postorius, our new Django-based web user interface for users and list administrators; * HyperKitty, our new Django-based web archiver, providing rich access to the historical record of mailing list traffic; * mailman.client, the official Python bindings to the core's REST API; * mailman-bundler, a set of scripts to make it easy to deploy the full suite inside Python virtual environments. What's new about Mailman 3? Well, lots! Some highlights include: * Backed by a relational database; * True support for multiple domains, with no cross-domain mailing list naming restrictions; * One user account to manage all your subscriptions on a site; * The core's functionality exposed through an administrative REST+JSON API; * All passwords hashed by default, and no monthly password reminders! * Users can post to lists via the web interface; * Built-in archive searching! and more. Tons more. There will be things you love about Mailman 3, and things you don't like. You'll glimpse great possibilities and glaring holes. You'll be excited and frustrated. Such is life with an all-volunteer free software project. For the things you like, and the exciting possibilities, we encourage you to experiment, to do wacky things we haven't thought of, integrate it with your own tools, or just carefully go about deploying a Mailman 3 system. Tell us how you're using it! For the things you don't like, we invite you to join us. Come to the mailing list and talk with us. Submit bug reports and pull requests. Help us close the gaps and make Mailman 3 better. Whether your interests are for Internet RFCs, web site development, operations, or you just want to find a fun Python project to hack on with cool people, as they say, contributions are welcome. See the release notes, as well as links to download each component: http://wiki.list.org/Mailman3 You probably want to start with the bundler and let it grab and install all the other parts. More information is available at: http://www.list.org http://wiki.list.org http://launchpad.net/mailman #mailman on freenode mailman-developers at python.org Happy Mailman Day, -Barry & the Mailman Cabal -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From barry at list.org Wed Apr 29 01:03:10 2015 From: barry at list.org (Barry Warsaw) Date: Tue, 28 Apr 2015 19:03:10 -0400 Subject: [Mailman-Developers] mailman 3.0 roadmap, feature-parity with mailman 2.x and documentation In-Reply-To: <553FE3BF.10203@hamaralinux.org> References: <553FE3BF.10203@hamaralinux.org> Message-ID: <20150428190310.225615af@limelight.wooz.org> On Apr 29, 2015, at 01:17 AM, shirish wrote: >"We aim to release Mailman 3.0rc1 in late April, 2015." - wiki entry >What would be nice is if there is some ETA as to when 3.0 will be released to >the general public. Are there going to be another 2-3-4 RC releases before >3.0 is ready ? Actually, we just released 3.0 today. :) >While this is good to know, is there a matrix of features somewhere which >shows features of mailman 2.x vs mailman 3.0 . I am unable to find such a >page in the wiki or perhaps I didn't search enough. We don't really have this right now. I think we'll start to fill out the bug tracker with features or fixes that need to be forward ported to Mailman 3. Some things you won't miss, like passwords in clear text, monthly password reminders, having multiple accounts to manage subscriptions with different email addresses, no built-in archive searching, restrictions on naming lists in multiple domains, etc. >Lastly, the documentation for 3.0.x seems to be a good way at >http://gnu-mailman.readthedocs.org/en/latest/ would be nicer if there was a >way to generate .pdf from the content therein. You can do it from the source tree. We build the docs with Sphinx and I believe it has a PDF option. We likely won't officially distribute PDFs. Cheers, -Barry From skip.montanaro at gmail.com Wed Apr 29 01:52:03 2015 From: skip.montanaro at gmail.com (Skip Montanaro) Date: Tue, 28 Apr 2015 18:52:03 -0500 Subject: [Mailman-Developers] ANNOUNCING: GNU Mailman 3.0 In-Reply-To: <20150428180005.6337c2a1@limelight.wooz.org> References: <20150428180005.6337c2a1@limelight.wooz.org> Message-ID: Barry, Congratulations, you mail d(a)emon, you! And all the other responsible d(a)emons. Has it really been 20 years since the NIST workshop? Skip From brian at emwd.com Wed Apr 29 17:03:13 2015 From: brian at emwd.com (Brian Carpenter) Date: Wed, 29 Apr 2015 11:03:13 -0400 Subject: [Mailman-Developers] mailman 3.0 roadmap, feature-parity with mailman 2.x and documentation In-Reply-To: <20150428190310.225615af@limelight.wooz.org> References: <553FE3BF.10203@hamaralinux.org> <20150428190310.225615af@limelight.wooz.org> Message-ID: <3d3101d0828d$9dab1920$d9014b60$@emwd.com> > -----Original Message----- > From: Mailman-Developers [mailto:mailman-developers- > bounces+brian=emwd.com at python.org] On Behalf Of Barry Warsaw > Sent: Tuesday, April 28, 2015 7:03 PM > To: mailman-developers at python.org > Subject: Re: [Mailman-Developers] mailman 3.0 roadmap, feature-parity > with mailman 2.x and documentation > > On Apr 29, 2015, at 01:17 AM, shirish wrote: > > >"We aim to release Mailman 3.0rc1 in late April, 2015." - wiki entry > > >What would be nice is if there is some ETA as to when 3.0 will be released to > >the general public. Are there going to be another 2-3-4 RC releases before > >3.0 is ready ? > > Actually, we just released 3.0 today. :) > > >While this is good to know, is there a matrix of features somewhere which > >shows features of mailman 2.x vs mailman 3.0 . I am unable to find such a > >page in the wiki or perhaps I didn't search enough. > > We don't really have this right now. I think we'll start to fill out the bug > tracker with features or fixes that need to be forward ported to Mailman 3. > Some things you won't miss, like passwords in clear text, monthly password > reminders, having multiple accounts to manage subscriptions with different > email addresses, no built-in archive searching, restrictions on naming lists > in multiple domains, etc. > > >Lastly, the documentation for 3.0.x seems to be a good way at > >http://gnu-mailman.readthedocs.org/en/latest/ would be nicer if there > was a > >way to generate .pdf from the content therein. > > You can do it from the source tree. We build the docs with Sphinx and I > believe it has a PDF option. We likely won't officially distribute PDFs. > > Cheers, > -Barry Hi Barry: Just to be clear, this is a stable fully working version of Mailman 3.0? I tried setting up Mailman 3 on a CentOS server about 2 weeks ago and had a number of issues including listinfo pages not working (404 errors), no clear directions on setting up users, various bugs such as internal server errors. The server admin that I had hired informed me there was a number of python related bugs and he felt Mailman 3 was not ready for production use. I am ready to give this another try but I want to make sure that this version will be a full working version of Mailman 3. Thanks, Brian From 24.sneha at gmail.com Wed Apr 29 21:16:50 2015 From: 24.sneha at gmail.com (Sneha Priscilla) Date: Thu, 30 Apr 2015 00:46:50 +0530 Subject: [Mailman-Developers] Welcome to GSoC 2015 In-Reply-To: References: <20150427190542.GA25538@soc2> <87383lqbiu.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: Hi everyone, Congratulations to all the GSoC students selected this year! Looking forward to working with you. I think Abhilash has covered almost everything in his welcome email so I would advise all the students to go through that. :) A brief introduction about myself since I haven't spoken to some of you earlier: While I have never directly been a GSoC student for GNU Mailman, I have worked on Mailman under the Systers organisation (Postorius mainly) and was a co-mentor for the previous Summer of Code. My experience with this organisation and the people here has been a wonderful, inspiring one and I have learnt a LOT. I only hope you feel the same way at the end of this summer program and have fun along the way! Best, Sneha IRC: stylistica On Tue, Apr 28, 2015 at 6:05 PM, Ankush Sharma < ankush.sharma.ece12 at iitbhu.ac.in> wrote: > Congratulations everybody and thanks to all Mailman mentors for their > constant support. > > Thanks, > Ankush Sharma > http://github.com/black-perl > > On Tue, Apr 28, 2015 at 7:06 AM, Stephen J. Turnbull > wrote: > > > Florian Fuchs writes: > > > Fellow friends of Mailman, dear students, > > > > > > welcome to GSoC 2015 (the Mailman edition)! > > > > Congratulations to all of the applicants on the high quality of > > applications! > > > > For those who were not selected, I'd be happy to discuss your > > applications off-list (and by mail, not IRC, I'm still catching up on > > $DAYJOB so replies may take a few days). > > > > > But now, without further ado, let's welcome our three GSoC > > > students: > > > > Congratulations to the selected students! > > > > And a personal note: > > > > > Bhavesh Goyal - A Dashboard for Admins/Owners/Moderators > > > Mentors: Abhilash Raj, Sneha Priscilla Makini > > > > I've mentored a similar project in the past (Shanu Salunke's "Mailman > > Interface" for Systers), so feel free to include me in discussions. > > > > That said, speaking as an individual mentor, I would really like to > > see most technical discussions take place on this list, or at least be > > summarized here. I hope folks not participating in GSoC will bear > > with us (hi, Andrew! some of your older posts are in my queue, someday > > soon...). Besides wanting to see what students I'm *not* mentoring > > are up to, we've had issues in the past where a project went off in an > > unprofitable (ie, hard to integrate) direction when the mentor and > > student were communicating almost exclusively in personal mail and IRC > > direct messages. > > > > Although your mentor has a *responsibility* to answer you, the rest of > > us care and want to contribute, and that's easiest if you post to this > > list. > > > > Here's to a fun and productive summer for everyone! > > > > Steve > > > > > > _______________________________________________ > > Mailman-Developers mailing list > > Mailman-Developers at 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/ankush.sharma.ece12%40itbhu.ac.in > > > > Security Policy: http://wiki.list.org/x/QIA9 > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at 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/24.sneha%40gmail.com > > Security Policy: http://wiki.list.org/x/QIA9 > From danil at smirnov.la Wed Apr 29 22:24:13 2015 From: danil at smirnov.la (Danil Smirnov) Date: Wed, 29 Apr 2015 23:24:13 +0300 Subject: [Mailman-Developers] mailman 3.0 roadmap, feature-parity with mailman 2.x and documentation In-Reply-To: <3d3101d0828d$9dab1920$d9014b60$@emwd.com> References: <553FE3BF.10203@hamaralinux.org> <20150428190310.225615af@limelight.wooz.org> <3d3101d0828d$9dab1920$d9014b60$@emwd.com> Message-ID: 2015-04-29 18:03 GMT+03:00 Brian Carpenter : > Just to be clear, this is a stable fully working version of Mailman 3.0? I > tried setting up Mailman 3 on a CentOS server about 2 weeks ago and had a > number of issues including listinfo pages not working (404 errors), no clear > directions on setting up users, various bugs such as internal server errors. > The server admin that I had hired informed me there was a number of python > related bugs and he felt Mailman 3 was not ready for production use. > > I am ready to give this another try but I want to make sure that this > version will be a full working version of Mailman 3. I had similar experience a week ago (after PyCon sprint) and there were couple bugs in the installation process on Centos 7 including hard one with bad virtualenv version which is still not reflected in the installation manual: https://bugs.launchpad.net/mailman/+bug/1445764/comments/19 I suppose anyone who try to install Mailman on Centos 7 will face this bug. Danil From brian at emwd.com Wed Apr 29 22:26:07 2015 From: brian at emwd.com (Brian Carpenter) Date: Wed, 29 Apr 2015 16:26:07 -0400 Subject: [Mailman-Developers] mailman 3.0 roadmap, feature-parity with mailman 2.x and documentation In-Reply-To: References: <553FE3BF.10203@hamaralinux.org> <20150428190310.225615af@limelight.wooz.org> <3d3101d0828d$9dab1920$d9014b60$@emwd.com> Message-ID: <45d001d082ba$b97ded30$2c79c790$@emwd.com> > -----Original Message----- > From: Mailman-Developers [mailto:mailman-developers- > bounces+brian=emwd.com at python.org] On Behalf Of Danil Smirnov > Sent: Wednesday, April 29, 2015 4:24 PM > To: Mailman Developers > Subject: Re: [Mailman-Developers] mailman 3.0 roadmap, feature-parity > with mailman 2.x and documentation > > 2015-04-29 18:03 GMT+03:00 Brian Carpenter : > > Just to be clear, this is a stable fully working version of Mailman 3.0? I > > tried setting up Mailman 3 on a CentOS server about 2 weeks ago and had a > > number of issues including listinfo pages not working (404 errors), no clear > > directions on setting up users, various bugs such as internal server errors. > > The server admin that I had hired informed me there was a number of > python > > related bugs and he felt Mailman 3 was not ready for production use. > > > > I am ready to give this another try but I want to make sure that this > > version will be a full working version of Mailman 3. > > I had similar experience a week ago (after PyCon sprint) and there > were couple bugs in the installation process on Centos 7 including > hard one with bad virtualenv version which is still not reflected in > the installation manual: > https://bugs.launchpad.net/mailman/+bug/1445764/comments/19 > > I suppose anyone who try to install Mailman on Centos 7 will face this bug. > > Danil The OS was CentOS 6.5 in my case. Is there a recommended server environment to run Mailman 3? Brian From mark at msapiro.net Thu Apr 30 03:42:48 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 29 Apr 2015 18:42:48 -0700 Subject: [Mailman-Developers] mailman 3.0 roadmap, feature-parity with mailman 2.x and documentation In-Reply-To: <45d001d082ba$b97ded30$2c79c790$@emwd.com> References: <553FE3BF.10203@hamaralinux.org> <20150428190310.225615af@limelight.wooz.org> <3d3101d0828d$9dab1920$d9014b60$@emwd.com> <45d001d082ba$b97ded30$2c79c790$@emwd.com> Message-ID: <55418898.80703@msapiro.net> On 04/29/2015 01:26 PM, Brian Carpenter wrote: > > Is there a recommended server environment to run Mailman 3? It should install and run on any *nix server that supports both Python 2.7 and Python 3.0, an MTA capable of LMTP delivery to Mailman (currently configurations for Postfix and Exim are provided) and a web server compatible with Django. We haven't tested all the possible combinations, and we've admittedly been a moving target, but things should get better and if you try and have issues, report them to this list or the appropriate (Mailman, Postorius or HyperKitty) bug tracker on Launchpad, and we will both try to help you through them and fix them. Note, during the PyCon sprints, I did test installing and running Mailman 3 along side a running Mailman 2.1.20+ on my Ubuntu 14.10 laptop. I did have to sort out some dependencies, but it worked with the one caveat that if you have both a Mailman 2.1 list and a Mailman 3 list with the exact same posting address, in our recommended setup at least, Postfix will deliver a post only to the MM 3 list. We understand we have a way to go, and it will be 3.1 before we get a clean, tested migration path and little or no loss of feature/function (the MM 3 core is based on an older 2.1 version), but we need people to start using MM 3 now, if only in limited environments, or we're never going to find the problem areas. This is a major project and we are fewer than a dozen main contributers to its development, and we are all volunteers who do this for our own personal reasons, but not for money (most of us have day jobs; I'm fortunate enough to be retired). We need your involvement to make this successful. We welcome your help. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From brian at emwd.com Thu Apr 30 05:45:19 2015 From: brian at emwd.com (Brian Carpenter) Date: Wed, 29 Apr 2015 23:45:19 -0400 Subject: [Mailman-Developers] mailman 3.0 roadmap, feature-parity with mailman 2.x and documentation In-Reply-To: <55418898.80703@msapiro.net> References: <553FE3BF.10203@hamaralinux.org> <20150428190310.225615af@limelight.wooz.org> <3d3101d0828d$9dab1920$d9014b60$@emwd.com> <45d001d082ba$b97ded30$2c79c790$@emwd.com> <55418898.80703@msapiro.net> Message-ID: <4acb01d082f8$1466dc10$3d349430$@emwd.com> > -----Original Message----- > From: Mailman-Developers [mailto:mailman-developers- > bounces+brian=emwd.com at python.org] On Behalf Of Mark Sapiro > Sent: Wednesday, April 29, 2015 9:43 PM > To: mailman-developers at python.org > Subject: Re: [Mailman-Developers] mailman 3.0 roadmap, feature-parity > with mailman 2.x and documentation > > On 04/29/2015 01:26 PM, Brian Carpenter wrote: > > > > Is there a recommended server environment to run Mailman 3? > > > It should install and run on any *nix server that supports both Python > 2.7 and Python 3.0, an MTA capable of LMTP delivery to Mailman > (currently configurations for Postfix and Exim are provided) and a web > server compatible with Django. > > We haven't tested all the possible combinations, and we've admittedly > been a moving target, but things should get better and if you try and > have issues, report them to this list or the appropriate (Mailman, > Postorius or HyperKitty) bug tracker on Launchpad, and we will both try > to help you through them and fix them. > > This is a major project and we are fewer than a dozen main contributers > to its development, and we are all volunteers who do this for our own > personal reasons, but not for money (most of us have day jobs; I'm > fortunate enough to be retired). We need your involvement to make this > successful. We welcome your help. > > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Thanks Mark. I will have my developer update Mailman 3 on my CentOS 6 server when I come back from vacation. I will then do some thorough testing and post my findings to this list. Brian Carpenter EMWD.com From mark at msapiro.net Thu Apr 30 05:53:11 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 29 Apr 2015 20:53:11 -0700 Subject: [Mailman-Developers] mailman 3.0 roadmap, feature-parity with mailman 2.x and documentation In-Reply-To: <4acb01d082f8$1466dc10$3d349430$@emwd.com> References: <553FE3BF.10203@hamaralinux.org> <20150428190310.225615af@limelight.wooz.org> <3d3101d0828d$9dab1920$d9014b60$@emwd.com> <45d001d082ba$b97ded30$2c79c790$@emwd.com> <55418898.80703@msapiro.net> <4acb01d082f8$1466dc10$3d349430$@emwd.com> Message-ID: <5541A727.7000907@msapiro.net> On 04/29/2015 08:45 PM, Brian Carpenter wrote: >> >> On 04/29/2015 01:26 PM, Brian Carpenter wrote: >>> >>> Is there a recommended server environment to run Mailman 3? >> >> >> It should install and run on any *nix server that supports both Python >> 2.7 and Python 3.0 That's wrong. I was conflating Mailman and Python Releases. Mailman 3.0 nominally requires Python 2.7 and Python 3.4. It may run with earlier Python 3.x releases, but no guarantees and probably not as old as 3.0 or even 3.1 in any case. > Thanks Mark. I will have my developer update Mailman 3 on my CentOS 6 server > when I come back from vacation. I will then do some thorough testing and > post my findings to this list. Thank you. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From alangiderick at gmail.com Thu Apr 30 12:05:24 2015 From: alangiderick at gmail.com (Alangi Derick) Date: Thu, 30 Apr 2015 11:05:24 +0100 Subject: [Mailman-Developers] Congratulations to selected GSoCers Message-ID: Hello, I just want to cease this opportunity and congratulate all selected GSoCers for this organisation this year 2015. Not with standing, i will like to contribute to this organisation, with or without GSoC. So i want to start from now so i can get myself familiar with the code base and start fixing bugs and writing patches. Regards Alangi Derick Ndimnain