Mailman 3 March 2013 - Mailman-Developers

Re: [Mailman-Developers] unable to tear down.. [errno 98]
by Barry Warsaw 11 Mar '13

11 Mar '13

On Mar 11, 2013, at 09:47 AM, Chris Cargile wrote: >I hope to offer suggestions on ways to make developing easier for newcomers >after succeeding in getting a test score of 100% and to provide a URL from >which an image file (.vmdk format) can be wget'ed to a more permanent home >for a shareable development-ready machine image - the second goal will be a >quicker part of the effort I'm hoping since I am learning all this remotely >via AWS (which does not cost anything) We look forward to your suggestions! If you have specific documentation fixes, please do a merge proposal. If you have questions about how to contribute patches to Mailman, don't hesitate to ask. :) -Barry

1 0

Re: [Mailman-Developers] unable to tear down.. [errno 98]
by Barry Warsaw 11 Mar '13

11 Mar '13

Sorry, I'm just plain slammed trying to get ready for Pycon. On Mar 08, 2013, at 04:50 PM, Chris Cargile wrote: >Is the smtp port setting declared in a configuration file used to bind a >mailman instance to a particular process (such as the MTA) on a particular >port? Yes. The base configuration values are in src/mailman/config/schema.cfg. These get overridden/specialized by src/mailman/config/mailman.cfg by default, and whatever mailman.cfg file you might have installed when you run MM3 in production. In a testing environment, src/mailman/testing/testing.cfg is the top configuration file. Look in the [mta] section and you'll see that by default, Mailman connects to localhost:25. This changes to localhost:9025 when running the test suite. >I tried looking through the configuration files to identify the location to >which I thought the stmpd was trying to bind but did not figure out how it >worked MM3 uses the lazr.config system. http://pythonhosted.org/lazr.config/ >I am hoping to learn how this works (and to hack my configuration, if >needed) to get past the SMTP/RestLayer teardowns, and am stuck getting: > >[Errno 98] Address already in use (log >file<http://pastebin.com/raw.php?i=HM6ej8V4> >) If you're getting this during the tests, it almost always means that the Python subprocess binding to that address didn't exit. The test suite (and MM3 in general) is pretty careful about shutting down its subprocesses, but sometimes this fails. Use killall or friends to actually stop the process. We use lazr.smtptest <http://pythonhosted.org/lazr.smtptest/> to start up the SMTPd for testing, and this should properly set the reuse flag on the socket. Cheers, -Barry

1 0

Re: [Mailman-Developers] unable to tear down.. [errno 98]
by Chris Cargile 11 Mar '13

11 Mar '13

I am not getting no failures but got around the 'address in use' error message (..and in its place have discovered a world of possible other error messages, but that's good!) I hope to offer suggestions on ways to make developing easier for newcomers after succeeding in getting a test score of 100% and to provide a URL from which an image file (.vmdk format) can be wget'ed to a more permanent home for a shareable development-ready machine image - the second goal will be a quicker part of the effort I'm hoping since I am learning all this remotely via AWS (which does not cost anything) On Fri, Mar 8, 2013 at 4:50 PM, Chris Cargile <follybeachris(a)gmail.com>wrote: > Is the smtp port setting declared in a configuration file used to bind a > mailman instance to a particular process (such as the MTA) on a particular > port? > > I tried looking through the configuration files to identify the location > to which I thought the stmpd was trying to bind but did not figure out how > it worked > > I am hoping to learn how this works (and to hack my configuration, if > needed) to get past the SMTP/RestLayer teardowns, and am stuck getting: > > [Errno 98] Address already in use (log file<http://pastebin.com/raw.php?i=HM6ej8V4> > ) >

1 0

unable to tear down.. [errno 98]
by Chris Cargile 08 Mar '13

08 Mar '13

Is the smtp port setting declared in a configuration file used to bind a mailman instance to a particular process (such as the MTA) on a particular port? I tried looking through the configuration files to identify the location to which I thought the stmpd was trying to bind but did not figure out how it worked I am hoping to learn how this works (and to hack my configuration, if needed) to get past the SMTP/RestLayer teardowns, and am stuck getting: [Errno 98] Address already in use (log file<http://pastebin.com/raw.php?i=HM6ej8V4> )

1 0

Wiki Migration Update
by Paul Boddie 07 Mar '13

07 Mar '13

Hello, This is really just a quick mail to let you know that I haven't forgotten about my promise to look into migrating the Wiki content to MoinMoin. As always, you can monitor the status of the work here: http://hgweb.boddie.org.uk/ConfluenceConverter/ I aim to upload a snapshot of the translated content to a demonstration site (as I did before) in the next few days, and hopefully will have improved the output a bit by then. Although I have mostly been focusing on the old Confluence Wiki markup in the past couple of days, I think that the recent changes have improved the "fidelity" of the old page revisions somewhat, and with the new XHTML-style markup being somewhat easier to deal with, I aim to have parity between the two formats fairly soon. If there's anything in particular beyond basic content migration that you'd like to see in MoinMoin, please let me know. The markup mapping page... http://moinmo.in/ConfluenceConverter/DevelopmentNotes/MarkupMapping ...describes some macros and other features that should be reproduced in the Moin-based solution, and I've attempted to incorporate existing page comments (as I described before) and page navigation features, but it would be useful to know what people currently depend upon so that any extra macros or extensions can be written. I'll send another update soon. Thanks for being patient! Paul

3 6

Re: [Mailman-Developers] buildout instructions
by Barry Warsaw 06 Mar '13

06 Mar '13

On Mar 06, 2013, at 02:44 PM, Chris Cargile wrote: >python >=2.7 has been done, case these issues are related. Here is the my >buildout-stacktrace <http://pastebin.com/raw.php?i=wi19Qta2> in case >someone can advise That looks like a network issue actually. buildout can't seem to talk to server providing restish. I just tried to buildout a fresh checkout of the v3 branch and while I got errors trying to talk to http://ish.io, it did manage to grab 0.12.1 from PyPI afaict. Cheers, -Barry

2 1

Re: [Mailman-Developers] Mailman 3 and New Lists (Templates for Defining?)
by Barry Warsaw 06 Mar '13

06 Mar '13

On Mar 02, 2013, at 10:38 AM, Tom Browder wrote: >Earlier I was pointed to the REST API for programatically generating a new >list--looks good. However, the docs mention a default set of attributes for >a new list and I wonder if there are yet any other choices. > >I guess the real question for me is: is there a templating system in MM 3 so >that different list types can be defined? My search through the code so far >hasn't found such except for language templates. Yes, these are called "list styles". See the IStyle interface in src/mailman/interfaces/styles.py for the API and src/mailman/styles/default.py for the two built-in styles, both essentially legacy styles. Note that styles are only applied when a list is created, so it is better to think of them as the default set of attributes for a list. IOW, if you changed a style after a list is created, the list attributes do not change. In fact, the mailing list doesn't record what styles were applied to it. The mailman.cfg file has a [styles] section, with a `paths` variable and a `default` variable. The `paths` variable names Python dotted-module paths which are searched for IStyle implementations. Thus, if you arranged for your MM3 installation to include on sys.path, the package mylocal.mailman.styles, you could put your own styles in there and Mailman should find them automatically. At that point, you can use one of your named styles as the default (via the `[styles]default` variable), or you can specify the style to use when creating a new list through the REST API. See src/mailman/rest/docs/list.rst for details. >Having just agonizingly set up a true (IMHO) read-only list under Mailman 2, >I think such a template to choose (at least to start from) would be very >helpful in Mailman 3. (I don't doubt there is an easier way under Mailman 2, >but I find the various inputs in the web interface too scattered around for >my tastes.) Hopefully the above makes sense, and provides enough information to play with the feature in MM3. I'm absolutely open to ideas for making list styles easier to add, customize, and use. Cheers, -Barry

5 6

Re: [Mailman-Developers] Mailman 3 and New Lists (Templates for Defining?)
by Barry Warsaw 06 Mar '13

06 Mar '13

On Mar 05, 2013, at 07:51 PM, Tom Browder wrote: >> Yes, these are called "list styles". See the IStyle interface in >> src/mailman/interfaces/styles.py for the API and >> src/mailman/styles/default.py for the two built-in styles, both essentially >> legacy styles. > >Ah, that's where it is! (And I assume ALL "attributes" are defined >there.) But to my non-Python eyes I see only one actually defined. There are two classes in default.py, LegacyDefaultStyle and LegacyAnnounceOnly, both of which have @implementer(IStyle) decorators. This is the way you declare that a class implements a particular interface, and it's how Mailman auto-discovers available styles. >But there is where we could add some other mailman-defined styles, correct? Probably not. However, if we wanted to package some new "out-of-the-box" styles, we'd probably create a new module in that directory and add new classes there that declare they implement the IStyle. But MM3 is designed to be extensible, so your own styles don't need to be in this package directory. As long as they are on Python's sys.path, and defined in your own mailman.cfg file, Mailman should be able to find them and allow them to be used. Cheers, -Barry

1 0

buildout instructions
by Chris Cargile 06 Mar '13

06 Mar '13

I am getting stuck during my buildout due to a mix-up b/w what versions zc.buildout and/or eggs are expected and am assuming this is an ongoing issue from zope, per a 9/6/12 developers-list message<http://www.mail-archive.com/mailman-developers%40python.org/msg13152.html> , I could not surpass the buildout step as the system complained about the ScriptBase module not being found and was hoping someone might kindly guide me past this fwiw, working through zc-buildout/recipe issues<http://blog.gocept.com/2012/11/09/python-2-and-3-compatible-builds-with-zc-…> w/ python >=2.7 has been done, case these issues are related. Here is the my buildout-stacktrace <http://pastebin.com/raw.php?i=wi19Qta2> in case someone can advise thanks! Chris

1 0

Mailman 3 and New Lists (Templates for Defining?)
by Tom Browder 02 Mar '13

02 Mar '13

Earlier I was pointed to the REST API for programatically generating a new list--looks good. However, the docs mention a default set of attributes for a new list and I wonder if there are yet any other choices. I guess the real question for me is: is there a templating system in MM 3 so that different list types can be defined? My search through the code so far hasn't found such except for language templates. Having just agonizingly set up a true (IMHO) read-only list under Mailman 2, I think such a template to choose (at least to start from) would be very helpful in Mailman 3. (I don't doubt there is an easier way under Mailman 2, but I find the various inputs in the web interface too scattered around for my tastes.) Best regards, -Tom

1 0