I just got an email from a fellow in Germany wanting to know where he
could find courier-to-mailman.py, a script I contributed to mailman some
time ago and which is included in the distribution, but apparently not
parsed for replacement tokens and installed in the contrib directory at
It might be a good idea to patch configure.in with the proper line to
take care of this:
--- configure.in.old 2012-03-12 13:41:57.512455181 -0500
+++ configure.in 2012-03-12 13:42:21.252451587 -0500
@@ -681,6 +681,7 @@
... and run autoconf so that the distributed configure file reflects
You have the equivalent script for qmail properly generated, but not the
courier script. Qmail is pretty much obsolete these days, while courier
is under active development and is widely used, notably outside the US.
I've been using the courier-to-mailman.py script for the better part of
Lindsay Haisley | "Everything works if you let it"
FMP Computer Services |
512-259-1190 | --- The Roadie
I was going through ideas page of mailman for GSoC 2012. I would like
to work with mailman.
If there are more ideas i would like to see it. Currently i am 3rd
year of under-graduation at K.B.N.C.E Gulbarga.
In the bug 837700, I have implemented the suggestions you have made in the
comment in launchpad. I am unable to test the bug in the first place. Is
there a way in which I can reproduce the bug. Since there are only three
legitimate users who are are hard coded in the Rest API, how can I give
them preferred addresses.
With Pycon 2012 coming up in the next few days, and most of the core Mailman
developers attending the sprints, we have a opportunity to reach some
important milestones with Mailman 3.
You are of course invited to join us. Please sign up on the project page
below so we can make the appropriate plans.
Don't forget to come to my talk on Saturday at 4:55pm local time.
We'll have two main goals for the sprint, and possibly a third:
- Do a face-to-face integration of the web ui for MM3, identifying any
concerns or missing functionality in the API, reviewing the ui design,
fix related bugs, etc.
- Solidify the core engine so that I can release beta 1.
- Possibly, make progress on the next-gen archiver.
Yes, you read that right. At long last, I believe the core engine is solid
enough to move into beta. This means we'll freeze the database schema and use
the migration mechanism for any future updates, and we'll also feature freeze
so we can concentrate on bug fixing. So beta 1 is planned for during or
just after the sprints.
Finally, I have put up a test server, which you are invited to join and use.
Right now, you only have access to the email command interface, meaning you
must join and leave the mailing list via email commands and confirmations.
Once joined, you can of course post to the list.
Note that this list is running on a virtual machine, so it, the domain, or the
Mailman service can disappear at any time. Occasionally, I'll stop the
system, run it in debug mode (meaning your posts will not go to the list),
update the software, etc. If something looks weird, please try again, or
email me, or file a bug on Launchpad. Please include the original email or
at least the Message-Id of the message you sent that caused the problem.
I will be watching the logs when I can. Be good citizens and reasonable
users. Abuse will not be tolerated and will get you banned at the MTA.
- Subscribe by sending a message to playground-join(a)groon.org
- Unsubscribe by sending a message to playground-leave(a)groon.org
- Get help by sending a message to playground-request(a)groon.org with the
word 'help' (sans quotes) in the Subject
- Post to the list at playground(a)groon.org
Enjoy, and I hope to see you at Pycon.
 I guess I should write it, eh? <wink>
 Of course, I get to decide what's a bug and what's a missing feature :)
Please tag the bug with 'mailman3'