Now that Mailman 3 is in beta, I would like to spend more time working
on it. To that end, I am planning to release Mailman 2.1.15 soon. This
release fixes quite a few bugs and adds some needed new features. See
the NEWS file at
This release contains several new message strings and a template
modification, none of which have been translated. So, if you are a
language champion or just an interested user or anything between, I need
There is a new feature to request a password reminder from the private
archive login page. This necessitated an addition to
templates/<language>/private.html. I have added the new information to
all the templates, but it is in English. If you can help translate this
into your language, get the private.html template from your language
and send me a translated template.
Also, all the message catalogs have been merged from the new mailman.pot
and there are fuzzy translations and untranslated strings as a result.
If you can help with fixing these, get the current
LC_MESSAGES/mailman.po file from your language directory at
and send me an updated version.
If you can help with this, please do it before the end of April. If you
want to help but aren't sure what to do, let me know and I'll try to
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
Hello Mailman Developers,
Sorry in advance if this is not the right place for my query.
I wanted to start contributing to Mailman-Development, and wanted a little
head start for that. I would love to get any sort of guidance in this
respect. I am a second year IT student with knowledge of c, c++, and trying
my hands on web development.
On Mar 24, 2012, at 03:41 PM, Stephen J. Turnbull wrote:
>On Sat, Mar 24, 2012 at 12:15 AM, Barry Warsaw <barry(a)list.org> wrote:
>> Not all of that will be needed. For example, I do want to eventually get rid
>> of zc.buildout, zope.testing, and zope.testrunner, so some of those
>> dependencies will go away as a result of that.
>But presumably new dependencies will be added to support those
>functions, and while Python 3 support is an important desideratum,
>for replacements, I don't think that it's a good idea to let it override
>quality in the implementation of dependencies.
Agreed. However, In these cases, there are already compelling technical
reasons to find replacements.
Someone told me that I should poke Barry about Python3 support, so here
I am ;)
It's clearly something that can be done really soon, but I think it's
worth to start thinking about it.
In particular I noticed that lazr.config have been untouched since 2009,
which makes me think that is less likely that they will be ported to
Is it a valid assumption or there is a porting plan?
Are there any other blocking factors in general from libraries or other
I am Vikash and very much interested in contributing to mailman and being a
GSoC student this year. So far, I have successfully installed mailman in my
I do have skills in Python 2.7 but as I am very new to mailman thus I am
looking for something small to hack and doable in this summer.
Also, the idea page doesnot mention the skills required for the project so
its somewhat difficult for me to choose one. As a result I would like you
to guide me over the same .
I am willing to learn a lot this summer :-)
sent via HTC Sensation
On 3/22/2012 5:48 PM, Stephen J. Turnbull wrote:
> On Fri, Mar 23, 2012 at 1:09 AM, Barry Warsaw <barry(a)list.org> wrote:
>> If we add something like $archive_url to the decoration interpolation
>> dictionary, what happens when we have multiple archivers that support
>> permalink() enabled? Do we chose one at random (these are unordered)?
I agree so -2. I thinking is if you list administrator/owner has not
defined an order, make it simple and impose a known order in that case -
alphabetize/sort the order and pick the first one.
>> Do we add a configuration variable to select a "primary" archiver for this?
This would allow the list administrator/owner to define and pick the
primary archiver. For any other archivers, people can go to the
> If there's *no* archiver configuration variable, we don't know where to
> point to anyway for Gmane-like archivers (yes, I know, catering to Gmane
> will give Brad hives, but some people like Gmane). The local archive, if it
> exists, may seem TOOWTDI, but it might not be the preferred one even if
> it's the only one configured in Mailman (although that seems a lot less
> likely than the case where somebody just grandfathers an existing Gmane
> subscription as the archive URL of choice).
>> Do we allow something like $archive_url.prototype as an interpolation
>> variable to select e.g. the 'prototype' archiver?
> Too complex. If people want alternative archives, they can go to
> the list FAQ or the Archived-At headers. If we go this way, we'd
> better have a *really* good comment and a pre-existing entry in
> the FAQ to save Mark some time. :-)
I agree with Stephen. Too complex and can be confusing without it being
well documented with a number of examples.
But how does the option get into your web UI? If you have to put it
in there by editing
mm_config, I don't see the gain. Remember, many archivers already
have the rather
convenient (to non-shell-on-Mailman-host list owners and even ordinary
users) UI of
simply subscribing the archiver to the list.
I would say that one way to implement this would be as a role in the
Instead of subscribing an archiver as "member", subscribe it with the
Gmane would probably be willing to do this, for example, if the
were as simple as subscribing an ordinary member. I suppose the same goes for
On Fri, Mar 23, 2012 at 10:13 AM, andrea crotti
> My idea as a user would be to be able to select from my
> web configuration page an option:
> send_public_url_in_mail_footers: [
> And maybe it would be cool (if possible I have no idea) to add a mail
> command that when I send
> subject: public $mailing_list $id
> I get back an email with this url. Because maybe from one mailing list
> I'm normally not interested in the url and I also want it in some cases.
> Not sure I anyone else in the world would like this feature though :D
> Mailman-Developers mailing list
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/
> Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/stephen%40xemacs.…
> Security Policy: http://wiki.list.org/x/QIA9
My idea as a user would be to be able to select from my
web configuration page an option:
And maybe it would be cool (if possible I have no idea) to add a mail
command that when I send
subject: public $mailing_list $id
I get back an email with this url. Because maybe from one mailing list
I'm normally not interested in the url and I also want it in some cases.
Not sure I anyone else in the world would like this feature though :D
I filed in two bugs today:
because I thought we could have a discussion there about these topics.
But now I was wondering if it is a good idea, is it maybe better to
write on the mailing list for
these kind of things??
PS. ironically today they asked me for the first time in my life to
check why Mailman was not
working on a Linux server. The problem was that /var was full, but well
knowing more about
Mailman certainly helped :D