Mailman 3 January 2015 - Mailman-Developers

before next release: disable backscatter in default installation
by Jo Rhett Nov. 7, 2022

Nov. 7, 2022

Hi. There's a fairly simple problem here that needs to be addressed. And it's mostly a documentation/install problem. I'm hoping we can get this resolved before the next release. PROBLEM: Mailman comes out of the box ready to backscatter spam people. Yes, it's easy enough to fix. But because it comes stock this way, and is documented to install this way, most people install it to do this. Those of us who work in abuse departments are tired of hearing "well that's how Mailman … [View More]

21 168

Announcing the new wiki.list.org
by Barry Warsaw March 3, 2015

March 3, 2015

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 conversion work, almost single-handedly reverse engineering the Confluence dump through several iterations. Of course, our thanks also go to John Viega, owner of the list.org domain and Mailman's … [View More]

6 21

Adding CSS to mailman archives
by Andrew Daviel Feb. 13, 2015

Feb. 13, 2015

A little while ago (November 2012 probably) I changed a mailing list from Hypermail to Mailman and wanted to keep some of the look-and-feel of the archives, e.g. background colour and fonts. So I patched mailman 2.1.9 in CentOS 5 to include a CSS stylesheet link in each generated HTML page, replacing e.g. <BODY BGCOLOR="#ffffff"> with just <body> and adding e.g. body {background-color: #ffffff ; color: black; } in /pipermail/mailman.css, so that HTML style such as FONT and SIZE … [View More]

7 17

Signed Mailing Lists
by Abhilash Raj Jan. 30, 2015

Jan. 30, 2015

Hi all, I worked in GSoC 2013 (thanks to Steve and Barry!) to add support for verification and re-signing of emails in mailman3. I am working on the branch to rebase it with the recent changes in the trunk and make it ready to be merged. The reason for this post is to discuss about the current feature set and possible enhancements/changes to it (which probably was not included in my proposal due to time-limit of 3 months). * A new `signature` rule checks for validity and age of the signature … [View More]

1 0

Launch band & song
by Andrew Stuart Jan. 30, 2015

Jan. 30, 2015

Hey Barry If you are thinking of launching at Pycon, what do you think of the idea of playing some music - you’re a guitarist right? Maybe there could be “The Mailmen” - a Mailman band - if you can rope in some other musicians. Perhaps the song could be a play on Elton John’s “Rocket Man”. A bit of marketing theatre for the bloggers to post a Youtube video of. Would help to get the word out there about the launch. as

2 1

Mailman 2.1.19 release
by Mark Sapiro Jan. 30, 2015

Jan. 30, 2015

I am pleased to announce the first release candidate for Mailman 2.1.19. Python 2.4 is the minimum supported, but Python 2.7 is recommended. This release has several new features, some newly implemented and some backported from the now truly defunct 2.2 branch - there is nothing left in that branch that isn't in this release. There are also bug fixes. See the attached README for more details. Associated with those changes are many things that have i18n impacts including new and modified … [View More]

1 0

Who is the "site administrator"?
by Andrew Stuart Jan. 26, 2015

Jan. 26, 2015

Is this defined in any way? Is there any concept that a given Mailman user has “site admin rights”? Or is the concept of the “site administrator” not realised in the application and just considered to be someone with operating system level access to the system that Mailman is running on? thanks

5 12

TODOs for Mailman suite 3.0, PyCon sprint plans
by Sumana Harihareswara Jan. 25, 2015

Jan. 25, 2015

I chatted with Barry a few days ago to clarify what we need to do if we want to release the Mailman suite, version 3.0, at the end of the PyCon sprints. The sprints are April 13th-16th, 11 weeks from now. I used what he said to update the TODO list for Mailman core, the client, Postorius, HyperKitty, the bundler, and the suite as a whole: http://wiki.mailman.psf.io/DEV/Mailman%203.0 If there are pieces that we ought to finish when we're together in person, maybe they ought to go here: http://… [View More]

1 0

Heads up on pending Mailman 2.1.19 release
by Mark Sapiro Jan. 24, 2015

Jan. 24, 2015

I will soon be packaging and announcing the first release candidate for Mailman 2.1.19. The details of changes since the 2.1.18-1 release are in the attached README. The reason for this heads up is there are many things in this release that have i18n impacts and I want to give as much notice as possible of these changes so that people who are interested in updating templates and the message catalogs for a particular language can hopefully get their changes in in time for the final release. If … [View More]

1 0

How can I run the REST tests against live servers?
by Andrew Stuart Jan. 24, 2015

Jan. 24, 2015

I want to run the REST tests against my live Mailman server with its Postfix mail server and Postgres database, via: nose2 -v -P rest After many (many) hours of digging deep and figuring out how it works, I suspect at this stage that maybe the tests set up their own mock servers? If so, I’m guessing these mock servers are getting in the way of using the live servers and thus preventing the tests from running? Assuming it is correct that the tests are setting up their own mock http smtp … [View More]

3 12

Introductory mail
by Stephen J. Turnbull Jan. 24, 2015

Jan. 24, 2015

Pranjal Yadav writes: > I also learned about previous year's GSOC project and I > can see mailman core is already ported to ver 3.4 however potorius > / hyperkitty / mailman.client needs to be done. Also test suite > would be interesting work to couple with all this. I would like to > know if these 2 projects can be coupled for this year's work or > not? If you think of them as two projects, then they probably are. As a mentor, I won't touch that -- most … [View More]

1 0

Re: [Mailman-Developers] Introductory mail
by Barry Warsaw Jan. 23, 2015

Jan. 23, 2015

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

1 0

Re: [Mailman-Developers] Introductory mail
by Abhilash Raj Jan. 23, 2015

Jan. 23, 2015

Hi Pranjal! On Thursday 22 January 2015 12:58 PM, Pranjal Yadav wrote: > Hello > > I'm a programming enthusiast and recently started working in > python about 6 months back, I have had experience in cryptography and many > machine learning techniques. I started reading about mailman few weeks back > and I have setup a local and server dev env successfully. > > I also learned about previous year's GSOC project and I can see > mailman core is already … [View More]

1 0

Re: [Mailman-Developers] Introductory mail
by Rajeev S Jan. 23, 2015

Jan. 23, 2015

On Thu, Jan 22, 2015 at 12:58 PM, Pranjal Yadav <godricglow(a)gmail.com> wrote: > Hello > > I'm a programming enthusiast and recently started working in > python about 6 months back, I have had experience in cryptography and many > machine learning techniques. I started reading about mailman few weeks back > and I have setup a local and server dev env successfully. > > I also learned about previous year's GSOC project and I can see > mailman … [View More]

1 0

Introductory mail
by Pranjal Yadav Jan. 22, 2015

Jan. 22, 2015

Hello I'm a programming enthusiast and recently started working in python about 6 months back, I have had experience in cryptography and many machine learning techniques. I started reading about mailman few weeks back and I have setup a local and server dev env successfully. I also learned about previous year's GSOC project and I can see mailman core is already ported to ver 3.4 however potorius / hyperkitty / mailman.client needs to be done. Also test suite would be … [View More]

1 0

REST API first pass at Swagger spec
by Andrew Stuart Jan. 20, 2015

Jan. 20, 2015

Attached is a first pass at a Swagger spec for the REST API. You can find out about Swagger at http://swagger.io The Swagger spec that I am working on is attached to this message or can be found here: http://www.mailripper.com/api-docs.json If you want to see the attached spec in action against the Mailman REST API, go to http://www.mailripper.com/swagger-ui/index.html Give it a try at http://www.mailripper.com/swagger-ui/index.html - you are welcome to change anything, it’s a test Mailman … [View More]

3 8

installation problems blocking a new developer
by Sumana Harihareswara Jan. 20, 2015

Jan. 20, 2015

Hi all! Thank you for your IRC help and for merging several of my patches. :) I'm running into installation problems with Mailman and mailman.client . The Mailman core one, I can work around, but the client bug is stopping me from getting a running dev environment so I can fix bugs in Postorius: https://bugs.launchpad.net/mailman/+bug/1411435 after initial install, master runner crashes when config file is missing https://bugs.launchpad.net/mailman.client/+bug/1411653 Installation fails … [View More]

4 3

Mailman user identification questions
by Andrew Stuart Jan. 19, 2015

Jan. 19, 2015

I am working on authenticating users, just want to clarify a few things in concrete. Does every Mailman user have a single, unique userid? Is a Mailman userid secret or public information - i.e. any reason not to use the userid in, for example, a cookie that is potentially public information? Is it possible to be a Mailman user WITHOUT having a related Mailman userid i.e. somehow you can use Mailman with an email address that has no corresponding Mailman userid? Do all email addresses map back … [View More]

1 0

Re: [Mailman-Developers] MM 3: Virtual Environment Required?
by Terri Oda Jan. 19, 2015

Jan. 19, 2015

On 2015-01-13, 1:35 PM, Tom Browder wrote: > I want to install, and use, MM 3. I'm on a single-user, Debian 7 > server, and control the whole thing. > > Is it important to use a virtual environment? I'm sure I will be > updating from the development branch until the stable release, and I > am prepared to have interruptions in service along the way. It *can* make your life easier if you're running multiple versions of python (which is why developers often like to use it) … [View More]

1 0

Re: [Mailman-Developers] MM 3: Virtual Environment Required?
by Abhilash Raj Jan. 17, 2015

Jan. 17, 2015

Hi Tom, On Wednesday 14 January 2015 03:05 AM, Tom Browder wrote: > I want to install, and use, MM 3. I'm on a single-user, Debian 7 > server, and control the whole thing. > > Is it important to use a virtual environment? I'm sure I will be > updating from the development branch until the stable release, and I > am prepared to have interruptions in service along the way. I don't think you would need a virtualenv unless you are developing mailman. You can simply download … [View More]

1 0

Fwd: Your confirmation is required to leave the Mailman-Developers mailing list
by Andrew Stuart Jan. 14, 2015

Jan. 14, 2015

errr…. is this someone saying they would prefer I wasn’t on this list? I’d rather hear directly from someone if you feel that way. Begin forwarded message: From: mailman-developers-confirm+e1a7bed1fbf00db07dc7590dcbdba1e364ecc240(a)python.org To: andrew.stuart(a)supercoders.com.au Subject: Your confirmation is required to leave the Mailman-Developers mailing list Reply-To: mailman-developers-confirm+e1a7bed1fbf00db07dc7590dcbdba1e364ecc240(a)python.org Date: 12 January 2015 1:23:31 pm AEDT … [View More]

5 5

MM 3: Virtual Environment Required?
by Tom Browder Jan. 13, 2015

Jan. 13, 2015

I want to install, and use, MM 3. I'm on a single-user, Debian 7 server, and control the whole thing. Is it important to use a virtual environment? I'm sure I will be updating from the development branch until the stable release, and I am prepared to have interruptions in service along the way. Note that I may eventually allow other users, but I will probably remain the supreme administrator. Thanks. -Tom

1 0

REST API returns are plain text for errors, JSON or nothing for successful
by Andrew Stuart Jan. 12, 2015

Jan. 12, 2015

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 returns a plain text error message rather than a JSON error message. For example attempting to create a domain that exists returns a 400 error with the response text “Domain exists”. Do you think this matters? Probably not much but does mean handling valid … [View More]

3 7

REST API returning value of password field in user record
by Andrew Stuart Jan. 10, 2015

Jan. 10, 2015

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? thanks

3 3

English in UTF-8 [was: Does mailman 2.1.18 support hebrew language ?]
by Stephen J. Turnbull Jan. 10, 2015

Jan. 10, 2015

On Mailman-Users, Mark Sapiro writes: > 3) You can set Mailman's character set for English to utf-8 by putting > > add_language('en', 'English (USA)', 'utf-8') > > in mm_cfg.py (and restarting Mailman). The downside of this is the > bodies of Mailman generated messages including plain digests will be > base64 encoded and will not be readable by non-MIME aware MUAs. Does Mailman 3/Python 3 have this limitation? (One of my MUAs is grep .... :-) Steve

2 2

REST API returning etags as slashed quoted
by Andrew Stuart Jan. 10, 2015

Jan. 10, 2015

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": "\"d6d174c76c5fbb5f8a69b648ecd3b27b53a5d27e\”", thanks

2 1

REST API Difference between PUT and PATCH?
by Andrew Stuart Jan. 10, 2015

Jan. 10, 2015

The user endpoint supports PUT and PATCH methods. PATCH does a partial update of the user’s configuration PUT does a full update of the user’s configuration It seems that for user, the field that can be modified between these two methods are display_name and cleartext_password What is the difference exactly between partial and full update? Are the two fields required in one case and optional in the other? thanks

2 1

Postorius merge proposals: translatability & accuracy in templates
by Sumana Harihareswara Jan. 9, 2015

Jan. 9, 2015

I've proposed two new branches for merge into Postorius: * https://code.launchpad.net/~sumanah/postorius/bug-1157947/+merge/245979 fixes bug # 1157947 by finding all user-visible occurrences of hard-coded English strings in templates and templatizing them for translatability. * https://code.launchpad.net/~sumanah/postorius/metrics-template/+merge/245965 fixes bug #1409033 by correcting the messages in a template associated with three metrics. I'd welcome any reviews. Thanks! (And I also see … [View More]

1 0

Dark Mail
by Barry Warsaw Jan. 8, 2015

Jan. 8, 2015

Something interesting to keep an eye on, especially to see if it might relate to encrypted mailing lists. http://arstechnica.com/security/2015/01/lavabit-founder-wants-to-make-dark-… Cheers, -Barry

1 0

RELEASED: GNU Mailman (core) 3.0b5
by Barry Warsaw Jan. 8, 2015

Jan. 8, 2015

Hello friends of Mailman, and Happy New Year! You can roll that stone To the top of the hill Drag your ball and chain behind you Once again, it's time for the traditional "avoid the copyright year bump" release. I'm happy to announce the fifth beta release of Mailman 3.0 core, code named "Carve Away The Stone". We're really quite close now, but this release is a little different. Those of you who follow the proceedings on the mailman-developers mailing list will note that I … [View More]have ported the core engine to Python 3.4. While it is my intent to release Mailman 3.0 core[*] final as a Python 3 application, some of the details are still be hashed out on the mailing list, and in the code base. For this reason, I am releasing two "flavors" of 3.0b5: * "A" release, which remains on Python 2.7 * "B" release, which is only compatible with Python 3.4 The A and B releases are functionally equivalent. There may be different bugs in them, but they both implement the exact same feature set, with the only difference being the version of Python they are compatible with. Some time early in 2015, I will be merging the Python 3 branch back into trunk, and dropping Python 2 support. I would encourage you to download the "B" release and try it out. If you do try both, please submit bugs for any functional differences you encounter. You can download GNU Mailman 3.0b5 core (both "A" and "B" releases) from the Python Cheeseshop: https://pypi.python.org/pypi/mailman/3.0.0b5 The documentation is available online at: http://pythonhosted.org/mailman Mailman 3.0 is released under the terms of the GNU General Public License version 3 or later. Detailed changes in 3.0b5 are available here: http://tinyurl.com/p9fpgrh Bugs can be reported here: https://bugs.launchpad.net/mailman Special thanks go to Abhilash Raj and Aurélien Bompard, who implemented the conversion of the ORM layer from Storm to SQLAlchemy and Alembic. Thanks also to Kurt Griffiths for his excellent Falcon Framework package, which now replaces restish as our WSGI-compatible REST layer. Both of these changes were critical in allowing me to port the core to Python 3. Enjoy, and Happy New Year. -Barry [*] Postorious and HyperKitty will port to Python 3 on their own time schedule, and may remain Python 2 applications for the final release of the GNU Mailman Suite. mailman.client, the standalone REST client will be a bilingual library, supporting both Python 2 and Python 3. [View Less]

6 10

Re: [Mailman-Developers] RELEASED: GNU Mailman (core) 3.0b5
by Barry Warsaw Jan. 7, 2015

Jan. 7, 2015

On Jan 07, 2015, at 11:42 PM, Paul Wise wrote: >What about just a backport of Python 3.4 (and any future mailman3 package)? > >http://backports.debian.org/ For sure, Python 3.4 should be in backports, IMHO. Cheers, -Barry

1 0

Re: [Mailman-Developers] RELEASED: GNU Mailman (core) 3.0b5
by Tanstaafl Jan. 7, 2015

Jan. 7, 2015

On 1/7/2015 2:13 AM, Paul Wise <pabs3(a)bonedaddy.net> wrote: > On Wed, Jan 7, 2015 at 3:09 PM, Tanstaafl wrote: >> Not for those wanting to avoid systemd. > systemd is optional and easy to avoid in Debian. Until it isn't, and that is the overriding concern, and with very good reason considering the relatively short track record that systemd has.

1 0

Re: [Mailman-Developers] RELEASED: GNU Mailman (core) 3.0b5
by Tanstaafl Jan. 7, 2015

Jan. 7, 2015

On 1/6/2015 8:36 PM, Paul Wise <pabs3(a)bonedaddy.net> wrote: > On Wed, Jan 7, 2015 at 1:48 AM, Tanstaafl wrote: > >> So, wheezy admins will be left out in the cold. > > I expect Debian jessie will become Debian stable soon enough. Not for those wanting to avoid systemd.

2 1

Some raw thinking on user level authorization and authentication
by Andrew Stuart Jan. 6, 2015

Jan. 6, 2015

This is as much gathering my thoughts on research. Anyone with questions or comments or ideas welcome. Just raw ideas at this stage. The goal is to build user level REST authentication for Mailman on top of the existing REST API. Mailman user REST authentication/authorization. Use Falcon/Talons wherever appropriate for consistency with Mailman. Authentication - establish the identity of the user Authorization - allow or deny access to specific Mailman resources based on the user identity #… [View More]###############Authentication & authorization process overview: step 1: authentication —- HTTP client provides username and password —- username and password sent to Mailman REST server —- if Mailman REST server authenticates username and password: —- authentication token returned to client step 2: authorization -- examines inbound requests —- if request contains valid authentication information, continue —- examine requested Mailman resource -— send REST request to Mailman REST server to find out if this user is allowed to do this resource request —- if user is allowed access to resource, goto step 3 step 3: action At this stage I have three candidates for what happens next: action 1: —- treat the inbound request as an external proxy authentication subrequest action 2: —- directly proxy the request action 3: -- wsgi drop-through - just let the request pass through to the next level in the wsgi stack ################Possible actions action 1: —- treat the inbound request as an external proxy authentication subrequest In which the inbound HTTP request is first handled by an external proxy server (for example Nginx), which first sends a “subrequest” to our authentication/authorization server. If our authentication/authorization server approves the request, it responses 200 OK to the external proxy server which then directly sends the request to the Mailman REST API ** downside of subrequest based proxying —- depends on external proxy (i.e. Nginx) that suports subrequests based authentication http://nginx.org/en/docs/http/ngx_http_auth_request_module.html —- it would be possible to write the pure Python proxy to user this mechanism, making an external subrequesting authenticating proxy an option rather than requirement ** upside of subrequest based proxying: — once the request is authenticated/authorized, it makes alot of sense for a specialised, high performance proxy to handle the proxying directly with the back end. All proxying edges cases and gotchas are left to the specialised proxy (i.e. Nginx) to handle, and proxy performance is as fast as the external proxy server and the Mailman REST API can talk to each other. action 2: —- directly proxy the request In which the request is then sent on to the Mailman REST API and the response returned to the HTTP client **downside of proxying: —- proxying is a minefield of gotchas and edge cases —- places the authenticating proxy in the path of all requests, certainly slower than raw access to Mailman REST API **upside of proxying: —- can be done as pure Python, no reliance on the behaviour of external proxy servers —- the are probably fewer gotchas when dealing with one know API (i.e. Mailman REST API) versus trying to implement a generalised proxy server action 3: -- wsgi drop-through - just let the request pass through to the next level in the wsgi stack In which the inbound HTTP request comes first through the authorization/authentication wsgi layers then directly to the existing Mailman API via wsgi ** downside of wsgi drop through: —- requires execution of the Mailman REST API as a wsgi application, which is potentially complex and more tightly coupled than desirable and would require implementation into the Mailman code base —- put another way, the auth functions will operate entirely via queries to the Mailman REST API, and such decoupling of auth functions makes for a simpler system [View Less]

2 1

Re: [Mailman-Developers] MM3 REST API testing [was: Python 3]
by Florian Fuchs Jan. 6, 2015

Jan. 6, 2015

Am 26.12.2014 um 16:38 schrieb Aurelien Bompard: > And mailman.client must be ported too, since it does import stuff from > mailman for testing purposes. I think Postorious is safe, but that must be > verified (I believe it imports the testing framework from mailman.client > and thus must be ported too). I think, this is worth another thread. So far we haven't found a perfect solution for testing packages that rely heavily on the MM3 REST API. As far as mailman.client, Postorius … [View More]

4 11

Re: [Mailman-Developers] X-Message-ID-Hash header (was Re: Python 3)
by Barry Warsaw Jan. 6, 2015

Jan. 6, 2015

On Jan 04, 2015, at 03:10 PM, Jeff Breidenbach wrote: >So the homebrew hash was dumb idea, and will gracefully >retire in favor of the standard mailman hash algorithm. It >was pretty neat to see some usage, though. And Archived-At >still looks like a winner. Definitely. X-Message-ID-Hash was just a way to elaborate on RFC 5064 $3.2, and because Base 32 was chosen, there isn't any need to worry about needing to escaping non-ascii characters in the Message-ID, nor case/letter/… [View More]

1 0

Re: [Mailman-Developers] Python 3
by Barry Warsaw Jan. 6, 2015

Jan. 6, 2015

On Jan 06, 2015, at 02:55 PM, Aurelien Bompard wrote: >> > What if a site wanted to run them on different VMs for example? >> > >Yeah, but certainly there should be a limit to that. What if a site wanted to >run each mailman runner on a different VM for example? There's already some support for that, in a way. The runners with queues already employ an algorithm to safely split the queue space up into 2^n separate runners without the need for locking. They do of … [View More]

1 0

Introduction and GSoC project requests
by Konstantinos N Jan. 6, 2015

Jan. 6, 2015

Hello mailman devs and Happy New Year. Since this summer i have been looking at the mailman project as it was the first project that attracted me, being a tool i use at my university to collaborate with my fellow sysadmins. I am generally interested in participating in GSoC at some time but first i would like to start contributing in some way so i can develop better programming skills,learn code researching and bugfixing and generally give back to software that helps me do my work better.… [View More]

1 1

Re: [Mailman-Developers] Python 3
by Barry Warsaw Jan. 6, 2015

Jan. 6, 2015

On Jan 06, 2015, at 01:37 PM, Aurelien Bompard wrote: >I must also consider how much work it would be to just port HyperKitty & >KittyStore to Python3. All things considered, it may very well be faster and >more reliable. Of course, I encourage any porting to Python 3 just on principle :) and certainly if I can help, let me know. But you may still want to consider a more distributed communication protocol between core and HK. What if a site wanted to run them on different VMs … [View More]

3 2

Re: [Mailman-Developers] Python 3
by Barry Warsaw Jan. 6, 2015

Jan. 6, 2015

On Dec 28, 2014, at 01:51 PM, Aurelien Bompard wrote: >> As I mentioned, I think LMTP *could* work, but REST (inside HK) could >> work too. Aurelien, what do you think? > >I'd go with REST, it seems more flexible and we already have nice libraries >for it. REST will be very nice, and I think with something like Falcon, pretty easy to implement. You probably don't need the object-based (i.e. restish-like) traversal stuff, but if so, I'd be happy to split that out into a … [View More]

3 2

Re: [Mailman-Developers] X-Message-ID-Hash header (was Re: Python 3)
by Jeff Breidenbach Jan. 4, 2015

Jan. 4, 2015

I should probably report the experience of mail-archive.com, which has supported a homebrew message-id hash algorithm for over 6 years. Only one organization has ever used it (LibreOffice). They put it in the Archived-At headers, not message footers. However, links did end up getting manually referenced in message bodies 575 times. Folks here might want to take a look at how people used it. Christian Lohmaier from LibreOffice is a good contact if anyone wants to talk to him directly. The … [View More]

1 0

Re: [Mailman-Developers] Python 3
by Stephen J. Turnbull Jan. 3, 2015

Jan. 3, 2015

Aurelien Bompard writes: > Barry writes: > > One of the advantages of accessing the core through the REST API > > is that it doesn't matter what clients like HyperKitty and > > Postorious are written in. > I'm not exclusively using the REST API though. I'm importing a > couple interfaces, mostly the archiver interface. This was a design mistake, I think. An IArchiver really needs to be in core for two reasons: first, it needs to generate a permalink and … [View More]

6 11

new wiki, get-togethers, and 3.0 blockers
by Sumana Harihareswara Jan. 3, 2015

Jan. 3, 2015

Hi Mailman developers! I am becoming one of you :) and have gotten as far as a first patch.[0] Congrats on the new 3.0b5 release! A few questions: * I saw on http://wiki.list.org that we're in the process of moving to a new wiki, and I saw https://mail.python.org/pipermail/mailman-developers/2014-October/024001.ht… in which I heard that we're still in the process of finishing up the conversion. Is there anything you need to help make this happen? Money for SSL certs, wiki gardening time, or … [View More]

4 3