Mailman 3 May 2002 - Mailman-Developers

[ mailman-Patches-551327 ] Makefile fix so that errors propagate
by noreply＠sourceforge.net May 3, 2002

May 3, 2002

Patches item #551327, was opened at 2002-05-02 09:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=551327&group_id… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel Resare (noa) Assigned to: Nobody/Anonymous (nobody) Summary: Makefile fix so that errors propagate Initial Comment: While I was trying to build mailman-2.1b1 as an rpm i encountered problems with my python installation that made the build in misc fail. Unfortunately, the error didn't propagate to the toplevel make process so it took some time to track down. The attached patch simply propagates any errors from make subprocesses to the topelevel make in an automake like fashion. ---------------------------------------------------------------------- >Comment By: Daniel Resare (noa) Date: 2002-05-03 08:48 Message: Logged In: YES user_id=24013 Since english is not my first language I don't understand what you mean with 'comprehensive'. Does it indicate that my patch is hard to understand? (Sounds unlikely to me) ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:54 Message: Logged In: YES user_id=12800 I think a more comprehensive solution might be necessary. I introduced a delivery mistake (calling it email-2.0.3 in misc/Makefile.in) and the build process didn't stop. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=551327&group_id…

1 0

[ mailman-Bugs-551730 ] traceback on double rename
by noreply＠sourceforge.net May 3, 2002

May 3, 2002

Bugs item #551730, was opened at 2002-05-03 06:50 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=551730&group_id… Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Marc Merlin (marcmerlin) Assigned to: Nobody/Anonymous (nobody) Summary: traceback on double rename Initial Comment: I have a user who says he got this on mailman 2.1b1cvs He explains below how he did it. ----- Forwarded message from David T-G <davidtg(a)justpickone.org> ----- Subject: Mailman results for Empeg-faq From: empeg-faq-request(a)merlins.org To: davidtg-empeg(a)justpickone.org X-List-Administrivia: yes This is an automated response. There were problems with the email commands you sent to Mailman via the administrative address empeg-faq-request(a)empeg.merlins.org. To obtain instructions on valid Mailman email commands, send email to empeg-faq-request(a)empeg.merlins.org with the word "help" in the subject line or in the body of the message. If you want to reach the human being that manages this mailing list, please send your message to empeg-faq-owner(a)empeg.merlins.org. The following is a detailed description of the problems. ***** confirm 97bbfd70939538b155776d5e652af14bc6032c36 >>>>> An unexpected Mailman error has occurred. >>>>> >>>>> Please forward your request to the human list administrator in charge >>>>> of this list at <empeg-faq-owner(a)empeg.merlins.org>. The traceback is >>>>> attached below and will be forwarded to the list administrator >>>>> automatically. Traceback (most recent call last): File "/var/local/mailman/Mailman/MailCommandHandler.py", line 273, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/var/local/mailman/Mailman/MailCommandHandler.py", line 727, in ProcessConfirmCmd results = self.ProcessConfirmation(args[0], msg) File "/var/local/mailman/Mailman/MailList.py", line 1041, in ProcessConfirmation self.ApprovedChangeMemberAddress(oldaddr, newaddr, globally) File "/var/local/mailman/Mailman/MailList.py", line 976, in ApprovedChangeMemberAddress self.changeMemberAddress(oldaddr, newaddr) File "/var/local/mailman/Mailman/OldStyleMemberships.py", line 234, in changeMemberAddress self.__assertIsMember(member) File "/var/local/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member NotAMemberError: davidtg(a)bigfoot.com ----- End forwarded message ----- ----- Forwarded message from David T-G <davidtg(a)justpickone.org> ----- % Were you trying to change your subscription from davidtg(a)bigfoot.com to % davidtg-empeg(a)justpickone.org via the mail interface? No; I did it thru the web interface. % If so, do you mind sending me a copy of the mails you sent to the list % manager (I run a devel version of the upcoming mailman, and I try to help Sorry; any sort of subscribe and confirm messages I just toss in the bit bucket. In addition, once the subscriptions were confirmed, I tossed the list server messages as well. Sorry! % out with small bugs. This one seems to be minor, but we should probably look % into it anyway) Sorry :-) It should be easy to duplicate, though; subscribe to two lists (like empeg-faq and empeg-announce), open two web browsers, go to the two list control pages and log in on each, and then send a change from one and a change from the other. Remember to hit "global" at some point along the way. When replying to the confirmation messages, reply to the first before doing the global change but the second, which might confusingly arrive after said global change, later after the web is done. ----- End forwarded message ----- ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=551730&group_id…

1 0

[ mailman-Feature Requests-228008 ] Need full name & phone in list user database
by noreply＠sourceforge.net May 3, 2002

May 3, 2002

Feature Requests item #228008, was opened at 2001-01-08 01:36 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=228008&group_id… Category: (un)subscribing Group: None >Status: Closed >Resolution: Fixed Priority: 3 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Need full name & phone in list user database Initial Comment: I need a better authentication method for people who want to subscribe to a list, and right now the only info that a user type in is an e-mail address -- there's no easy way for him to type in his full name and phone number. I can change the text of the e-mail that the user gets ("confirm" is checked in the admin/privacy page of the list) to request that the user send in this info, but the list-admin@hostserver never gets the user's reply to the confirm e-mail. Regardless, I need to track full names and phone numbers associated with each subscriber's e-mail. This should be a fairly simple change to user databases, but a little beyond my capabilities. I hope "bugs" is the right place to request this, I didn't see a better place. webbi(a)caa-austin.org ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:50 Message: Logged In: YES user_id=12800 MM2.1 can now track the fullnames, but it doesn't track phone numbers. Such "extra information" is better placed in a real unified user database since it isn't really of any relevance to Mailman. In MM2.1 you could back Mailman with an external database bridge to accomplish something similar. ---------------------------------------------------------------------- Comment By: Jens Larsson (jenslarsson) Date: 2001-07-06 12:15 Message: Logged In: YES user_id=245275 This is something I really miss. I was just going to file this as a feature request myself. It is very hard to manually administer a list with a few hundred recipients when strange mail-addresses is all you have. /jens ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2001-03-02 03:45 Message: Logged In: YES user_id=34209 It's a feature request, which is kind of a bug. This is also not trivial to arrange because Mailman lacks a user-database entirely, at the moment. All that is stored is a per-list list of emailaddr/password pairs. Moved to feature requests. ---------------------------------------------------------------------- Comment By: Jeffrey M. Vinocur (jvinocur) Date: 2001-01-11 11:23 Message: I agree. (Other list software keeps the database as a list of RFC 822 addresses, like "user@host", "J. Random User <user@host>", "user@host (J. Random User)". This would be nice... ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=228008&group_id…

1 0

[ mailman-Feature Requests-228127 ] Improve Pipermail's memory footprint
by noreply＠sourceforge.net May 3, 2002

May 3, 2002

Feature Requests item #228127, was opened at 2001-01-08 22:07 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=228127&group_id… Category: Pipermail Group: None >Status: Closed Resolution: Later Priority: 3 Submitted By: Bob Tanner (tanner) Assigned to: Nobody/Anonymous (nobody) >Summary: Improve Pipermail's memory footprint Initial Comment: I run several very active mailing lists. And the mbox files are starting to approach critical size. With 2.4 coming out and reiserfs I no longer have to working about the single file size limitation. BUT pipermail is terrible on handling mbox files that are GB in size. My feature request to to re-write pipermail and store the files in Maildir format. Get pipermail so that it does not have to read the entire mbox (or Maildir) info in order to rebuild the archives. I have a dual P3 550 zeon box with 1Gb of memory and I am constantly running out of core and VM because pipermail consumes resources like a wild thing. I also have difficulty backing up the "archives" directory. By the time BRU, tar, amanda, etc... dump the GB mbox file to tape, I have received several more messages and the check of the file on disk against the file on tape never matches. Maildir format would help solve this problem as well. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:48 Message: Logged In: YES user_id=12800 I've changed the subject header to more accurately reflect this RFE. MM2.1 is a leeetle bit better here in that you can regenerate the archive in more bite-sized chunks. It still sucks, but it should be good enough until someone steps up for a complete MM rewrite. As for the backup problem, in MM2.1 you could shut down the archive queue runner for the duration of the backup, and then turn it back on and have it process the queued messages when the backup is finished. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2001-03-02 03:59 Message: Logged In: YES user_id=34209 Rewriting the archiver has been a long standing feature request, yes :) The maildir suggestion hadn't occured to me yet, but does make sense. In the mean time, you can use an external archiver, like (I believe) MHonarc and others. We should probably get someone who's done that to write up a quick HOWTO for it. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=228127&group_id…

1 0

[ mailman-Feature Requests-230429 ] Feature request: Single password for all lists
by noreply＠sourceforge.net May 3, 2002

May 3, 2002

Feature Requests item #230429, was opened at 2001-01-29 22:59 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=230429&group_id… Category: (un)subscribing Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Matthew Saltzman (cumthsc) Assigned to: Nobody/Anonymous (nobody) Summary: Feature request: Single password for all lists Initial Comment: It would be a convenience for users that subscribe to several lists on a single server if the same password worked for all lists subscribed with a particular e-mail address. I'd like the subscribe function to check for existence of the new subscriber's address on any other lists and take the password from there. Of course, password changes should propagate to all subscribed lists too. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:45 Message: Logged In: YES user_id=12800 I'm going to close this because while the confederated userdb is a MM3 design goal, in the meantime, in MM2.1 users will be able to change their passwords for all lists "globally". It'll have the same effect. The user will still have to do a manual "change password globally" step though. That should be good enough for now. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2001-03-02 09:00 Message: Logged In: YES user_id=34209 A separate userdb has been a longstanding feature request, both from a lot of users as from Barry himself :) Moving to feature requests. (Mental note: we should create tasks for all feature requests, and just mark the repeating requests as closed.) ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-02-01 11:30 Message: One of the items that has been on the planning bench for a long while (since I started using mailman in late '99, anyway) is to re-orient mailman's databasing scheme so that the subscriber info is abstracted into a separate "profile" DB. Then the list DBS themselves would only contain references to the users profile DB entries instead of their real e-mail addresses. Some of the benefits of this are: -a user could opt to have a single password for all lists they are a member of -if their e-mail address ever changes a user would only have to change it in one place -would allow a user to unsubscribe from all lists at once. -more information about each user could (optionally) be stored by mailman. -would allow mailman to perform a little profiling about who is subscribed to what lists, etc. Some of the downsides are (from my understanding anyway): -would need to replace the DB system with a faster one, possibly even a third party one like MySql or something (which would complicate installation and setup a fair bit) -would take a lot of re-coding (more than most want to do right now) -introduces more possible stability problems and security holes. Just my $.02... ~ Rick ~ ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=230429&group_id…

1 0

[ mailman-Feature Requests-404691 ] Strip attachments and web store them
by noreply＠sourceforge.net May 3, 2002

May 3, 2002

Feature Requests item #404691, was opened at 2001-02-27 15:51 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=404691&group_id… Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Stefano Santoro (vtkstef) Assigned to: Nobody/Anonymous (nobody) Summary: Strip attachments and web store them Initial Comment: Like mailtar where attachments are stripped from list postings, and stored on a configurable directory wich can be referenced by a configurable URL. The posting itself is edited by replacing the attachement with the URL of the stored stripped attachement. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:42 Message: Logged In: YES user_id=12800 Pipermail in MM2.1 has much better support for stripping attachments in the archive, and storing them under separate url. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-08-02 16:53 Message: Logged In: NO This sounds similar to a feature in MHonArc. From http://www.mhonarc.org/MHonArc/doc/faq/general.html#compare : "MHonArc has fairly robust MIME support, including the ability to extend the list of media-types supported. .." Eric P. Los Gatos, CA ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=404691&group_id…

1 0

[ mailman-Feature Requests-406137 ] Make RFC 2369 extra headers optional
by noreply＠sourceforge.net May 3, 2002

May 3, 2002

Feature Requests item #406137, was opened at 2001-03-05 17:18 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=406137&group_id… Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Make RFC 2369 extra headers optional Initial Comment: There could easily be a toggle for "add RFC 2369 headers" on a per-list basis. I've gotten some complaints from users that "there are all these extra headers being displayed in their mail program". I'm trying to resist being the BOFH and telling them to change their damn mailer if they can't configure it, but thought I'd suggest the idea here anyway. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:41 Message: Logged In: YES user_id=12800 I've given in to pressure and, if the site administrator enables this, list owners will have the power to disable these headers in MM2.1 ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=406137&group_id…

1 0

[ mailman-Feature Requests-409071 ] Crypt/md5 change on the fly
by noreply＠sourceforge.net May 3, 2002

May 3, 2002

Feature Requests item #409071, was opened at 2001-03-16 05:06 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=409071&group_id… Category: None Group: None >Status: Closed Resolution: Fixed Priority: 5 Submitted By: Karsten Thygesen (karthy) Assigned to: Nobody/Anonymous (nobody) Summary: Crypt/md5 change on the fly Initial Comment: Hi Pr. default, Mailman tries to use crypt if it is available, and if not, it uses md5. Fine. If an installation is using a python without crypt capability, mailman will be using md5, but if the python installation is changed and now supports crypt, mailman fails do validate any passwords. Suggestion: store the encryption method together with the crypted password, so that multiple encryption methods can be used at once. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:40 Message: Logged In: YES user_id=12800 MM2.1 never uses crypt or md5 -- it always uses sha. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=409071&group_id…

1 0

[ mailman-Feature Requests-409071 ] Crypt/md5 change on the fly
by noreply＠sourceforge.net May 3, 2002

May 3, 2002

Feature Requests item #409071, was opened at 2001-03-16 05:06 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=409071&group_id… Category: None Group: None Status: Open >Resolution: Fixed Priority: 5 Submitted By: Karsten Thygesen (karthy) Assigned to: Nobody/Anonymous (nobody) Summary: Crypt/md5 change on the fly Initial Comment: Hi Pr. default, Mailman tries to use crypt if it is available, and if not, it uses md5. Fine. If an installation is using a python without crypt capability, mailman will be using md5, but if the python installation is changed and now supports crypt, mailman fails do validate any passwords. Suggestion: store the encryption method together with the crypted password, so that multiple encryption methods can be used at once. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:40 Message: Logged In: YES user_id=12800 MM2.1 never uses crypt or md5 -- it always uses sha. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=409071&group_id…

1 0

[ mailman-Feature Requests-410645 ] wish: change my email address across all
by noreply＠sourceforge.net May 3, 2002

May 3, 2002

Feature Requests item #410645, was opened at 2001-03-22 20:08 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=410645&group_id… Category: None Group: None >Status: Closed Resolution: Out of Date Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: wish: change my email address across all Initial Comment: I'm changing email addresses. Mailman already knows how to find all lists on a server that I'm subscribed to, which is very helpful. It would be even better if there was a way to update all these addresses in one go. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2001-08-04 10:34 Message: Logged In: YES user_id=12800 Mailman 2.1 will support this. ---------------------------------------------------------------------- Comment By: Andrew Shugg (yautja) Date: 2001-08-04 03:30 Message: Logged In: YES user_id=38234 Agreed, this would be an extremely useful feature. In fact I am surprised Mailman doesn't already allow it. How else can a subscriber change their address without going through a full unsubscribe/resubscribe process? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=410645&group_id…

1 0