Mailman 3 July 2007 - Mailman-Users

Re: [Mailman-Users] Mailman roadmap
by Krystal F. Zipfel 11 Jul '07

11 Jul '07

Hello Barry (and all), I may have a few more coming from my colleagues regarding this, but I do have one point I'd like to mention. Not sure if it's ever been given thought. Currently, Mailman looks at the list-name as strictly "list-name", instead of "list-name@domain". Why I bring this up? I have a set of servers (eight, in fact) running several thousand lists (about 10,000 of them), all from different people with different domains. Many of these users often pick the same list name, which we of course make them pick a new list name. Reason being, having two list names identical on one server causes delivery problems, file storage, database problems, log problems, the works. Is there any consideration made, or is it possible to have Mailman recognize that "listname(a)domaina.com" is different than "listname(a)domainb.com", and operate as normal based on that? Just a thought. :-) Glad to see Mailman on the move! Krystal ----- Original Message ---- From: Barry Warsaw <barry(a)python.org> To: Mailman Developers <Mailman-Developers(a)python.org> Cc: Mailman Users <mailman-users(a)python.org> Sent: Saturday, July 7, 2007 12:36:54 PM Subject: [Mailman-Users] Mailman roadmap -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry, I forgot to cross-post this to mailman-users, so I'm reposting. - -Barry Now that we've successfully navigated the switch to Bazaar, it's time to lay out plans for future Mailman releases. I've talked to several people about what to do about Mailman's future and I'd like to take this opportunity to describe my thoughts and get your feedback. First some background. Mailman 2.1 is (shockingly) four and a half years old, having been initially released on 30-Dec-2002. The last release in the series, 2.1.9 was made almost a year ago. In the meantime, Mark and Tokio have been doing a great job maintaining the 2.1 branch, with several important patches in the tree now that will eventually become 2.1.10. The problem of course is that we can't add any new features to the 2.1 family <wink>, so we should be thinking about a new major release. I've been making good progress on the SQAlchemy/Elixir version, which will finally get rid of pickles and put Mailman on a Real Database (tm). It's been clear to me for a while that this branch will have a unified user database. It simply makes no sense to build the database back-end without once and for all fixing this design constraint. I've always said that the unified user database will be in Mailman 3, and thus this branch is indeed called "Mailman 3.0". I've been slowly building things back up from the ground floor. The basic data model is in pretty good shape and I'm taking a religious test-driven approach to making things work again. But the branch still needs a lot of work, and I have no ETA for Mailman 3.0. In the meantime, Andrew Kuchling and others have volunteered to work on modernizing the Mailman web u/i, and Terri recently started a thread discussing updates to the archiver. I think it makes sense to bless these efforts, towards the goal of releasing them in Mailman 2.2. I intend to create an official Mailman 2.2 branch in bzr where these efforts can land as they mature. My hope of course is that we'll also be able to use much of this new code for Mailman 3. I'd like to keep the changes for 2.2 focused on the web u/i and archiver, with a small number of additional features to be determined. Mailman 2.2 should see no changes to the basic architecture or 'database'; we'll continue to use pickles by default for Mailman 2.2. While I won't rule out other new features, I want to be very picky about those that are accepted for 2.2, and would not feel bad at all if we rejected or deferred until 3.0 most of those proposed. Criteria for other 2.2 features must include minimal code impact with a high degree of reliability and stability. I plan on updating the wiki pages to reflect this thinking, but I would like to get feedback from y'all about the plan. It would be awesome if we could see a release of Mailman 2.2 some time in late 2007 or early 2008. Comments, question? - -Barry

7 8

Remove Text
by Jason L 11 Jul '07

11 Jul '07

I need to remove text from emails sent to the lists. Is there a way to do this with Mailman. I'm trying to remove text like this. But I have others I am trying to remove. THIS IS A WARNING THAT SEVERE THUNDERSTORMS WITH TORNADOES ARE IMMINENT OR OCCURRING IN THESE REGIONS. MONITOR WEATHER CONDITIONS. TAKE IMMEDIATE SAFETY PRECAUTIONS.

2 1

Error when sending from an unsubscribed address
by Simon Helson 11 Jul '07

11 Jul '07

I'm trying to send email to a mailman list from an address that isn't subscribed to the list, The expected behaviour (or the configured at least) would be for this message to be held for moderation, however it's not, and I'm getting the following error. Versions: Python 2.5.1, Mailman is 2.1.9. List members can post to the list fine. Jul 10 17:11:58 2007 (28644) Uncaught runner exception: unbound method reason_notice() must be called with ImplicitDestination instance as first argument (got nothing instead) Jul 10 17:11:58 2007 (28644) Traceback (most recent call last): File "/opt/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/opt/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/Mailman/Queue/IncomingRunner.py", line 129, in _dispose status = self._dopipeline(mlist, msg, msgdata, pipeline) File "/opt/mailman/Mailman/Queue/IncomingRunner.py", line 152, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/opt/mailman/Mailman/Handlers/Hold.py", line 162, in process hold_for_approval(mlist, msg, msgdata, ImplicitDestination) File "/opt/mailman/Mailman/Handlers/Hold.py", line 205, in hold_for_approval reason = Utils.wrap(exc.reason_notice()) TypeError: unbound method reason_notice() must be called with ImplicitDestination instance as first argument (got nothing instead) Jul 10 17:11:58 2007 (28644) SHUNTING: 1184083917.788264+31f0e344a0c344044943f7eb4b0669288a21e319 Cheers Simon

4 4

a bug found in 2.1.9
by Scott Berry 10 Jul '07

10 Jul '07

Hello there list, I am a new person using mailman and it looks like a bug is prevalent in 2.1.9. Here is what I got off the web page: Bug in Mailman version 2.1.9 Bug in Mailman version 2.1.9 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. I am using Fedora and could not find any erros. Scott

3 2

Problema com a interface web do Mailman
by Richardson Lima 09 Jul '07

09 Jul '07

Estou com um problema que é o seguinte, a interface WEB do MailMan não esta mais respondendo a minha interação,não estou conseguindo mais moderar as mensagens , o que vocês acham que poderia está ocorrendo ? Um abraço ! -- --------------------------------------------------------------- * Richardson Edson de Lima < Hachid > >> Unix Network Security (Gnu/Linux, OpenBSD and FreeBSD) > // GSM Mobile: +55 81-94157228 > // Skype: richardsonpindoramalinux > // MSN . yhwhh1d3ncypherpunk[at]msn[dot]com Portal: http://richardson.infinitehost.com.br/ Unix User Group : http://openbsd-pe.codigolivre.org.br --------------------------------------------------------------- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)

2 2

Programtically Adding/Removing Users remotely
by Davy Durham 09 Jul '07

09 Jul '07

Hi, I'm using an hosting provider that provides mailman facilities but mailman is running on a server that I do not have shell access on. I would like to programatically add/remove users from a mailing list. If I were ON the mail processing server then I would simply use the add_members and remove_members utilties. So, I'm asking to find out if anyone knows of any tools that can do these 2 operations on a remote mailman installation (perhaps using the administrative interface via http using a username and password of course) I can probably handle writing it myself, but was hoping something already exists. Thanks

3 6

Problem with mailman
by mattias jonsson 09 Jul '07

09 Jul '07

I have problem with mailman Curentlu my listadress are list@myipadress How to change it to my own domain And can i use my isps smtpserver to send mail?

2 1

Mailman roadmap
by Barry Warsaw 07 Jul '07

07 Jul '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry, I forgot to cross-post this to mailman-users, so I'm reposting. - -Barry Now that we've successfully navigated the switch to Bazaar, it's time to lay out plans for future Mailman releases. I've talked to several people about what to do about Mailman's future and I'd like to take this opportunity to describe my thoughts and get your feedback. First some background. Mailman 2.1 is (shockingly) four and a half years old, having been initially released on 30-Dec-2002. The last release in the series, 2.1.9 was made almost a year ago. In the meantime, Mark and Tokio have been doing a great job maintaining the 2.1 branch, with several important patches in the tree now that will eventually become 2.1.10. The problem of course is that we can't add any new features to the 2.1 family <wink>, so we should be thinking about a new major release. I've been making good progress on the SQAlchemy/Elixir version, which will finally get rid of pickles and put Mailman on a Real Database (tm). It's been clear to me for a while that this branch will have a unified user database. It simply makes no sense to build the database back-end without once and for all fixing this design constraint. I've always said that the unified user database will be in Mailman 3, and thus this branch is indeed called "Mailman 3.0". I've been slowly building things back up from the ground floor. The basic data model is in pretty good shape and I'm taking a religious test-driven approach to making things work again. But the branch still needs a lot of work, and I have no ETA for Mailman 3.0. In the meantime, Andrew Kuchling and others have volunteered to work on modernizing the Mailman web u/i, and Terri recently started a thread discussing updates to the archiver. I think it makes sense to bless these efforts, towards the goal of releasing them in Mailman 2.2. I intend to create an official Mailman 2.2 branch in bzr where these efforts can land as they mature. My hope of course is that we'll also be able to use much of this new code for Mailman 3. I'd like to keep the changes for 2.2 focused on the web u/i and archiver, with a small number of additional features to be determined. Mailman 2.2 should see no changes to the basic architecture or 'database'; we'll continue to use pickles by default for Mailman 2.2. While I won't rule out other new features, I want to be very picky about those that are accepted for 2.2, and would not feel bad at all if we rejected or deferred until 3.0 most of those proposed. Criteria for other 2.2 features must include minimal code impact with a high degree of reliability and stability. I plan on updating the wiki pages to reflect this thinking, but I would like to get feedback from y'all about the plan. It would be awesome if we could see a release of Mailman 2.2 some time in late 2007 or early 2008. Comments, question? - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRo/BJnEjvBPtnXfVAQL7iwP/TfPPvMsTnrrSxQAlvPjQoR27ySqUYh+P yZCvGxxp9DgNoFQOWl0mo1QzZ9ozXtiFfIHx4CJLybOis+yuiq+BWtih2MJnGBf7 SzD8qsBOu6N4sE8sn4n0tdmXr1fnh4qnrgTobvBX+3toJtHNGQTEVEZCxiWb5fKq JsUKDVVvOhQ= =CVNK -----END PGP SIGNATURE-----

1 0

Bounce Messages
by Fred Atkinson 07 Jul '07

07 Jul '07

I have configured both of my Mailman lists to discard messages by non-members. But I keep getting the bounce messages. Is there any way to disable them? Regards, Fred

2 1

Re-sending digests
by Ivan Van Laningham 05 Jul '07

05 Jul '07

Hi All-- I couldn't find it, and I couldn't find information in the FAQ or the docs, so I suspect the capability is simply not there: is there any way to retrieve or re-create a digest once it has been sent out? I have subscribers who occasionally miss digests and I'd like to be able to re-send them. Short of subscribing to the digest myself, that is. It seems to me it would be hand to have a page where I could select various digests by vol & issue and enter an email or group of emails, push submit and have the selected digest re-sent. Metta, Ivan -- Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laning… Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours

2 1