[Mailman-Developers] The full Mailman 3 suite is now on GitLab

Hi everyone. Through Abhilash's diligent work, we've finally brought all Mailman 3 development under one group on GitLab. https://gitlab.com/groups/mailman This includes the Core, Postorius, HyperKitty, the client library, the bundler, Postorius-standalone, documentation, and even the soon-to-be

Re: [Mailman-Developers] Recipient address rejected: User unknown in virtual alias table

On May 30, 2015, at 12:58 AM, Danil Smirnov wrote: >Now I have working Postorius and I can subscribe myself to the test >list and get the welcome message (with incorrect urls in it!). Known bug! The default templates actually need to be updated to not include those urls, because the core doesn't

Re: [Mailman-Developers] [Project Discussion] Assigining Default Priority levels to user tasks

On May 24, 2015, at 01:43 AM, Bhavesh Goyal wrote: >Whenever a new task gets added automatically ( when someone makes a >subscription request for instance), what priority level should it be >assigned. ? Perhaps that should be configurable? As a list administrator, I might prefer to handle subscr

Re: [Mailman-Developers] MM3 install on RHEL 5.11

On May 28, 2015, at 11:13 AM, bill.co...@unh.edu wrote: >Well a former boss had a saying that I've taken to heart. "Don't >be first. Don't be last." Are there *any* production MM 3 sites >up at this point? There are, but I don't know if there are many *public* sites yet. I'm hoping we can fix

Re: [Mailman-Developers] mailman 3 and mysql

On May 27, 2015, at 04:49 PM, Danil Smirnov wrote: >1) Does this also relate to Postorius and HyperKitty db configuration >set in file production.py? Can I use MySQL for them?.. Others can provide more detailed answers but it might be a good idea to keep all three components in the same database.

Re: [Mailman-Developers] mailman 3 and mysql

On May 27, 2015, at 03:39 PM, Danil Smirnov wrote: >As I see on page >https://pythonhosted.org/mailman/src/mailman/docs/DATABASE.html > >Mailman 3 should work with MySQL/MariaDB database. Well, that page is careful to say that SQLAlchemy, the ORM layer we use, is compatible with MySQL, but it doe

Re: [Mailman-Developers] [Project Discussion] Approach for Implementing Admin Tasks

On May 26, 2015, at 01:26 PM, Stephen J. Turnbull wrote: >I really think we should reserve 3.1 for fixing major problems (and I expect >to have a lot of user-noticable problems, starting with lots of Mailman 2 >functionality that went unimplemented for one reason or another). +1. I do intend to

Re: [Mailman-Developers] [Project Discussion] Approach for Implementing Admin Tasks

On May 25, 2015, at 05:27 PM, Abhilash Raj wrote: >I think a better idea would be to keep everything in Postorius. Held messages >and subscription requests are already available through the REST API, and >hence can easily be used to create the `Tasks` model in Postorius. Barry, >Florian thoughts?

Re: [Mailman-Developers] [GSoc Project] Error Creating a New Model for The Database

On May 16, 2015, at 08:05 PM, Bhavesh Goyal wrote: >What can it be that I may be missing which is preventing me to query the >table. Really desperate for any hep on this :) Thanks... Can you post a link to the branch? Cheers, -Barry ___ Mailman-Develop

Re: [Mailman-Developers] Storing extra data during pipeline processing

On May 07, 2015, at 10:51 PM, Juraj Variny wrote: >I have tried already to use msgdata parameter or adding headers to message >itself, but was not successful so far. I was thinking about adding external >database and putting the data there by message ID, but sure there must be a >better way? I hop

[Mailman-Developers] Moving to git and gitlab

With the release of Mailman 3.0, it's time to take a look at our project management, with an eye toward making it easier for core developers, easier for non-core contributors, and providing improved quality, all while staying true to the GNU project's principles. There's a lot to like about Bazaar

[Mailman-Developers] Please consider donating to the GNU Mailman project

I should have included this in our release announcement. I'd like to remind everyone that GNU Mailman has a directed donation fund set up at the Free Software Foundation. Please consider donating! http://wiki.list.org/x/4816967 This year, we used a portion of our fund to sponsor Abhilash coming

Re: [Mailman-Developers] mailman 3.0 roadmap, feature-parity with mailman 2.x and documentation

On Apr 29, 2015, at 08:53 PM, Mark Sapiro wrote: >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. Nobody

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,

[Mailman-Developers] ANNOUNCING: GNU Mailman 3.0

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 fo

Re: [Mailman-Developers] Welcome to GSoC 2015

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: St

Re: [Mailman-Developers] [Bug 1414154] Re: switch to external translation system

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

Re: [Mailman-Developers] Mailman 3 discussion

On Apr 20, 2015, at 10:41 PM, Danil Smirnov wrote: >Look at this please: >http://dpaste.com/3N8ABXY Darn, that expired. Cheers, -Barry ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-de

Re: [Mailman-Developers] Mailman 3 discussion

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 looki

Re: [Mailman-Developers] Small change to REST API for held subscription requests

On Mar 21, 2015, at 09:32 PM, Barry Warsaw wrote: >I want to make some minor backward incompatible changes to the JSON >representation for pending mailing lists requests, e.g. subscription holds. > >The first change is that `type: subscription` requests will change their >`address

Re: [Mailman-Developers] Fine grained subscription control, scaling, noise, relevancy, subscription rules, dynamic lists

On Mar 20, 2015, at 09:53 AM, Andrew Stuart wrote: >The systers have recognised this problem and their solution is Dynamic >sublists And we may have a GSoC on dlists. I think Systers is pretty happy with dlist functionality, but it'll be interesting to see how it works as a more general feature.

Re: [Mailman-Developers] Getting "approval" to go ahead

On Mar 25, 2015, at 01:02 PM, Stephen J. Turnbull wrote: >(1) Suppose you change a small function whose formatting is not PEP 8 >conformant (or otherwise so ugly you can't help fixing it -- of >course, check "blame" first, if Barry committed those lines, have >your eyes checked instead

Re: [Mailman-Developers] Common use case archiving via configuration

On Mar 25, 2015, at 01:07 PM, Stephen J. Turnbull wrote: >A nice option would be that in the admin interface, the admin could >tick a box saying "show me contrib archivers" and then tick and >configure the appropriate one. The instructions for contrib >configurations would say that Mailman is not

Re: [Mailman-Developers] Common use case archiving via configuration

On Mar 24, 2015, at 05:01 PM, Andrew Stuart wrote: >@barry - would you mind confirming please you’re OK with this please? These are all pretty interesting. We'd have to think about whether we'd want some, any, or all them in the main tree, which essentially means we're committing to supporting t

Re: [Mailman-Developers] Small change to REST API for held subscription requests

On Mar 23, 2015, at 08:39 PM, Andrew Stuart wrote: >Any thoughts on how we could integrate with LDAP? The intent is that the user database could be backed by, or augmented by LDAP, although that is currently a goal, not reality. >Maybe of Mailman had some sort of event notification hook system f

Re: [Mailman-Developers] Getting "approval" to go ahead

On Mar 24, 2015, at 02:38 PM, Andrew Stuart wrote: >I haven’t really worked on an open source project before. You're fitting right in though! :) >It wouldn’t make sense to come up with an idea, write some code, submit it >and have it rejected because it’s not OK with the project owners and doesn

Re: [Mailman-Developers] How do I turn on/off moderation of subscription requests?

On Mar 23, 2015, at 12:17 PM, Aurelien Bompard wrote: >But there's something else: the SubscriptionWorkflow class does not seem to >be used anywhere except in the current unit test. Am I missing something ? Nope. It needs to be hooked up. The branch wasn't merged because it was incomplete. Che

Re: [Mailman-Developers] Small change to REST API for held subscription requests

On Mar 23, 2015, at 09:34 AM, Andrew Stuart wrote: >How would user passwords work if not stored in the core? > >When someone logs in currently I just ask the core if the password is valid >and off we go. WFM. As I said, the core doesn't (currently) use it, but certainly it's available through th

Re: [Mailman-Developers] Small change to REST API for held subscription requests

On Mar 22, 2015, at 09:55 PM, Florian Fuchs wrote: >As for the `password` key: It's recognized by mailman.client and >exposed within the mlist instance's `requests` property. But it's used >nowhere in postorius and I would be surprised if it's used anywhere in >hyperkitty (Aurélien...?). I guess i

[Mailman-Developers] Small change to REST API for held subscription requests

I want to make some minor backward incompatible changes to the JSON representation for pending mailing lists requests, e.g. subscription holds. You'll see these for example in urls like: >>> dump_json('http://localhost:9001/3.0/lists/a...@example.com/requests') entry 0: delivery_mo

Re: [Mailman-Developers] How do I turn on/off moderation of subscription requests?

On Mar 21, 2015, at 10:50 AM, Aurelien Bompard wrote: >Hmm, could you point me to this Dia file please, I can't find it. Thanks! Oops. Looks like I'd forgotten to push them. They should now be available in lp:~barry/mailman/subpolicy Cheers, -Barry pgpUyR2fuW394.pgp Description: OpenPGP digi

Re: [Mailman-Developers] Regarding Subscriber profile pages project

On Mar 17, 2015, at 10:36 PM, Ashish Kumar wrote: >1. Use of different email addresses - so called aliases - for sending >emails Mailman 3's model is that users can have one or more addresses linked to their record, and can specific a preferred address. You can subscribe to a mailing list with a

Re: [Mailman-Developers] GSOC'15: Improving styles for lists

On Mar 19, 2015, at 03:31 PM, Stephen J. Turnbull wrote: >Also, I suspect it would be useful to allow very incomplete templates so that >you could apply template A to get the basic character, then apply template B >(which is very incomplete and only changes two attributes) to get the effect >you w

Re: [Mailman-Developers] How do I turn on/off moderation of subscription requests?

On Mar 20, 2015, at 04:39 PM, Aurelien Bompard wrote: >Alright, I resurrected your branch to the best of my understanding. I hope >it's more Lazarus than Reanimator. > > https://code.launchpad.net/~abompard/mailman/subpolicy > >All tests pass, but there's still a missing part: the new attribute i

Re: [Mailman-Developers] [Fwd: Re: Discussion about Mailman plugins(GSOC 2015)]

On Mar 20, 2015, at 12:35 PM, Aanand Shekhar Roy wrote: >I wonder if we could add our modules of plugin to the var/ext( which is built >for plug-ins), and then importing those modules(i.e. handlers ,rules etc) to >the config.py using python imports, by doing this we wont have to add our >modules t

Re: [Mailman-Developers] [Bug 1418276] Re: Deleting a user via the REST API does not delete their user preferences

On Mar 20, 2015, at 05:41 PM, Abhishek wrote: >In rest/tests/test_users.py you have used >config.db.store.query(Preferences) inside with. But there is another >usage of it in line 221 and also in the file model/tests/test_user.py >which are not inside with block. Any specific reason for the >diffe

Re: [Mailman-Developers] Unofficial git mirror of GNU Mailman 3

On Mar 18, 2015, at 05:34 PM, Aamir Khan wrote: >It seems gitorious has been recently acquired by gitlab and would be >shutting down by May[1]. How about setting a read-only mirror on github >instead? > >[1] https://about.gitlab.com/2015/03/03/gitlab-acquires-gitorious/ Not github, gitlab please.

[Mailman-Developers] Some bare minimums for submitting patches (GSoC students take note)

A quick note for GSoC students, although this can apply to anyone submitting merge proposals to the core. You really need to run the test suite before submitting your branch. If the test suite fails, I am going to mark your branch 'needs fixing' and move on. Of course, ideally your branch would

Re: [Mailman-Developers] Discussion about Mailman plugins(GSOC 2015)

On Mar 05, 2015, at 03:09 PM, Stephen J. Turnbull wrote: >I'm really having trouble with this interest in "plugins" as opposed >to "rules for chains" and "handlers for pipelines". To install a rule >or handler is a three-step process done by the site administrator: > >1. Write or download a modul

Re: [Mailman-Developers] How do I turn on/off moderation of subscription requests?

On Mar 07, 2015, at 07:24 AM, Andrew Stuart wrote: >I also found a message from you in Dec 2014 (can’t find it now after a few >minutes digging….ugh) saying that currently it’s not possible to create lists >via the REST API that require moderator approval to subscribe. I think it >refered to the

Re: [Mailman-Developers] Fast development environment setup for newbies using mmdev_bootstrap

On Mar 11, 2015, at 04:21 AM, Ankush Sharma wrote: >The newbies starting to contribute to mailman sometimes face difficulty in >setting up the dev environment for Mailman. Just a quick bzr hint in case folks are unaware: I create all my branches in a "shared repo". This is basically a parent dir

Re: [Mailman-Developers] [Queries] Related to list styles.

On Mar 13, 2015, at 01:23 PM, prakhar joshi wrote: >I have some queries related to project for GSOC'15 named "Improving list >styles" , as I have seen right now styles have been dependent on zope >interface. So do we have to remove the zope dependencies ? or We have to work >around to make a UI th

Re: [Mailman-Developers] Query regarding ambiguous behavior of REST API due to case-sensitivity of email addresses

On Mar 03, 2015, at 02:15 PM, Ankush Sharma wrote: >> 2. Later on, in the same function the following code checks if the email >> is matched: >> >> *for address in user.addresses:* >> *if address.email == email:* >> * break* >> >> Here *email* is in *preserved case* w

Re: [Mailman-Developers] Error while setting up Mailman

On Mar 03, 2015, at 04:20 AM, Akash Agrawall wrote: >I am new to Mailman. I followed " >http://wiki.list.org/DEV/A%205%20minute%20guide%20to%20get%20the%20Mailman%20web%20UI%20running >" to set-up Mailman. >When I run the command "sudo python3.4 setup.py install" I get the error " >http://pastebin

Re: [Mailman-Developers] GSoC 2015: We're in...

On Mar 02, 2015, at 10:35 PM, Florian Fuchs wrote: >just a quick FYI: Mailman has been accepted into GSoC 2015. \o/ Thanks >to everyone who contributed ideas and/or helped with wiki gardening! Really fantastic news! Thanks everyone who has participated so far, and I'm looking forward to a great

Re: [Mailman-Developers] MIME footers

On Feb 27, 2015, at 11:46 AM, Murray S. Kucherawy wrote: >How absurd would it be to propose a flag for Mailman that would take your >first case (non-MIME, or single-part text/plain) and convert it to a >multipart/mixed with a child part of the original text/plain, and then >apply the algorithm you

Re: [Mailman-Developers] GSoC 2015: brainstorming ideas suitable for beginners?

On Feb 27, 2015, at 01:02 PM, Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA wrote: >A personalized mailing list will allow mailman users to send personalized >emails to all the list members from a common email template. Almost all the pieces are already there to suppor

Re: [Mailman-Developers] GSoC 2015: brainstorming ideas suitable for beginners?

On Feb 25, 2015, at 04:12 PM, Andrew Stuart wrote: >I’m looking forward to being able to set and get domainowner and serverowner >(or siteowner or whatever its called). It will allow me to delete lots of >code and there’s no greater joy than deleting code. > >Are you anticipating this will be in V

Re: [Mailman-Developers] Ideas for injecting test messages

On Feb 25, 2015, at 09:28 AM, Sumana Harihareswara wrote: >Andrew is using the list properly. I agree. Frankly, I'm a bit jealous that he gets to spend all his time on Mailman. :) I don't mind answering good questions here, and I welcome the interesting discussions on this list. Just please be

Re: [Mailman-Developers] Ideas for injecting test messages

On Feb 25, 2015, at 10:04 AM, Andrew Stuart wrote: >I want to inject some test messages into Mailman to test moderation functions >via the REST API. > >Any ideas on a simple way to do that? I think you found the command line interface for injecting messages, but you can also do it via the REST AP

Re: [Mailman-Developers] GSoC 2015: brainstorming ideas suitable for beginners?

On Feb 24, 2015, at 07:53 AM, Chris Nulk wrote: >Also, I believe I remember a goal for Mailman v3 was to have one instance of >Mailman be able to host lists for multiple domains. Yes, but not on physically distinct hosts. Or in other words, yes MM3 supports virtual domains >Given that informati

Re: [Mailman-Developers] Auth databases redux [was: GSoC 2015: brainstorming ... beginners?]

On Feb 23, 2015, at 09:10 AM, Andrew Stuart wrote: >The two things that I’ve suggested might be worth including in the core are >hopefully of broad value and not specific only to what I’m doing. (rounding >out the permissions, with serverowner and domainowner, including an >application data table

Re: [Mailman-Developers] GSoC 2015: brainstorming ideas suitable for beginners?

On Feb 20, 2015, at 07:25 PM, Andrew Stuart wrote: >It’s workable as a part of the auth proxy but feels like it would fit better >in the Mailman core database since the data is so tightly bound to Mailman >resources. It’ll need an effective replication mechanism to ensure >consistency with Mailma

Re: [Mailman-Developers] REST API PUT versus PATCH - is there in any point in PUT and PATCH?

On Feb 19, 2015, at 08:10 AM, Andrew Stuart wrote: >Is there any actual benefit in those PUT methods? I can’t see what they >offer over the PATCH methods. PUT is defined in HTTP/1.1. PATCH is (only) defined in RFC 5789, so it may not be universally supported. E.g. back in the restish days, I h

Re: [Mailman-Developers] GSoC 2015: brainstorming ideas suitable for beginners?

On Feb 18, 2015, at 12:24 AM, Abhilash Raj wrote: >How about domain-wide settings for default list styles or maybe set a >default list style for an entire mailman installation through Postorius? >That could make the work of list-admins easy if they manage too many >lists and don't want to do repet

Re: [Mailman-Developers] Soliciting feedback on idea for rounding out the permissions model.

On Feb 17, 2015, at 01:36 PM, Stephen J. Turnbull wrote: > > As you've noticed, we have IMember objects which encapsulate the > > list-centric roles for users. It's important to note though that > > this isn't quite complete because it's possible for validated, > > non-user linked addresses to al

Re: [Mailman-Developers] Soliciting feedback on idea for rounding out the permissions model.

On Feb 17, 2015, at 12:37 PM, Andrew Stuart wrote: >I figured that an archive, which isn’t really a Mailman resource anyway(?), >has the same permissions as the list that it gets its emails from. I think so. The owner of the mailing list has authoritative control over which archivers are enabled

Re: [Mailman-Developers] Soliciting feedback on idea for rounding out the permissions model.

This looks like a reasonable analysis. On Feb 16, 2015, at 11:39 AM, Andrew Stuart wrote: >To implement, it would need to be possible to define as user as being a >‘serverowner’, and also to be able to define a user as being a ‘domainowner’ >for any given domain. As you've noticed, we have IMemb

Re: [Mailman-Developers] fqdn_listname - is it strict in what type of input it accepts?

On Feb 17, 2015, at 11:48 AM, Andrew Stuart wrote: >As I understand it, fqdn_listname is effectively the email address of a >mailing list. i.e. testl...@example.org > >The RFC 2369 list-id is the same thing but with a dot instead of an @ >symbol. i.e. testlist.example.org List-ID is actually defi

Re: [Mailman-Developers] A couple of archiving questions

On Feb 16, 2015, at 10:11 PM, Andrew Stuart wrote: >Can there only be one active archiver or multiple? There are no limits on the number of IArchive implementations that can be registered with the system. Mailing lists themselves can enable any or all of the archivers registered with the system.

Re: [Mailman-Developers] A couple of archiving questions

On Feb 16, 2015, at 06:57 PM, Stephen J. Turnbull wrote: >It's no harder than that to write a Handler in Mailman 2, and IIRC the >additional burden (adding the message-id-hash) in Mailman 3 is >elsewhere in the pipeline. Here's the whole thing for MM 2: It's a little different in Mailman 3 becau

Re: [Mailman-Developers] A couple of archiving questions

Steve's explained most of the current thinking on archiving, and as you observe, archiving is a push interface (from Mailman to the archivers). At one point I thought about having a sort of built-in archiver that wasn't any smarter than just an maildir or some other dump on-disk dump. Mailman 2 h

Re: [Mailman-Developers] A couple of archiving questions

On Feb 16, 2015, at 05:01 AM, Pranjal Yadav wrote: >So it should be possible to choose one (or more) of them in postorius. In >/mailman/src/mailman/archiving/docs/common.rst ; It says we have Mail-Archive >and MHonArc archivers available however there are some issues with the >non-public lists.

Re: [Mailman-Developers] Is there a way to get member id via REST API?

On Feb 14, 2015, at 09:43 AM, Andrew Stuart wrote: >GET /addresses/{email}/memberships >GET /members > >Both seem to return member id in self_link but I can’t see it elsewhere. > >Anywhere I can get member id without parsing it out of the self_link? Maybe >I’m not looking in the right place. Nope

Re: [Mailman-Developers] Question about member role and PATCH /members/{id}

On Feb 14, 2015, at 09:08 AM, Andrew Stuart wrote: >When a user is subscribed to a list, they can be assigned a role, one of >member, owner, moderator nonmember. > >The PATCH /members/{id} method does not allow changes to the role and >display_name. > >I’m just wondering what the thinking is behin

Re: [Mailman-Developers] Don't trust X-No-Archive to keep your secrets.

On Feb 12, 2015, at 12:50 PM, J.B. Nicholson-Owens wrote: >I believe this is the case for two reasons: >1. Structurally: Few search engine companies will throw away an opportunity >to collect data when there's so much for that organization to gain by >indexing that data. > >2. Specific to Google:

Re: [Mailman-Developers] Support for X-No-Archive

On Feb 12, 2015, at 01:42 AM, Mark Sapiro wrote: >apparently does occur in the wild, if we can confirm that the semantics >of this should be 'do archive', file a bug and I'll fix it. It's been ages, but IIRC the reason for accepting any value is exactly because of the double negative. People had

Re: [Mailman-Developers] Date normalization - opinions sought

On Feb 12, 2015, at 11:09 PM, Andrew Stuart wrote: >Does Mailman normalize dates on emails to UTC? I'm not sure which dates you mean. Are you asking whether Mailman should modify the Date header on emails? Definitely not. :) Ideally I do think any internal dates gathered from external sources

Re: [Mailman-Developers] When a user is deleted, is the uid record intentionally not deleted?

On Feb 10, 2015, at 02:04 PM, Andrew Stuart wrote: >Sounds good to me. Another thought: https://bugs.launchpad.net/mailman/+bug/1420083 Feel free to comment on the bug, instead of here. Cheers, -Barry ___ Mailman-Developers mailing list Mailman-Devel

Re: [Mailman-Developers] User id - integer or UUID?

On Feb 02, 2015, at 10:04 AM, Andrew Stuart wrote: >The other possibility, distasteful as it may be, is to make the changes to >publish the UUID to the REST API and deprecate the use of the user_id as >integer. I suggest this because others who come after me will have the same >question and may ru

Re: [Mailman-Developers] When a user is deleted, is the uid record intentionally not deleted?

On Feb 06, 2015, at 04:17 PM, Andrew Stuart wrote: >Yes it’s a tough question. I agree with leaving the uid records in the >database to prevent reuse. You are correct my test code is exercising a full >working system. It would be good if my tests could leave the database in the >same state after

Re: [Mailman-Developers] /3.0/addresses/c...@example.com/user' - multi purpose REST API method

On Feb 08, 2015, at 12:28 AM, Andrew Stuart wrote: >TLDR - This API methods does multiple things and depends on information apart >from the URL to define its behaviour mode, making it hard to give a clear >authentication scope to. I wonder if it should be broken out into individual >REST API metho

Re: [Mailman-Developers] [Mailman-Announce] Announcing the new wiki.list.org

On Feb 09, 2015, at 02:07 PM, Barry Warsaw wrote: >If I had to be picky, I'd probably suggest scaling down the upper right logo, >so that the top and side bars can be a bit narrower. In comparison to >www.list.org, the wiki logo seems larger, and thus the navbars seem out of >

Re: [Mailman-Developers] Announcing the new wiki.list.org

On Feb 09, 2015, at 02:45 PM, Mark Sapiro wrote: >Shall we go ahead and make it the default theme for new users? +1 -Barry ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mai

Re: [Mailman-Developers] [Mailman-Announce] Announcing the new wiki.list.org

On Feb 08, 2015, at 12:59 PM, Jim Tittsler wrote: >I've derived a simple brown theme from "modern" that looks more like >list.org, but with a couple of intentional deviations (maximum line >widths, and no underlining of links unless you hover). Great job, I like it a lot! If I had to be picky, I

Re: [Mailman-Developers] REST API delete user function does not delete every 2nd linked address

On Feb 09, 2015, at 07:06 AM, Andrew Stuart wrote: >This appears to fix the problme in rest/users.py > >def on_delete(self, request, response): >"""Delete the named user, all her memberships, and addresses.""" >if self._user is None: >not_found(response) >

Re: [Mailman-Developers] When a user is deleted, is the uid record intentionally not deleted?

On Feb 05, 2015, at 10:53 AM, Andrew Stuart wrote: >I notice that when a user is deleted, the uid record remains. > >Is this because there is a bug in which the uid should be deleted but is not? > >or is this intentional behaviour to prevent the uid from being recreated as a >duplicate? > >My test

Re: [Mailman-Developers] Is there a way to delete an unlinked/orphaned address via the REST API?

On Feb 05, 2015, at 11:55 AM, Andrew Stuart wrote: >After unlinking an address from a user, there is an address in the addresses >table that is orphaned - i.e. it does not have a linked user. This is the >expected behaviour (I think) - that’s fine, no problems at this point. Correct. >However, I

Re: [Mailman-Developers] "Address already exists" when creating users, but it creates a new user anyway

On Feb 05, 2015, at 09:32 AM, Andrew Stuart wrote: >After a bit of deep cave diving into the code I suspect it’s this in >model/usermanager.py You're exactly right. Thanks for filing LP: #1418280. I'll commit your fix along with some new tests. Cheers, -Barry __

Re: [Mailman-Developers] Security - XSS JavaScript and SQL injection in Mailman, Postorius and Hyperkitty

On Feb 06, 2015, at 09:22 AM, Andrew Stuart wrote: >Does the code of Mailman 3, Hyperkitty and Postorius do anything to address >concerns around SQL and JavaScript injections, either from inbound emails or >via the fields coming in via web interface or REST API? The core does not. It doesn't exp

Re: [Mailman-Developers] "Address already exists" when creating users, but it creates a new user anyway

Hi Andrew, Thanks for the detailed response. I'll try to find some time tonight to go through your recipe step-by-step. Some questions in the meantime: On Feb 04, 2015, at 09:26 PM, Andrew Stuart wrote: >For a clean start I deleted my Mailman 3 installation. I downloaded the >latest version a

Re: [Mailman-Developers] User id - integer or UUID?

On Feb 01, 2015, at 11:54 AM, Andrew Stuart wrote: >I’m going to store as string representation of the integer as I don’t want to >be dealing with databases or anything else that makes a distinction between >different types and lengths of integer. That makes sense to me. Since Aurelien was okay

Re: [Mailman-Developers] "Address already exists" when creating users, but it creates a new user anyway

On Feb 01, 2015, at 07:23 PM, Andrew Stuart wrote: >In the commands below you can see that I start by getting a list of users, it >returns "total_size": 1 How was this user created and with what email address? >I then execute a POST to the REST API multiple times. Each time it says >“Address al

Re: [Mailman-Developers] Launch band & song

On Jan 31, 2015, at 07:38 AM, Andrew Stuart wrote: >If you are thinking of launching at Pycon, what do you think of the idea of >playing some music - you’re a guitarist right? Bass player, as is Florian! (Now can you guess the origin of the name Postorius? :). I can hack out some bar chords tho

Re: [Mailman-Developers] Announcing the new wiki.list.org

On Jan 27, 2015, at 11:27 AM, Mark Sapiro wrote: >See to start. There may be something >in the ThemeMarket that's good, e.g. maybe > with just a change in color >would be a lot closer to as a starti

Re: [Mailman-Developers] [Mailman-Announce] Announcing the new wiki.list.org

On Jan 26, 2015, at 10:10 AM, Barry Warsaw wrote: >If you had write access to the old wiki and want it again for the new wiki, >you will have to re-submit a request to mailman-ca...@python.org. Please be >sure to register with wiki.list.org and provide us with your user name. Paul r

[Mailman-Developers] Announcing the new wiki.list.org

I am very happy to announce our new wiki! If you go to wiki.list.org you will see our shiny new Moin-based wiki. We are retiring the old Confluence-based wiki at the end of February. Until then, you can access it at old-wiki.list.org. Our very huge thanks go to Paul Boddie who did the amazing c

Re: [Mailman-Developers] Who is the "site administrator"?

On Jan 24, 2015, at 04:05 PM, Andrew Stuart wrote: >The main thing I’m looking for is whether there is an authorisation concept >that operates at a higher level than the list. No, there isn't[*]. >I wonder is there the concept of some sort of “special” mailing list that is >different or hidden o

Re: [Mailman-Developers] Introductory mail

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

Re: [Mailman-Developers] How can I run the REST tests against live servers?

On Jan 22, 2015, at 12:02 AM, Andrew Stuart wrote: >Barry - would you like the authenticating proxy to be part of Mailman core or >a third party project? For now, I think it should not be distributed as part of core. Maybe after the 3.0 release. The code could still be donated to the FSF and ma

Re: [Mailman-Developers] REST API first pass at Swagger spec

On Jan 12, 2015, at 12:47 PM, Andrew Stuart wrote: >I’m not a fan of integrating the Swagger specification into the code - seems >to make for a VERY large amount of work, a huge amount of complexity and >massive potential for introduction of bugs. Agreed. >I’ve taken the approach of a single sta

Re: [Mailman-Developers] installation problems blocking a new developer

On Jan 20, 2015, at 11:38 AM, Sumana Harihareswara wrote: >https://bugs.launchpad.net/mailman/+bug/1411435 >after initial install, master runner crashes when config file is missing This is fixed in trunk now! Cheers, -Barry ___ Mailman-Developers maili

Re: [Mailman-Developers] Your confirmation is required to leave the Mailman-Developers mailing list

On Jan 14, 2015, at 11:00 PM, Stephen J. Turnbull wrote: >It could try, but it wouldn't be 100% successful, and it would surely >break DKIM signatures. A third-party add-on, sure. A Mailman >feature, I'm -1 on that. Right. I don't think it's a good idea for Mailman to attempt to strip body con

Re: [Mailman-Developers] REST API returns are plain text for errors, JSON or nothing for successful

On Jan 11, 2015, at 06:23 AM, Andrew Stuart wrote: >Happy to do so if you like. Would you mind pointing me in the direction of >some instructions for filing bugs please? > >FWIW I’d probably favor a REST API that is behaving improperly by returning >plain text error responses (i.e. the current si

Re: [Mailman-Developers] REST API first pass at Swagger spec

On Jan 11, 2015, at 08:51 AM, Andrew Stuart wrote: >Attached is a first pass at a Swagger spec for the REST API. > >You can find out about Swagger at http://swagger.io > >The Swagger spec that I am working on is attached to this message or can be >found here: http://www.mailripper.com/api-docs.jso

Re: [Mailman-Developers] REST API returns are plain text for errors, JSON or nothing for successful

On Jan 11, 2015, at 06:06 AM, Andrew Stuart wrote: >I don’t think it’s a big deal in the short term because the plain text error >message can easily be read from the response. > >The only thing that’s somewhat odd is that the content-type is >application/json even though the content isn’t (for err

Re: [Mailman-Developers] REST API returns are plain text for errors, JSON or nothing for successful

On Jan 10, 2015, at 03:42 PM, Andrew Stuart wrote: >Successful requests to the REST API return a 2xx HTTP code to indicate >success either with or without JSON data depending on the context of the >request. > >At least one (I’ve not checked the othes yet) 4xx error returned from the >REST API retu

Re: [Mailman-Developers] REST API returning value of password field in user record

On Jan 10, 2015, at 01:57 PM, Stephen J. Turnbull wrote: >In the long run we need to do something about this. However, Mailman >has operated based on passing around *cleartext* passwords by *email* >for decades, with no serious issues that I know of. Just to be, ahem, clear, by default MM3 does

Re: [Mailman-Developers] REST API returning etags as slashed quoted

On Jan 10, 2015, at 10:52 AM, Andrew Stuart wrote: >The REST API is returning etags as slashed quoted. > >Just wondering if this is intentional, does not seem consistent with the >behaviour of the other fields returned from the API. > >i.e. > >"http_etag": "\"d6d174c76c5fbb5f8a69b648ecd3b27b53a5d2

Re: [Mailman-Developers] REST API returning value of password field in user record

On Jan 10, 2015, at 10:58 AM, Andrew Stuart wrote: >I’m aware that it’s not the actual cleartext password. > >From a security perspective should even salted and hashed passwords should >stay behind the API or might there be a need for something on the other side >of the API to access that field?

<    1   2   3   4   5   6   7   8   9   10   >