From noreply@sourceforge.net Wed May 1 13:34:22 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 01 May 2002 05:34:22 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-214205 ] e-mail<->usenet gateway Reply-To header (PR#303) Message-ID: Bugs item #214205, was opened at 2000-09-11 22:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id=103 Category: nntp/news Group: None Status: Open Resolution: None Priority: 4 Submitted By: Nobody/Anonymous (nobody) Assigned to: Barry Warsaw (bwarsaw) Summary: e-mail<->usenet gateway Reply-To header (PR#303) Initial Comment: Jitterbug-Id: 303 Submitted-By: orion@tribble.dyndns.org Date: Mon, 24 Jul 2000 18:54:02 -0400 (EDT) Version: 2.0beta4 OS: Debian linux potato I'm running a plain e-mail<->usenet gateway. When someone replies to a usenet post through the list, his e-mail client sets an In-Reply-To: header instead of a Reply-To: header. This causes newsreaders to improperly thread messages. I inserted the following bit into Mailman/Handlers/ToUsenet.py at around line 82: # if the message is a reply to a previous post, change the header so # that newsreaders can thread it properly if msg.getheader('in-reply-to'): msg.headers.append('References: %s\n' % msg.getheader('in-reply-to')) del msg['in-reply-to'] I'm happy to say that this solved the problem. (before you laugh at me, take note that I never looked at python before.) ==================================================================== Audit trail: None ---------------------------------------------------------------------- Comment By: Giovanni Lopedote (giuans) Date: 2002-05-01 14:34 Message: Logged In: YES user_id=531451 What a coincidence! I had the same problem and I looked into the code, then modified it to work properly. The coincidence is that my patch is *identical* to yours. So, for sure it works :-) ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2000-09-27 23:00 Message: RFC 2076 says nothing about using In-Reply-To for news, so it might not be a bad idea to copy In-Reply-To to References when gating a message from mail to news. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2000-09-19 18:48 Message: This sounds like the email client in question is broken. Mine for example, correctly inserts References: headers and the news readers properly thread the messages. I'm not inclined to cater to broken email or news clients. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id=103 From noreply@sourceforge.net Wed May 1 21:43:33 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 01 May 2002 13:43:33 -0700 Subject: [Mailman-Developers] [ mailman-Patches-543945 ] easily disable display of sponsor Message-ID: logos Patches item #543945, was opened at 2002-04-15 00:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id=103 Category: Web UI Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) >Summary: easily disable display of sponsor logos Initial Comment: Creates a new boolean configuration variable in Defaults.py called DISABLE_SPONSOR_LOGOS (to be overridden in mm_cfg.py) which quickly disables display of sponsor logos. You no longer need to hack htmlformat.py. Patch is against version 2.0.8. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-01 16:43 Message: Logged In: YES user_id=12800 No file is attached. Did you forget to check the "upload & attach file" checkbox? Do you feel like porting your patch to MM2.1? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id=103 From noreply@sourceforge.net Wed May 1 21:47:01 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 01 May 2002 13:47:01 -0700 Subject: [Mailman-Developers] [ mailman-Patches-543945 ] easily disable display of sponsor Message-ID: logos Patches item #543945, was opened at 2002-04-15 00:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id=103 Category: Web UI Group: Mailman 2.0.x >Status: Closed Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) Summary: easily disable display of sponsor logos Initial Comment: Creates a new boolean configuration variable in Defaults.py called DISABLE_SPONSOR_LOGOS (to be overridden in mm_cfg.py) which quickly disables display of sponsor logos. You no longer need to hack htmlformat.py. Patch is against version 2.0.8. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-01 16:43 Message: Logged In: YES user_id=12800 No file is attached. Did you forget to check the "upload & attach file" checkbox? Do you feel like porting your patch to MM2.1? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id=103 From noreply@sourceforge.net Wed May 1 21:47:25 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 01 May 2002 13:47:25 -0700 Subject: [Mailman-Developers] [ mailman-Patches-543943 ] removes redundant " Patches item #543943, was opened at 2002-04-15 00:22 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543943&group_id=103 Category: Web UI Group: Mailman 2.0.x >Status: Closed Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) >Summary: removes redundant "Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-01 16:47 Message: Logged In: YES user_id=12800 No patch was attached. Is this still relevant for MM2.1? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543943&group_id=103 From noreply@sourceforge.net Wed May 1 21:50:04 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 01 May 2002 13:50:04 -0700 Subject: [Mailman-Developers] [ mailman-Patches-543945 ] easily disable display of sponsorlogos Message-ID: Patches item #543945, was opened at 2002-04-15 04:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id=103 Category: Web UI Group: Mailman 2.0.x Status: Closed Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) >Summary: easily disable display of sponsorlogos Initial Comment: Creates a new boolean configuration variable in Defaults.py called DISABLE_SPONSOR_LOGOS (to be overridden in mm_cfg.py) which quickly disables display of sponsor logos. You no longer need to hack htmlformat.py. Patch is against version 2.0.8. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-01 20:43 Message: Logged In: YES user_id=12800 No file is attached. Did you forget to check the "upload & attach file" checkbox? Do you feel like porting your patch to MM2.1? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id=103 From noreply@sourceforge.net Wed May 1 21:56:07 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 01 May 2002 13:56:07 -0700 Subject: [Mailman-Developers] [ mailman-Patches-543943 ] removes redundant " Patches item #543943, was opened at 2002-04-15 04:22 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543943&group_id=103 Category: Web UI Group: Mailman 2.0.x Status: Closed Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) >Summary: removes redundant "Comment By: Adi Fairbank (adifairbank) Date: 2002-05-01 20:56 Message: Logged In: YES user_id=515566 Sorry, I just attached the patch. Don't know if it's relevant for MM2.1.. I haven't installed that yet. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-01 20:47 Message: Logged In: YES user_id=12800 No patch was attached. Is this still relevant for MM2.1? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543943&group_id=103 From noreply@sourceforge.net Wed May 1 21:54:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 01 May 2002 13:54:55 -0700 Subject: [Mailman-Developers] [ mailman-Patches-543943 ] removes redundant " Patches item #543943, was opened at 2002-04-15 04:22 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543943&group_id=103 Category: Web UI Group: Mailman 2.0.x Status: Closed Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) >Summary: removes redundant " Patches item #413257, was opened at 2001-04-02 23:08 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=413257&group_id=103 Category: command line scripts Group: None >Status: Closed Resolution: None Priority: 5 Submitted By: Marc Merlin (marcmerlin) Assigned to: Nobody/Anonymous (nobody) Summary: patch to allow for mass unsubscribes Initial Comment: It allows you to unsubscribe Emails from all your mailing lists at once. I ran it on 10,000+ lists on sourceforge, and it ran in less than 10mn, which beats my wrapper shell script by one order of magnitude or two. (the patch adds a special list name '_alllists_') Here's what it looks like: usw-sf-list1:/var/local/mailman/bin# time ./remove_members -f /tmp/badmails _alllists_ User `gb@viscomvisual.com' removed from list `berlin-fresco' User `jprice@chiinc.com' removed from list `foxgui-announce' User `bmcgroarty@high-voltage.com' removed from list `freenet-announce' User `Wilhelm.Pastoors@vetmed.uni-giessen.de' removed from list `gump-develop' User `oscu@sina.com' removed from list `linux-usb-devel' User `mehdi-laurent.akkar@fr.delarue.com' removed from list `madchat-annonces' User `ras@colltech.com' removed from list `sendpage-devel' User `mkimball@pdi.com' removed from list `utah-glx-cvs' User `mkimball@pdi.com' removed from list `utah-glx-dev' User `mkimball@pdi.com' removed from list `utah-glx-users' User `brianp@pdi.com' removed from list `vacm-develop' User `guido@comlog.nl' removed from list `wxwindows-users' User `frekytah@jono.com' removed from list `solar-empire-developer' User `dan@dar.net' removed from list `xemacs-winnt' real 7m26.294s user 1m9.120s sys 1m10.640s ---------------------------------------------------------------------- >Comment By: Marc Merlin (marcmerlin) Date: 2002-05-01 20:57 Message: Logged In: YES user_id=6500 This was rewritten and integrated in mailman 2.1 cvs ---------------------------------------------------------------------- Comment By: Marc Merlin (marcmerlin) Date: 2001-12-12 17:11 Message: Logged In: YES user_id=6500 Ooops, wrong file. Uploading the real diff. ---------------------------------------------------------------------- Comment By: Marc Merlin (marcmerlin) Date: 2001-12-12 17:09 Message: Logged In: YES user_id=6500 New version of the patch against mailman cvs ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=413257&group_id=103 From noreply@sourceforge.net Wed May 1 21:58:17 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 01 May 2002 13:58:17 -0700 Subject: [Mailman-Developers] [ mailman-Patches-543945 ] easily disable display of sponsorlogos Message-ID: Patches item #543945, was opened at 2002-04-15 04:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id=103 Category: Web UI Group: Mailman 2.0.x Status: Closed Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) Summary: easily disable display of sponsorlogos Initial Comment: Creates a new boolean configuration variable in Defaults.py called DISABLE_SPONSOR_LOGOS (to be overridden in mm_cfg.py) which quickly disables display of sponsor logos. You no longer need to hack htmlformat.py. Patch is against version 2.0.8. ---------------------------------------------------------------------- >Comment By: Adi Fairbank (adifairbank) Date: 2002-05-01 20:58 Message: Logged In: YES user_id=515566 I will port the patch to 2.1 once I get a chance to upgrade. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-01 20:43 Message: Logged In: YES user_id=12800 No file is attached. Did you forget to check the "upload & attach file" checkbox? Do you feel like porting your patch to MM2.1? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id=103 From Dan Mick Wed May 1 23:05:27 2002 From: Dan Mick (Dan Mick) Date: Wed, 1 May 2002 15:05:27 -0700 (PDT) Subject: [Mailman-Developers] Prompt Enhancement Request. Message-ID: <200205012205.g41M5ubH004916@utopia.West.Sun.COM> Suggestions? It's always been pretty obvious to me, so I'm no good as a test case. > What would be the chance of enhancing the following text in the > membership modificiation page? > > I find a lot of people using this option to 'unsubscribe' from the > list. I think this would happen less often if there was a better > description with a pointer that this is not an unsubscribe function. > > ------------------- > > Disable mail delivery > > Turn this on if you want mail to not be delivered to you for a little > while. > > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers From noreply@sourceforge.net Wed May 1 22:54:16 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 01 May 2002 14:54:16 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-550314 ] Sending to multiple lists chooses one. Message-ID: Bugs item #550314, was opened at 2002-04-29 18:48 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550314&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jeff Posner (jposnersails) Assigned to: Nobody/Anonymous (nobody) Summary: Sending to multiple lists chooses one. Initial Comment: When I send a single message addressed as multiple lists on to 'TO:' line, each recipient receives exactly one copy. If a single user is a memeber of more than one list, he receives the copy to a "seemingly" random list. I am new to this version (just upgraded from 1.x) and have not seen this problem before. Thanks. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-01 21:54 Message: Logged In: YES user_id=10725 Just tested with close-to-current 2.1CVS; it works for me. Two test lists, one post with both lists on To: line, I get two copies as expected. What version are you running? It might be worth checking the archives to see if the message got to both places; maybe one list is broken. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550314&group_id=103 From Dan Mick Wed May 1 23:52:37 2002 From: Dan Mick (Dan Mick) Date: Wed, 1 May 2002 15:52:37 -0700 (PDT) Subject: [Mailman-Developers] Postfix instructions in 2.0.10's INSTALL Message-ID: <200205012253.g41Mr6bH008387@utopia.West.Sun.COM> 2.0.10's INSTALL file has this section: Problem: I use Postfix for my MTA and the mail wrapper programs are logging complaints about the wrong GID. Solution: Create a separate aliases file for Postfix in its main.cf config file under the variable "alias_maps". Put the file somewhere in Mailman's home directory, or somewhere else where the user mailman has write access to it; *as user mailman* call Postfix's "postalias" on the alias file. % postalias Also as user mailman, run % python -c'import os; print os.getgid()' This should print out the group id that Mailman should be configured to expect when the mail wrapper programs are run. Call it "thegid". Rebuild Mailman with % ./configure --with-mail-gid=thegid What is this supposed to do? "postalias " appears to simply create an alias.dir/alias.pag pair in that same directory, but not affect the Postfix delivery at all. Is this a Postfix version skew problem? Is it expected that postalias actually "installs" the aliases somehow? It doesn't seem like that's the case. (There was a question on mailman-users that prompted me to wonder what this meant.) From mrbill@mrbill.net Thu May 2 04:02:39 2002 From: mrbill@mrbill.net (Bill Bradford) Date: Wed, 1 May 2002 22:02:39 -0500 Subject: [Mailman-Developers] Postfix instructions in 2.0.10's INSTALL In-Reply-To: <200205012253.g41Mr6bH008387@utopia.West.Sun.COM> References: <200205012253.g41Mr6bH008387@utopia.West.Sun.COM> Message-ID: <20020502030239.GJ2196@mrbill.net> On Wed, May 01, 2002 at 03:52:37PM -0700, Dan Mick wrote: > What is this supposed to do? "postalias " > appears to simply create an alias.dir/alias.pag pair in that > same directory, but not affect the Postfix delivery at all. > Is this a Postfix version skew problem? Is it expected > that postalias actually "installs" the aliases somehow? > It doesn't seem like that's the case. You have to setup your /etc/postfix/main.cf like this: alias_maps = dbm:/etc/postfix/aliases, dbm:/usr/local/mailman/aliases.mailman alias_database = dbm:/etc/postfix/aliases, dbm:/usr/local/mailman/aliases.mailman Then, I just do "postalias aliases.mailman" when I change ~mailman/aliases.mailman Bill -- Bill Bradford | "Fear leads to anger. Anger leads to hate. mrbill@mrbill.net | Hate leads to using Windows for mission-critical Austin, TX | applications." -- What Yoda *meant* to say From barry@zope.com Thu May 2 04:14:53 2002 From: barry@zope.com (Barry A. Warsaw) Date: Wed, 1 May 2002 23:14:53 -0400 Subject: [Mailman-Developers] I bit the bullet Message-ID: <15568.44845.9043.598989@anthem.wooz.org> The MailCommandHandler.py module was just completely unmaintainable, so I bit the bullet and replaced it over the last several nights. The framework we've got now is much more extensible, flexible, and maintainable. Basically, each command is implemented in its own module inside the Mailman/Commands directory. You can add new commands by adding a file like cmd_.py to the directory. You can delete commands by removing the files (e.g. Marc might want to remove cmd_lists.py :). See the existing files for examples. Through some clever programming, you can limit commands on a per-list, per-domain, per-sender, or per-message basis. Now the only cruft left is Pipermail . Hopefully over the next several days, I can get back to answering mmdev email, fixing bugs and getting beta2 out. Please start to use the SF trackers for all bugs you find in MM2.1, and all patches against the MM2.1 codebase. My inbox is overflowing, and I'm afraid of missing important bugs and patches. Cheers, -Barry From barry@zope.com Thu May 2 04:17:56 2002 From: barry@zope.com (Barry A. Warsaw) Date: Wed, 1 May 2002 23:17:56 -0400 Subject: [Mailman-Developers] Postfix instructions in 2.0.10's INSTALL References: <200205012253.g41Mr6bH008387@utopia.West.Sun.COM> <20020502030239.GJ2196@mrbill.net> Message-ID: <15568.45028.903967.522454@anthem.wooz.org> >>>>> "BB" == Bill Bradford writes: | alias_maps = dbm:/etc/postfix/aliases, | dbm:/usr/local/mailman/aliases.mailman I usually use hash: files, but it doesn't matter much. I end up with aliases.db files, but either way it works. -Barry From barry@zope.com Thu May 2 04:52:14 2002 From: barry@zope.com (Barry A. Warsaw) Date: Wed, 1 May 2002 23:52:14 -0400 Subject: [Mailman-Developers] a bug? References: <20020429221943.GC2799@abulafia.casa> Message-ID: <15568.47086.816173.881767@anthem.wooz.org> >>>>> "SP" == Simone Piunno writes: SP> The site language of my installation is 'it'. Creating a new SP> list with the only permitted language as 'en' I have a list SP> with ['en','it'] (which makes sense) and the preferred SP> language marked as 'it', (which is wrong) It is (currently) not possible to create a list which doesn't support the site language, and the default language for a newly created list will always be the site language (although you can change this through the web). I'm not sure of the ramifications of changing this. -Barry From barry@zope.com Thu May 2 05:03:54 2002 From: barry@zope.com (Barry A. Warsaw) Date: Thu, 2 May 2002 00:03:54 -0400 Subject: [Mailman-Developers] I bit the bullet References: <15568.44845.9043.598989@anthem.wooz.org> Message-ID: <15568.47786.331566.59259@anthem.wooz.org> >>>>> "BAW" == Barry A Warsaw writes: BAW> The MailCommandHandler.py module was just completely BAW> unmaintainable, so I bit the bullet and replaced it over the BAW> last several nights. The framework we've got now is much BAW> more extensible, flexible, and maintainable. I forgot to mention that I've also taken the liberty of cleaning up the existing commands, and adding a new one or two. Although the new commands are close (some are unchanged), I don't plan on supporting backwards compatibility with the MM2.0 email command set. Please take a look at the new command set and let me know what you think. -Barry From barry@zope.com Thu May 2 05:08:08 2002 From: barry@zope.com (Barry A. Warsaw) Date: Thu, 2 May 2002 00:08:08 -0400 Subject: [Mailman-Developers] Uncaught runner exception: 'NoneType' object References: Message-ID: <15568.48040.291618.405593@anthem.wooz.org> >>>>> "tm" == totschnig michael writes: tm> an error related to NoneType objects having no attributes has tm> already been reported on this list. I get such an error only tm> when I create a new list, only the mail sent to mailman-owner tm> enumerating the new aliases to add seems to get caught in tm> this. Should I test the patch Barry sent in message tm> <15534.7944.843739.720556@anthem.wooz.org> to solve this tm> problem? My MTA is sendmail. Thanks, Michael This is fixed in cvs now. It only happens when you create new lists through the web and you've got the following in your mm_cfg.py (or use the default): MTA = 'Manual' -Barry From barry@zope.com Thu May 2 05:16:21 2002 From: barry@zope.com (Barry A. Warsaw) Date: Thu, 2 May 2002 00:16:21 -0400 Subject: [Mailman-Developers] Prompt Enhancement Request. References: Message-ID: <15568.48533.248915.573843@anthem.wooz.org> >>>>> "PB" == Phil Barnett writes: PB> What would be the chance of enhancing the following text in PB> the membership modificiation page? PB> I find a lot of people using this option to 'unsubscribe' from PB> the list. I think this would happen less often if there was a PB> better description with a pointer that this is not an PB> unsubscribe function. PB> Disable mail delivery PB> Turn this on if you want mail to not be delivered to you for a PB> little while. Note that in MM2.1, it reads: Mail delivery Set this option to Enabled to receive messages posted to this mailing list. Set it to Disabled if you don't want mail delivered to you for a while (i.e. you're going on vacation). If you disable mail delivery, don't forget to come back after your vacation to re-enable it! Is that better? Good enough? -Barry From noreply@sourceforge.net Thu May 2 06:52:14 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 01 May 2002 22:52:14 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-550314 ] Sending to multiple lists chooses one. Message-ID: Bugs item #550314, was opened at 2002-04-29 11:48 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550314&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jeff Posner (jposnersails) Assigned to: Nobody/Anonymous (nobody) Summary: Sending to multiple lists chooses one. Initial Comment: When I send a single message addressed as multiple lists on to 'TO:' line, each recipient receives exactly one copy. If a single user is a memeber of more than one list, he receives the copy to a "seemingly" random list. I am new to this version (just upgraded from 1.x) and have not seen this problem before. Thanks. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-05-01 22:52 Message: Logged In: NO If your users run Cyrus, or some similar mail system, messages with duplicate message-IDs are only stored once. This may, or may not, be relevant. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-01 14:54 Message: Logged In: YES user_id=10725 Just tested with close-to-current 2.1CVS; it works for me. Two test lists, one post with both lists on To: line, I get two copies as expected. What version are you running? It might be worth checking the archives to see if the message got to both places; maybe one list is broken. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550314&group_id=103 From noreply@sourceforge.net Thu May 2 10:17:00 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 02:17:00 -0700 Subject: [Mailman-Developers] [ mailman-Patches-551327 ] Makefile fix so that errors propagate Message-ID: 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=103 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. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=551327&group_id=103 From noreply@sourceforge.net Thu May 2 15:27:43 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 07:27:43 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-540978 ] eMailadress too long ? Message-ID: Bugs item #540978, was opened at 2002-04-08 14:56 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=540978&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Markus Mandalka (mandalka) Assigned to: Nobody/Anonymous (nobody) Summary: eMailadress too long ? Initial Comment: I have a list antiatomforum@lists.kommunikationssystem.de and others with long names. It seems that mailman can not handle with such long names, because in the subscribe-mail (which you have to answer to be in the list) the first columns are some things from the header (unsubscribe: xxx@lists.xxx and so on). Whith names like atest@lists.kommunikationssystem.de it works. ---------------------------------------------------------------------- Comment By: Giovanni Lopedote (giuans) Date: 2002-05-02 16:27 Message: Logged In: YES user_id=531451 I've found it. A fast fix for is to comment lines 149-150 in Mailman/Handlers:/CookHeaders.py: --- CookHeaders.py 2002-05-02 14:51:36.000000000 +0200 +++ CookHeaders.py.new 2002-05-02 16:12:09.000000000 +0200 @@ -146,8 +146,8 @@ # Wrap these lines if they are too long. 78 character width probably # shouldn't be hardcoded, but is at least text-MUA friendly. The # adding of 2 is for the colon-space separator. - if len(h) + 2 + len(v) > 78: - v = CONTINUATION.join(v.split(', ')) +# if len(h) + 2 + len(v) > 78: +# v = CONTINUATION.join(v.split(', ')) msg[h] = v # Always delete List-Archive header, but only add it back if the list is # actually archiving Tested with Mailman 2.1b1, Source Mage GNU/Linux 2.4.18, Postfix 1.1.7. I know there should be a better way, but I'm not a Python programmer at all. :) ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-12 00:03 Message: Logged In: YES user_id=12800 I've confirmed this bug, but don't have a fix for it right now. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=540978&group_id=103 From terri@zone12.com Thu May 2 19:59:34 2002 From: terri@zone12.com (Terri Oda) Date: Thu, 02 May 2002 14:59:34 -0400 Subject: [Mailman-Developers] Prompt Enhancement Request. In-Reply-To: <15568.48533.248915.573843@anthem.wooz.org> References: Message-ID: <5.1.0.14.0.20020502145810.03238b70@pop.ncf.carleton.ca> At 12:16 AM 02/05/02 -0400, Barry A. Warsaw wrote: >Note that in MM2.1, it reads: > > Mail delivery > > Set this option to Enabled to receive messages posted to this mailing > list. Set it to Disabled if you don't want mail delivered to you for a > while (i.e. you're going on vacation). If you disable mail delivery, > don't forget to come back after your vacation to re-enable it! > >Is that better? Good enough? I think it's good enough, but I'd say "Set it to Disabled if you want to stay subscribed but don't want mail delivered to you..." just to be sure. Terri From barry@zope.com Thu May 2 21:24:47 2002 From: barry@zope.com (Barry A. Warsaw) Date: Thu, 2 May 2002 16:24:47 -0400 Subject: [Mailman-Developers] Prompt Enhancement Request. References: <5.1.0.14.0.20020502145810.03238b70@pop.ncf.carleton.ca> Message-ID: <15569.41103.21873.674764@anthem.wooz.org> >>>>> "TO" == Terri Oda writes: TO> I think it's good enough, but I'd say "Set it to Disabled if TO> you want to stay subscribed but don't want mail delivered to TO> you..." just to be sure. Thanks for the suggestions. -Barry From Dan Mick Thu May 2 21:40:20 2002 From: Dan Mick (Dan Mick) Date: Thu, 2 May 2002 13:40:20 -0700 (PDT) Subject: [Mailman-Developers] Postfix instructions in 2.0.10's INSTALL Message-ID: <200205022040.g42KepbH006339@utopia.West.Sun.COM> > On Wed, May 01, 2002 at 03:52:37PM -0700, Dan Mick wrote: > > What is this supposed to do? "postalias " > > appears to simply create an alias.dir/alias.pag pair in that > > same directory, but not affect the Postfix delivery at all. > > Is this a Postfix version skew problem? Is it expected > > that postalias actually "installs" the aliases somehow? > > It doesn't seem like that's the case. > > You have to setup your /etc/postfix/main.cf like this: > > alias_maps = dbm:/etc/postfix/aliases, > dbm:/usr/local/mailman/aliases.mailman > > alias_database = dbm:/etc/postfix/aliases, > dbm:/usr/local/mailman/aliases.mailman > > Then, I just do "postalias aliases.mailman" when I change > ~mailman/aliases.mailman Well, that makes sense, but without that extra bit of "alias_maps" configuration, the Problem/Solution as written doesn't make much sense. I'm sure it's fixed for 2.1 with the README.POSTFIX file, but 2.0.10 users are rightfully confused by that entry. Also, INSTALL in 2.1 has that partially-useful Problem/Solution entry; even though it has been updated to point to README.POSTFIX, it probably shouldn't come off like it solves that problem. From barry@zope.com Fri May 3 02:49:08 2002 From: barry@zope.com (Barry A. Warsaw) Date: Thu, 2 May 2002 21:49:08 -0400 Subject: [Mailman-Developers] Postfix instructions in 2.0.10's INSTALL References: <200205022040.g42KepbH006339@utopia.West.Sun.COM> Message-ID: <15569.60564.641793.121150@anthem.wooz.org> >>>>> "DM" == Dan Mick writes: DM> I'm sure it's fixed for 2.1 with the README.POSTFIX file, but DM> 2.0.10 users are rightfully confused by that entry. DM> Also, INSTALL in 2.1 has that partially-useful DM> Problem/Solution entry; even though it has been updated to DM> point to README.POSTFIX, it probably shouldn't come off like DM> it solves that problem. As soon as I release 2.1b2 I'm going to create a mailman-docs mailing list for folks who want to help improve the documentation. I personally want to spend some time creating a real Texinfo manual, rewriting the mass of READMEs and producing a much better web site. Volunteers will, of course, be welcome! -Barry From noreply@sourceforge.net Fri May 3 02:54:26 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 18:54:26 -0700 Subject: [Mailman-Developers] [ mailman-Patches-551327 ] Makefile fix so that errors propagate Message-ID: Patches item #551327, was opened at 2002-05-02 05:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=551327&group_id=103 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: Barry Warsaw (bwarsaw) Date: 2002-05-02 21: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=103 From noreply@sourceforge.net Fri May 3 04:15:37 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 20:15:37 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-550524 ] archiving with invalid dates Message-ID: Bugs item #550524, was opened at 2002-04-30 07:58 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550524&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Michael Kallas (valshaq) Assigned to: Nobody/Anonymous (nobody) Summary: archiving with invalid dates Initial Comment: If you look at http://mail.gnu.org/mailman/listinfo/help-hurd you'll notice there are mails archived into future archives (because of faked timestamps). I think this should not happen, either deleting it instead (SPAM) or archiving it into the current archive. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-03 03:15 Message: Logged In: YES user_id=10725 The list item clobber_date has been present in Mailman for a very long time, to address this issue. There's a GUI item for it. Have you experimented with setting clobber_date? Or alternatively, if you're using 2.1, see settings in Defaults.py about dates in archives. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550524&group_id=103 From noreply@sourceforge.net Fri May 3 04:18:11 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 20:18:11 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-517192 ] 2.0.8 borks on dot in local part of addr Message-ID: Bugs item #517192, was opened at 2002-02-13 21:20 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: Out of Date Priority: 5 Submitted By: CrackMonkey (monkeymaster) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0.8 borks on dot in local part of addr Initial Comment: In a mail address's local part (the part to the left of the at sign), it is perfectly valid to have periods. However, mailman stops reading the address right at the @, so that "mr.bad@pigdog.org" is shown as "mr.bad". this is disastrous for lists where only subscribers are allowed to post, since the system doesn't allow for exceptions that lack an @ and a FQDN. Either allowing exceptions to be of a more forgiving format, or fixing the broken regex that truncates the mail addresses would solve my problem. I'm getting tired of moderating a legitimate user's posts, especially since the system won't even send the warnings to the correct address. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-03 03:18 Message: Logged In: YES user_id=10725 I can echo that Python 2.2 doesn't have the parseaddr problem. monkeymaster, can you try Barry's two-line experiment and see if that works or fails? ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-29 22:21 Message: Logged In: YES user_id=76237 This happens even when I use python 2.2 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-27 16:34 Message: Logged In: YES user_id=12800 This is really a bug with earlier versions of Python, I believe. MM2.0.x uses the standard library function rfc822.parseaddr() to break and address into its realname + email constituent parts. Here are some examples: % python Python 2.2.1 (#1, Apr 22 2002, 17:14:12) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('Mr. Bad', 'mr.bad@pigdog.org') % python2.1 Python 2.1.3 (#1, Apr 22 2002, 18:17:38) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('', 'Mr.Bad') So this is clearly broken in Python 2.1.3, and works in Python 2.2.1. I'll look at backporting the fix to Python 2.1 in case there's ever a 2.1.4. But if you're using an earlier version of Python, this will still be broken. Consider upgrading to Python 2.2.1. ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-26 19:54 Message: Logged In: YES user_id=76237 The bug turns out not to be when there is a period in the address, but in the plain text name. The mail address in question is: Mr. Bad I realized this when I saw people who had different text names from their e-mail addresses, as in: Jr. Pickle This would show up as the mythical address "jr.pickle" in mailman, and things would b0rk. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-03-14 19:18 Message: Logged In: YES user_id=12800 Either I need more information, or this problem is fixed in MM2.1. Quite often I uses test addresses like "barry.warsaw@" and I've had no problems with it. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 From bob@nleaudio.com Fri May 3 05:07:27 2002 From: bob@nleaudio.com (bob@nleaudio.com) Date: Fri, 3 May 2002 00:07:27 -0400 (EDT) Subject: [Mailman-Developers] Postfix instructions in 2.0.10's INSTALL Message-ID: <20020503040727.2ADE313D127@main.nlenet.net> This is a MIME-encapsulated message. --------------526765244746288680126959 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Actually, alias_database only appears to affect the "newaliases" command, and really isn't needed for what Mailman is doing, as I believe Mailman is using the "postalias" command to create the .db file, isn't it? Bob > >> On Wed, May 01, 2002 at 03:52:37PM -0700, Dan Mick wrote: >> > What is this supposed to do? "postalias " >> > appears to simply create an alias.dir/alias.pag pair in that >> > same directory, but not affect the Postfix delivery at all. >> > Is this a Postfix version skew problem? Is it expected >> > that postalias actually "installs" the aliases somehow? >> > It doesn't seem like that's the case. >> >> You have to setup your /etc/postfix/main.cf like this: >> >> alias_maps = dbm:/etc/postfix/aliases, >> dbm:/usr/local/mailman/aliases.mailman >> >> alias_database = dbm:/etc/postfix/aliases, >> dbm:/usr/local/mailman/aliases.mailman >> >> Then, I just do "postalias aliases.mailman" when I change >> ~mailman/aliases.mailman > >Well, that makes sense, but without that extra bit of "alias_maps" >configuration, the Problem/Solution as written doesn't make >much sense. > >I'm sure it's fixed for 2.1 with the README.POSTFIX file, but 2.0.10 >users are rightfully confused by that entry. > >Also, INSTALL in 2.1 has that partially-useful Problem/Solution >entry; even though it has been updated to point to README.POSTFIX, >it probably shouldn't come off like it solves that problem. > > > >_______________________________________________ >Mailman-Developers mailing list >Mailman-Developers@python.org >http://mail.python.org/mailman/listinfo/mailman-developers > --------------526765244746288680126959-- From noreply@sourceforge.net Fri May 3 05:07:43 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 21:07:43 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-517192 ] 2.0.8 borks on dot in local part of addr Message-ID: Bugs item #517192, was opened at 2002-02-13 16:20 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: Out of Date Priority: 5 Submitted By: CrackMonkey (monkeymaster) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0.8 borks on dot in local part of addr Initial Comment: In a mail address's local part (the part to the left of the at sign), it is perfectly valid to have periods. However, mailman stops reading the address right at the @, so that "mr.bad@pigdog.org" is shown as "mr.bad". this is disastrous for lists where only subscribers are allowed to post, since the system doesn't allow for exceptions that lack an @ and a FQDN. Either allowing exceptions to be of a more forgiving format, or fixing the broken regex that truncates the mail addresses would solve my problem. I'm getting tired of moderating a legitimate user's posts, especially since the system won't even send the warnings to the correct address. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 00:07 Message: Logged In: YES user_id=12800 BTW, I'm attaching the patch to Python 2.1.3's rfc822.py that I plan on checking in momentarily. This backports the Python 2.2.1 patch for the problem, and with this, my 2-line example below also succeeds for Python 2.1.3. If there's ever a Python 2.1.4, this patch will be part of it. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-02 23:18 Message: Logged In: YES user_id=10725 I can echo that Python 2.2 doesn't have the parseaddr problem. monkeymaster, can you try Barry's two-line experiment and see if that works or fails? ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-29 18:21 Message: Logged In: YES user_id=76237 This happens even when I use python 2.2 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-27 12:34 Message: Logged In: YES user_id=12800 This is really a bug with earlier versions of Python, I believe. MM2.0.x uses the standard library function rfc822.parseaddr() to break and address into its realname + email constituent parts. Here are some examples: % python Python 2.2.1 (#1, Apr 22 2002, 17:14:12) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('Mr. Bad', 'mr.bad@pigdog.org') % python2.1 Python 2.1.3 (#1, Apr 22 2002, 18:17:38) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('', 'Mr.Bad') So this is clearly broken in Python 2.1.3, and works in Python 2.2.1. I'll look at backporting the fix to Python 2.1 in case there's ever a 2.1.4. But if you're using an earlier version of Python, this will still be broken. Consider upgrading to Python 2.2.1. ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-26 15:54 Message: Logged In: YES user_id=76237 The bug turns out not to be when there is a period in the address, but in the plain text name. The mail address in question is: Mr. Bad I realized this when I saw people who had different text names from their e-mail addresses, as in: Jr. Pickle This would show up as the mythical address "jr.pickle" in mailman, and things would b0rk. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-03-14 14:18 Message: Logged In: YES user_id=12800 Either I need more information, or this problem is fixed in MM2.1. Quite often I uses test addresses like "barry.warsaw@" and I've had no problems with it. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 From noreply@sourceforge.net Fri May 3 05:08:44 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 21:08:44 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-517192 ] 2.0.8 borks on dot in local part of addr Message-ID: Bugs item #517192, was opened at 2002-02-13 16:20 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: Out of Date Priority: 5 Submitted By: CrackMonkey (monkeymaster) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0.8 borks on dot in local part of addr Initial Comment: In a mail address's local part (the part to the left of the at sign), it is perfectly valid to have periods. However, mailman stops reading the address right at the @, so that "mr.bad@pigdog.org" is shown as "mr.bad". this is disastrous for lists where only subscribers are allowed to post, since the system doesn't allow for exceptions that lack an @ and a FQDN. Either allowing exceptions to be of a more forgiving format, or fixing the broken regex that truncates the mail addresses would solve my problem. I'm getting tired of moderating a legitimate user's posts, especially since the system won't even send the warnings to the correct address. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 00:08 Message: Logged In: YES user_id=12800 monkeymaster, please try the patch, or include a Python 2.2.1 session that shows the bug still exists. I believe this bug report should be marked closed. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 00:07 Message: Logged In: YES user_id=12800 BTW, I'm attaching the patch to Python 2.1.3's rfc822.py that I plan on checking in momentarily. This backports the Python 2.2.1 patch for the problem, and with this, my 2-line example below also succeeds for Python 2.1.3. If there's ever a Python 2.1.4, this patch will be part of it. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-02 23:18 Message: Logged In: YES user_id=10725 I can echo that Python 2.2 doesn't have the parseaddr problem. monkeymaster, can you try Barry's two-line experiment and see if that works or fails? ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-29 18:21 Message: Logged In: YES user_id=76237 This happens even when I use python 2.2 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-27 12:34 Message: Logged In: YES user_id=12800 This is really a bug with earlier versions of Python, I believe. MM2.0.x uses the standard library function rfc822.parseaddr() to break and address into its realname + email constituent parts. Here are some examples: % python Python 2.2.1 (#1, Apr 22 2002, 17:14:12) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('Mr. Bad', 'mr.bad@pigdog.org') % python2.1 Python 2.1.3 (#1, Apr 22 2002, 18:17:38) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('', 'Mr.Bad') So this is clearly broken in Python 2.1.3, and works in Python 2.2.1. I'll look at backporting the fix to Python 2.1 in case there's ever a 2.1.4. But if you're using an earlier version of Python, this will still be broken. Consider upgrading to Python 2.2.1. ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-26 15:54 Message: Logged In: YES user_id=76237 The bug turns out not to be when there is a period in the address, but in the plain text name. The mail address in question is: Mr. Bad I realized this when I saw people who had different text names from their e-mail addresses, as in: Jr. Pickle This would show up as the mythical address "jr.pickle" in mailman, and things would b0rk. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-03-14 14:18 Message: Logged In: YES user_id=12800 Either I need more information, or this problem is fixed in MM2.1. Quite often I uses test addresses like "barry.warsaw@" and I've had no problems with it. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 From barry@zope.com Fri May 3 05:21:38 2002 From: barry@zope.com (Barry A. Warsaw) Date: Fri, 3 May 2002 00:21:38 -0400 Subject: [Mailman-Developers] Postfix instructions in 2.0.10's INSTALL References: <20020503040727.2ADE313D127@main.nlenet.net> Message-ID: <15570.4178.463394.448190@anthem.wooz.org> >>>>> "bob" == writes: bob> Actually, alias_database only appears to affect the bob> "newaliases" command, and really isn't needed for what bob> Mailman is doing, as I believe Mailman is using the bob> "postalias" command to create the .db file, isn't it? In MM2.1, yes that's correct. -Barry From noreply@sourceforge.net Fri May 3 05:40:28 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 21:40:28 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-550524 ] archiving with invalid dates Message-ID: Bugs item #550524, was opened at 2002-04-30 03:58 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550524&group_id=103 Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Michael Kallas (valshaq) Assigned to: Nobody/Anonymous (nobody) Summary: archiving with invalid dates Initial Comment: If you look at http://mail.gnu.org/mailman/listinfo/help-hurd you'll notice there are mails archived into future archives (because of faked timestamps). I think this should not happen, either deleting it instead (SPAM) or archiving it into the current archive. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 00:40 Message: Logged In: YES user_id=12800 Dan's right, there are knobs you can twiddle so this doesn't happen. Thanks Dan! ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-02 23:15 Message: Logged In: YES user_id=10725 The list item clobber_date has been present in Mailman for a very long time, to address this issue. There's a GUI item for it. Have you experimented with setting clobber_date? Or alternatively, if you're using 2.1, see settings in Defaults.py about dates in archives. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550524&group_id=103 From noreply@sourceforge.net Fri May 3 06:03:51 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:03:51 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-548321 ] Listproc archive to Mailman Conversion Message-ID: Feature Requests item #548321, was opened at 2002-04-24 17:15 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=548321&group_id=103 Category: None Group: None >Status: Closed Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Listproc archive to Mailman Conversion Initial Comment: Is it possible. we have a listproc archive and we would like to convert it to mailman format. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:03 Message: Logged In: YES user_id=12800 If the listproc archive is in Unix mailbox format then yes. If it's in a different format recognized by Python mailbox module then it might be possible with a little bit of Python hacking. As it is, this question is better asked on the mailman-users@python.org mailing list. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=548321&group_id=103 From noreply@sourceforge.net Fri May 3 06:07:04 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:07:04 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-224058 ] Wishlist: New Header X-Subscribed-as: Message-ID: Feature Requests item #224058, was opened at 2000-12-01 11:56 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=224058&group_id=103 Category: mail delivery Group: None >Status: Closed >Resolution: Out of Date Priority: 3 Submitted By: Eduardo Marcel Maçan (emacan) Assigned to: Nobody/Anonymous (nobody) Summary: Wishlist: New Header X-Subscribed-as: Initial Comment: I run a very busy and large list with mailman and frequently face the following problem: Many people subscribe using and e-mail redirector, or changes jobs/provider leaving a mail redirection in the former address. When the new mailbox is full, or worst, when it is not valid anymore we get e-mails bouncing from an Address not subscribed to the list. The offending address cannot be taken care automatically by mailman, and most of the times the list administrator cannot find it by using list_members or by browsing logs, because he does not necessarily has access to the server running his mailing list (Browsing all users in the web interface is not effective in this case, specially for large mailing lists). Other similar situation is that some large ISPs use internal e-mail routing rules to map address@somewhere.com to things like user1342@state.somewhere.com for an example, and errors usually return to list-admin in the second form. By using a header similar to X-Subscribed-as: email@somewhere.com in the message headers we could easily identify such offending e-mails, and maybe even take actions automatically. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:07 Message: Logged In: YES user_id=12800 Mailman 2.1 will (optionally) support verp and personalized messages. Yes, it increases the load on the mail server. With verp/personalization enabled, MM2.1 does not add a separate X-Subscribed-As: header, but I also don't think it's necessary, since the subscribed address is encoded in the envelope sender, so it should always be extractable both automatically and manually. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-10-06 08:22 Message: Logged In: NO The thing about the incerased Load is only partly true. On the one Hand qmail threads a message to several people already as several seperate messages at least concerning SMTP handling, on the other hand a lot of features whished for mailman really really need per subscriber messages. * VERP * Easy unsubscribe * Customized Messages , "Dear Mx. X," --drt@un.bewaff.net ---------------------------------------------------------------------- Comment By: Cord Beermann (cord) Date: 2001-08-16 15:43 Message: Logged In: YES user_id=50101 If you don't want to add such a header it would be nice if Mailman sends one bounce through to the List-admin, so he/she can deal with it. Yet there are only log-entries which can only be vied by someone with an acoount on the computer. Cord ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2001-02-26 03:25 Message: Logged In: YES user_id=34209 The problem with this is that it requires sending each message seperately. Mailman currently does it in bulk, which for big lists greatly (and I mean *greatly*) reduces the load on both the Mailman machine and the SMTP server that it uses, not to mention mailservers that host a lot of the subscribers to that list. Still, might be worth doing optionally, if both the site owner and the list owner (and possibly the subscriber themselves, though maybe not :) enable it. (Not a mailman developer, just a user giving his opinion ;) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=224058&group_id=103 From noreply@sourceforge.net Fri May 3 06:18:57 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:18:57 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-537022 ] Requesting email not attached in confirmation message Message-ID: Feature Requests item #537022, was opened at 2002-03-30 00:59 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=537022&group_id=103 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ben Bucksch (benb) Assigned to: Nobody/Anonymous (nobody) Summary: Requesting email not attached in confirmation message Initial Comment: When somebody requests to be signed up to a mailing list, there's a comformation message sent out to the email address being (in the process of being) subscribed. However, it seems like mailman doesn't include the IP address and timestamp of the user trying to sign up the email address. This information is critical in case somebody else tried to subscribe you without your consent (i.e. the whole point of the confirmation messages). In our case, somebody tries to sign up the public Mozilla mailing lists to other mailing lists. Since the lists are public, the confirmation messages are mostly useless. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:18 Message: Logged In: YES user_id=12800 Actually, with the freshly rewritten command handler, you now get a copy of your original request. However, it doesn't come with the confirmation message, it comes with a results notification of your original request. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-03 19:00 Message: Logged In: YES user_id=12800 I'm moving this to the feature request tracker. It may or may not make it into MM2.1 ---------------------------------------------------------------------- Comment By: Ben Bucksch (benb) Date: 2002-04-02 01:04 Message: Logged In: YES user_id=1193 OK. You say "when using the web to make a subscription request". I just tried to subscribe to your mailman-announce list (which is run by Mailman 2.0.8) via *email*, and it just includes the From address. That's of course useless, as that can be forged trivially. IMO, including the full subscription message, esp. headers, would be needed. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-02 00:35 Message: Logged In: YES user_id=12800 Uh, yeah! Mailman 1.1 is really old. ---------------------------------------------------------------------- Comment By: Ben Bucksch (benb) Date: 2002-04-02 00:34 Message: Logged In: YES user_id=1193 I have a subscription message (caused by an attacker) here, sent from Mailman 1.1. I guess you fixed it in the meantime? ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-01 16:06 Message: Logged In: YES user_id=12800 When using the web to make a subscription request, the confirmation message does indeed include the IP address of the browser client, as provided in the cgi environment. It's true that the timestampe isn't given, although I'm unsure how useful that would be given that the Date: on the confirmation message is probably pretty close. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=537022&group_id=103 From noreply@sourceforge.net Fri May 3 06:21:43 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:21:43 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-534234 ] Automatic RSS feed generation Message-ID: Feature Requests item #534234, was opened at 2002-03-24 00:12 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=534234&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rob Lanphier (robla) Assigned to: Nobody/Anonymous (nobody) Summary: Automatic RSS feed generation Initial Comment: It would be really great to have an automatic RSS feed as a result of using Mailman archiving. More info on RSS: http://purl.org/rss/1.0/ http://directory.google.com/Top/Reference/Libraries/Library_and_Information_Science/Technical_Services/Cataloguing/Metadata/Resource_Description_Framework_-_RDF/Applications/RSS/ RSS Validator: http://aggregator.userland.com/validator ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:21 Message: Logged In: YES user_id=12800 Care to submit a patch? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=534234&group_id=103 From noreply@sourceforge.net Fri May 3 06:22:40 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:22:40 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-536172 ] bounce processing exceptions Message-ID: Feature Requests item #536172, was opened at 2002-03-28 05:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=536172&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Seb Wills (sebwills) Assigned to: Nobody/Anonymous (nobody) Summary: bounce processing exceptions Initial Comment: It would be useful to have a configurable list of addresses for which bounce processing is not attempted (i.e. bounce messages relating to those list members go to the list owner). This would be useful in two situations: (a) there are some really important addresses for which the list manager definitely wants to know if there is a delivery failure (e.g. addresses used for list archiving). (b) from the bounce log the list owner notices some addresses behaving strangely and wants to check out exactly what the bounce messages say. [A different feature - optional logging of, say, the first 30 lines of all bounce messages, would also be useful for situation (b).] ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:22 Message: Logged In: YES user_id=12800 It's a good idea, care to work out a patch? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=536172&group_id=103 From noreply@sourceforge.net Fri May 3 06:24:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:24:55 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-527143 ] button for "discard all" Message-ID: Feature Requests item #527143, was opened at 2002-03-07 15:48 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=527143&group_id=103 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Sjoerd Mullender (sjoerd) Assigned to: Nobody/Anonymous (nobody) >Summary: button for "discard all" Initial Comment: It would be very nice if there were a button to select the Discard checkmark on all held messages on the administrative requests page for a mailing list. This button should just check all messages but not yet submit. I often go through the list for the python-list, and invariably I have to discard 90% to 100% of the messages, but it is a pain to do when there are 20 or so messages. It is much easier if they are all already checked to be discarded after which I can approve/reject the ones that need to be approved/rejected. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:24 Message: Logged In: YES user_id=12800 Hmm, MM2.1 has a summary overview of held messages, sorted by author. I think (although it hasn't gotten a lot of practical experience) that this will solve most of the problems with the admindb interface, which I agree can be painful. The new admindb page is also integrated with the sender filters so you can immediately and permanently discard (and ban!) postings from known spammers. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=527143&group_id=103 From noreply@sourceforge.net Fri May 3 06:25:56 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:25:56 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-511857 ] custom reminder intervals per user Message-ID: Feature Requests item #511857, was opened at 2002-02-01 14:38 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=511857&group_id=103 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Len Lattanzi (zardoz) Assigned to: Nobody/Anonymous (nobody) Summary: custom reminder intervals per user Initial Comment: Allow user to set password reminder interval[or limit reminders to no more frequent than posts for low traffic lists like security-announce@lists.apple.com] ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:25 Message: Logged In: YES user_id=12800 In MM2.1, members can turn off their password reminders altogether, and only get them when they explicitly ask for them. I think this will be good enough. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=511857&group_id=103 From noreply@sourceforge.net Fri May 3 06:27:26 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:27:26 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-502278 ] Handle multipart e-mails Message-ID: Feature Requests item #502278, was opened at 2002-01-11 07:04 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=502278&group_id=103 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Handle multipart e-mails Initial Comment: Dear developers, There are 2 weeks since I'm trying to fix a bug in Mailman. The ISP I work for, has some mailing lists, managed by Mailman, and most of subscribers, are sending mails through Windows (especially M$ Outlook). As known, Outlook sends every e-mail using multipart e-mail format, something that Mailman doesn't manage well. The bug is that when MaiLman tries to put a header & footer to the message's body. When the mail's content type is text/plain, then everything is ok. But when it is multipart/*, header & footer are positioned to wrong place. The worst case is when sending an multipart e-mail with attachements!! I'm trying 2 weeks to fix the problem (I think I found it), but I would like to inform you about this bug (if you didn't already know about it :-), and ask you a few questions: - It is in your plans to fix this bug in the near future? (e.g. in version 2.1?) - I want to add to header, the recipient's name. Is there a variable for that? e.g. %(recipient) - If not how could I add such info to header? I also send you an attachement (replaces Devorate.py) which fixes the above bug, but it is not secure enough & well tested. However it might help you fix the bug. Thanks a lot, Paschalis Pagonidis (ppag@dsg.internet.gr) Systems Engineer Internet Hellas www.internet.gr Hellas (Greece) ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:27 Message: Logged In: YES user_id=12800 All this has been completely rewritten for MM2.1, and I believe this specific case is now fixed. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=502278&group_id=103 From noreply@sourceforge.net Fri May 3 06:28:01 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:28:01 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-499232 ] MIME/HTML filter Message-ID: Feature Requests item #499232, was opened at 2002-01-03 22:09 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=499232&group_id=103 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: MIME/HTML filter Initial Comment: It sure would be nice to have an integrated MIME/HTML/attachment filter for the list and archives. I'm looking at installing deMime now, but it'd be *real* nice to have this ability as an administrative option rather than having to add a patch or pipe. Thanks! ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:28 Message: Logged In: YES user_id=12800 MM2.1 has this feature, called "content filters". ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-01-17 14:59 Message: Logged In: NO I totally agree to you! Denying attachment is one of the most important options of a mailing list in my opinion. Please, do this soon :-)! Winfried ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=499232&group_id=103 From noreply@sourceforge.net Fri May 3 06:29:42 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:29:42 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-491809 ] separate send and recieve addresses Message-ID: Feature Requests item #491809, was opened at 2001-12-11 18:22 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=491809&group_id=103 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Stig Hackvan (hackvan) Assigned to: Nobody/Anonymous (nobody) Summary: separate send and recieve addresses Initial Comment: problematic situation: lists are subscribed as user-listname@site.org (qmail-ish syntax) or user+listname@site.org (postfix-ish syntax) but mail to the lists is sent from user@site.org and it bounces to the moderator. this is silly. solution(1): automatically grok address permutations from qmail-extension and postfix+extension address styles. solution(2): add a preferences option for separate in & outbound addresses ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:29 Message: Logged In: YES user_id=12800 Closing this because 1) the solution for MM2.1 will probably be good enough for now, and 2) I know how to really do this right for MM3, but that's a long ways off. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-05 01:24 Message: Logged In: YES user_id=12800 Moving this to feature requests tracker. The idea is that MM3 will allow a user to attach multiple addresses to their account, so that a posting from any of those addresses is enough to satisfy the "must be a member" test. In the short term, MM2.1 will allow the admin to add the extended addresses to a "accept these non-members" list so that while they'll still be held for moderation once, they can be cleared for subsequent postings. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=491809&group_id=103 From noreply@sourceforge.net Fri May 3 06:36:58 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:36:58 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-455064 ] Use MTA on external machine via SMTP Message-ID: Feature Requests item #455064, was opened at 2001-08-24 15:20 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=455064&group_id=103 Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Use MTA on external machine via SMTP Initial Comment: I know this is possible. However, do you feel it would be beneficial to allow for MTA's on external machines to handle incoming and outgoing emails to any of the hosted lists? The administrator would create an address for the list on the MTA machine. Mailman would check this address for new messages every so often, and forward them on to the rest of the list using the currently opened connection. During the process Mailman would need to complete all of its normal everyday duties just as it would do using an MTA on the host machine. Bradley M. Handy Jack-of-all-trades Programming Services --www.jack-of-all-trades.net --bhandy@jack-of-all-trades.net ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:36 Message: Logged In: YES user_id=12800 There are several solutions to moving the primary mail processing to an external machine. For outgoing mail it's easy; just change the SMTPHOST and SMTPPORT in your mm_cfg.py file. For incoming mail you probably want to run a stripped down smtpd that only accepts incoming connections from your public server. The public server must know about all the Mailman lists, and forward messages as appropriate to the local incoming-only smtpd. Whether this is beneficial or not depends on your system and network configuration! ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=455064&group_id=103 From noreply@sourceforge.net Fri May 3 06:38:24 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:38:24 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-447373 ] Virtual hosts? Message-ID: Feature Requests item #447373, was opened at 2001-08-02 21:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=447373&group_id=103 Category: None Group: None >Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Virtual hosts? Initial Comment: Is it possible to configure Mailman to support virtual hosts without creating completely redundant installations (i.e, $prefix/virtual_host1/ and $prefix/virtual_host2/ instead of $prefix1 and $prefix2)? Eric P. Los Gatos, CA ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:38 Message: Logged In: YES user_id=12800 The answer is yes, with one caveat: no two lists in the same installation can have the same name, regardless of virtual host setup. This limitation will be removed in MM3. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=447373&group_id=103 From noreply@sourceforge.net Fri May 3 06:40:00 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:40:00 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-410645 ] wish: change my email address across all Message-ID: 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=103 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=103 From noreply@sourceforge.net Fri May 3 06:40:50 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:40:50 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-409071 ] Crypt/md5 change on the fly Message-ID: 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=103 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=103 From noreply@sourceforge.net Fri May 3 06:41:04 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:41:04 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-409071 ] Crypt/md5 change on the fly Message-ID: 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=103 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=103 From noreply@sourceforge.net Fri May 3 06:41:48 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:41:48 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-406137 ] Make RFC 2369 extra headers optional Message-ID: 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=103 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=103 From noreply@sourceforge.net Fri May 3 06:42:44 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:42:44 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-404691 ] Strip attachments and web store them Message-ID: 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=103 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=103 From noreply@sourceforge.net Fri May 3 06:45:38 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:45:38 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-230429 ] Feature request: Single password for all lists Message-ID: 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=103 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=103 From noreply@sourceforge.net Fri May 3 06:48:33 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:48:33 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-228127 ] Improve Pipermail's memory footprint Message-ID: 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=103 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=103 From noreply@sourceforge.net Fri May 3 06:50:45 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 22:50:45 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-228008 ] Need full name & phone in list user database Message-ID: 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=103 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@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 (J. Random User)". This would be nice... ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=228008&group_id=103 From noreply@sourceforge.net Fri May 3 07:50:59 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 02 May 2002 23:50:59 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-551730 ] traceback on double rename Message-ID: 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=103 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 ----- Subject: Mailman results for Empeg-faq From: empeg-faq-request@merlins.org To: davidtg-empeg@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@empeg.merlins.org. To obtain instructions on valid Mailman email commands, send email to empeg-faq-request@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@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 . 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@bigfoot.com ----- End forwarded message ----- ----- Forwarded message from David T-G ----- % Were you trying to change your subscription from davidtg@bigfoot.com to % davidtg-empeg@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=103 From noreply@sourceforge.net Fri May 3 09:48:36 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 03 May 2002 01:48:36 -0700 Subject: [Mailman-Developers] [ mailman-Patches-551327 ] Makefile fix so that errors propagate Message-ID: 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=103 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=103 From noreply@sourceforge.net Fri May 3 14:38:07 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 03 May 2002 06:38:07 -0700 Subject: [Mailman-Developers] [ mailman-Patches-551327 ] Makefile fix so that errors propagate Message-ID: Patches item #551327, was opened at 2002-05-02 05:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=551327&group_id=103 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: Barry Warsaw (bwarsaw) Date: 2002-05-03 09:38 Message: Logged In: YES user_id=12800 No problem. No the patch was easy to understand, I just don't think it goes far enough. See the simple mistake I introduced that didn't stop the build process. By comprehensive I mean that more Makefile.in's probably need to be patched so that any error in any of them will stop the build process. ---------------------------------------------------------------------- Comment By: Daniel Resare (noa) Date: 2002-05-03 04: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-02 21: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=103 From carson@taltos.org Fri May 3 15:32:22 2002 From: carson@taltos.org (Carson Gaspar) Date: Fri, 03 May 2002 10:32:22 -0400 Subject: [Mailman-Developers] Mile long subject prefixes Message-ID: <2212301.1020421942@[172.22.48.53]> OK, personally, I think subject prefixes are evil, but I understand some folks like them. But: "[Mailman-Developers] [ mailman-Feature Requests-502278 ]" as a subject prefix is just INSANE. Can someone please do _something_ useful about this? -- Carson From noreply@sourceforge.net Fri May 3 16:31:33 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 03 May 2002 08:31:33 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-551892 ] Easy interface for "moderate first post" Message-ID: Feature Requests item #551892, was opened at 2002-05-03 10:31 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=551892&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David Abrahams (david_abrahams) Assigned to: Nobody/Anonymous (nobody) Summary: Easy interface for "moderate first post" Initial Comment: My mailing list has a "moderate first-time posters" policy. I'd like it if that were easier to manage with Mailman. The interface should provide an explicit setting for this. The moderation response for first-time posters should be optionally set to "approve" by default and there should be a checkbox (optionally unchecked by default) labelled "moderate future postings" which allows the moderator to quickly approve a poster for unmoderated posting. As far as I could tell from my quick look at 2.1, there was no similarly convenient facility. Thanks, Dave ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=551892&group_id=103 From Dan Mick Sat May 4 00:22:34 2002 From: Dan Mick (Dan Mick) Date: Fri, 3 May 2002 16:22:34 -0700 (PDT) Subject: [Mailman-Developers] Mile long subject prefixes Message-ID: <200205032323.g43NN5bH019167@utopia.West.Sun.COM> > OK, personally, I think subject prefixes are evil, but I understand some > folks like them. But: > > "[Mailman-Developers] [ mailman-Feature Requests-502278 ]" > > as a subject prefix is just INSANE. > > Can someone please do _something_ useful about this? Like, suggest procmail for those who can't take it anymore? From barry@zope.com Sat May 4 00:35:40 2002 From: barry@zope.com (Barry A. Warsaw) Date: Fri, 3 May 2002 19:35:40 -0400 Subject: [Mailman-Developers] Traceback on double rename References: <20020427215214.GJ12548@merlins.org> Message-ID: <15571.7884.291642.299132@anthem.wooz.org> >>>>> "MM" == Marc MERLIN writes: MM> I have a user who says he got this on mailman 2.1b1cvs MM> He explains below how he did it. MM> Sorry :-) It should be easy to duplicate, though; subscribe to MM> two lists (like empeg-faq and empeg-announce), open two web MM> browsers, go to the two list control pages and log in on each, MM> and then send a change from one and a change from the other. MM> Remember to hit "global" at some point along the way. When MM> replying to the confirmation messages, reply to the first MM> before doing the global change but the second, which might MM> confusingly arrive after said global change, later after the MM> web is done. Great description, thanks! I was catching the wrong exception. Fixed in cvs now. -Barry From noreply@sourceforge.net Sat May 4 19:34:27 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 04 May 2002 11:34:27 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-551730 ] traceback on double rename Message-ID: Bugs item #551730, was opened at 2002-05-03 02:50 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=551730&group_id=103 Category: (un)subscribing Group: 2.1 beta >Status: Closed >Resolution: Fixed 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 ----- Subject: Mailman results for Empeg-faq From: empeg-faq-request@merlins.org To: davidtg-empeg@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@empeg.merlins.org. To obtain instructions on valid Mailman email commands, send email to empeg-faq-request@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@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 . 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@bigfoot.com ----- End forwarded message ----- ----- Forwarded message from David T-G ----- % Were you trying to change your subscription from davidtg@bigfoot.com to % davidtg-empeg@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=103 From noreply@sourceforge.net Sat May 4 21:56:45 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 04 May 2002 13:56:45 -0700 Subject: [Mailman-Developers] [ mailman-Patches-518863 ] syncmail patch: unified + contextlines Message-ID: Patches item #518863, was opened at 2002-02-17 16:07 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=518863&group_id=103 Category: mail delivery Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Carsten Klapp (carstenklapp) Assigned to: Nobody/Anonymous (nobody) Summary: syncmail patch: unified + contextlines Initial Comment: This patch allows the number of context lines to be specified when requesting emailed unified diffs. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-04 16:56 Message: Logged In: YES user_id=12800 Can you resubmit this on the cvs-syncmail project at SourceForge? It's not really relevant to the Mailman project. Thanks. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=518863&group_id=103 From frizal@softhome.net Sun May 5 15:04:42 2002 From: frizal@softhome.net (M. Fahrizal Rasad) Date: Sun, 5 May 2002 21:04:42 +0700 (JAVT) Subject: [Mailman-Developers] python scripts to auto generates/removes .qmail-* Message-ID: <20020505140442.4611.qmail@add.co.id> Dear all, First, I am sorry if my question is more to python script. I am running Mailman (2.0.10) list in the exist virtual domain (qmail+vpopmail, had some users (POP3) and 2 mailing-lists /w ezmlm). Because I dont want to creates/removes files .qmail-* manually, I tried to insert (newbie) script commands in file "newlist", where it will automatically generates .qmail-* in the proper location (Mailman directory OR vpopmail 'domain*name' directory) and it works. The problem is I am a very newbie with python, (in file rmlist) I don't know how to create script commands to removes the relevant .qmail-* automatically, any help for the script would be appreciated. Thanks. configured with: --prefix=/home/mailman --with-mail-gid=vchkpw \ --with-cgi-id=nobody --with-cgi-gid=nobody mm_cfg.py : ----------- DEFAULT_HOST_NAME = 'list.add.com.id' #example MTA_ALIASES_STYLE = 'qmail' # vpopmail domains directory, usually '/home/vpopmail/domains', # '' if not using vpopmail (virtual list only domains) VPDPREFIX = '/home/vpopmail/domains' from file bin/newlist : ----------------------- ... ... print STDOUTMSG print output ##--start-- insert--## # will creates .qmail-* at PREFIX directory or at vpopmail 'domain*name' # directory (/home/vpopmail/domains/list.add.com.id) for listname 'test': # .qmail-test, .qmail-owner-test, .qmail-test-admin, .qmail-test-owner, # .qmail-test-request if style == 'qmail': from Mailman.mm_cfg import PREFIX, DEFAULT_HOST_NAME, VPDPREFIX WRAPLOC = os.path.join(PREFIX, 'mail', 'wrapper') if VPDPREFIX != '': DOTLOC = os.path.join(VPDPREFIX, DEFAULT_HOST_NAME) else: DOTLOC = PREFIX dotq='.qmail-' dotqext = open(DOTLOC+"/"+dotq+listname, 'w') dotqext.write( "|preline " +WRAPLOC +" post " +listname +"\012" ) dotqext.close() dotqext = open(DOTLOC+"/"+dotq+listname+"-admin", "w" ) dotqext.write( "|preline " +WRAPLOC +" mailowner " +listname +"\012" ) dotqext.close() dotqext = open(DOTLOC+"/"+dotq+listname+"-owner", "w" ) dotqext.write( "|preline " +WRAPLOC +" mailowner " +listname +"\012" ) dotqext.close() dotqext = open(DOTLOC+"/"+dotq+"owner-"+listname, "w" ) dotqext.write( "|preline " +WRAPLOC +" mailowner " +listname +"\012" ) dotqext.close() dotqext = open(DOTLOC+"/"+dotq+listname+"-request", "w" ) dotqext.write( "|preline " +WRAPLOC +" mailcmd " +listname +"\012" ) dotqext.close() ##-- end --## if appendfile: fp = open(appendfile, 'a') fp.write(output) fp.write('\n') fp.close() ... ... ------------------------------------------------------------------------ From marc_news@vasoftware.com Sun May 5 23:32:03 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sun, 5 May 2002 15:32:03 -0700 Subject: [Mailman-Developers] chuckle Message-ID: <20020505223202.GO29582@merlins.org> --- Topic for #mailman is Mailman mailinglist manager http://www.list.org/ -- Current stable version: 2.0.10 -- Current devel version: 2.1beta1 --- Topic for #mailman set by ChanServ at Fri Apr 19 12:48:02 --> t1nsley (~notme@24-196-133-126.mad.wi.charter.com) has joined #mailman hrm has mailman ever been audited? nope, it pays it taxes on time Ok, ok, I had to share since the audience on the channel was very low :-) Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From barry@zope.com Mon May 6 05:46:19 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 6 May 2002 00:46:19 -0400 Subject: [Mailman-Developers] Re: [Mailman-Users] Re: Editability of messages References: <20020415033446.29700.82480.Mailman@mail.python.org> <1598000234.1018857301@tom-9k5kaocfpin> <20020415210955.GM25045@merlins.org> <15551.17014.271050.657394@anthem.wooz.org> <20020419215756.GC9044@merlins.org> <15552.37971.201825.842594@anthem.wooz.org> Message-ID: <15574.2715.631966.75809@anthem.wooz.org> [about occasionally exhausting file descriptors...] >>>>> "JWB" == John W Baxter writes: JWB> We haven't moved to either Mailman 2.1 or Exim 4 (on the JWB> Mailman machine) yet. JWB> But...we are seeing a Python-based web dynamic page server JWB> (not Zope...in-house) leaving open files behind with a fairly JWB> new Python. JWB> We've temporized by having a monitor which does a suitable JWB> lsof and counts the relevant open files...killing and JWB> restarting that server when the count reaches 1000. JWB> I'll pass along to the (really sharp) guy who is working on JWB> that problem that you're seeing something at least vaguely JWB> similar. We've been operating on the theory that the problem JWB> is in our code, but...perhaps not? Possibly not, although I don't recall seeing anything on the Python lists about it. I'm running Mailman (both 2.0.10 and 2.1b2) on Python 2.1.2. I should probably upgrade to 2.1.3. However I never saw the problem until we upgraded to Exim 4. OTOH, we also turned on SpamAssassin full-bore about the same time, so there are lots of variables in this equation . I haven't seen the problem in at least a week, so who knows? We're certainly catching lots of spam! Greg Ward should be back online any time now, so he probably won't have time to look at this until he catches up (he's our Exim guru). -Barry From barry@zope.com Mon May 6 05:57:27 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 6 May 2002 00:57:27 -0400 Subject: [Mailman-Developers] RELEASED Mailman 2.1 beta 2 Message-ID: <15574.3383.393550.438002@anthem.wooz.org> I've released Mailman 2.1 beta 2; see below for a list of changes since version 2.1 beta 1. There have been lots of bug fixes, Korean language support aded, and a couple of new features (a bit of a thaw in the feature freeze ;). Remember that discussions about version 2.1 are preferred on mailman-developers. I plan on moving mailman-developers over to the new version tomorrow, and if that works well, the other mailman-* mailing lists at python.org too. Enjoy, -Barry 2.1 beta 2 (05-May-2002) Lots of bug fixing, and the following new features and changes: - A "de-mime" content filter feature has been added. This oft-requested feature allows you to specify MIME types that Mailman should strip off of any messages before they're posted to the list. You can also optionally convert text/html to text/plain (by default, through lynx if it's available). - Changes to the way the RFC 2919 and 2369 headers (i.e. the List-*: headers) are added: o List-Id: is always added o List-Post:, List-Help:, List-Subscribe:, List-Unsubscribe:, and List-Archive: are only added to posting messages. o X-List-Administrivia: is only added to messages Mailman creates and sends out of its own accord. Also, if the site administrator allows it, list owners can suppress the addition of all the List-*: headers. List owners can also separately suppress the List-Post: header for announce-only lists. - A new framework for email commands has been added. This allows you to easily add, delete, or change the email commands that Mailman understands, on a per-site, per-list, or even per-user basis. - Users can now change their digest delivery type from MIME to plain text globally, for all lists they are subscribed to. - No language select pulldowns are shown if the list only supports one language. - More mylist-admin eradication. - Several performance improvements in the bounce qrunner, one of which is to make it run only once per minute instead of once per second. - Korean language support as been added. - Gatewaying from news -> mail uses its connections to the nntpd more efficiently. - In bin/add_members, -n/--non-digest-members-file command line switch is deprecated in favor of -r/--regular-members-file. - bin/sync_members grew a -g/--goodbye-msg switch. From jwblist@olympus.net Mon May 6 06:27:20 2002 From: jwblist@olympus.net (John W Baxter) Date: Sun, 5 May 2002 22:27:20 -0700 Subject: [Mailman-Developers] Re: [Mailman-Users] Re: Editability of messages In-Reply-To: <15574.2715.631966.75809@anthem.wooz.org> References: <20020415033446.29700.82480.Mailman@mail.python.org> <1598000234.1018857301@tom-9k5kaocfpin> <20020415210955.GM25045@merlins.org> <15551.17014.271050.657394@anthem.wooz.org> <20020419215756.GC9044@merlins.org> <15552.37971.201825.842594@anthem.wooz.org> <15574.2715.631966.75809@anthem.wooz.org> Message-ID: At 0:46 -0400 5/6/2002, Barry A. Warsaw wrote: >[about occasionally exhausting file descriptors...] > >>>>>> "JWB" == John W Baxter writes: > > JWB> We haven't moved to either Mailman 2.1 or Exim 4 (on the > JWB> Mailman machine) yet. > > JWB> But...we are seeing a Python-based web dynamic page server > JWB> (not Zope...in-house) leaving open files behind with a fairly > JWB> new Python. > > JWB> We've temporized by having a monitor which does a suitable > JWB> lsof and counts the relevant open files...killing and > JWB> restarting that server when the count reaches 1000. > > JWB> I'll pass along to the (really sharp) guy who is working on > JWB> that problem that you're seeing something at least vaguely > JWB> similar. We've been operating on the theory that the problem > JWB> is in our code, but...perhaps not? > >Possibly not, although I don't recall seeing anything on the Python >lists about it. I think our problem--now seemingly solved by a change in our code--is unrelated to the Mailman problem. Unfortunately, I'm not the one who made the change, and I don't know the details. Sorry for the false alarm (or hope, whichever it was). --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA From barry@zope.com Mon May 6 06:29:05 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 6 May 2002 01:29:05 -0400 Subject: [Mailman-Developers] Number of Mailman users? References: <5.1.0.14.0.20020414163331.045f6830@ella.mills.edu> <20020414234338.GM347@merlins.org> Message-ID: <15574.5281.784675.405821@anthem.wooz.org> >>>>> "MM" == Marc MERLIN writes: MM> I think you'llhave to stick to "several millions", this is MM> open source software, and Barry doesn't receive per user MM> license fees, so he can't count them either :-) You haven't balanced your checkbook in a while then, have you Marc? True, there are no licensing fees, but I receive 1/20th of a penny for every message anybody sends through a Mailman system anywhere in the world, debited directly from their checking accounts (see Mailman/Handlers/Bwaahaahaa.py). My beach front property (with a poolside gigabit wireless and waterproof laptop) is nearly finished, and delivery on the Maddenbus (I hate to fly) is just waiting on a decision about the color of the toilet seats. Yes, there are 7; I have a big entourage -- no smart aleck remarks please! if-you-can't-get-rich-quick-at-least-get-rich-eventual-ly y'rs, -Barry :) From barry@zope.com Mon May 6 06:37:59 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 6 May 2002 01:37:59 -0400 Subject: [Mailman-Developers] after processing a confirm in the subject line, the body should be ignored (v2.1b1) References: <200204111011.g3BABFO01698@sun31.imbi.uni-freiburg.de> Message-ID: <15574.5815.191914.408517@anthem.wooz.org> >>>>> "GK" == Georg Koch writes: GK> if you send a "subscribe" or "unsubscribe" command via email GK> to list-request@mailmanhost you get a confirmation message in GK> reply which says "To confirm that you want to be removed from GK> this mailing list, simply reply to this message, keeping the GK> Subject: header intact.". GK> If you do so, but include the body of the confirm message, you GK> get TWO messages back: a success message and a long error GK> message stating "There were problems with the email commands GK> you sent". GK> I find this confusing and think you cannot expect everyone to GK> understand "reply" as "reply with an empty body". I would GK> therefore propose the following behaviour change: GK> After a confirm command from the Subject: header field of a GK> message is processed successfully, the body of this message is GK> ignored (not processed). Please take a look at the new command processor in MM2.1b2. I think it's a lot better (hopefully you'll agree. ;). -Barry From barry@zope.com Mon May 6 06:41:54 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 6 May 2002 01:41:54 -0400 Subject: [Mailman-Developers] Well, here's an interesting one References: <200204101318.g3ADIfQ23578@babylon5.cc.vt.edu> Message-ID: <15574.6050.571888.36147@anthem.wooz.org> >>>>> "RJ" == Ron Jarrell writes: RJ> Apr 10 03:19:57 2002 (12285) message is unparsable: RJ> 1018423196.419311+a81685d7af 1f6631ce6392a83aff01fde476543f RJ> Apr 10 03:19:57 2002 (12285) lost data files for filebase: RJ> 1018423196.419311+a81 685d7af1f6631ce6392a83aff01fde476543f RJ> I don't mind the unparseability so much as the fact that it RJ> lost the files, so now I can't see *why* it was unparseable... RJ> Based on the syslog, I see which one it must have been. Looks RJ> like it was spam anyway, so hopefully it was just their RJ> spamming package mangling the message. Set QRUNNER_SAVE_BAD_MESSAGES = 1 in your mm_cfg.py file and the unparseable messages will be left in qfiles/bad/*.txt. I agree it was likely spam because (most) legit mail is promerly MIME chromed. I'm not psyched about trying harder to parse or handle legitimate, but incorrectly MIME chromed messages. :/ -Barry From danny@terweij.nl Mon May 6 10:39:06 2002 From: danny@terweij.nl (Danny Terweij) Date: Mon, 6 May 2002 11:39:06 +0200 Subject: [Mailman-Developers] Installed 2.1b2 over 2.1b1 and we just hit a bug.. Message-ID: <00aa01c1f4e1$ddce7a80$1e00a8c0@poema.yi.org> Hi all, What is wrong? When going to http://domain.com/mailman/admin/[listname]/language Bug in Mailman version 2.1b2 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 82, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admin.py", line 192, in main show_results(mlist, doc, category, subcat, cgidata) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 519, in show_results form.AddItem(show_variables(mlist, category, subcat, cgidata, doc)) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 528, in show_variables options = mlist.GetConfigInfo(category, subcat) File "/usr/local/mailman/Mailman/MailList.py", line 396, in GetConfigInfo value = gui.GetConfigInfo(self, category, subcat) File "/usr/local/mailman/Mailman/Gui/Language.py", line 50, in GetConfigInfo allnames = [_(Utils.GetLanguageDescr(L)) for L in all] File "/usr/local/mailman/Mailman/Utils.py", line 645, in GetLanguageDescr return mm_cfg.LC_DESCRIPTIONS[lang][0] KeyError: nl ---------------------------------------------------------------------------- ---- Python information: Variable Value sys.version 2.1.1 (#1, Aug 13 2001, 19:37:40) [GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-96)] sys.executable /usr/bin/python2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ---------------------------------------------------------------------------- ---- Environment variables: Variable Value DOCUMENT_ROOT /var/www/html SERVER_ADDR 192.168.0.2 HTTP_ACCEPT_ENCODING gzip, deflate SERVER_PORT 80 PATH_TRANSLATED /var/www/html/poema-test/language REMOTE_ADDR 192.168.0.1 HTTP_ACCEPT_LANGUAGE nl GATEWAY_INTERFACE CGI/1.1 SERVER_NAME lnx.poema.yi.org HTTP_CONNECTION Keep-Alive HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows 98) HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* REQUEST_URI /mailman/admin/poema-test/language QUERY_STRING SCRIPT_FILENAME /usr/local/mailman/cgi-bin/admin PATH_INFO /poema-test/language HTTP_HOST poema.yi.org:81 REQUEST_METHOD GET SERVER_SIGNATURE Apache/1.3.22 Server at lnx.poema.yi.org Port 80 SCRIPT_NAME /mailman/admin SERVER_ADMIN root@localhost SERVER_SOFTWARE Apache/1.3.22 PYTHONPATH /usr/local/mailman HTTP_COOKIE poema-test+admin=280200000069324dd63c732800000030306139316363333961623435376 338366631636163323361613230373763663537353165306461; simpnews[lastvisit]=2002-05-02+20%3A03%3A00 SERVER_PROTOCOL HTTP/1.1 REMOTE_PORT 4293 HTTP_REFERER http://poema.yi.org:81/mailman/admin/poema-test/members Groetjes Danny Terweij From danny@terweij.nl Mon May 6 10:51:49 2002 From: danny@terweij.nl (Danny Terweij) Date: Mon, 6 May 2002 11:51:49 +0200 Subject: [Mailman-Developers] vcard's (with) Message-ID: <00f401c1f4e3$a4e66280$1e00a8c0@poema.yi.org> This is a multi-part message in MIME format. ------=_NextPart_000_00F1_01C1F4F4.67D822A0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable When putting a vcrad in an html message there are 2
lines adden. Can this please be removed? (exists at 2.1b1 and 2.1b2) I add now a vcard and my next message without a vcard. Groetjes Danny Terweij =20 ------=_NextPart_000_00F1_01C1F4F4.67D822A0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
When putting a vcrad in an html message there are 2 = <hr>=20 lines adden.
Can this please be removed? (exists at 2.1b1 and=20 2.1b2)
 
I add now a vcard and my next message without a=20 vcard.
 

Groetjes Danny Terweij
 
 
------=_NextPart_000_00F1_01C1F4F4.67D822A0-- From danny@terweij.nl Mon May 6 10:53:25 2002 From: danny@terweij.nl (Danny Terweij) Date: Mon, 6 May 2002 11:53:25 +0200 Subject: [Mailman-Developers] vcard (with) Message-ID: <010201c1f4e3$ddbba3e0$1e00a8c0@poema.yi.org> This is a multi-part message in MIME format. ------=_NextPart_000_00FE_01C1F4F4.A0F08780 Content-Type: multipart/alternative; boundary="----=_NextPart_001_00FF_01C1F4F4.A0F08780" ------=_NextPart_001_00FF_01C1F4F4.A0F08780 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable With vcard Did not added it pervious message. Danny. ------=_NextPart_001_00FF_01C1F4F4.A0F08780 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
With vcard
 
Did not added it pervious message.
Danny.
 
 
 
------=_NextPart_001_00FF_01C1F4F4.A0F08780-- ------=_NextPart_000_00FE_01C1F4F4.A0F08780 Content-Type: text/x-vcard; name="Dannny Terweij.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Dannny Terweij.vcf" BEGIN:VCARD VERSION:2.1 N:Terweij;Dannny FN:Dannny Terweij NICKNAME:POEMA NOTE:POEMA SERVICES X-WAB-GENDER:2 URL;HOME:http://poema.yi.org URL;WORK:http://poema.yi.org BDAY:20020413 EMAIL;PREF;INTERNET:poema-test@lnx.poema.yi.org REV:20020506T095325Z END:VCARD ------=_NextPart_000_00FE_01C1F4F4.A0F08780-- From danny@terweij.nl Mon May 6 10:54:20 2002 From: danny@terweij.nl (Danny Terweij) Date: Mon, 6 May 2002 11:54:20 +0200 Subject: [Mailman-Developers] vcard without it Message-ID: <010b01c1f4e3$fe8a13e0$1e00a8c0@poema.yi.org> This is a multi-part message in MIME format. ------=_NextPart_000_0108_01C1F4F4.C1E08940 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable vcard not attached Groetjes Danny Terweij =20 ------=_NextPart_000_0108_01C1F4F4.C1E08940 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
vcard not attached
 
Groetjes Danny Terweij
 
 
------=_NextPart_000_0108_01C1F4F4.C1E08940-- From danny@terweij.nl Mon May 6 10:57:40 2002 From: danny@terweij.nl (Danny Terweij) Date: Mon, 6 May 2002 11:57:40 +0200 Subject: [Mailman-Developers] vcard and this list Message-ID: <012601c1f4e4$75abd1c0$1e00a8c0@poema.yi.org> This is a multi-part message in MIME format. ------=_NextPart_000_0123_01C1F4F5.39024720 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable looks like html is tripped on this list :-) Groetjes Danny Terweij =20 ------=_NextPart_000_0123_01C1F4F5.39024720 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
looks like html is tripped on this list :-)

Groetjes Danny Terweij
 
 
------=_NextPart_000_0123_01C1F4F5.39024720-- From danny@terweij.nl Mon May 6 11:14:27 2002 From: danny@terweij.nl (Danny Terweij) Date: Mon, 6 May 2002 12:14:27 +0200 Subject: [Mailman-Developers] Approving moderated messages Message-ID: <01ba01c1f4e6$ce1f55a0$1e00a8c0@poema.yi.org> This is a multi-part message in MIME format. ------=_NextPart_000_01B7_01C1F4F7.914C9820 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Even on 2.1b1 i can still not with 2.1b2 approve the held messages. When i press the radio button "accept" and press the "Submit all changes = button" it is doing nothing with this message. its stays there and will = not be send out. Alle my lists can not handle moderated messages. it just stays at the = Pending moderator requests. (already send about this on the mailman-users list a while ago). Groetjes Danny Terweij =20 ------=_NextPart_000_01B7_01C1F4F7.914C9820 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Even on 2.1b1 i can still not with 2.1b2 approve the = held=20 messages.
 
When i press the radio button "accept" and press the = "Submit=20 all changes button" it is doing nothing with this message. its stays = there and=20 will not be send out.
 
Alle my lists can not handle moderated messages. it = just stays=20 at the Pending moderator requests.
 
(already send about this on the mailman-users list a = while=20 ago).
 

Groetjes Danny Terweij
 
 
------=_NextPart_000_01B7_01C1F4F7.914C9820-- From david@midrange.com Mon May 6 12:20:06 2002 From: david@midrange.com (David Gibbs) Date: Mon, 6 May 2002 06:20:06 -0500 Subject: [Mailman-Developers] Upgrading from 2.0.10 to 2.1.b2 Message-ID: Folks: I'm trying to give MM 2.1b2 a few tests, but cannot get any of my existing mailing lists converted (I'm just trying to convert some test and internal lists). Whenever I copy the list files over from the 2.0.10 install directory, and run bin/update -f, I get the following results ... [root@linux mailman]# bin/update -f Upgrading from version 0x20100b2 to 0x20100b2 getting rid of old source files Updating mailing list: list-owners Traceback (most recent call last): File "bin/update", line 542, in ? errors = main() File "bin/update", line 424, in main errors = errors + dolist(listname) File "bin/update", line 184, in dolist mlist = MailList.MailList(listname, lock=0) File "/usr/local/mailman/Mailman/MailList.py", line 101, in __init__ self.Load() File "/usr/local/mailman/Mailman/MailList.py", line 574, in Load self.CheckValues() File "/usr/local/mailman/Mailman/MailList.py", line 625, in CheckValues for name, pattern, desc, emptyflag in self.topics: File "/usr/local/mailman/Mailman/MailList.py", line 128, in __getattr__ raise AttributeError, name AttributeError: topics Any ideas? Thanks! david From jarrell@vt.edu Mon May 6 15:20:29 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Mon, 06 May 2002 10:20:29 -0400 Subject: [Mailman-Developers] Well, here's an interesting one In-Reply-To: <15574.6050.571888.36147@anthem.wooz.org> References: <200204101318.g3ADIfQ23578@babylon5.cc.vt.edu> Message-ID: <5.1.0.14.2.20020506101922.086d26d0@lennier.cc.vt.edu> At 01:41 AM 5/6/02 -0400, Barry A. Warsaw wrote: >>>>>> "RJ" == Ron Jarrell writes: > > RJ> Apr 10 03:19:57 2002 (12285) message is unparsable: > RJ> 1018423196.419311+a81685d7af 1f6631ce6392a83aff01fde476543f > RJ> Apr 10 03:19:57 2002 (12285) lost data files for filebase: > RJ> 1018423196.419311+a81 685d7af1f6631ce6392a83aff01fde476543f > > RJ> I don't mind the unparseability so much as the fact that it > RJ> lost the files, so now I can't see *why* it was unparseable... > > RJ> Based on the syslog, I see which one it must have been. Looks > RJ> like it was spam anyway, so hopefully it was just their > RJ> spamming package mangling the message. > >Set QRUNNER_SAVE_BAD_MESSAGES = 1 in your mm_cfg.py file and the >unparseable messages will be left in qfiles/bad/*.txt. Actually, I *had* set it. Other messages since then have been properly dumped into the file -- and each of them has been a virus that wasn't parseable. Gee, I consider that a feature :-). That one, for some reason, just vanished into thin ether. From parris@isciences.com Mon May 6 18:06:03 2002 From: parris@isciences.com (Thomas M. Parris) Date: Mon, 6 May 2002 13:06:03 -0400 Subject: [Mailman-Developers] RE: [Mailman-Announce] RELEASED Mailman 2.1 beta 2 In-Reply-To: <15574.3383.393550.438002@anthem.wooz.org> Message-ID: <000b01c1f520$4e095e80$eb755f42@CHERRYBLOSSOM> Barry, Thanks for your hard work. There are a bunch of us out here who truly value your efforts. I have a thought about your "de-mime" feature. You indicate a method for converting text/html to text/plain via an external filter (lynx). In principle, this could be generalized to convert other mime types to text via appropriate external filters. For example, postscript and pdf files could be converted to text via ghostscript. There are also filters for converting MS-Word and rtf files to text. As someone who is becoming more and more paranoid about the use of binary attachments on my lists, this would be an excellent way to go. Do you have intentions along these lines? Or, should I continue to examine the growing body of external tools that do this? Many thanks, -- Tom -----Original Message----- From: mailman-announce-admin@python.org [mailto:mailman-announce-admin@python.org]On Behalf Of Barry A. Warsaw Sent: Monday, May 06, 2002 12:57 AM To: mailman-announce@python.org Cc: mailman-users@python.org; mailman-developers@python.org Subject: [Mailman-Announce] RELEASED Mailman 2.1 beta 2 I've released Mailman 2.1 beta 2; see below for a list of changes since version 2.1 beta 1. There have been lots of bug fixes, Korean language support aded, and a couple of new features (a bit of a thaw in the feature freeze ;). Remember that discussions about version 2.1 are preferred on mailman-developers. I plan on moving mailman-developers over to the new version tomorrow, and if that works well, the other mailman-* mailing lists at python.org too. Enjoy, -Barry 2.1 beta 2 (05-May-2002) Lots of bug fixing, and the following new features and changes: - A "de-mime" content filter feature has been added. This oft-requested feature allows you to specify MIME types that Mailman should strip off of any messages before they're posted to the list. You can also optionally convert text/html to text/plain (by default, through lynx if it's available). - Changes to the way the RFC 2919 and 2369 headers (i.e. the List-*: headers) are added: o List-Id: is always added o List-Post:, List-Help:, List-Subscribe:, List-Unsubscribe:, and List-Archive: are only added to posting messages. o X-List-Administrivia: is only added to messages Mailman creates and sends out of its own accord. Also, if the site administrator allows it, list owners can suppress the addition of all the List-*: headers. List owners can also separately suppress the List-Post: header for announce-only lists. - A new framework for email commands has been added. This allows you to easily add, delete, or change the email commands that Mailman understands, on a per-site, per-list, or even per-user basis. - Users can now change their digest delivery type from MIME to plain text globally, for all lists they are subscribed to. - No language select pulldowns are shown if the list only supports one language. - More mylist-admin eradication. - Several performance improvements in the bounce qrunner, one of which is to make it run only once per minute instead of once per second. - Korean language support as been added. - Gatewaying from news -> mail uses its connections to the nntpd more efficiently. - In bin/add_members, -n/--non-digest-members-file command line switch is deprecated in favor of -r/--regular-members-file. - bin/sync_members grew a -g/--goodbye-msg switch. _______________________________________________ Mailman-announce mailing list Mailman-announce@python.org http://mail.python.org/mailman/listinfo/mailman-announce From mrbill@mrbill.net Mon May 6 18:03:07 2002 From: mrbill@mrbill.net (Bill Bradford) Date: Mon, 6 May 2002 12:03:07 -0500 Subject: [Mailman-Developers] RE: [Mailman-Announce] RELEASED Mailman 2.1 beta 2 In-Reply-To: <000b01c1f520$4e095e80$eb755f42@CHERRYBLOSSOM> References: <15574.3383.393550.438002@anthem.wooz.org> <000b01c1f520$4e095e80$eb755f42@CHERRYBLOSSOM> Message-ID: <20020506170307.GO3731@mrbill.net> On Mon, May 06, 2002 at 01:06:03PM -0400, Thomas M. Parris wrote: > Barry, > Thanks for your hard work. There are a bunch of us out here who truly value > your efforts. > I have a thought about your "de-mime" feature. You indicate a method for > converting text/html to text/plain via an external filter (lynx). In > principle, this could be generalized to convert other mime types to text via > appropriate external filters. For example, postscript and pdf files could > be converted to text via ghostscript. There are also filters for converting > MS-Word and rtf files to text. I'd love to have an option to just "pipe through external filter"; I'm already doing something similar to this with "demime" and 2.0.10: austin: "|/bin/demime - |/usr/local/mailman/mail/wrapper post austin" etc. Bill -- Bill Bradford mrbill@mrbill.net Austin, TX From chuqui@plaidworks.com Mon May 6 18:24:28 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Mon, 06 May 2002 10:24:28 -0700 Subject: [Mailman-Developers] RE: [Mailman-Announce] RELEASED Mailman 2.1 beta 2 In-Reply-To: <20020506170307.GO3731@mrbill.net> Message-ID: On 5/6/02 10:03 AM, "Bill Bradford" wrote: > I'd love to have an option to just "pipe through external filter"; I don't think this is a 2.1 type thing, but I like this idea. It potentially simplifies a lot of things, and gives admins the ability to configure stuff on systems where they don't have access to anything but the admin pages. I would, by the way, do two of these: a pre-filter and a post-filter. The pre-filter is primarily for cleaning up before it goes for delivery. If you allow it to return a set of known values, you can even use it for determining moderator hold, rejection, etc (and through that, plug into tools like spamassasin). The post-filter would be a nice, easy hook into things like mhonarc for customized archive systems and the like... -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ He doesn't have ulcers, but he's a carrier. From dgc@uchicago.edu Mon May 6 18:43:34 2002 From: dgc@uchicago.edu (David Champion) Date: Mon, 6 May 2002 12:43:34 -0500 Subject: [Mailman-Developers] Re: A RELEASED Mailman 2.1 beta 2 In-Reply-To: References: <20020506170307.GO3731@mrbill.net> Message-ID: <20020506174334.GN9707@dust.uchicago.edu> Just a quickie while I'm in between crises: * On 2002.05.06, in , * "Chuq Von Rospach" wrote: > I would, by the way, do two of these: a pre-filter and a post-filter. The Delivery filter and archiving filter? A little clearer in intent. Good idea. Along these lines, it might be nice if the site op could set up certain filters (or handlers) and make them available at the discretion of the list admin, with the flick of a checkbox. Technically we can do that now, but it would be nice if just by defining the filter, the checkbox is automatically made available in the admin pages. $ cat /path/to/mailman/filters/braindump.filter ## ## Anything ending in *.filter is a filter definition file. ## ## %s is the basename of the file, minus ".filter" DESCRIPTION=The %s filter removes the word 'foo' in mail messages. ## ## Booleans control whether to pass the header or body or both to the filter. FILTERHEADER=false FILTERBODY=true ## ## Is this filter available for delivery filtration? DELIVERY=true ## ## ... for archival filtration? ARCHIVE=true ## ## $EXEC sets a command line to accept a message on stdin ## and process to stdout EXEC=/usr/local/foo-filter ## ## Or alternatively, write it in python and execute it in the same process. ## if there's a CALLBACK setting, then "from $CALLBACK import Filter" or ## something. #CALLBACK=/usr/local/foo-filter.py This would automatically place into the admin pages: -------- Filter Options: Description Value Enable the braindump filter? The braindump filter [x] yes [ ] no removes the word 'foo' in mail messages. -------- The list admin wouldn't need to be knowledgeable of unix or the particular system hosting the list if the site op can set up some common wishlist filters. -- -D. dgc@uchicago.edu NSIT University of Chicago From jarrell@vt.edu Mon May 6 18:50:03 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Mon, 06 May 2002 13:50:03 -0400 Subject: [Mailman-Developers] RE: [Mailman-Announce] RELEASED Mailman 2.1 beta 2 In-Reply-To: References: <20020506170307.GO3731@mrbill.net> Message-ID: <5.1.0.14.2.20020506134450.06389330@lennier.cc.vt.edu> At 10:24 AM 5/6/02 -0700, Chuq Von Rospach wrote: >I don't think this is a 2.1 type thing, but I like this idea. It potentially >simplifies a lot of things, and gives admins the ability to configure stuff >on systems where they don't have access to anything but the admin pages. Definitely not a 2.1 type thing... If Barry keeps stuffing things into the delivery pipeline, we'll never be able to thoroughly test it before it goes production :-). From noreply@sourceforge.net Mon May 6 22:34:07 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 06 May 2002 14:34:07 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-553033 ] subscribing via web does not work Message-ID: Bugs item #553033, was opened at 2002-05-06 21:34 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553033&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: javier wilson (javierwilson) Assigned to: Nobody/Anonymous (nobody) Summary: subscribing via web does not work Initial Comment: Users trying to subscribe via web were redirected to the options web page. This only happened with users using Spanish templates. The problem seems to be in the spanish template listinfo.html Instead of "" it should say: "". Is this correct? javier wilson ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553033&group_id=103 From barry@zope.com Tue May 7 02:09:12 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 6 May 2002 21:09:12 -0400 Subject: [Mailman-Developers] Upgrading from 2.0.10 to 2.1.b2 References: Message-ID: <15575.10552.622025.10298@anthem.wooz.org> >>>>> "DG" == David Gibbs writes: DG> I'm trying to give MM 2.1b2 a few tests, but cannot get any of DG> my existing mailing lists converted (I'm just trying to DG> convert some test and internal lists). I just migrated mailman-developers to MM2.1b2 and hit the same problem. Attached is a fix, which will require a quick b3 release. If this message goes through, it's a good sign the upgrade went well. :) If so, I'll post instructions momentarily. -Barry -------------------- snip snip -------------------- Index: MailList.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/MailList.py,v retrieving revision 2.76 diff -u -r2.76 MailList.py --- MailList.py 2 May 2002 03:07:48 -0000 2.76 +++ MailList.py 7 May 2002 01:07:49 -0000 @@ -571,8 +571,8 @@ # mailing list object, then run sanity check on the data. self.__dict__.update(dict) if check_version: - self.CheckValues() self.CheckVersion(dict) + self.CheckValues() # From david@midrange.com Tue May 7 02:40:20 2002 From: david@midrange.com (David Gibbs) Date: Mon, 06 May 2002 20:40:20 -0500 Subject: [Mailman-Developers] Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <15575.10552.622025.10298@anthem.wooz.org> References: Message-ID: <5.1.0.14.2.20020506203919.02407918@linux.midrange.com> At 08:09 PM 5/6/2002, Barry A. Warsaw wrote: > DG> I'm trying to give MM 2.1b2 a few tests, but cannot get any of > DG> my existing mailing lists converted (I'm just trying to > DG> convert some test and internal lists). >I just migrated mailman-developers to MM2.1b2 and hit the same >problem. Attached is a fix, which will require a quick b3 release. >If this message goes through, it's a good sign the upgrade went >well. :) If so, I'll post instructions momentarily. Applied the fix and tried to force an upgrade again ... got this ... [root@linux mailman]# bin/update -f Upgrading from version 0x20100b2 to 0x20100b2 getting rid of old source files Updating mailing list: list-owners Traceback (most recent call last): File "bin/update", line 542, in ? errors = main() File "bin/update", line 424, in main errors = errors + dolist(listname) File "bin/update", line 184, in dolist mlist = MailList.MailList(listname, lock=0) File "/usr/local/mailman/Mailman/MailList.py", line 101, in __init__ self.Load() File "/usr/local/mailman/Mailman/MailList.py", line 575, in Load self.CheckValues() File "/usr/local/mailman/Mailman/MailList.py", line 625, in CheckValues for name, pattern, desc, emptyflag in self.topics: File "/usr/local/mailman/Mailman/MailList.py", line 128, in __getattr__ raise AttributeError, name AttributeError: topics david -- | Internet: david@midrange.com | WWW: http://david.fallingrock.net | AIM: MidrangeMan | | If you can't fly, run; if you can't run, walk; | if you can't walk, crawl. | -mlk From asl@launay.org Tue May 7 02:48:56 2002 From: asl@launay.org (Arnaud Launay) Date: Tue, 7 May 2002 03:48:56 +0200 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <15575.10552.622025.10298@anthem.wooz.org>; from barry@zope.com on Mon, May 06, 2002 at 09:09:12PM -0400 References: <15575.10552.622025.10298@anthem.wooz.org> Message-ID: <20020507034856.A12008@launay.org> Le Mon, May 06, 2002 at 09:09:12PM -0400, Barry A. Warsaw a écrit: > If this message goes through, it's a good sign the upgrade went > well. :) If so, I'll post instructions momentarily. It went. Just a small remark, I noticed the Sender field has changed, it was Sender: mailman-developers-admin@python.org and is now Sender: mailman-developers-bounces@python.org which means that everybody filtering on Sender will have to change their filters. Would it be possible either to stand on the past field, or to fix the field once for all ? Thanks, Arnaud (and sorry if this has been discussed previously, I've not enough time to read everything I'd like). From barry@zope.com Tue May 7 02:53:46 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 6 May 2002 21:53:46 -0400 Subject: [Mailman-Developers] Upgrading from 2.0.10 to 2.1.b2 References: <15575.10552.622025.10298@anthem.wooz.org> Message-ID: <15575.13226.368935.689600@anthem.wooz.org> >>>>> "BAW" == Barry A Warsaw writes: BAW> If this message goes through, it's a good sign the upgrade BAW> went well. :) If so, I'll post instructions momentarily. Yay! Okay, migration when pretty smoothly. Here's what I did. Note that we're using Exim 4.something and Apache 1.3.something on python.org. I'm assuming you've got some list under MM2.0.x and you want to migrate it to MM2.1. Let's assume further that you have both versions installed on the same machine, in different locations. - First set your MTA to only accept incoming mail from localhost. You do this because you don't want messages coming in for your list while you're moving it. In Exim4 (and I believe Exim3), the magic is: local_interfaces = 127.0.0.1 and restart. - Turn off your web server, for the same reason. You want your databases to remain quiescent during the move. - Now let MM2.0.x's qrunner clear its qfiles directory. - Do the following: % mv $prefix20/lists/mylist $prefix21/lists % mv $prefix20/archives/private/mylist $prefix21/archives/private % mv $prefix20/archives/private/mylist.mbox $prefix21/archives/private % rm $prefix20/archives/public/mylist % rm $prefix20/archives/public/mylist.mbox % cd $prefix21 % bin/withlist -l -r fix_url mylist - Edit your web server to redirect the old url to the new url. For Apache, I used RedirectMatch /mailman/(.*)/mylist(.*) http://dom.ain/mailman-21/$1/mylist$2 RedirectMatch /pipermail/mylist(.*) http://dom.ain/pipermail-21/mylist$1 - Restart your web server - Do any changes to your MTA to make sure mylist aliases point to the MM2.1 wrapper (this is automatic with the nice Exim config hacks). - Turn on the public interface for your MTA and restart. That's it. -Barry From noreply@sourceforge.net Tue May 7 03:37:58 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 06 May 2002 19:37:58 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-517192 ] 2.0.8 borks on dot in local part of addr Message-ID: Bugs item #517192, was opened at 2002-02-13 13:20 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: Out of Date Priority: 5 Submitted By: CrackMonkey (monkeymaster) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0.8 borks on dot in local part of addr Initial Comment: In a mail address's local part (the part to the left of the at sign), it is perfectly valid to have periods. However, mailman stops reading the address right at the @, so that "mr.bad@pigdog.org" is shown as "mr.bad". this is disastrous for lists where only subscribers are allowed to post, since the system doesn't allow for exceptions that lack an @ and a FQDN. Either allowing exceptions to be of a more forgiving format, or fixing the broken regex that truncates the mail addresses would solve my problem. I'm getting tired of moderating a legitimate user's posts, especially since the system won't even send the warnings to the correct address. ---------------------------------------------------------------------- >Comment By: CrackMonkey (monkeymaster) Date: 2002-05-06 19:37 Message: Logged In: YES user_id=76237 So when testing the 2.2.1 Python, I see the difference. However, the following headers cause it to reject "mr.bad" as a non-subscriber: Received: from mail15.speakeasy.net (mail.speakeasy.net) [216.254.0.215] by zork.zork.net with esmtp (Exim 3.35 #1 (Debian)) id 174ukJ-0000VO-00; Mon, 06 May 2002 19:30:31 -0700 Received: (qmail 3123 invoked from network); 7 May 2002 02:30:29 -0000 Received: from unknown (HELO tyrell) ([66.217.50.46]) (envelope-sender ) by mail15.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 7 May 2002 02:30:29 -0000 Received: from evan by tyrell with local (Exim 3.35 #1 (Debian)) id 174uii-0002m8-00 for ; Mon, 06 May 2002 22:28:52 -0400 To: crackmonkey@crackmonkey.org Subject: %^$!$^$%!! W32.Elkern and Kin From: Mr. Bad Organization: Pigdog Journal X-PGP-Fingerprint: 91F8 6B2D EBEA 8D7A 3F20 E5B0 6D97 B3BC F498 A1D9 X-Revolutionary-Date: Septidi, 17 Flore'al 210 9:25:94 -20833 Date: Mon, 06 May 2002 22:28:48 -0400 Message-ID: <878z6wofmn.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> Lines: 27 User-Agent: Gnus/5.090005 (Oort Gnus v0.05) Emacs/21.1 (i386-debian-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-02 21:08 Message: Logged In: YES user_id=12800 monkeymaster, please try the patch, or include a Python 2.2.1 session that shows the bug still exists. I believe this bug report should be marked closed. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-02 21:07 Message: Logged In: YES user_id=12800 BTW, I'm attaching the patch to Python 2.1.3's rfc822.py that I plan on checking in momentarily. This backports the Python 2.2.1 patch for the problem, and with this, my 2-line example below also succeeds for Python 2.1.3. If there's ever a Python 2.1.4, this patch will be part of it. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-02 20:18 Message: Logged In: YES user_id=10725 I can echo that Python 2.2 doesn't have the parseaddr problem. monkeymaster, can you try Barry's two-line experiment and see if that works or fails? ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-29 15:21 Message: Logged In: YES user_id=76237 This happens even when I use python 2.2 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-27 09:34 Message: Logged In: YES user_id=12800 This is really a bug with earlier versions of Python, I believe. MM2.0.x uses the standard library function rfc822.parseaddr() to break and address into its realname + email constituent parts. Here are some examples: % python Python 2.2.1 (#1, Apr 22 2002, 17:14:12) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('Mr. Bad', 'mr.bad@pigdog.org') % python2.1 Python 2.1.3 (#1, Apr 22 2002, 18:17:38) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('', 'Mr.Bad') So this is clearly broken in Python 2.1.3, and works in Python 2.2.1. I'll look at backporting the fix to Python 2.1 in case there's ever a 2.1.4. But if you're using an earlier version of Python, this will still be broken. Consider upgrading to Python 2.2.1. ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-26 12:54 Message: Logged In: YES user_id=76237 The bug turns out not to be when there is a period in the address, but in the plain text name. The mail address in question is: Mr. Bad I realized this when I saw people who had different text names from their e-mail addresses, as in: Jr. Pickle This would show up as the mythical address "jr.pickle" in mailman, and things would b0rk. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-03-14 11:18 Message: Logged In: YES user_id=12800 Either I need more information, or this problem is fixed in MM2.1. Quite often I uses test addresses like "barry.warsaw@" and I've had no problems with it. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 From mrbill@mrbill.net Tue May 7 03:40:42 2002 From: mrbill@mrbill.net (Bill Bradford) Date: Mon, 6 May 2002 21:40:42 -0500 Subject: [Mailman-Developers] Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <15575.13226.368935.689600@anthem.wooz.org> References: <15575.10552.622025.10298@anthem.wooz.org> <15575.13226.368935.689600@anthem.wooz.org> Message-ID: <20020507024042.GR27488@mrbill.net> On Mon, May 06, 2002 at 09:53:46PM -0400, Barry A. Warsaw wrote: > % mv $prefix20/lists/mylist $prefix21/lists > % mv $prefix20/archives/private/mylist $prefix21/archives/private > % mv $prefix20/archives/private/mylist.mbox $prefix21/archives/private > % rm $prefix20/archives/public/mylist > % rm $prefix20/archives/public/mylist.mbox > % cd $prefix21 > % bin/withlist -l -r fix_url mylist One thing I"ve had to do when moving lists between machines (both running 2.0.9/10), is "newlist" the lists on the destination machine, then overwrite the $prefix/lists/$listname directories/files and $prefix/archives/private/ $listname files with the tarballs I made from the machine currently hosting the list. If I *dont* do this (newlist, then overwrite the "empty" list info files with the "real" stuff), I get errors about the lists not existing. Am I doing something wrong? I've moved one particular list twice now, using this method, with no problems... Bill -- Bill Bradford mrbill@mrbill.net Austin, TX From barry@zope.com Tue May 7 03:53:22 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 6 May 2002 22:53:22 -0400 Subject: [Mailman-Developers] RE: [Mailman-Announce] RELEASED Mailman 2.1 beta 2 References: <20020506170307.GO3731@mrbill.net> <5.1.0.14.2.20020506134450.06389330@lennier.cc.vt.edu> Message-ID: <15575.16802.701761.896596@anthem.wooz.org> >>>>> "RJ" == Ron Jarrell writes: RJ> Definitely not a 2.1 type thing... If Barry keeps stuffing RJ> things into the delivery pipeline, we'll never be able to RJ> thoroughly test it before it goes production :-). Right you are, but you've also hit the nail on the head. The current pipeline architecture /ought/ to be flexible enough to insert any kind of filtering you want, anywhere in the pipeline process. -Barry From barry@zope.com Tue May 7 03:54:12 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 6 May 2002 22:54:12 -0400 Subject: [Mailman-Developers] Re: A RELEASED Mailman 2.1 beta 2 References: <20020506170307.GO3731@mrbill.net> <20020506174334.GN9707@dust.uchicago.edu> Message-ID: <15575.16852.650305.361552@anthem.wooz.org> >>>>> "DC" == David Champion writes: DC> Along these lines, it might be nice if the site op could set DC> up certain filters (or handlers) and make them available at DC> the discretion of the list admin, with the flick of a DC> checkbox. Technically we can do that now, but it would be nice DC> if just by defining the filter, the checkbox is automatically DC> made available in the admin pages. Good idea. I'll put that on the list for post-MM2.1. -Barry From noreply@sourceforge.net Tue May 7 03:57:28 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 06 May 2002 19:57:28 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-553033 ] subscribing via web does not work Message-ID: Bugs item #553033, was opened at 2002-05-06 17:34 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553033&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: javier wilson (javierwilson) Assigned to: Nobody/Anonymous (nobody) Summary: subscribing via web does not work Initial Comment: Users trying to subscribe via web were redirected to the options web page. This only happened with users using Spanish templates. The problem seems to be in the spanish template listinfo.html Instead of "" it should say: "". Is this correct? javier wilson ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-06 22:57 Message: Logged In: YES user_id=12800 Yes, but someone who speaks Spanish is going to have to update the es/listinfo.html file. I took a quick look and couldn't tell for sure what should be changed. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553033&group_id=103 From noreply@sourceforge.net Tue May 7 03:59:22 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 06 May 2002 19:59:22 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-517192 ] 2.0.8 borks on dot in local part of addr Message-ID: Bugs item #517192, was opened at 2002-02-13 16:20 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: Out of Date Priority: 5 Submitted By: CrackMonkey (monkeymaster) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0.8 borks on dot in local part of addr Initial Comment: In a mail address's local part (the part to the left of the at sign), it is perfectly valid to have periods. However, mailman stops reading the address right at the @, so that "mr.bad@pigdog.org" is shown as "mr.bad". this is disastrous for lists where only subscribers are allowed to post, since the system doesn't allow for exceptions that lack an @ and a FQDN. Either allowing exceptions to be of a more forgiving format, or fixing the broken regex that truncates the mail addresses would solve my problem. I'm getting tired of moderating a legitimate user's posts, especially since the system won't even send the warnings to the correct address. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-06 22:59 Message: Logged In: YES user_id=12800 I don't quite understand, are you saying that even though "mr.bad@pigdog.org" is a member of the list, this message is being not matching as being posted from a member? Under Python 2.2.1? ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-05-06 22:37 Message: Logged In: YES user_id=76237 So when testing the 2.2.1 Python, I see the difference. However, the following headers cause it to reject "mr.bad" as a non-subscriber: Received: from mail15.speakeasy.net (mail.speakeasy.net) [216.254.0.215] by zork.zork.net with esmtp (Exim 3.35 #1 (Debian)) id 174ukJ-0000VO-00; Mon, 06 May 2002 19:30:31 -0700 Received: (qmail 3123 invoked from network); 7 May 2002 02:30:29 -0000 Received: from unknown (HELO tyrell) ([66.217.50.46]) (envelope-sender ) by mail15.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 7 May 2002 02:30:29 -0000 Received: from evan by tyrell with local (Exim 3.35 #1 (Debian)) id 174uii-0002m8-00 for ; Mon, 06 May 2002 22:28:52 -0400 To: crackmonkey@crackmonkey.org Subject: %^$!$^$%!! W32.Elkern and Kin From: Mr. Bad Organization: Pigdog Journal X-PGP-Fingerprint: 91F8 6B2D EBEA 8D7A 3F20 E5B0 6D97 B3BC F498 A1D9 X-Revolutionary-Date: Septidi, 17 Flore'al 210 9:25:94 -20833 Date: Mon, 06 May 2002 22:28:48 -0400 Message-ID: <878z6wofmn.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> Lines: 27 User-Agent: Gnus/5.090005 (Oort Gnus v0.05) Emacs/21.1 (i386-debian-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 00:08 Message: Logged In: YES user_id=12800 monkeymaster, please try the patch, or include a Python 2.2.1 session that shows the bug still exists. I believe this bug report should be marked closed. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 00:07 Message: Logged In: YES user_id=12800 BTW, I'm attaching the patch to Python 2.1.3's rfc822.py that I plan on checking in momentarily. This backports the Python 2.2.1 patch for the problem, and with this, my 2-line example below also succeeds for Python 2.1.3. If there's ever a Python 2.1.4, this patch will be part of it. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-02 23:18 Message: Logged In: YES user_id=10725 I can echo that Python 2.2 doesn't have the parseaddr problem. monkeymaster, can you try Barry's two-line experiment and see if that works or fails? ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-29 18:21 Message: Logged In: YES user_id=76237 This happens even when I use python 2.2 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-27 12:34 Message: Logged In: YES user_id=12800 This is really a bug with earlier versions of Python, I believe. MM2.0.x uses the standard library function rfc822.parseaddr() to break and address into its realname + email constituent parts. Here are some examples: % python Python 2.2.1 (#1, Apr 22 2002, 17:14:12) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('Mr. Bad', 'mr.bad@pigdog.org') % python2.1 Python 2.1.3 (#1, Apr 22 2002, 18:17:38) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('', 'Mr.Bad') So this is clearly broken in Python 2.1.3, and works in Python 2.2.1. I'll look at backporting the fix to Python 2.1 in case there's ever a 2.1.4. But if you're using an earlier version of Python, this will still be broken. Consider upgrading to Python 2.2.1. ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-26 15:54 Message: Logged In: YES user_id=76237 The bug turns out not to be when there is a period in the address, but in the plain text name. The mail address in question is: Mr. Bad I realized this when I saw people who had different text names from their e-mail addresses, as in: Jr. Pickle This would show up as the mythical address "jr.pickle" in mailman, and things would b0rk. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-03-14 14:18 Message: Logged In: YES user_id=12800 Either I need more information, or this problem is fixed in MM2.1. Quite often I uses test addresses like "barry.warsaw@" and I've had no problems with it. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 From barry@zope.com Tue May 7 04:01:10 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 6 May 2002 23:01:10 -0400 Subject: [Mailman-Developers] Upgrading from 2.0.10 to 2.1.b2 References: <15575.10552.622025.10298@anthem.wooz.org> <15575.13226.368935.689600@anthem.wooz.org> <20020507024042.GR27488@mrbill.net> Message-ID: <15575.17270.242902.384839@anthem.wooz.org> >>>>> "BB" == Bill Bradford writes: BB> One thing I"ve had to do when moving lists between machines BB> (both running 2.0.9/10), is "newlist" the lists on the BB> destination machine, then overwrite the BB> $prefix/lists/$listname directories/files and BB> $prefix/archives/private/ $listname files with the tarballs I BB> made from the machine currently hosting the list. BB> If I *dont* do this (newlist, then overwrite the "empty" list BB> info files with the "real" stuff), I get errors about the BB> lists not existing. When do you get this error? Note that it may be a virtual host mismatch. Do you still get this error after running fix_url? That's a crucial step. BB> Am I doing something wrong? I've moved one particular list BB> twice now, using this method, with no problems... It shouldn't be necessary, but it's been a long time since I moved a list between machines. -Barry From noreply@sourceforge.net Tue May 7 04:01:54 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 06 May 2002 20:01:54 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-517192 ] 2.0.8 borks on dot in local part of addr Message-ID: Bugs item #517192, was opened at 2002-02-13 13:20 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: Out of Date Priority: 5 Submitted By: CrackMonkey (monkeymaster) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0.8 borks on dot in local part of addr Initial Comment: In a mail address's local part (the part to the left of the at sign), it is perfectly valid to have periods. However, mailman stops reading the address right at the @, so that "mr.bad@pigdog.org" is shown as "mr.bad". this is disastrous for lists where only subscribers are allowed to post, since the system doesn't allow for exceptions that lack an @ and a FQDN. Either allowing exceptions to be of a more forgiving format, or fixing the broken regex that truncates the mail addresses would solve my problem. I'm getting tired of moderating a legitimate user's posts, especially since the system won't even send the warnings to the correct address. ---------------------------------------------------------------------- >Comment By: CrackMonkey (monkeymaster) Date: 2002-05-06 20:01 Message: Logged In: YES user_id=76237 mr.bad@pigdog.org *is* a member of the list, but those headers cause mailman to tell me: List: CrackMonkey@crackmonkey.org From: mr.bad Subject: %^$!$^$%!! W32.Elkern and Kin Reason: Post by non-member to a members-only list Note the lack of an @ or FQDN in the From: Yes, I am using python 2.2.1 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-06 19:59 Message: Logged In: YES user_id=12800 I don't quite understand, are you saying that even though "mr.bad@pigdog.org" is a member of the list, this message is being not matching as being posted from a member? Under Python 2.2.1? ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-05-06 19:37 Message: Logged In: YES user_id=76237 So when testing the 2.2.1 Python, I see the difference. However, the following headers cause it to reject "mr.bad" as a non-subscriber: Received: from mail15.speakeasy.net (mail.speakeasy.net) [216.254.0.215] by zork.zork.net with esmtp (Exim 3.35 #1 (Debian)) id 174ukJ-0000VO-00; Mon, 06 May 2002 19:30:31 -0700 Received: (qmail 3123 invoked from network); 7 May 2002 02:30:29 -0000 Received: from unknown (HELO tyrell) ([66.217.50.46]) (envelope-sender ) by mail15.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 7 May 2002 02:30:29 -0000 Received: from evan by tyrell with local (Exim 3.35 #1 (Debian)) id 174uii-0002m8-00 for ; Mon, 06 May 2002 22:28:52 -0400 To: crackmonkey@crackmonkey.org Subject: %^$!$^$%!! W32.Elkern and Kin From: Mr. Bad Organization: Pigdog Journal X-PGP-Fingerprint: 91F8 6B2D EBEA 8D7A 3F20 E5B0 6D97 B3BC F498 A1D9 X-Revolutionary-Date: Septidi, 17 Flore'al 210 9:25:94 -20833 Date: Mon, 06 May 2002 22:28:48 -0400 Message-ID: <878z6wofmn.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> Lines: 27 User-Agent: Gnus/5.090005 (Oort Gnus v0.05) Emacs/21.1 (i386-debian-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-02 21:08 Message: Logged In: YES user_id=12800 monkeymaster, please try the patch, or include a Python 2.2.1 session that shows the bug still exists. I believe this bug report should be marked closed. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-02 21:07 Message: Logged In: YES user_id=12800 BTW, I'm attaching the patch to Python 2.1.3's rfc822.py that I plan on checking in momentarily. This backports the Python 2.2.1 patch for the problem, and with this, my 2-line example below also succeeds for Python 2.1.3. If there's ever a Python 2.1.4, this patch will be part of it. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-02 20:18 Message: Logged In: YES user_id=10725 I can echo that Python 2.2 doesn't have the parseaddr problem. monkeymaster, can you try Barry's two-line experiment and see if that works or fails? ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-29 15:21 Message: Logged In: YES user_id=76237 This happens even when I use python 2.2 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-27 09:34 Message: Logged In: YES user_id=12800 This is really a bug with earlier versions of Python, I believe. MM2.0.x uses the standard library function rfc822.parseaddr() to break and address into its realname + email constituent parts. Here are some examples: % python Python 2.2.1 (#1, Apr 22 2002, 17:14:12) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('Mr. Bad', 'mr.bad@pigdog.org') % python2.1 Python 2.1.3 (#1, Apr 22 2002, 18:17:38) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('', 'Mr.Bad') So this is clearly broken in Python 2.1.3, and works in Python 2.2.1. I'll look at backporting the fix to Python 2.1 in case there's ever a 2.1.4. But if you're using an earlier version of Python, this will still be broken. Consider upgrading to Python 2.2.1. ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-26 12:54 Message: Logged In: YES user_id=76237 The bug turns out not to be when there is a period in the address, but in the plain text name. The mail address in question is: Mr. Bad I realized this when I saw people who had different text names from their e-mail addresses, as in: Jr. Pickle This would show up as the mythical address "jr.pickle" in mailman, and things would b0rk. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-03-14 11:18 Message: Logged In: YES user_id=12800 Either I need more information, or this problem is fixed in MM2.1. Quite often I uses test addresses like "barry.warsaw@" and I've had no problems with it. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 From marc_news@vasoftware.com Tue May 7 04:09:46 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Mon, 6 May 2002 20:09:46 -0700 Subject: [Mailman-Developers] Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <20020507024042.GR27488@mrbill.net> References: <15575.10552.622025.10298@anthem.wooz.org> <15575.13226.368935.689600@anthem.wooz.org> <20020507024042.GR27488@mrbill.net> Message-ID: <20020507030946.GZ29582@merlins.org> On Mon, May 06, 2002 at 09:40:42PM -0500, Bill Bradford wrote: > One thing I"ve had to do when moving lists between machines (both running > 2.0.9/10), is "newlist" the lists on the destination machine, then overwrite > the $prefix/lists/$listname directories/files and $prefix/archives/private/ > $listname files with the tarballs I made from the machine currently hosting > the list. You don't need to do that. I've moved lists before and that step is not necessary if you move everything you need (list, archives, and alias entries if you're not running exim) > If I *dont* do this (newlist, then overwrite the "empty" list info files > with the "real" stuff), I get errors about the lists not existing. You probably aren't running exim and forgot to move the alias entries. Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From noreply@sourceforge.net Tue May 7 05:43:49 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 06 May 2002 21:43:49 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-517192 ] 2.0.8 borks on dot in local part of addr Message-ID: Bugs item #517192, was opened at 2002-02-13 13:20 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: Out of Date Priority: 5 Submitted By: CrackMonkey (monkeymaster) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0.8 borks on dot in local part of addr Initial Comment: In a mail address's local part (the part to the left of the at sign), it is perfectly valid to have periods. However, mailman stops reading the address right at the @, so that "mr.bad@pigdog.org" is shown as "mr.bad". this is disastrous for lists where only subscribers are allowed to post, since the system doesn't allow for exceptions that lack an @ and a FQDN. Either allowing exceptions to be of a more forgiving format, or fixing the broken regex that truncates the mail addresses would solve my problem. I'm getting tired of moderating a legitimate user's posts, especially since the system won't even send the warnings to the correct address. ---------------------------------------------------------------------- >Comment By: CrackMonkey (monkeymaster) Date: 2002-05-06 21:43 Message: Logged In: YES user_id=76237 Oh, and for what it's worth, I applied that patch as well to my 2.1 copy, so there's no chance that's screwing this up (it's pretty definitely running 2.2.1 now, which doesn't have that 2822 problem) ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-05-06 20:01 Message: Logged In: YES user_id=76237 mr.bad@pigdog.org *is* a member of the list, but those headers cause mailman to tell me: List: CrackMonkey@crackmonkey.org From: mr.bad Subject: %^$!$^$%!! W32.Elkern and Kin Reason: Post by non-member to a members-only list Note the lack of an @ or FQDN in the From: Yes, I am using python 2.2.1 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-06 19:59 Message: Logged In: YES user_id=12800 I don't quite understand, are you saying that even though "mr.bad@pigdog.org" is a member of the list, this message is being not matching as being posted from a member? Under Python 2.2.1? ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-05-06 19:37 Message: Logged In: YES user_id=76237 So when testing the 2.2.1 Python, I see the difference. However, the following headers cause it to reject "mr.bad" as a non-subscriber: Received: from mail15.speakeasy.net (mail.speakeasy.net) [216.254.0.215] by zork.zork.net with esmtp (Exim 3.35 #1 (Debian)) id 174ukJ-0000VO-00; Mon, 06 May 2002 19:30:31 -0700 Received: (qmail 3123 invoked from network); 7 May 2002 02:30:29 -0000 Received: from unknown (HELO tyrell) ([66.217.50.46]) (envelope-sender ) by mail15.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 7 May 2002 02:30:29 -0000 Received: from evan by tyrell with local (Exim 3.35 #1 (Debian)) id 174uii-0002m8-00 for ; Mon, 06 May 2002 22:28:52 -0400 To: crackmonkey@crackmonkey.org Subject: %^$!$^$%!! W32.Elkern and Kin From: Mr. Bad Organization: Pigdog Journal X-PGP-Fingerprint: 91F8 6B2D EBEA 8D7A 3F20 E5B0 6D97 B3BC F498 A1D9 X-Revolutionary-Date: Septidi, 17 Flore'al 210 9:25:94 -20833 Date: Mon, 06 May 2002 22:28:48 -0400 Message-ID: <878z6wofmn.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> Lines: 27 User-Agent: Gnus/5.090005 (Oort Gnus v0.05) Emacs/21.1 (i386-debian-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-02 21:08 Message: Logged In: YES user_id=12800 monkeymaster, please try the patch, or include a Python 2.2.1 session that shows the bug still exists. I believe this bug report should be marked closed. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-02 21:07 Message: Logged In: YES user_id=12800 BTW, I'm attaching the patch to Python 2.1.3's rfc822.py that I plan on checking in momentarily. This backports the Python 2.2.1 patch for the problem, and with this, my 2-line example below also succeeds for Python 2.1.3. If there's ever a Python 2.1.4, this patch will be part of it. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-02 20:18 Message: Logged In: YES user_id=10725 I can echo that Python 2.2 doesn't have the parseaddr problem. monkeymaster, can you try Barry's two-line experiment and see if that works or fails? ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-29 15:21 Message: Logged In: YES user_id=76237 This happens even when I use python 2.2 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-27 09:34 Message: Logged In: YES user_id=12800 This is really a bug with earlier versions of Python, I believe. MM2.0.x uses the standard library function rfc822.parseaddr() to break and address into its realname + email constituent parts. Here are some examples: % python Python 2.2.1 (#1, Apr 22 2002, 17:14:12) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('Mr. Bad', 'mr.bad@pigdog.org') % python2.1 Python 2.1.3 (#1, Apr 22 2002, 18:17:38) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad ') ('', 'Mr.Bad') So this is clearly broken in Python 2.1.3, and works in Python 2.2.1. I'll look at backporting the fix to Python 2.1 in case there's ever a 2.1.4. But if you're using an earlier version of Python, this will still be broken. Consider upgrading to Python 2.2.1. ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-26 12:54 Message: Logged In: YES user_id=76237 The bug turns out not to be when there is a period in the address, but in the plain text name. The mail address in question is: Mr. Bad I realized this when I saw people who had different text names from their e-mail addresses, as in: Jr. Pickle This would show up as the mythical address "jr.pickle" in mailman, and things would b0rk. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-03-14 11:18 Message: Logged In: YES user_id=12800 Either I need more information, or this problem is fixed in MM2.1. Quite often I uses test addresses like "barry.warsaw@" and I've had no problems with it. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id=103 From noreply@sourceforge.net Tue May 7 05:48:45 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 06 May 2002 21:48:45 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-553128 ] cant use alternate port Message-ID: Bugs item #553128, was opened at 2002-05-06 22:48 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553128&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Christopher Donald Wiegand (cdwiegand) Assigned to: Nobody/Anonymous (nobody) Summary: cant use alternate port Initial Comment: I have to use port 81 for my webserver (due to a NAT issue on the firewall, as port 80 is already in use). I have adjusted DEFAULT_URL_HOST, and have also tried adjusting DEFAULT_URL_PATTERN, and in most places this works, however, when a list has it's archive made private, it does not include the :81 I appended to the variable... This *appears* to be a bug with Mailman 2.1b1. Also affects the submit button when you reject/ignore/approve moderated items from the list admin menu. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553128&group_id=103 From claw@kanga.nu Tue May 7 05:57:22 2002 From: claw@kanga.nu (J C Lawrence) Date: Mon, 06 May 2002 21:57:22 -0700 Subject: [Mailman-Developers] RE: [Mailman-Announce] RELEASED Mailman 2.1 beta 2 In-Reply-To: Message from Chuq Von Rospach of "Mon, 06 May 2002 10:24:28 PDT." References: Message-ID: <30907.1020747442@kanga.nu> On Mon, 06 May 2002 10:24:28 -0700 Chuq Von Rospach wrote: > I would, by the way, do two of these: a pre-filter and a > post-filter. The pre-filter is primarily for cleaning up before it > goes for delivery. If you allow it to return a set of known values, > you can even use it for determining moderator hold, rejection, etc > (and through that, plug into tools like spamassasin). The post-filter > would be a nice, easy hook into things like mhonarc for customized > archive systems and the like... I would kill for a post-filter. Why? So I can inject every message with the URL of where it sits in the web archives. _______________________________________________ WhatEver Mailing list whatever@some.domain http://some.domain/lists/listinfo/whatever Message archived at: http://some.domain/archives/whatever/2002Q2/mesg0009.php -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From barry@zope.com Tue May 7 06:12:25 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 01:12:25 -0400 Subject: [Mailman-Developers] 2.1b1 Moderation and From: vs. Sender: References: <25756.1017157154@elisabeth.cfrq.net> Message-ID: <15575.25145.291906.900927@anthem.wooz.org> >>>>> "HK" == Harald Koch writes: HK> However, my 'trick' of adding a Sender: field doesn't work HK> anymore, and I get a confusing log/hold message that says HK> "humour post from chk@cfrq.net held: Post by a moderated HK> member". 'chk@cfrq.net' is not moderated. HK> It turns out that, in order to find the moderation flag of the HK> user that send a message, Handlers/Moderate.py calls HK> msg.get_senders, which returns a *list* of senders with the HK> Sender: last; Moderate.py only looks at the first return HK> value, which is the From: header. The address in the From: HK> field *is* moderated, and so the message is rejected. Later, HK> however, Handlers/Hold.py routine hold_for_approval calls the HK> old msg.get_sender (singular vs. plural), which returns the HK> Sender: field if "USE_ENVELOPE_SENDER = 1" is set, which is HK> why I get the confusing log message. HK> So, two things: HK> 1) The message rejection is confusing. HK> 2) What's the right way to do this under 2.1? >>>>> Later... >>>>> "HK" == Harald Koch writes: HK> Ok, I just found the Approved: header processing... *sigh. HK> The hold message is still confusing though. You're right it is. And I'll fix that. I believe that using the Approved: header is the better way to go, since it's more difficult to fake out (someone would have to have the list admin password, rather than trivially be able to forge the Sender: or From: or whatever header). -Barry From marc_news@vasoftware.com Tue May 7 06:16:13 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Mon, 6 May 2002 22:16:13 -0700 Subject: [Mailman-Developers] RE: [Mailman-Announce] RELEASED Mailman 2.1 beta 2 In-Reply-To: <30907.1020747442@kanga.nu> References: <30907.1020747442@kanga.nu> Message-ID: <20020507051613.GE29582@merlins.org> On Mon, May 06, 2002 at 09:57:22PM -0700, J C Lawrence wrote: > On Mon, 06 May 2002 10:24:28 -0700 > Chuq Von Rospach wrote: > > > I would, by the way, do two of these: a pre-filter and a > > post-filter. The pre-filter is primarily for cleaning up before it > > goes for delivery. If you allow it to return a set of known values, > > you can even use it for determining moderator hold, rejection, etc > > (and through that, plug into tools like spamassasin). The post-filter > > would be a nice, easy hook into things like mhonarc for customized > > archive systems and the like... > > I would kill for a post-filter. Why? So I can inject every message > with the URL of where it sits in the web archives. Yeah, liststar does that, and it's *quite* nice. Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From marc_news@vasoftware.com Tue May 7 06:21:29 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Mon, 6 May 2002 22:21:29 -0700 Subject: [Mailman-Developers] RE: [Mailman-Announce] RELEASED Mailman 2.1 beta 2 In-Reply-To: <20020507051613.GE29582@merlins.org> References: <30907.1020747442@kanga.nu> <20020507051613.GE29582@merlins.org> Message-ID: <20020507052129.GG29582@merlins.org> On Mon, May 06, 2002 at 10:16:13PM -0700, Marc MERLIN wrote: > > I would kill for a post-filter. Why? So I can inject every message > > with the URL of where it sits in the web archives. > > Yeah, liststar does that, and it's *quite* nice. Never mind, I misread. What I meant to say is that it'd be nice to strip attachments, and give the URL to the attachments in the web archive, like liststar does Of course, that's probably home hacking, or post mm 2.1 stuff Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From barry@zope.com Tue May 7 06:25:15 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 01:25:15 -0400 Subject: [Mailman-Developers] RE: [Mailman-Announce] RELEASED Mailman 2.1 beta 2 References: <30907.1020747442@kanga.nu> Message-ID: <15575.25915.125177.318110@anthem.wooz.org> >>>>> "JCL" == J C Lawrence writes: JCL> I would kill for a post-filter. Why? So I can inject every JCL> message with the URL of where it sits in the web archives. >>>>> "MM" == Marc MERLIN writes: MM> Yeah, liststar does that, and it's *quite* nice. It could be done with just a moderate bit of hacking. I could see making it easy to add with just a couple of hooks. The tricky part, of course is calculating the url from some information in the message, the Message-ID: perhaps? Or do you ask the archive itself? If so, how? Given the ability to extract or calculate that url, it's probably not much more than an hour's hack. -Barry From claw@kanga.nu Tue May 7 06:27:04 2002 From: claw@kanga.nu (J C Lawrence) Date: Mon, 06 May 2002 22:27:04 -0700 Subject: [Mailman-Developers] RE: [Mailman-Announce] RELEASED Mailman 2.1 beta 2 In-Reply-To: Message from Marc MERLIN of "Mon, 06 May 2002 22:21:29 PDT." <20020507052129.GG29582@merlins.org> References: <30907.1020747442@kanga.nu> <20020507051613.GE29582@merlins.org> <20020507052129.GG29582@merlins.org> Message-ID: <31489.1020749224@kanga.nu> On Mon, 6 May 2002 22:21:29 -0700 Marc MERLIN wrote: > On Mon, May 06, 2002 at 10:16:13PM -0700, Marc MERLIN wrote: >>> I would kill for a post-filter. Why? So I can inject every >>> message with the URL of where it sits in the web archives. >> Yeah, liststar does that, and it's *quite* nice. > Never mind, I misread. What I meant to say is that it'd be nice to > strip attachments, and give the URL to the attachments in the web > archive, like liststar does Of course, that's probably home hacking, > or post mm 2.1 stuff Which, given post-filters (which as Barry says, should be fairly easy to do under 2.1) that should be pretty easy to do: message -> Mailman -> MHonArc -> demime -> postfilter -> MTA The postfilter (ignoring the fact that its all a postfilter) just inserts the URLs to the bits that MHonArc extracted (and demime later stripped) -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From barry@zope.com Tue May 7 06:27:27 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 01:27:27 -0400 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 References: <15575.10552.622025.10298@anthem.wooz.org> <20020507034856.A12008@launay.org> Message-ID: <15575.26047.681641.9884@anthem.wooz.org> >>>>> "AL" == Arnaud Launay writes: AL> Just a small remark, I noticed the Sender field has changed, AL> it was Sender: mailman-developers-admin@python.org and is now AL> Sender: mailman-developers-bounces@python.org AL> which means that everybody filtering on Sender will have to AL> change their filters. Would it be possible either to stand on AL> the past field, or to fix the field once for all ? Do a lot of people filter on Sender: and if so, why filter on that header instead of one of the recipient headers? In any event, I don't see changing the Sender: header any time soon, so I'd like to say it's fixed in stone <3.0 wink>. -Barry From stijn@win.tue.nl Tue May 7 06:29:53 2002 From: stijn@win.tue.nl (Stijn Hoop) Date: Tue, 7 May 2002 07:29:53 +0200 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <15575.26047.681641.9884@anthem.wooz.org>; from barry@zope.com on Tue, May 07, 2002 at 01:27:27AM -0400 References: <15575.10552.622025.10298@anthem.wooz.org> <20020507034856.A12008@launay.org> <15575.26047.681641.9884@anthem.wooz.org> Message-ID: <20020507072953.A57829@pcwin002.win.tue.nl> On Tue, May 07, 2002 at 01:27:27AM -0400, Barry A. Warsaw wrote: > > >>>>> "AL" == Arnaud Launay writes: > > AL> Just a small remark, I noticed the Sender field has changed, > AL> it was Sender: mailman-developers-admin@python.org and is now > AL> Sender: mailman-developers-bounces@python.org > AL> which means that everybody filtering on Sender will have to > AL> change their filters. Would it be possible either to stand on > AL> the past field, or to fix the field once for all ? > > Do a lot of people filter on Sender: and if so, why filter on that > header instead of one of the recipient headers? I do, and I don't know why :) At least my inbox was full of mailman mail this morning, instead of my =mailman folder :) > In any event, I don't see changing the Sender: header any time soon, > so I'd like to say it's fixed in stone <3.0 wink>. OK, I'll change my recipe. --Stijn -- In the force if Yoda's so strong, construct a sentence with words in the proper order then why can't he? From barry@zope.com Tue May 7 06:36:40 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 01:36:40 -0400 Subject: [Mailman-Developers] Upgrading from 2.0.10 to 2.1.b2 References: <5.1.0.14.2.20020506203919.02407918@linux.midrange.com> Message-ID: <15575.26600.909733.161628@anthem.wooz.org> >>>>> "DG" == David Gibbs writes: DG> Applied the fix and tried to force an upgrade again ... got DG> this ... Hmm, I can't reproduce this. I just tried creating a list under 2.0.10, then migrated it to 2.1, ran bin/update and it works just fine. bin/withlist showed me that the list had the topics attribute. What happens when you do % bin/withlist list-owners >>> m.topics ? -Barry From barry@zope.com Tue May 7 06:38:05 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 01:38:05 -0400 Subject: [Mailman-Developers] RE: [Mailman-Announce] RELEASED Mailman 2.1 beta 2 References: <30907.1020747442@kanga.nu> <20020507051613.GE29582@merlins.org> <20020507052129.GG29582@merlins.org> Message-ID: <15575.26685.772123.795906@anthem.wooz.org> >>>>> "MM" == Marc MERLIN writes: MM> Never mind, I misread. What I meant to say is that it'd be MM> nice to strip attachments, and give the URL to the attachments MM> in the web archive, like liststar does Of course, that's MM> probably home hacking, or post mm 2.1 stuff Ah yes, but it probably requires more cooperation from your archiver than we have with Pipermail. Definitely post-2.1 stuff. -Barry From barry@zope.com Tue May 7 06:41:17 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 01:41:17 -0400 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 References: <15575.10552.622025.10298@anthem.wooz.org> <20020507034856.A12008@launay.org> <15575.26047.681641.9884@anthem.wooz.org> <20020507072953.A57829@pcwin002.win.tue.nl> Message-ID: <15575.26877.643640.472131@anthem.wooz.org> >>>>> "SH" == Stijn Hoop writes: SH> I do, and I don't know why :) :) SH> At least my inbox was full of mailman mail this morning, SH> instead of my =mailman folder :) >> In any event, I don't see changing the Sender: header any time >> soon, so I'd like to say it's fixed in stone <3.0 wink>. SH> OK, I'll change my recipe. I ask because, although I don't do procmail, I still filter stuff in my MUA, but I do it on either a `recip' filter (which matches To: and Cc:) or the Subject: header, which matches the prefix. -Barry From claw@kanga.nu Tue May 7 07:00:06 2002 From: claw@kanga.nu (J C Lawrence) Date: Mon, 06 May 2002 23:00:06 -0700 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: Message from barry@zope.com (Barry A. Warsaw) of "Tue, 07 May 2002 01:27:27 EDT." <15575.26047.681641.9884@anthem.wooz.org> References: <15575.10552.622025.10298@anthem.wooz.org> <20020507034856.A12008@launay.org> <15575.26047.681641.9884@anthem.wooz.org> Message-ID: <32623.1020751206@kanga.nu> On Tue, 7 May 2002 01:27:27 -0400 Barry A Warsaw wrote: > Do a lot of people filter on Sender: and if so, why filter on that > header instead of one of the recipient headers? I filter by default on Sender:. Why? In general its unique across all lists, no matter the MLM used (Yahoo groups are the big exception, sadly). RFC 2369 headers may or may not be there. Checking To/CC missed BCC's and confuses direct vs list messages for non-reply-to-munging lists. Sender, with rare exception, is reliable as a distinguishing factor for all lists. > In any event, I don't see changing the Sender: header any time soon, > so I'd like to say it's fixed in stone <3.0 wink>. I wouldn't rate changing Sender as much of a problem. Its an upgrade. 3rd party unrelated systems are expected to have to adapt -- and this is a pretty minor adaption. ObNote: Actually my procmail filters are sufficiently generous with their regexes that the new pattern gets matched just fine, so there! Nyahh! -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From chuqui@plaidworks.com Tue May 7 07:06:40 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Mon, 06 May 2002 23:06:40 -0700 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <20020507034856.A12008@launay.org> Message-ID: On 5/6/02 6:48 PM, "Arnaud Launay" wrote: > Sender: mailman-developers-bounces@python.org > > which means that everybody filtering on Sender will have to > change their filters. The real answer, IMHO, is "why are you filtering on Sender, anyway? That's what List-ID is for". -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ Very funny, Scotty. Now beam my clothes down here, will you? From claw@kanga.nu Tue May 7 07:12:12 2002 From: claw@kanga.nu (J C Lawrence) Date: Mon, 06 May 2002 23:12:12 -0700 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: Message from Chuq Von Rospach of "Mon, 06 May 2002 23:06:40 PDT." References: Message-ID: <347.1020751932@kanga.nu> On Mon, 06 May 2002 23:06:40 -0700 Chuq Von Rospach wrote: > The real answer, IMHO, is "why are you filtering on Sender, anyway? > That's what List-ID is for". Sadly, less than a third of the lists I'm subscribed to have RFC 2369 headers. All but (counts quickly) 6 (all Yahoo Groups) have unique Sender: headers tho. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From stijn@win.tue.nl Tue May 7 07:57:24 2002 From: stijn@win.tue.nl (Stijn Hoop) Date: Tue, 7 May 2002 08:57:24 +0200 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <15575.26877.643640.472131@anthem.wooz.org>; from barry@zope.com on Tue, May 07, 2002 at 01:41:17AM -0400 References: <15575.10552.622025.10298@anthem.wooz.org> <20020507034856.A12008@launay.org> <15575.26047.681641.9884@anthem.wooz.org> <20020507072953.A57829@pcwin002.win.tue.nl> <15575.26877.643640.472131@anthem.wooz.org> Message-ID: <20020507085724.A58355@pcwin002.win.tue.nl> ---------------------- multipart/signed attachment On Tue, May 07, 2002 at 01:41:17AM -0400, Barry A. Warsaw wrote: > I ask because, although I don't do procmail, I still filter stuff in > my MUA, but I do it on either a `recip' filter (which matches To: and > Cc:) or the Subject: header, which matches the prefix. I suspect it's just an old habit of mine - before I got to use mailman lists, I was subscribed on lists didn't prefix their subjects. I carried ov= er my filters from those lists, which is why I was filtering on ^From. It might be smart to document the different From line though. --Stijn --=20 "I used to think I was indecisive, but now I'm not so sure." ---------------------- multipart/signed attachment A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://mail.python.org/pipermail-21/mailman-developers/attachments/95757a60/attachment.bin ---------------------- multipart/signed attachment-- From asl@launay.org Tue May 7 10:41:52 2002 From: asl@launay.org (Arnaud Launay) Date: Tue, 7 May 2002 11:41:52 +0200 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <15575.26047.681641.9884@anthem.wooz.org>; from barry@zope.com on Tue, May 07, 2002 at 01:27:27AM -0400 References: <15575.10552.622025.10298@anthem.wooz.org> <20020507034856.A12008@launay.org> <15575.26047.681641.9884@anthem.wooz.org> Message-ID: <20020507114152.B2092@launay.org> Le Tue, May 07, 2002 at 01:27:27AM -0400, Barry A. Warsaw a écrit: > In any event, I don't see changing the Sender: header any time > soon, so I'd like to say it's fixed in stone <3.0 wink>. Question is, why did it change between 2.0.10 and 2.1.b2 :-) When other sites will upgrade, if they generate lots of traffic, it will be a pain to filter the posts by hand... Arnaud. -- Plus je connais les hommes, plus j'aime mon chien. Plus je connais les femmes, moins j'aime ma chienne. From david@midrange.com Tue May 7 12:20:28 2002 From: david@midrange.com (David Gibbs) Date: Tue, 07 May 2002 06:20:28 -0500 Subject: [Mailman-Developers] Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <15575.26600.909733.161628@anthem.wooz.org> References: <5.1.0.14.2.20020506203919.02407918@linux.midrange.com> Message-ID: <5.1.0.14.2.20020507061724.02436828@linux.midrange.com> At 12:36 AM 5/7/2002, Barry A. Warsaw wrote: >What happens when you do > > % bin/withlist list-owners > >>> m.topics /usr/local/mailman $bin/withlist list-owners Loading list list-owners (unlocked) Traceback (most recent call last): File "bin/withlist", line 271, in ? main() File "bin/withlist", line 252, in main r = do_list(listname, args, func) File "bin/withlist", line 178, in do_list m = MailList.MailList(listname, lock=LOCK) File "/usr/local/mailman/Mailman/MailList.py", line 101, in __init__ self.Load() File "/usr/local/mailman/Mailman/MailList.py", line 575, in Load self.CheckValues() File "/usr/local/mailman/Mailman/MailList.py", line 625, in CheckValues for name, pattern, desc, emptyflag in self.topics: File "/usr/local/mailman/Mailman/MailList.py", line 128, in __getattr__ raise AttributeError, name AttributeError: topics Just to clarify what I did ... I did a virgin install of 2.1b2, copied over the entire "lists/list-owners" directory from my 2.0.10 install directory to 2.1b2 directory, then ran bin/update -f. Would it be useful to have the a copy of the list data? It's a very small list. david -- | Internet: david@midrange.com | WWW: http://david.fallingrock.net | AIM: MidrangeMan | | If you can't fly, run; if you can't run, walk; | if you can't walk, crawl. | -mlk From barry@zope.com Tue May 7 15:04:48 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 10:04:48 -0400 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 References: <15575.10552.622025.10298@anthem.wooz.org> <20020507034856.A12008@launay.org> <15575.26047.681641.9884@anthem.wooz.org> <20020507114152.B2092@launay.org> Message-ID: <15575.57088.331868.201259@anthem.wooz.org> >>>>> "AL" == Arnaud Launay writes: AL> Question is, why did it change between 2.0.10 and 2.1.b2 :-) The -admin address is deprecated. We wanted to unify the the address extension and the script that handles them because it makes life much more easy for MTA integration based on regexps. And it was too hard to keep track of whether -admin did bounce processing or not. AL> When other sites will upgrade, if they generate lots of AL> traffic, it will be a pain to filter the posts by hand... Sigh, you can't win, can ya? -Barry From barry@zope.com Tue May 7 15:06:52 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 10:06:52 -0400 Subject: [Mailman-Developers] Upgrading from 2.0.10 to 2.1.b2 References: <5.1.0.14.2.20020506203919.02407918@linux.midrange.com> <5.1.0.14.2.20020507061724.02436828@linux.midrange.com> Message-ID: <15575.57212.18477.739816@anthem.wooz.org> >>>>> "DG" == David Gibbs writes: DG> Just to clarify what I did ... I did a virgin install of DG> 2.1b2, copied over the entire "lists/list-owners" directory DG> from my 2.0.10 install directory to 2.1b2 directory, then ran DG> bin/update -f. And you're positive you did this /after/ you applied the patch and did a make install, right? DG> Would it be useful to have the a copy of the list data? It's DG> a very small list. If you can send me the MM2.0 version of the list, tar up the whole $prefix/lists/list-owners directory, and send that to me directly. -Barry From danny@terweij.nl Tue May 7 15:32:18 2002 From: danny@terweij.nl (Danny Terweij) Date: Tue, 7 May 2002 16:32:18 +0200 Subject: [Mailman-Developers] When deleting a list not all data is cleaned up mm21b2 Message-ID: <02dc01c1f5d3$ffd2e380$1e00a8c0@poema.yi.org> This is a multi-part message in MIME format. ---------------------- multipart/mixed attachment ------=_NextPart_001_02D9_01C1F5E4.C185BB00 Hi, When deleting a list with ./rmlist, all the held messages stored are not = erased. (~mailman/data) Danny. ------=_NextPart_001_02D9_01C1F5E4.C185BB00 An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail-21/mailman-developers/attachments/79c7ea93/attachment.html ------=_NextPart_001_02D9_01C1F5E4.C185BB00-- ---------------------- multipart/mixed attachment A non-text attachment was scrubbed... Name: Dannny Terweij.vcf Type: text/x-vcard Size: 260 bytes Desc: not available Url : http://mail.python.org/pipermail-21/mailman-developers/attachments/55485a82/DannnyTerweij.vcf ---------------------- multipart/mixed attachment-- From danny@terweij.nl Tue May 7 15:40:24 2002 From: danny@terweij.nl (Danny Terweij) Date: Tue, 7 May 2002 16:40:24 +0200 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) Message-ID: <030601c1f5d5$1fd9ef60$1e00a8c0@poema.yi.org> This is a multi-part message in MIME format. ---------------------- multipart/alternative attachment And also you see here the vcard problem! Nice this list is upgraded to the mm2.1 beta :-) I want get rid of these
lines when send an vcard as attachment in = an HTML mail. ----- Original Message -----=20 From: Danny Terweij=20 To: mailman-developers@python.org=20 Sent: Tuesday, May 07, 2002 4:32 PM Subject: [Mailman-Developers] When deleting a list not all data is = cleaned up mm21b2 -------------------------------------------------------------------------= ----- Hi, When deleting a list with ./rmlist, all the held messages stored are = not erased. (~mailman/data) Danny. -------------------------------------------------------------------------= ----- _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman-21/listinfo/mailman-developers ---------------------- multipart/alternative attachment An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail-21/mailman-developers/attachments/567a3431/attachment.html ---------------------- multipart/alternative attachment-- From chk@pobox.com Tue May 7 16:08:39 2002 From: chk@pobox.com (Harald Koch) Date: Tue, 07 May 2002 11:08:39 -0400 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: Your message of "Tue, 07 May 2002 16:40:24 +0200". <030601c1f5d5$1fd9ef60$1e00a8c0@poema.yi.org> References: <030601c1f5d5$1fd9ef60$1e00a8c0@poema.yi.org> Message-ID: <32495.1020784119@elisabeth.cfrq.net> > And also you see here the vcard problem! > Nice this list is upgraded to the mm2.1 beta :-) > I want get rid of these
lines when send an vcard as attachment in = > an HTML mail. I think you're confused. There are no
lines in the first message you sent (the one with the vcard attached). Your mailer might be displaying the attachments strangely, but that's not mailman's fault. Of course, some others might remind you that most of us despise seeing a vcard attached to every message, but not me :-) -- Harald Koch From danny@terweij.nl Tue May 7 16:24:48 2002 From: danny@terweij.nl (Danny Terweij) Date: Tue, 7 May 2002 17:24:48 +0200 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) References: <030601c1f5d5$1fd9ef60$1e00a8c0@poema.yi.org> <32495.1020784119@elisabeth.cfrq.net> Message-ID: <034d01c1f5db$5374efe0$1e00a8c0@poema.yi.org> This is a multi-part message in MIME format. ---------------------- multipart/mixed attachment ------=_NextPart_001_034A_01C1F5EC.16C23D80 From: "Harald Koch" > > And also you see here the vcard problem! > > Nice this list is upgraded to the mm2.1 beta :-) > > I want get rid of these
lines when send an vcard as attachment = in =3D > > an HTML mail. =20 > I think you're confused. There are no
lines in the first message > you sent (the one with the vcard attached). Your mailer might be > displaying the attachments strangely, but that's not mailman's fault. There is! and i doing convert this message to HTML and put the VCARD in = it. All my lists-owners and members are complaining. My lists are used to be a alternative for yahoo groups and the e-mails = posted are HTML stationeries. So alle mails are written end read with Microsoft outlook express 5 and = 6. The vcard is used on yahoo groups to get rid of the advertisements = banners (bug at yahoo??) =20 > Of course, some others might remind you that most of us despise seeing = a > vcard attached to every message, but not me :-) I know.. so i ask any developer to handle this problem and look at it. I = want not see the 2
lines at the mails. (it is added by mailman = somewhere..) Danny. ------=_NextPart_001_034A_01C1F5EC.16C23D80 An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail-21/mailman-developers/attachments/b265f1e8/attachment.html ------=_NextPart_001_034A_01C1F5EC.16C23D80-- ---------------------- multipart/mixed attachment A non-text attachment was scrubbed... Name: Dannny Terweij.vcf Type: text/x-vcard Size: 260 bytes Desc: not available Url : http://mail.python.org/pipermail-21/mailman-developers/attachments/29fb6fc7/DannnyTerweij.vcf ---------------------- multipart/mixed attachment-- From chuqui@plaidworks.com Tue May 7 16:32:07 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Tue, 07 May 2002 08:32:07 -0700 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <347.1020751932@kanga.nu> Message-ID: On 5/6/02 11:12 PM, "J C Lawrence" wrote: > Sadly, less than a third of the lists I'm subscribed to have RFC 2369 > headers. All but (counts quickly) 6 (all Yahoo Groups) have unique > Sender: headers tho. So? So use list-id when it exists, and filter on non-standard things when it doesn't. List-ID is guaranteed unique and to not change. Sender -- isn't. Yes, Sender is useful when the List-ID isn't there, but if you depend on it, stuff like this happens. That's why List-ID was invented and why Mailman supports it. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ IMHO: Jargon. Acronym for In My Humble Opinion. Used to flag as an opinion something that is clearly from context an opinion to everyone except the mentally dense. Opinions flagged by IMHO are actually rarely humble. IMHO. (source: third unabridged dictionary of chuqui-isms). From chuqui@plaidworks.com Tue May 7 16:35:22 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Tue, 07 May 2002 08:35:22 -0700 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <15575.57088.331868.201259@anthem.wooz.org> Message-ID: On 5/7/02 7:04 AM, "Barry A. Warsaw" wrote: > AL> When other sites will upgrade, if they generate lots of > AL> traffic, it will be a pain to filter the posts by hand... > > Sigh, you can't win, can ya? I'm sorry, but I'll take a hard line here. If you're filtering messages THE WRONG WAY (using Sender instead of List-ID), then you shouldn't complain that it breaks because you're using a header line in a way it's not intended to be used for. The whole purpose of List-ID is identification and filtering. Sender isn't. That Sender was used for that doesn't mean it SHOULD be used for it when the proper tool is there. This is a case of yelling about "how I want things to be", not "how things should be". And I just can't work up much angst over non-standard personal preferences that are in conflict with the supported standards... -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ The Cliff's Notes Cliff's Notes on Hamlet: And they all died happily ever after From mrbill@mrbill.net Tue May 7 16:53:42 2002 From: mrbill@mrbill.net (Bill Bradford) Date: Tue, 7 May 2002 10:53:42 -0500 Subject: [Mailman-Developers] Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <20020507030946.GZ29582@merlins.org> References: <15575.10552.622025.10298@anthem.wooz.org> <15575.13226.368935.689600@anthem.wooz.org> <20020507024042.GR27488@mrbill.net> <20020507030946.GZ29582@merlins.org> Message-ID: <20020507155342.GY27488@mrbill.net> On Mon, May 06, 2002 at 08:09:46PM -0700, Marc MERLIN wrote: > You don't need to do that. I've moved lists before and that step is not > necessary if you move everything you need (list, archives, and alias entries > if you're not running exim) So far, I've done this numerous times, and it *is* necessary, and yes, I moved EVERYTHING (list, archives, aliases). Its like MM doesent realize that the files are *there*, in $prefix/lists/ > You probably aren't running exim and forgot to move the alias entries. Running Postfix, and yeah, I *did* move aliases.. Bill -- Bill Bradford mrbill@mrbill.net Austin, TX From dgibbs@mks.com Tue May 7 17:04:50 2002 From: dgibbs@mks.com (David Gibbs) Date: Tue, 7 May 2002 11:04:50 -0500 Subject: [Mailman-Developers] Re: Re: Upgrading from 2.0.10 to 2.1.b2 References: <15575.57088.331868.201259@anthem.wooz.org> Message-ID: "Chuq Von Rospach" wrote in message news:B8FD424A.320F8%chuqui@plaidworks.com... > I'm sorry, but I'll take a hard line here. If you're filtering messages THE > WRONG WAY (using Sender instead of List-ID), then you shouldn't complain > that it breaks because you're using a header line in a way it's not intended > to be used for. The whole purpose of List-ID is identification and > filtering. Sender isn't. That Sender was used for that doesn't mean it > SHOULD be used for it when the proper tool is there. When you have to deal with many different types of email clients, there is no *WRONG*WAY* to filter ... not every email client has all the filtering capabilities one would like. Outlook, Outlook express, Domino, among others, have rather limited filtering capabilities. david From carson@taltos.org Tue May 7 17:02:20 2002 From: carson@taltos.org (Carson Gaspar) Date: Tue, 07 May 2002 12:02:20 -0400 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <15575.26877.643640.472131@anthem.wooz.org> References: <15575.26877.643640.472131@anthem.wooz.org> Message-ID: <176750968.1020772940@[192.168.0.1]> --On Tuesday, May 07, 2002 1:41 AM -0400 "Barry A. Warsaw" wrote: > I ask because, although I don't do procmail, I still filter stuff in > my MUA, but I do it on either a `recip' filter (which matches To: and > Cc:) or the Subject: header, which matches the prefix. To: and Cc: are unreliable. People Bcc: lists all the time. Most lists I use are run by people who, like me, hate subject prefixes. So that won't work. I used to filter on Sender:, because it was the most reliable header. Now I filter on List-ID:, if it exists, and fall back to Sender: if it doesn't. -- Carson Gaspar - carson@taltos.org Queen Trapped in a Butch Body From marc_news@vasoftware.com Tue May 7 18:16:18 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Tue, 7 May 2002 10:16:18 -0700 Subject: [Mailman-Developers] Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <20020507155342.GY27488@mrbill.net> References: <15575.10552.622025.10298@anthem.wooz.org> <15575.13226.368935.689600@anthem.wooz.org> <20020507024042.GR27488@mrbill.net> <20020507030946.GZ29582@merlins.org> <20020507155342.GY27488@mrbill.net> Message-ID: <20020507171618.GR30327@merlins.org> On Tue, May 07, 2002 at 10:53:42AM -0500, Bill Bradford wrote: > On Mon, May 06, 2002 at 08:09:46PM -0700, Marc MERLIN wrote: > > You don't need to do that. I've moved lists before and that step is not > > necessary if you move everything you need (list, archives, and alias entries > > if you're not running exim) > > So far, I've done this numerous times, and it *is* necessary, and yes, I > moved EVERYTHING (list, archives, aliases). Its like MM doesent realize > that the files are *there*, in $prefix/lists/ I don't know what to tell you. I have done this too, more than once, and it's always worked. If the two installs weren't in the same directory, I obviously had to run move_list, but that was it. > > You probably aren't running exim and forgot to move the alias entries. > > Running Postfix, and yeah, I *did* move aliases.. What error did you get? A bounce from postfix saying that the list didn't exist or an error from the mailman wrapper? Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From asl@launay.org Tue May 7 18:44:18 2002 From: asl@launay.org (Arnaud Launay) Date: Tue, 7 May 2002 19:44:18 +0200 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: ; from chuqui@plaidworks.com on Tue, May 07, 2002 at 08:32:07AM -0700 References: <347.1020751932@kanga.nu> Message-ID: <20020507194418.A6536@launay.org> Le Tue, May 07, 2002 at 08:32:07AM -0700, Chuq Von Rospach a écrit: > That's why List-ID was invented and why Mailman supports it. Does the term 'history' means something to you ? I'm beginning to be very tired to modify my filters with each new release of mailman. And I used Sender because, for a long time, it was the only reliable header. Arnaud. -- User: I'm having problems with my text editor. Help desk: Which editor are you using? User: I don't know, but it's version VI (pronounced: 6). Help desk: Oh, then you should upgrade to version VIM (pronounced: 994). From jarrell@vt.edu Tue May 7 19:10:53 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Tue, 07 May 2002 14:10:53 -0400 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: <030601c1f5d5$1fd9ef60$1e00a8c0@poema.yi.org> Message-ID: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> At 04:40 PM 5/7/02 +0200, Danny Terweij wrote: >And also you see here the vcard problem! >Nice this list is upgraded to the mm2.1 beta :-) >I want get rid of these
lines when send an vcard as attachment in an HTML mail. > I think that's your client doing that... I'm not seeing the HR lines in my copy of your email, but did see them in the copy you forwarded back to the list! From danny@terweij.nl Tue May 7 19:18:06 2002 From: danny@terweij.nl (Danny Terweij) Date: Tue, 7 May 2002 20:18:06 +0200 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> Message-ID: <041901c1f5f3$88d987a0$1e00a8c0@poema.yi.org> From: "Ron Jarrell" > >And also you see here the vcard problem! > >Nice this list is upgraded to the mm2.1 beta :-) > >I want get rid of these
lines when send an vcard as attachment in an HTML mail. > I think that's your client doing that... I'm not seeing the HR lines in my copy of your email, but did see them in the copy you forwarded back to the list! If it is the mail client then Microsoft did make a wrong version of all outlook express versions. When i send a peronal mail to a person then no HR lines are added. When i send to another mailing list on Yahoo, groupcare and coollist then no HR lines are added. When i send to a mailman list even here, there are added 2 HR lines.. so mailman is adding this lines, and has nothing to do with the mail client. See a screen shot here : http://poema.no-ip.com/vcard.jpg (435kb) I hope i did now clear enough to prove it is a mailman bug/problem. So i hope it is in the next version solved (b2+ ?) Danny Terweij. From barry@zope.com Tue May 7 19:39:07 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 14:39:07 -0400 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 References: <347.1020751932@kanga.nu> <20020507194418.A6536@launay.org> Message-ID: <15576.8011.395463.875212@anthem.wooz.org> >>>>> "AL" == Arnaud Launay writes: AL> Does the term 'history' means something to you ? AL> I'm beginning to be very tired to modify my filters with each AL> new release of mailman. And I used Sender because, for a long AL> time, it was the only reliable header. >>>>> "DG" == David Gibbs writes: DG> When you have to deal with many different types of email DG> clients, there is no *WRONG*WAY* to filter ... not every email DG> client has all the filtering capabilities one would like. DG> Outlook, Outlook express, Domino, among others, have rather DG> limited filtering capabilities. See? I told you, you can't win. :) -Barry From noreply@sourceforge.net Tue May 7 19:45:25 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 07 May 2002 11:45:25 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-553385 ] Translation strings Message-ID: Bugs item #553385, was opened at 2002-05-07 20:45 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553385&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Translation strings Initial Comment: #: Mailman/Gui/ContentFilter.py:38 Minor typo; the entry reads: "Policies concerning concerning the content [...]" #: Mailman/Commands/cmd_set.py:186 msgid " %(status)s (%(how)s on %(date)s)" I'm not sure I fully understand what this is. status = delivery status? (disabled/enabled?) how = how it was disabled? date = the date it happened? How is the date written here? In english? According to the user's language setting? According to the locale? I believe this information is needed for many languages, to be able to translate this entry in the correct way... #: Mailman/Commands/cmd_set.py None of the commands should be translated, right? Should the various "set options" be translated? (e.g. 'ack', 'delivery', 'digest', etc.) If yes, then the output of the "set help" command would give the users a translated explanation to english commands. When they do "set show", the various options will also be translated, but english commands must be sent to the -request address, right? It is also currently not possible to translate the 'digest' option (there is no catalog entry for it). And why does the 'delivery' option have its own entries, when all the others have entries like this: "ack %(onoff)s" ? If no, then several cmd_set.py entries could probably be removed from the catalog, or they must be left blank so they default to their english value. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553385&group_id=103 From dgibbs@mks.com Tue May 7 19:47:46 2002 From: dgibbs@mks.com (David Gibbs) Date: Tue, 7 May 2002 13:47:46 -0500 Subject: [Mailman-Developers] Re: Re: Upgrading from 2.0.10 to 2.1.b2 References: <347.1020751932@kanga.nu><20020507194418.A6536@launay.org> <15576.8011.395463.875212@anthem.wooz.org> Message-ID: "Barry A. Warsaw" wrote in message news:15576.8011.395463.875212@anthem.wooz.org... > DG> When you have to deal with many different types of email > DG> clients, there is no *WRONG*WAY* to filter ... not every email > DG> client has all the filtering capabilities one would like. > See? I told you, you can't win. Oh yes you can ... just declare all existing email clients obsolete, replace it with your own, and declare yourself the victor. Oh, wait, that's what Microsoft's done ... hmmm. Never mind. david From barry@zope.com Tue May 7 19:50:36 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 14:50:36 -0400 Subject: [Mailman-Developers] Upgrading from 2.0.10 to 2.1.b2 References: <15575.10552.622025.10298@anthem.wooz.org> <15575.13226.368935.689600@anthem.wooz.org> <20020507024042.GR27488@mrbill.net> <20020507030946.GZ29582@merlins.org> <20020507155342.GY27488@mrbill.net> Message-ID: <15576.8700.572518.64191@anthem.wooz.org> >>>>> "BB" == Bill Bradford writes: BB> So far, I've done this numerous times, and it *is* necessary, BB> and yes, I moved EVERYTHING (list, archives, aliases). Its BB> like MM doesent realize that the files are *there*, in BB> $prefix/lists/ >> You probably aren't running exim and forgot to move the alias >> entries. BB> Running Postfix, and yeah, I *did* move aliases.. You can do a very simple test. Move a list without running bin/newlist first. Then cd to $prefix and do: % PYTHONPATH=pythonlib:. python Python 2.2.1 (#1, Apr 22 2002, 17:14:12) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from Mailman import Utils >>> Utils.list_names() ['list1, 'list2'] >>> Utils.list_exists('list1') 1 >>> from Mailman.MailList import MailList >>> m = MailList('list1', lock=0) >>> m.host_name 'wooz.org' >>> m.advertised 0 Question to ask: 1) Does your list show up in Utils.list_names()? If so, Mailman can find your list. If not, run check_perms. Anything funky there? No? Next question... 2) Did list_exists() return 1? If so, it's something else, if not, then for some reason none of lists/list1/config.{pck,pck.last,db,db.last} passed the os.path.exists() test. That doesn't seem like a Mailman problem. 3) Does the list's host_name match the url you expect? Maybe you didn't run fix_url? 4) What does the script bin/list_lists return? 5) Is the list in question not advertised? Answer those and we can go from there. -Barry From chk@pobox.com Tue May 7 19:53:57 2002 From: chk@pobox.com (Harald Koch) Date: Tue, 07 May 2002 14:53:57 -0400 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: Your message of "Tue, 07 May 2002 20:18:06 +0200". <041901c1f5f3$88d987a0$1e00a8c0@poema.yi.org> References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> <041901c1f5f3$88d987a0$1e00a8c0@poema.yi.org> Message-ID: <2670.1020797637@elisabeth.cfrq.net> > When i send to a mailman list even here, there are added 2 HR lines.. so > mailman is adding this lines, and has nothing to do with the mail client. Mailman is adding an extra part to the end of the message (the message_footer), and outlook is displaying multi-part message with three separate parts (the message, the vcard, and the footer). It's the outlook display, not the message itself, that has the horizontal lines. I've looked at the raw MIME message; no
s there. -- Harald Koch From jarrell@vt.edu Tue May 7 19:55:01 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Tue, 07 May 2002 14:55:01 -0400 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: <041901c1f5f3$88d987a0$1e00a8c0@poema.yi.org> References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> Message-ID: <5.1.0.14.2.20020507144834.08bb3300@lennier.cc.vt.edu> At 08:18 PM 5/7/02 +0200, Danny Terweij wrote: >From: "Ron Jarrell" > >When i send a peronal mail to a person then no HR lines are added. When i >send to another mailing list on Yahoo, groupcare and coollist then no HR >lines are added. > >When i send to a mailman list even here, there are added 2 HR lines.. so >mailman is adding this lines, and has nothing to do with the mail client. > >See a screen shot here : http://poema.no-ip.com/vcard.jpg (435kb) > >I hope i did now clear enough to prove it is a mailman bug/problem. >So i hope it is in the next version solved (b2+ ?) Ok, mailman is obviously *NOT* adding HR lines to your email. I'm using Eudora, and in your initial email to the list, as others have pointed out, there were NO HR lines in *our* copies. When you forwarded YOUR copy to the list, there were HR lines. Now, I'm willing to believe that mailman's mime chroming is adding *something* that YOUR CLIENT decides to render as an HR line, but there were physically no HR tags in the original copies we say, just your reforwarding. *My* copy of your note just had normal text. *Your* copy when it reforwarded included the following html embedded in it: (Note the META tag for MSHTML; outlook is wrapping whatever you're getting and changing it's appearence.)

 

Hi,
 
When deleting a list with ./rmlist, all the held messages stored are not erased. (~mailman/data)
 
 Danny.
 

_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
; from barry@zope.com on Tue, May 07, 2002 at 02:39:07PM -0400 References: <347.1020751932@kanga.nu> <20020507194418.A6536@launay.org> <15576.8011.395463.875212@anthem.wooz.org> Message-ID: <20020507210120.B7455@launay.org> Le Tue, May 07, 2002 at 02:39:07PM -0400, Barry A. Warsaw a écrit: > DG> Outlook, Outlook express, Domino, among others, have rather > DG> limited filtering capabilities. > See? I told you, you can't win. > :) Oh well. Die. :) Arnaud -- who modified its filters to have a mailman-developers.*@ form. -- - Comme il devait être pris en charge au plus vite par un asile d'aliénés, il a été conduit à la gendarmerie. From pioppo@ferrara.linux.it Tue May 7 20:03:04 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Tue, 7 May 2002 21:03:04 +0200 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: <041901c1f5f3$88d987a0$1e00a8c0@poema.yi.org> References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> <041901c1f5f3$88d987a0$1e00a8c0@poema.yi.org> Message-ID: <20020507190304.GC1986@abulafia.casa> martedì, 07 maggio 2002 alle 20:18:06, Danny Terweij ha scritto: > If it is the mail client then Microsoft did make a wrong version of all > outlook express versions. welcome to reality :) -- Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From danny@poema.yi.org Tue May 7 19:50:49 2002 From: danny@poema.yi.org (Danny Terweij) Date: Tue, 7 May 2002 20:50:49 +0200 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> <5.1.0.14.2.20020507144834.08bb3300@lennier.cc.vt.edu> Message-ID: <048c01c1f5f8$1b346e40$1e00a8c0@poema.yi.org> From: "Ron Jarrell" > Now, I'm willing to believe that mailman's mime chroming is adding *something* that YOUR CLIENT decides to render as an HR line, but there were physically no HR tags in the original copies we say, just your reforwarding. Oke thanx, now we are somewhere :) So my last final question about the subject, can it be solved at the mailman sources by developers? Danny Terweij. From barry@zope.com Tue May 7 20:04:45 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 15:04:45 -0400 Subject: [Mailman-Developers] Re: Re: Upgrading from 2.0.10 to 2.1.b2 References: <347.1020751932@kanga.nu> <20020507194418.A6536@launay.org> <15576.8011.395463.875212@anthem.wooz.org> Message-ID: <15576.9549.742767.171087@anthem.wooz.org> >>>>> "DG" == David Gibbs writes: DG> Oh yes you can ... just declare all existing email clients DG> obsolete, replace it with your own, and declare yourself the DG> victor. DG> Oh, wait, that's what Microsoft's done ... hmmm. DG> Never mind. I'll go half way there. Anybody who doesn't use VM under XEmacs is [sic] obsolete. bill-gate's-only-problem-is-that-he-hasn't-given-the-Mailman-Foundation- its-fair-share-of-that-U$40B-in-cash-he's-got-sitting-in-his-basement- ly y'rs, -Barry From danny@terweij.nl Tue May 7 20:00:23 2002 From: danny@terweij.nl (Danny Terweij) Date: Tue, 7 May 2002 21:00:23 +0200 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu><041901c1f5f3$88d987a0$1e00a8c0@poema.yi.org> <20020507190304.GC1986@abulafia.casa> Message-ID: <04b501c1f5f9$715a7520$1e00a8c0@poema.yi.org> From: "Simone Piunno" To: Sent: Tuesday, May 07, 2002 9:03 PM Subject: Re: [Mailman-Developers] Vcard .. at least i sample on this list :-) > > If it is the mail client then Microsoft did make a wrong version of all > > outlook express versions. > welcome to reality :) Hmm maybe ik can boot later today to my SuSe.. lets see what all mail clients do there :-) but i am sure now i wont see any lines (i think). It's a irritating subject on the lists here.. many and many members are making wonderfull stationeries, with java script/vbscript and so on.. so i can see the point of the members on the lists, they are frustated that there are 2 HR lines disturbing the whole look of the stationery. I hope it is a open case and the developers are working on an solution. Danny. From jarrell@vt.edu Tue May 7 20:18:39 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Tue, 07 May 2002 15:18:39 -0400 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: <048c01c1f5f8$1b346e40$1e00a8c0@poema.yi.org> References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> <5.1.0.14.2.20020507144834.08bb3300@lennier.cc.vt.edu> Message-ID: <5.1.0.14.2.20020507151712.043eaec0@lennier.cc.vt.edu> At 08:50 PM 5/7/02 +0200, Danny Terweij wrote: >From: "Ron Jarrell" > >> Now, I'm willing to believe that mailman's mime chroming is adding >*something* that YOUR CLIENT decides to render as an HR line, but there were >physically no HR tags in the original copies we say, just your reforwarding. > >Oke thanx, now we are somewhere :) > >So my last final question about the subject, can it be solved at the mailman >sources by developers? No, because mailman is not doing anything wrong. It's doing a perfectly legitimate mime attachment, which your client is choosing to display in a way you don't like. If there's no setting in outlook you can change, you'd need to complain to microsoft (good luck), or change clients to one that works the way you want it to. From Dale@Newfield.org Tue May 7 20:25:00 2002 From: Dale@Newfield.org (Dale Newfield) Date: Tue, 7 May 2002 15:25:00 -0400 (EDT) Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: <04b501c1f5f9$715a7520$1e00a8c0@poema.yi.org> Message-ID: On Tue, 7 May 2002, Danny Terweij wrote: > It's a irritating subject on the lists here.. many and many members are > making wonderfull stationeries, with java script/vbscript and so on.. so > i can see the point of the members on the lists, they are frustated that > there are 2 HR lines disturbing the whole look of the stationery. It's clearly a result of how outlook displays attachments, the way it fakes the vcard and pretends there is no attachment, and the fact that the footer is now added as an attachment. If you want to sidestep outlook's stupidity, then set the footer on that list to be empty. -Dale From danny@terweij.nl Tue May 7 20:15:18 2002 From: danny@terweij.nl (Danny Terweij) Date: Tue, 7 May 2002 21:15:18 +0200 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> <5.1.0.14.2.20020507144834.08bb3300@lennier.cc.vt.edu> <5.1.0.14.2.20020507151712.043eaec0@lennier.cc.vt.edu> Message-ID: <04cf01c1f5fb$86db4d00$1e00a8c0@poema.yi.org> From: "Ron Jarrell" > >So my last final question about the subject, can it be solved at the mailman > >sources by developers? > No, because mailman is not doing anything wrong. It's doing a perfectly legitimate mime attachment, which your client is choosing to display in a way you don't like. If there's no setting in outlook you can change, you'd need to complain to microsoft (good luck), or change clients to one that works the way you want it to. Thats is not a good answer. Okay lets say it another way, can mailman just strip the whole VCARD and mime that belongs to the VCARD? Maybe a option for the list-owners/admins to set it on and off? I know that any of the developer can do this. I am very sure. I'll think that this new "option" is very pleased for microsoft users. Please? (not a personal please.. all my members, list owners/admins are in that word please..) Danny. From danny@terweij.nl Tue May 7 20:16:53 2002 From: danny@terweij.nl (Danny Terweij) Date: Tue, 7 May 2002 21:16:53 +0200 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) References: Message-ID: <04d701c1f5fb$bf85d4e0$1e00a8c0@poema.yi.org> From: "Dale Newfield" > It's clearly a result of how outlook displays attachments, the way it > fakes the vcard and pretends there is no attachment, and the fact that the > footer is now added as an attachment. If you want to sidestep outlook's > stupidity, then set the footer on that list to be empty. I set default no footers. Just a empry string. All my lists are not using header and footers. Danny. From pioppo@ferrara.linux.it Tue May 7 20:31:38 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Tue, 7 May 2002 21:31:38 +0200 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: <04b501c1f5f9$715a7520$1e00a8c0@poema.yi.org> References: <20020507190304.GC1986@abulafia.casa> <04b501c1f5f9$715a7520$1e00a8c0@poema.yi.org> Message-ID: <20020507193138.GE1986@abulafia.casa> martedì, 07 maggio 2002 alle 21:00:23, Danny Terweij ha scritto: > It's a irritating subject on the lists here.. many and many members are > making wonderfull stationeries, with java script/vbscript and so on.. so i > can see the point of the members on the lists, they are frustated that there > are 2 HR lines disturbing the whole look of the stationery. > > I hope it is a open case and the developers are working on an solution. Ok, have you tried setting a void text for msg_footer in the lists' nondigest options? I think an empty text shouldn't add a MIME part to the original email... -- Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From jarrell@vt.edu Tue May 7 20:42:29 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Tue, 07 May 2002 15:42:29 -0400 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: <04cf01c1f5fb$86db4d00$1e00a8c0@poema.yi.org> References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> <5.1.0.14.2.20020507144834.08bb3300@lennier.cc.vt.edu> <5.1.0.14.2.20020507151712.043eaec0@lennier.cc.vt.edu> Message-ID: <5.1.0.14.2.20020507153720.08bf0970@lennier.cc.vt.edu> At 09:15 PM 5/7/02 +0200, Danny Terweij wrote: >From: "Ron Jarrell" > >> >So my last final question about the subject, can it be solved at the >mailman >> >sources by developers? > >> No, because mailman is not doing anything wrong. It's doing a perfectly >legitimate mime attachment, which your client is choosing to display in a >way you don't like. If there's no setting in outlook you can change, you'd >need to complain to microsoft (good luck), or change clients to one that >works the way you want it to. > > > >Thats is not a good answer. >Okay lets say it another way, can mailman just strip the whole VCARD and >mime that belongs to the VCARD? Maybe a option for the list-owners/admins to >set it on and off? >I know that any of the developer can do this. I am very sure. >I'll think that this new "option" is very pleased for microsoft users. > >Please? >(not a personal please.. all my members, list owners/admins are in that word >please..) 2.1b2 has a demime-ing option. That might solve your issue. Again, this is *not* a bug in mailman. *ANYTHING* that sends you a similar valid multi-part mime message like that will trigger this in outlook. Note that this will also strip off all the stationary stuff that your users are using too. Again, mailman *is not broken*. It is operating in a completely standards compliant way. Your client is, however, treating this standards compliant email in a stupid manner. Essentially, what you're asking is, to please your users, for the mailman developers to *break* mailman for you. Someone else suggested removing the list footer on your list. That would mean mailman wouldn't have to attach it, and that might also solve the issue. Check the faqs for using a separate "demime" program in your aliases file. You might write a separate script that you use locally, either as a standalone in your aliases file, or as a pipeline module for mailman (if you know python), which hunts down and destroys vcards. (Which I'd personally like on all mailing lists. vcards annoy the crap out of me.) From pioppo@ferrara.linux.it Tue May 7 20:42:44 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Tue, 7 May 2002 21:42:44 +0200 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: <20020507193138.GE1986@abulafia.casa> References: <20020507190304.GC1986@abulafia.casa> <04b501c1f5f9$715a7520$1e00a8c0@poema.yi.org> <20020507193138.GE1986@abulafia.casa> Message-ID: <20020507194244.GF1986@abulafia.casa> martedì, 07 maggio 2002 alle 21:31:38, Simone Piunno ha scritto: > I think an empty text shouldn't add a MIME part to the original email... Do people think this would be fair? --- Mailman/Handlers/Decorate.py Thu Apr 11 06:18:51 2002 +++ Mailman/Handlers/Decorate.py.new Tue May 7 21:39:41 2002 @@ -84,8 +84,10 @@ payload = msg.get_payload() if not isinstance(payload, ListType): payload = [payload] - payload.append(mimeftr) - payload.insert(0, mimehdr) + if footer: + payload.append(mimeftr) + if header: + payload.insert(0, mimehdr) msg.set_payload(payload) elif msg.get_main_type() <> 'multipart': # Okay, we've got some 'image/*' or 'audio/*' -like type. For # now, we -- Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From danny@terweij.nl Tue May 7 20:28:31 2002 From: danny@terweij.nl (Danny Terweij) Date: Tue, 7 May 2002 21:28:31 +0200 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) References: <20020507190304.GC1986@abulafia.casa><04b501c1f5f9$715a7520$1e00a8c0@poema.yi.org> <20020507193138.GE1986@abulafia.casa> Message-ID: <04fe01c1f5fd$5f54ab80$1e00a8c0@poema.yi.org> From: "Simone Piunno" > > I hope it is a open case and the developers are working on an solution. > Ok, have you tried setting a void text for msg_footer in the lists' > nondigest options? I think an empty text shouldn't add a MIME part > to the original email... Defaults.py : # These format strings will be expanded w.r.t. the dictionary for the # mailing list instance. DEFAULT_SUBJECT_PREFIX = "[%(real_name)s] " DEFAULT_MSG_HEADER = "" DEFAULT_MSG_FOOTER = "" All lists do not having a footer or header filled at the administration link web interface. Danny. From jarrell@vt.edu Tue May 7 20:46:03 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Tue, 07 May 2002 15:46:03 -0400 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: <04d701c1f5fb$bf85d4e0$1e00a8c0@poema.yi.org> References: Message-ID: <5.1.0.14.2.20020507154521.06268150@lennier.cc.vt.edu> At 09:16 PM 5/7/02 +0200, Danny Terweij wrote: >From: "Dale Newfield" > >> It's clearly a result of how outlook displays attachments, the way it >> fakes the vcard and pretends there is no attachment, and the fact that the >> footer is now added as an attachment. If you want to sidestep outlook's >> stupidity, then set the footer on that list to be empty. > >I set default no footers. Just a empry string. >All my lists are not using header and footers. If it's really an null string, and not, say a " " or a nl, then *that* could be considered a bug. Attaching a footer when the footer is null is a pointless exercise. From jarrell@vt.edu Tue May 7 20:49:42 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Tue, 07 May 2002 15:49:42 -0400 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: <20020507194244.GF1986@abulafia.casa> References: <20020507193138.GE1986@abulafia.casa> <20020507190304.GC1986@abulafia.casa> <04b501c1f5f9$715a7520$1e00a8c0@poema.yi.org> <20020507193138.GE1986@abulafia.casa> Message-ID: <5.1.0.14.2.20020507154833.08bf2190@lennier.cc.vt.edu> At 09:42 PM 5/7/02 +0200, Simone Piunno wrote: >marted=EC, 07 maggio 2002 alle 21:31:38, Simone Piunno ha scritto: > >> I think an empty text shouldn't add a MIME part to the original email... > >Do people think this would be fair? > >--- Mailman/Handlers/Decorate.py Thu Apr 11 06:18:51 2002 >+++ Mailman/Handlers/Decorate.py.new Tue May 7 21:39:41 2002 >@@ -84,8 +84,10 @@ > payload =3D msg.get_payload() > if not isinstance(payload, ListType): > payload =3D [payload] >- payload.append(mimeftr) >- payload.insert(0, mimehdr) >+ if footer: >+ payload.append(mimeftr) >+ if header: >+ payload.insert(0, mimehdr) > msg.set_payload(payload) > elif msg.get_main_type() <> 'multipart': > # Okay, we've got some 'image/*' or 'audio/*' -like type. For > # now, we Yes, in fact *not* doing it that way is probably wrong. Unless append and= insert are smart enough to be noops if there isn't really a footer and= header, which is sounds like they aren't. From danny@terweij.nl Tue May 7 20:37:21 2002 From: danny@terweij.nl (Danny Terweij) Date: Tue, 7 May 2002 21:37:21 +0200 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> <5.1.0.14.2.20020507144834.08bb3300@lennier.cc.vt.edu> <5.1.0.14.2.20020507151712.043eaec0@lennier.cc.vt.edu> <5.1.0.14.2.20020507153720.08bf0970@lennier.cc.vt.edu> Message-ID: <051301c1f5fe$9b286a60$1e00a8c0@poema.yi.org> From: "Ron Jarrell" > Check the faqs for using a separate "demime" program in your aliases file. You might write a separate script that you use locally, either as a standalone in your aliases file, or as a pipeline module for mailman (if you know python), which hunts down and destroys vcards. (Which I'd personally like on all mailing lists. vcards annoy the crap out of me.) > Hmm i think this is a good point for the developers to think about. I am not a programmer, i just create very light scripts here written for bash.. doing some automatic stuff here. (backups, virus scanning and so on..) Python is like C or other language for me.. i do not understand it. The only thing i run an linux box next my main windows 2000 server is that linux sometimes is better on some utils dan microshit. maybe one time on a day i migrate the whole stuff to linux :-) But there is just more for linux than windows. I can not find a simular program like Mailman for win32. So lets someone here start programming a vcard killer :-) Danny. From chuqui@plaidworks.com Tue May 7 21:12:22 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Tue, 07 May 2002 13:12:22 -0700 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <20020507194418.A6536@launay.org> Message-ID: On 5/7/02 10:44 AM, "Arnaud Launay" wrote: > Le Tue, May 07, 2002 at 08:32:07AM -0700, Chuq Von Rospach a =E9crit: >> That's why List-ID was invented and why Mailman supports it. >=20 > Does the term 'history' means something to you ? It does, except when it gets in the way of making things better. > I'm beginning to be very tired to modify my filters with each new > release of mailman. And I used Sender because, for a long time, > it was the only reliable header. So use it until it breaks, and then fix it right. Don't tell us to never fi= x it because you don't want to do it right, you want to do it easy.... --=20 Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ Stress is when you wake up screaming and you realize you haven't fallen asleep yet. From barry@zope.com Tue May 7 21:16:42 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 16:16:42 -0400 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) References: <20020507190304.GC1986@abulafia.casa> <04b501c1f5f9$715a7520$1e00a8c0@poema.yi.org> <20020507193138.GE1986@abulafia.casa> <20020507194244.GF1986@abulafia.casa> Message-ID: <15576.13866.46681.710016@anthem.wooz.org> >>>>> "SP" == Simone Piunno writes: >> I think an empty text shouldn't add a MIME part to the original >> email... SP> Do people think this would be fair? Yes Simone, I think you've hit it on the head. It's a bug that it doesn't do this. -Barry From pioppo@ferrara.linux.it Tue May 7 21:28:24 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Tue, 7 May 2002 22:28:24 +0200 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: <051301c1f5fe$9b286a60$1e00a8c0@poema.yi.org> References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> <5.1.0.14.2.20020507144834.08bb3300@lennier.cc.vt.edu> <5.1.0.14.2.20020507151712.043eaec0@lennier.cc.vt.edu> <5.1.0.14.2.20020507153720.08bf0970@lennier.cc.vt.edu> <051301c1f5fe$9b286a60$1e00a8c0@poema.yi.org> Message-ID: <20020507202824.GI1986@abulafia.casa> have you noted the subject in this thread is changing on each reply? the word "list" for some reason is walking to the right... -- Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From dgc@uchicago.edu Tue May 7 21:39:38 2002 From: dgc@uchicago.edu (David Champion) Date: Tue, 7 May 2002 15:39:38 -0500 Subject: [Mailman-Developers] Re: Vcard .. at least i sample on this list :-) In-Reply-To: <20020507202824.GI1986@abulafia.casa> References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> <5.1.0.14.2.20020507144834.08bb3300@lennier.cc.vt.edu> <5.1.0.14.2.20020507151712.043eaec0@lennier.cc.vt.edu> <5.1.0.14.2.20020507153720.08bf0970@lennier.cc.vt.edu> <051301c1f5fe$9b286a60$1e00a8c0@poema.yi.org> <20020507202824.GI1986@abulafia.casa> Message-ID: <20020507203938.GT9707@dust.uchicago.edu> * On 2002.05.07, in <20020507202824.GI1986@abulafia.casa>, * "Simone Piunno" wrote: > > have you noted the subject in this thread is changing on each reply? > the word "list" for some reason is walking to the right... When Ron replies to Danny, his Eudora splits the subject into two lines. When Danny replies to Ron, his Outlook joins the subject into one line, adding a space where the join occurred. What was it he said? "Maybe Microsoft made a mistake in Outlook Express?" :) -- -D. dgc@uchicago.edu NSIT University of Chicago From webmaster@eclickz.net Tue May 7 22:29:11 2002 From: webmaster@eclickz.net (eClickz) Date: Tue, 7 May 2002 14:29:11 -0700 Subject: [Mailman-Developers] New search engine! eClickz.net Message-ID: <200205072129.g47LTBD07881@camp.321host-it.com> eClickz is a brand new pay-per-click (ppc) search engine where users can find relevant information on any topic conceivable. Features lightning fast search results and an affiliate program where webmasters can earn money by placing a search box on their website. Enjoy ! From pioppo@ferrara.linux.it Tue May 7 22:34:22 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Tue, 7 May 2002 23:34:22 +0200 Subject: [Mailman-Developers] New search engine! eClickz.net In-Reply-To: <200205072129.g47LTBD07881@camp.321host-it.com> References: <200205072129.g47LTBD07881@camp.321host-it.com> Message-ID: <20020507213422.GK1986@abulafia.casa> martedì, 07 maggio 2002 alle 14:29:11, eClickz ha scritto: > eClickz is a brand new pay-per-click (ppc) search engine where SpamAssassin has failed... X-Spam-Status: No, hits=1.7 required=5.0 tests=PLING,SUPERLONG_LINE version=2.11 BTW: is there some doc on how to integrate it in Mailman? -- Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From claw@kanga.nu Tue May 7 22:41:32 2002 From: claw@kanga.nu (J C Lawrence) Date: Tue, 07 May 2002 14:41:32 -0700 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: Message from "Danny Terweij" of "Tue, 07 May 2002 20:18:06 +0200." <041901c1f5f3$88d987a0$1e00a8c0@poema.yi.org> References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> <041901c1f5f3$88d987a0$1e00a8c0@poema.yi.org> Message-ID: <14229.1020807692@kanga.nu> On Tue, 7 May 2002 20:18:06 +0200 Danny Terweij wrote: > If it is the mail client then Microsoft did make a wrong version of > all outlook express versions. Given that Microsoft has yet to make a version of Outlook that complies with Internet standards, this would hardly be a surprise. > When i send a peronal mail to a person then no HR lines are > added. When i send to another mailing list on Yahoo, groupcare and > coollist then no HR lines are added. Unfortunately behavioural analysis doesn't tend to get very far when analysing MIME structure behaviour, mostly due to the variant implementations of MIME parsers (something which Microsoft does excruciatingly poorly at, despite being a trivial thing to do let alone do right). > When i send to a mailman list even here, there are added 2 HR > lines.. so mailman is adding this lines, and has nothing to do with > the mail client. Pull both versions of the message (the full thing with all RFC 2822 headers etc) into a text editor, and then deconstruct and compare the MIME structures. That will reveal both the difference and the cause of the difference. I'll lay a pretty safe bet as to where the problem is. > I hope i did now clear enough to prove it is a mailman bug/problem. > So i hope it is in the next version solved (b2+ ?) If you'd like assistance, please attach both messages as message/RFC822 types in a post to this list explaining the problem. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From claw@kanga.nu Tue May 7 22:41:35 2002 From: claw@kanga.nu (J C Lawrence) Date: Tue, 07 May 2002 14:41:35 -0700 Subject: [Mailman-Developers] Vcard .. at least i sample on this list :-) In-Reply-To: Message from "Danny Terweij" of "Tue, 07 May 2002 20:18:06 +0200." <041901c1f5f3$88d987a0$1e00a8c0@poema.yi.org> References: <5.1.0.14.2.20020507141012.0477de20@lennier.cc.vt.edu> <041901c1f5f3$88d987a0$1e00a8c0@poema.yi.org> Message-ID: <14236.1020807695@kanga.nu> From barry@zope.com Tue May 7 22:54:37 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 17:54:37 -0400 Subject: [Mailman-Developers] New search engine! eClickz.net References: <200205072129.g47LTBD07881@camp.321host-it.com> <20020507213422.GK1986@abulafia.casa> Message-ID: <15576.19741.81780.614807@anthem.wooz.org> >>>>> "SP" =3D=3D Simone Piunno writes: SP> marted=EC, 07 maggio 2002 alle 14:29:11, eClickz ha scritto: >> eClickz is a brand new pay-per-click (ppc) search engine where SP> SpamAssassin has failed... SP> X-Spam-Status: No, hits=3D1.7 required=3D5.0 SP> tests=3DPLING,SUPERLONG_LINE version=3D2.11 Yes, I've reported this to our resident assassin. ;) SP> BTW: is there some doc on how to integrate it in Mailman? There's a patch on SF, but I haven't had time to look at it yet. -Barry From danny@terweij.nl Tue May 7 23:38:17 2002 From: danny@terweij.nl (Danny Terweij) Date: Wed, 8 May 2002 00:38:17 +0200 Subject: [Mailman-Developers] /bin/list_admins error Message-ID: <00c501c1f617$e1ea6480$1e00a8c0@poema.yi.org> Traceback (most recent call last): File "/usr/local/mailman/bin/list_admins", line 96, in ? main() File "/usr/local/mailman/bin/list_admins", line 90, in main owners = COMMASPACE.join(mlist.owner) UnboundLocalError: local variable 'mlist' referenced before assignment Called from a shell script: /usr/local/mailman/bin/list_admins $i > $TMPOWN $i holds the listname. When just running from a terminal its going fine (./list_admins testlist) Danny Terweij From Dale@Newfield.org Wed May 8 00:00:00 2002 From: Dale@Newfield.org (Dale Newfield) Date: Tue, 7 May 2002 19:00:00 -0400 (EDT) Subject: [Mailman-Developers] /bin/list_admins error In-Reply-To: <00c501c1f617$e1ea6480$1e00a8c0@poema.yi.org> Message-ID: On Wed, 8 May 2002, Danny Terweij wrote: > UnboundLocalError: local variable 'mlist' referenced before assignment > > Called from a shell script: > /usr/local/mailman/bin/list_admins $i > $TMPOWN > $i holds the listname. > > When just running from a terminal its going fine (./list_admins testlist) Then maybe the error is in the script, not list_admins? Verify that $i is a list during that iteration, then show us that "list_admins specific_list_name" causes a problem, and we're starting down the debugging path. As it is we don't have enough info. -Dale From danny@poema.yi.org Wed May 8 00:46:11 2002 From: danny@poema.yi.org (Danny Terweij) Date: Wed, 8 May 2002 01:46:11 +0200 Subject: [Mailman-Developers] /bin/list_admins error References: Message-ID: <00db01c1f621$5e6f7140$1e00a8c0@poema.yi.org> From: "Dale Newfield" > > UnboundLocalError: local variable 'mlist' referenced before assignment > > When just running from a terminal its going fine (./list_admins testlist) Also tested more and from teminal window it worked fine. > Then maybe the error is in the script, not list_admins? Verify that $i is > a list during that iteration, then show us that "list_admins > specific_list_name" causes a problem, and we're starting down the > debugging path. As it is we don't have enough info. Okay, more info : As you see i want to stop grabbing the list-owner info from the config_list and instead of that i want use list_admins I did make a own stats generator. someone did post the original script at mailman-users list a while ago for 2.0.x users. Maybe.. i doing now realise.. de LIST= command not compatible with 2.1? I do not even understand whats awk... sed.. and so on is doing :-) It worked fine for mm2.0.x. #! /bin/bash TMPFILE=`mktemp /tmp/mm_list_members.XXXXXX` || exit 1 LIST="`/usr/local/mailman/bin/list_lists |awk '{print $1}' |sed -n '2,$p'`" echo " " > $TMPFILE echo " ***** mailinglists inormation *****" >> $TMPFILE for i in $LIST do echo " " >> $TMPFILE echo "===> Listname: $i" >> $TMPFILE # TMPLST="/prv/mailman/$i.txt" TMPOWN="/prv/mailman/$i.tmp" /usr/local/mailman/bin/list_admins $i > $TMPOWN LSTOWNERX= <$TMPOWN # /usr/local/mailman/bin/config_list -o $TMPLST $i # LSTOWNER=`grep -i "owner =" $TMPLST` # echo "===> List-$LSTOWNER" >> $TMPFILE echo "===> $LSTOWNERX" >> $TMPFILE [cutted some parts] echo "===> Subscribers:" >> $TMPFILE /usr/local/mailman/bin/list_members $i >> $TMPFILE echo " " >> $TMPFILE done # Mail it mail -s "Mailing lists" root <$TMPFILE # remove the temp file rm $TMPFILE ----------------------------------- What about this.. same kind of faillure? : [root@lnx bin]# ./config_list -o config.test testlist Traceback (most recent call last): File "./config_list", line 268, in ? main() File "./config_list", line 261, in main do_output(listname, outfile) File "./config_list", line 113, in do_output do_list_categories(mlist, k, None, outfp) File "./config_list", line 162, in do_list_categories lines = value.replace('\r', '').split('\n') AttributeError: replace [root@lnx bin]# Danny. From danny@terweij.nl Wed May 8 00:47:20 2002 From: danny@terweij.nl (Danny Terweij) Date: Wed, 8 May 2002 01:47:20 +0200 Subject: [Mailman-Developers] /bin/list_admins error Message-ID: <00e301c1f621$870fd540$1e00a8c0@poema.yi.org> From: "Dale Newfield" > > UnboundLocalError: local variable 'mlist' referenced before assignment > > When just running from a terminal its going fine (./list_admins testlist) Also tested more and from teminal window it worked fine. > Then maybe the error is in the script, not list_admins? Verify that $i is > a list during that iteration, then show us that "list_admins > specific_list_name" causes a problem, and we're starting down the > debugging path. As it is we don't have enough info. Okay, more info : As you see i want to stop grabbing the list-owner info from the config_list and instead of that i want use list_admins I did make a own stats generator. someone did post the original script at mailman-users list a while ago for 2.0.x users. Maybe.. i doing now realise.. de LIST= command not compatible with 2.1? I do not even understand whats awk... sed.. and so on is doing :-) It worked fine for mm2.0.x. #! /bin/bash TMPFILE=`mktemp /tmp/mm_list_members.XXXXXX` || exit 1 LIST="`/usr/local/mailman/bin/list_lists |awk '{print $1}' |sed -n '2,$p'`" echo " " > $TMPFILE echo " ***** mailinglists inormation *****" >> $TMPFILE for i in $LIST do echo " " >> $TMPFILE echo "===> Listname: $i" >> $TMPFILE # TMPLST="/prv/mailman/$i.txt" TMPOWN="/prv/mailman/$i.tmp" /usr/local/mailman/bin/list_admins $i > $TMPOWN LSTOWNERX= <$TMPOWN # /usr/local/mailman/bin/config_list -o $TMPLST $i # LSTOWNER=`grep -i "owner =" $TMPLST` # echo "===> List-$LSTOWNER" >> $TMPFILE echo "===> $LSTOWNERX" >> $TMPFILE [cutted some parts] echo "===> Subscribers:" >> $TMPFILE /usr/local/mailman/bin/list_members $i >> $TMPFILE echo " " >> $TMPFILE done # Mail it mail -s "Mailing lists" root <$TMPFILE # remove the temp file rm $TMPFILE ----------------------------------- What about this.. same kind of faillure? : [root@lnx bin]# ./config_list -o config.test testlist Traceback (most recent call last): File "./config_list", line 268, in ? main() File "./config_list", line 261, in main do_output(listname, outfile) File "./config_list", line 113, in do_output do_list_categories(mlist, k, None, outfp) File "./config_list", line 162, in do_list_categories lines = value.replace('\r', '').split('\n') AttributeError: replace [root@lnx bin]# Danny. From jwblist@olympus.net Wed May 8 00:58:27 2002 From: jwblist@olympus.net (John W Baxter) Date: Tue, 7 May 2002 16:58:27 -0700 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: References: Message-ID: At 23:06 -0700 5/6/2002, Chuq Von Rospach wrote: >On 5/6/02 6:48 PM, "Arnaud Launay" wrote: > > >> Sender: mailman-developers-bounces@python.org >> >> which means that everybody filtering on Sender will have to >> change their filters. > >The real answer, IMHO, is "why are you filtering on Sender, anyway? That's >what List-ID is for". My collection of Eudora filters for lists goes WAY back in time (to 1995 or so). So I have many different techniques. They are fairly modern in other ways...I'm mostly filtering on the IMAP server now. List-ID makes sense for me (and Eudora, unlike some desktop MUAs, is happy to filter on any header one cares to name), and I'm tending to use it when I have to repair a list filter. Provided it's there, of course. --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA From jwblist@olympus.net Wed May 8 01:14:57 2002 From: jwblist@olympus.net (John W Baxter) Date: Tue, 7 May 2002 17:14:57 -0700 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <15575.57088.331868.201259@anthem.wooz.org> References: <15575.10552.622025.10298@anthem.wooz.org> <20020507034856.A12008@launay.org> <15575.26047.681641.9884@anthem.wooz.org> <20020507114152.B2092@launay.org> <15575.57088.331868.201259@anthem.wooz.org> Message-ID: At 10:04 -0400 5/7/2002, Barry A. Warsaw wrote: >>>>>> "AL" == Arnaud Launay writes: > > AL> Question is, why did it change between 2.0.10 and 2.1.b2 :-) > >The -admin address is deprecated. We wanted to unify the the address >extension and the script that handles them because it makes life much >more easy for MTA integration based on regexps. And it was too hard >to keep track of whether -admin did bounce processing or not. > > AL> When other sites will upgrade, if they generate lots of > AL> traffic, it will be a pain to filter the posts by hand... > >Sigh, you can't win, can ya? >-Barry We're viewing Mailman 2.1 as a major change point...so we'll try to be gentle with the existing Mailman lists. Including not jumping in for existing lists until 2.1 final is clearly working here. Meanwhile, we have a handful (half a hand, actually) of Majordomo lists left...I'm waiting to retrain th list owners directly to Mailman 2.1, rather than retraining to 2.0 and retraining again. --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA From terri@zone12.com Wed May 8 02:00:04 2002 From: terri@zone12.com (Terri Oda) Date: Tue, 07 May 2002 21:00:04 -0400 Subject: [Mailman-Developers] Changing version numbers Message-ID: <5.1.0.14.0.20020507205453.030c43f0@pop.ncf.carleton.ca> Just noticed this upgrading an installation from 2.0.8 to 2.0.10... why doesn't Version.py get overwritten by the new installation? I'm guessing that it's just in case you've got some freaky version system of your own worked out, but it seems a little strange to look at a new installation and discover that the old version number is among the preserved settings. I just copied over the new file and compiled it. Was there something more elaborate I was supposed to do? And where was I told to do it? :) From barry@zope.com Wed May 8 02:19:34 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 21:19:34 -0400 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 References: Message-ID: <15576.32038.932645.135525@anthem.wooz.org> >>>>> "JWB" == John W Baxter writes: JWB> List-ID makes sense for me (and Eudora, unlike some desktop JWB> MUAs, is happy to filter on any header one cares to name), JWB> and I'm tending to use it when I have to repair a list JWB> filter. JWB> Provided it's there, of course. Wouldn't that be a fair turnabout? People complaining about the /lack/ of the List-* headers instead of their existance! -Barry From barry@zope.com Wed May 8 02:20:57 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 7 May 2002 21:20:57 -0400 Subject: [Mailman-Developers] Re: Upgrading from 2.0.10 to 2.1.b2 References: <15575.10552.622025.10298@anthem.wooz.org> <20020507034856.A12008@launay.org> <15575.26047.681641.9884@anthem.wooz.org> <20020507114152.B2092@launay.org> <15575.57088.331868.201259@anthem.wooz.org> Message-ID: <15576.32121.493595.611150@anthem.wooz.org> >>>>> "JWB" == John W Baxter writes: JWB> We're viewing Mailman 2.1 as a major change point... I agree, and except for some political considerations, I probably should have called what we have now Mailman 3.0. Oh well. -Barry From noreply@sourceforge.net Wed May 8 04:15:13 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 07 May 2002 20:15:13 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-553557 ] Message Size not enforced properly Message-ID: Bugs item #553557, was opened at 2002-05-07 23:15 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553557&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: rich cowan (leftlink) Assigned to: Nobody/Anonymous (nobody) Summary: Message Size not enforced properly Initial Comment: I sent an 26K message that also was sent out by my eudora in an HTML version to a list that is supposed to be capped at a 40K limit. The html made the message into a 112K message, and it apparently went out anyway. the msg is at: http://lists.democracygroups.org/pipermail/rwwatch/2002 q2.txt This message was sent as both plain and styled text from eudora. It seems to me that if someone makes the mistake of leaving styled text on then Mailman should catch that, i.e. the "message body" should be calculated as the number of KB of both the plain and html portions of a message. the whole idea of the message size limit is to enforce a restriction so that a moderator of the list can make the email list more friendly to modem users, and when you end up letting huge html mail through, it kind of defeats the purpose. -rich cowan "Nonprofit Open Source Initiative" ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553557&group_id=103 From claw@kanga.nu Wed May 8 06:32:54 2002 From: claw@kanga.nu (J C Lawrence) Date: Tue, 07 May 2002 22:32:54 -0700 Subject: [Mailman-Developers] Re: Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: Message from barry@zope.com (Barry A. Warsaw) of "Tue, 07 May 2002 15:04:45 EDT." <15576.9549.742767.171087@anthem.wooz.org> References: <347.1020751932@kanga.nu> <20020507194418.A6536@launay.org> <15576.8011.395463.875212@anthem.wooz.org> <15576.9549.742767.171087@anthem.wooz.org> Message-ID: <22942.1020835974@kanga.nu> On Tue, 7 May 2002 15:04:45 -0400 Barry A Warsaw wrote: > I'll go half way there. Anybody who doesn't use VM under XEmacs is > [sic] obsolete. Ahem. MH thankyouverymuch. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From noreply@sourceforge.net Wed May 8 14:27:21 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 08 May 2002 06:27:21 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-553717 ] mail command interface doesn't work Message-ID: Bugs item #553717, was opened at 2002-05-08 15:27 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553717&group_id=103 Category: None Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Simone Piunno (pioppo) Assigned to: Nobody/Anonymous (nobody) Summary: mail command interface doesn't work Initial Comment: sending a message to the -request address I can't execute any command and no error is reported. Try yourself writing to test21b2-request@ferrara.linux.it The version installed is a recent 2.1b2+ from CVS BTW: this bug-submitting page should have a "mail interface" category. Bye ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553717&group_id=103 From jarrell@vt.edu Wed May 8 14:52:41 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Wed, 08 May 2002 09:52:41 -0400 Subject: [Mailman-Developers] Changing version numbers In-Reply-To: <5.1.0.14.0.20020507205453.030c43f0@pop.ncf.carleton.ca> Message-ID: <5.1.0.14.2.20020508095004.043bd810@lennier.cc.vt.edu> At 09:00 PM 5/7/02 -0400, Terri Oda wrote: >Just noticed this upgrading an installation from 2.0.8 to 2.0.10... why doesn't Version.py get overwritten by the new installation? I'm guessing that it's just in case you've got some freaky version system of your own worked out, but it seems a little strange to look at a new installation and discover that the old version number is among the preserved settings. > >I just copied over the new file and compiled it. Was there something more elaborate I was supposed to do? And where was I told to do it? :) You weren't told to do it anywhere, because you shouldn't have had to do it... The make install should have dropping in a new copy of Version.py, and then the compile_dir would have generated a new Version.pyc. You should carefully review the make install output, make sure there wasn't an error buried in the noise, and double check the permissions on the files, run check_perms, etc. From rcb@ucp.uchicago.edu Wed May 8 19:19:13 2002 From: rcb@ucp.uchicago.edu (Roy Bixler) Date: Wed, 8 May 2002 13:19:13 -0500 Subject: [Mailman-Developers] patch for using Bouncers/Catchall.py with Python 2.2.1 Message-ID: <20020508181913.GA8544@ucp.uchicago.edu> ---------------------- multipart/mixed attachment I just upgraded from Mailman v. 1.1 to v. 2.0.10 combined with a Python upgrade from v. 1.5.2 to v. 2.2.1. Mostly things went OK but I hit a snag when I found that the Mailman/Bouncers/Catchall.py file refers to the old regex and regsub modules and my Python v. 2.2.1 build doesn't define those. So, just in case anyone is interested, my patch below converts Mailman/Bouncers/Catchall.py to use the re module in place of regex and regsub. The patch has been lightly tested and seems to work. Regards, Roy Bixler The University of Chicago Press rcb@ucp.uchicago.edu ---------------------- multipart/mixed attachment --- Catchall.py.org Tue Apr 17 23:41:47 2001 +++ Catchall.py Wed May 8 12:07:21 2002 @@ -23,16 +23,9 @@ # annoying so if we can import the warnings module, we turn off warnings about # the import of regsub. It's not worth changing the uses of regsub to use the # re module because Catchall.py is going away in Mailman 2.1. -try: - import warnings - warnings.filterwarnings('ignore', module='regsub') -except ImportError: - pass import re import string -import regsub -import regex from types import StringType from Mailman import mm_cfg @@ -67,11 +60,10 @@ mime_info = msg.getheader('content-type') boundry = None if mime_info: - mime_info_parts = regsub.splitx( - mime_info, '[Bb][Oo][Uu][Nn][Dd][Aa][Rr][Yy]="[^"]+"') + mime_info_parts = re.split( + '([Bb][Oo][Uu][Nn][Dd][Aa][Rr][Yy]="[^"]+")', mime_info) if len(mime_info_parts) > 1: - boundry = regsub.splitx(mime_info_parts[1], - '"[^"]+"')[1][1:-1] + boundry = re.split('("[^"]+")', mime_info_parts[1])[1][1:-1] # snag out the message body msg.rewindbody() @@ -85,14 +77,13 @@ relevant_text = relevant_text[0] else: # This looks strange, but at least 2 are going to be no-ops. - relevant_text = regsub.split(msgbody, - '^.*Message header follows.*$')[0] - relevant_text = regsub.split(relevant_text, - '^The text you sent follows:.*$')[0] - relevant_text = regsub.split( - relevant_text, '^Additional Message Information:.*$')[0] - relevant_text = regsub.split(relevant_text, - '^-+Your original message-+.*$')[0] + relevant_text = re.split('^.*Message header follows.*$', msgbody)[0] + relevant_text = re.split('^The text you sent follows:.*$', + relevant_text)[0] + relevant_text = re.split('^Additional Message Information:.*$', + relevant_text)[0] + relevant_text = re.split('^-+Your original message-+.*$', + relevant_text)[0] BOUNCE = 1 REMOVE = 2 @@ -100,30 +91,30 @@ # Bounce patterns where it's simple to figure out the email addr. email_regexp = ']+@[^ \t@<>]+\.[^ \t<>.]+\)>?' simple_bounce_pats = ( - (regex.compile('.*451 %s.*' % email_regexp), BOUNCE), - (regex.compile('.*554 %s.*' % email_regexp), BOUNCE), - (regex.compile('.*552 %s.*' % email_regexp), BOUNCE), - (regex.compile('.*501 %s.*' % email_regexp), BOUNCE), - (regex.compile('.*553 %s.*' % email_regexp), BOUNCE), - (regex.compile('.*550 %s.*' % email_regexp), BOUNCE), - (regex.compile('%s .bounced.*' % email_regexp), BOUNCE), - (regex.compile('.*%s\.\.\. Deferred.*' % email_regexp), BOUNCE), - (regex.compile('.*User %s not known.*' % email_regexp), REMOVE), - (regex.compile('.*%s: User unknown.*' % email_regexp), REMOVE), - (regex.compile('.*%s\.\.\. User unknown' % email_regexp), REMOVE)) + (re.compile('.*451 %s.*' % email_regexp), BOUNCE), + (re.compile('.*554 %s.*' % email_regexp), BOUNCE), + (re.compile('.*552 %s.*' % email_regexp), BOUNCE), + (re.compile('.*501 %s.*' % email_regexp), BOUNCE), + (re.compile('.*553 %s.*' % email_regexp), BOUNCE), + (re.compile('.*550 %s.*' % email_regexp), BOUNCE), + (re.compile('%s .bounced.*' % email_regexp), BOUNCE), + (re.compile('.*%s\.\.\. Deferred.*' % email_regexp), BOUNCE), + (re.compile('.*User %s not known.*' % email_regexp), REMOVE), + (re.compile('.*%s: User unknown.*' % email_regexp), REMOVE), + (re.compile('.*%s\.\.\. User unknown' % email_regexp), REMOVE)) # patterns we can't directly extract the email (special case these) - messy_pattern_1 = regex.compile('^Recipient .*$') - messy_pattern_2 = regex.compile('^Addressee: .*$') - messy_pattern_3 = regex.compile('^User .* not listed.*$') - messy_pattern_4 = regex.compile('^550 [^ ]+\.\.\. User unknown.*$') - messy_pattern_5 = regex.compile('^User [^ ]+ is not defined.*$') - messy_pattern_6 = regex.compile('^[ \t]*[^ ]+: User unknown.*$') - messy_pattern_7 = regex.compile('^[^ ]+ - User currently disabled.*$') + messy_pattern_1 = re.compile('^Recipient .*$') + messy_pattern_2 = re.compile('^Addressee: .*$') + messy_pattern_3 = re.compile('^User .* not listed.*$') + messy_pattern_4 = re.compile('^550 [^ ]+\.\.\. User unknown.*$') + messy_pattern_5 = re.compile('^User [^ ]+ is not defined.*$') + messy_pattern_6 = re.compile('^[ \t]*[^ ]+: User unknown.*$') + messy_pattern_7 = re.compile('^[^ ]+ - User currently disabled.*$') # Patterns for cases where email addr is separate from error cue. separate_cue_1 = re.compile( '^554 .+\.\.\. unknown mailer error.*$', re.I) - separate_addr_1 = regex.compile('expanded from: %s' % email_regexp) + separate_addr_1 = re.compile('expanded from: %s' % email_regexp) message_grokked = 0 use_prospects = 0 @@ -131,34 +122,34 @@ for line in string.split(relevant_text, '\n'): for pattern, action in simple_bounce_pats: - if pattern.match(line) <> -1: + if pattern.match(line) is not None: email = extract(line) candidates.append((string.split(email,',')[0], action)) message_grokked = 1 # Now for the special case messages that are harder to parse... - if (messy_pattern_1.match(line) <> -1 - or messy_pattern_2.match(line) <> -1): + if (messy_pattern_1.match(line) is not None + or messy_pattern_2.match(line) is not None): username = string.split(line)[1] candidates.append(('%s@%s' % (username, remote_host), BOUNCE)) message_grokked = 1 continue - if (messy_pattern_3.match(line) <> -1 - or messy_pattern_4.match(line) <> -1 - or messy_pattern_5.match(line) <> -1): + if (messy_pattern_3.match(line) is not None + or messy_pattern_4.match(line) is not None + or messy_pattern_5.match(line) is not None): username = string.split(line)[1] candidates.append(('%s@%s' % (username, remote_host), REMOVE)) message_grokked = 1 continue - if messy_pattern_6.match(line) <> -1: + if messy_pattern_6.match(line) is not None: username = string.split(string.strip(line))[0][:-1] candidates.append(('%s@%s' % (username, remote_host), REMOVE)) message_grokked = 1 continue - if messy_pattern_7.match(line) <> -1: + if messy_pattern_7.match(line) is not None: username = string.split(string.strip(line))[0] candidates.append(('%s@%s' % (username, remote_host), REMOVE)) @@ -169,11 +160,12 @@ # Here's an error message that doesn't contain the addr. # Set a flag to use prospects found on separate lines. use_prospects = 1 - if separate_addr_1.search(line) != -1: + separate_addr_1_match = separate_addr_1.search(line) + if separate_addr_1_match is not None: # Found an addr that *might* be part of an error message. # Register it on prospects, where it will only be used if a # separate check identifies this message as an error message. - prospects.append((separate_addr_1.group(1), BOUNCE)) + prospects.append((separate_addr_1_match.group(1), BOUNCE)) if use_prospects and prospects: candidates = candidates + prospects @@ -186,7 +178,7 @@ who = who[:el] if len(who) > 1 and who[0] == '<': # Use stuff after open angle and before (optional) close: - who = regsub.splitx(who[1:], ">")[0] + who = re.split("(>)", who[1:])[0] if who not in did: did.append(who) ## return message_grokked @@ -195,8 +187,8 @@ def extract(line): - email = regsub.splitx(line, '[^ \t@<>]+@[^ \t@<>]+\.[^ \t<>.]+')[1] + email = re.split('([^ \t@<>]+@[^ \t@<>]+\.[^ \t<>.]+)', line)[1] if email[0] == '<': - return regsub.splitx(email[1:], ">")[0] + return re.split("(>)", email[1:])[0] else: return email ---------------------- multipart/mixed attachment-- From rlw@rlw.best.vwh.net Wed May 8 20:51:27 2002 From: rlw@rlw.best.vwh.net (Bob Weissman) Date: Wed, 08 May 2002 12:51:27 -0700 Subject: [Mailman-Developers] Putting teeth in VIRTUAL_HOST_OVERVIEW Message-ID: <5.1.0.14.0.20020508124221.030ca5e0@rlw.best.vwh.net> The VIRTUAL_HOST_OVERVIEW in Mailman 2.0.10 doesn't do what I want. I need to hide lists on a virtual host masquerading as a subdomain. That is, I don't want lists on internal.foo.org to be visible in the listinfo for foo.org. Currently, they are. May I propose a modification? Currently, VIRTUAL_HOST_OVERVIEW is either 0 or 1. I'd like to set it to 2 to indicate an exact virtual host name match must be performed, rather than a substring check. Something like the following. Thanks for your consideration, - Bob *** Defaults.py.orig Wed May 8 10:25:03 2002 --- Defaults.py Wed May 8 11:52:18 2002 *************** *** 230,235 **** --- 230,239 ---- # included within the URL by which the page is visited - only those "on the # virtual host". If unset, then all lists are included in the overview. The # admin page overview always includes all the lists. + # + # If set to 2, the match must be an exact virtual host match. That is, + # lists from private.foo.com will not be displayed on the overview + # for foo.com. (They will be displayed there if this is set to 1.) VIRTUAL_HOST_OVERVIEW = 1 DEFAULT_FILTER_PROG = '' # Currently not used! *************** *** Cgi/listinfo.py.orig Wed May 8 10:25:03 2002 --- Cgi/listinfo.py Wed May 8 11:52:18 2002 *************** *** 22,27 **** --- 22,28 ---- import os import cgi import string + from urlparse import urlparse from Mailman import mm_cfg from Mailman import Utils *************** *** 83,96 **** for n in names: mlist = MailList.MailList(n, lock=0) if mlist.advertised: ! if mm_cfg.VIRTUAL_HOST_OVERVIEW and \ ! http_host and \ string.find(http_host, mlist.web_page_url) == -1 and \ string.find(mlist.web_page_url, http_host) == -1: ! # List is for different identity of this host - skip it. ! continue ! else: ! advertised.append(mlist) if error: greeting = FontAttr(error, color="ff5060", size="+1") --- 84,105 ---- for n in names: mlist = MailList.MailList(n, lock=0) if mlist.advertised: ! if mm_cfg.VIRTUAL_HOST_OVERVIEW: ! if mm_cfg.VIRTUAL_HOST_OVERVIEW == 2: # Want an exact match ! # extract the host part of the url ! host_part = urlparse(mlist.web_page_url)[1] ! # remove the port, if any ! host_part = string.split(host_part, ":")[0] ! if http_host and host_part != http_host: ! # List is for different vhost - skip it. ! continue ! else: # Want a simple containment match ! if http_host and \ string.find(http_host, mlist.web_page_url) == -1 and \ string.find(mlist.web_page_url, http_host) == -1: ! # List is for different identity of this host - skip it. ! continue ! advertised.append(mlist) if error: greeting = FontAttr(error, color="ff5060", size="+1") From jwblist@olympus.net Wed May 8 21:31:21 2002 From: jwblist@olympus.net (John W Baxter) Date: Wed, 8 May 2002 13:31:21 -0700 Subject: [Mailman-Developers] patch for using Bouncers/Catchall.py with Python 2.2.1 In-Reply-To: <20020508181913.GA8544@ucp.uchicago.edu> References: <20020508181913.GA8544@ucp.uchicago.edu> Message-ID: At 13:19 -0500 5/8/2002, Roy Bixler wrote: >I just upgraded from Mailman v. 1.1 to v. 2.0.10 combined with a >Python upgrade from v. 1.5.2 to v. 2.2.1. Mostly things went OK but I >hit a snag when I found that the Mailman/Bouncers/Catchall.py file >refers to the old regex and regsub modules and my Python v. 2.2.1 >build doesn't define those. Interesting...my Python 2.2.1 on Mac OS X does include those modules (and issues a deprecation warning upon import at the interpreter command line). I didn't do anything special to include them. --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA From carson@taltos.org Wed May 8 21:50:10 2002 From: carson@taltos.org (Carson Gaspar) Date: Wed, 08 May 2002 16:50:10 -0400 Subject: [Mailman-Developers] Re: Re: Upgrading from 2.0.10 to 2.1.b2 In-Reply-To: <15576.9549.742767.171087@anthem.wooz.org> References: <15576.9549.742767.171087@anthem.wooz.org> Message-ID: <451674513.1020876609@[172.25.113.221]> --On Tuesday, May 07, 2002 3:04 PM -0400 "Barry A. Warsaw" wrote: > I'll go half way there. Anybody who doesn't use VM under XEmacs is [sic] > obsolete. Someday, if Kyle or I ever get around to adding real IMAP4 support to VM, I'll go back to it. Until then, I have to make due with mediocre mail clients that are useable with IMAP4 . And no, the VM IMAP as POP support that exists today is not adequate. *sigh* All I want for X-mas is a truckload of round-to-its. -- Carson From jarrell@vt.edu Thu May 9 18:38:42 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Thu, 09 May 2002 13:38:42 -0400 Subject: [Mailman-Developers] Another broken message Message-ID: <5.1.0.14.2.20020509133606.05e323d0@lennier.cc.vt.edu> Ok, I got another instance (that makes 5 I've seen now) of mailman sticking the headers into the body of the note.. There were extremely abbreviated headers, a blank line, a mangled header, and then the rest of the headers in the body of the note. The body starts: <20020509170855.SJAK2855.mtiwmhc25.worldnet.att.net@webmail.worldnet.att.net> for ; Thu, 9 May 2002 17:08:55 +0000 Received: from [12.91.124.228] by webmail.worldnet.att.net; Thu, 09 May 2002 17:08:55 +0000 Barry, having seen several examples now, it looks like something in the header code every so often dumps a null line into the output while building the message, thus causing the rest of the headers to look like they're in the body... From noreply@sourceforge.net Thu May 9 22:54:43 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 09 May 2002 14:54:43 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-554287 ] smart_address_match and .us Message-ID: Bugs item #554287, was opened at 2002-05-09 16:54 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554287&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Christopher Kolar (ckolar) Assigned to: Nobody/Anonymous (nobody) Summary: smart_address_match and .us Initial Comment: I know that it is noted in Defaults.py that the smart address needs to be fixed for international TLDs, but this is also broken for .us TLDs as well. I just wanted it to be in the bug log that this needs to be fixed for all of those people. Thanks, --ck ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554287&group_id=103 From noreply@sourceforge.net Thu May 9 22:59:31 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 09 May 2002 14:59:31 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-554290 ] request: invite text and message subject Message-ID: Bugs item #554290, was opened at 2002-05-09 16:59 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554290&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Christopher Kolar (ckolar) Assigned to: Nobody/Anonymous (nobody) Summary: request: invite text and message subject Initial Comment: Glad to see the invite functionality appearing in 2.1 I have two comments. 1. I would like to be able to invite people and include a custome text message (as on yahoogroups). That way I can invite them and remind them "I am inviting you to join this list because you gave me your email address at the conference and you said you might be interested." 2. The subject line of the invitation makes it look a lot like spam. I would make it something like: Subject: Invitation to join LISTNAME@HOSTNAME - confirm I have see this done where it is padded with spaces so that the ugly confirmation code will not appear in the window of most email readers, the invitee doesn't really need to sent it anyway. The link is awesome thought. Thanks for adding this. --chris ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554290&group_id=103 From jwblist@olympus.net Thu May 9 23:52:36 2002 From: jwblist@olympus.net (John W Baxter) Date: Thu, 9 May 2002 15:52:36 -0700 Subject: [Mailman-Developers] Another broken message In-Reply-To: <5.1.0.14.2.20020509133606.05e323d0@lennier.cc.vt.edu> References: <5.1.0.14.2.20020509133606.05e323d0@lennier.cc.vt.edu> Message-ID: At 13:38 -0400 5/9/2002, Ron Jarrell wrote: >Ok, I got another instance (that makes 5 I've seen now) of mailman >sticking the headers into the body of the note.. > >There were extremely abbreviated headers, a blank line, a mangled header, >and then the rest of the headers in the body of the note. > >The body starts: > > > > ><20020509170855.SJAK2855.mtiwmhc25.worldnet.att.net@webmail.worldnet.att.net> > for ; Thu, 9 May 2002 17:08:55 +0000 >Received: from [12.91.124.228] by webmail.worldnet.att.net; > Thu, 09 May 2002 17:08:55 +0000 > > >Barry, having seen several examples now, it looks like something in the >header code every so often dumps a null line into the output while >building the message, thus causing the rest of the headers to look like >they're in the body... If I were writing such an error, I would probably do it first by having a problem with doing header continuations, if the end of what should be the last line of the continued header exactly fills the allotted space for a line. (Having fixed that, I might get the same result more creatively. ;-) In fact, in other contexts I have done that. Too often. --John (who hopes to learn to leave the errors out altogether sometime) -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA From bob@nleaudio.com Fri May 10 02:33:08 2002 From: bob@nleaudio.com (Bob Puff@NLE) Date: Thu, 09 May 2002 21:33:08 -0400 Subject: [Mailman-Developers] Another broken message References: <5.1.0.14.2.20020509133606.05e323d0@lennier.cc.vt.edu> Message-ID: <3CDB2354.5D2E7C@nleaudio.com> I've seen quite a few of these messages from yahoogroups lists. I figured it was my bad netzero mail servers. Can't say I've seen these on the mail servers I maintain. FWIW. Bob From noreply@sourceforge.net Fri May 10 03:12:52 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 09 May 2002 19:12:52 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-554345 ] New Feature: Support no web access Message-ID: Bugs item #554345, was opened at 2002-05-10 02:12 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554345&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Julian Orbach (julian_orbach) Assigned to: Nobody/Anonymous (nobody) Summary: New Feature: Support no web access Initial Comment: Our Mailman 2.0 server is behind a firewall. Some groups of users are entirely within the firewall, and they can use the web interface to unsubscribe, etc. Mailman can handle these lists fine. Other lists include some users inside the firewall, and some users outside the firewall. On these lists, I do not want the URL to the web interface to be published, as it will not be accessible for many users. I only want to publish instructions on how to edit options through the mail interface (or perhaps through another web interface in our DMZ which translates the requests to SMTP requests). However, the standard messages that get sent to subscribing users includes a reference to that URL. I would like to control this on a per list basis. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554345&group_id=103 From barry@zope.com Fri May 10 06:00:47 2002 From: barry@zope.com (Barry A. Warsaw) Date: Fri, 10 May 2002 01:00:47 -0400 Subject: [Mailman-Developers] patch for using Bouncers/Catchall.py with Python 2.2.1 References: <20020508181913.GA8544@ucp.uchicago.edu> Message-ID: <15579.21503.151805.696273@anthem.wooz.org> >>>>> "JWB" == John W Baxter writes: JWB> Interesting...my Python 2.2.1 on Mac OS X does include those JWB> modules (and issues a deprecation warning upon import at the JWB> interpreter command line). I didn't do anything special to JWB> include them. And that module specifically imports the warnings module to silence the deprecation warnings in Python 2.2.x. Did you generate this patch because you saw those messages, or things were broken for you? -Barry From jwblist@olympus.net Fri May 10 08:02:45 2002 From: jwblist@olympus.net (John W Baxter) Date: Fri, 10 May 2002 00:02:45 -0700 Subject: [Mailman-Developers] patch for using Bouncers/Catchall.py with Python 2.2.1 In-Reply-To: <15579.21503.151805.696273@anthem.wooz.org> References: <20020508181913.GA8544@ucp.uchicago.edu> <15579.21503.151805.696273@anthem.wooz.org> Message-ID: At 1:00 -0400 5/10/2002, Barry A. Warsaw wrote: >>>>>> "JWB" == John W Baxter writes: > > JWB> Interesting...my Python 2.2.1 on Mac OS X does include those > JWB> modules (and issues a deprecation warning upon import at the > JWB> interpreter command line). I didn't do anything special to > JWB> include them. > >And that module specifically imports the warnings module to silence >the deprecation warnings in Python 2.2.x. Did you generate this patch >because you saw those messages, or things were broken for you? Someone else stated that the old regular modules were missing on Mac OS X and generated the patch. For me they are present on Mac OS X. I don't know why they are present for me and not for the patch generator. --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA From noreply@sourceforge.net Fri May 10 11:27:53 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 10 May 2002 03:27:53 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-553717 ] mail command interface doesn't work Message-ID: Bugs item #553717, was opened at 2002-05-08 15:27 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553717&group_id=103 Category: None Group: 2.1 beta Status: Open >Resolution: Invalid Priority: 5 Submitted By: Simone Piunno (pioppo) >Assigned to: Simone Piunno (pioppo) Summary: mail command interface doesn't work Initial Comment: sending a message to the -request address I can't execute any command and no error is reported. Try yourself writing to test21b2-request@ferrara.linux.it The version installed is a recent 2.1b2+ from CVS BTW: this bug-submitting page should have a "mail interface" category. Bye ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553717&group_id=103 From noreply@sourceforge.net Fri May 10 11:29:52 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 10 May 2002 03:29:52 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-553717 ] mail command interface doesn't work Message-ID: Bugs item #553717, was opened at 2002-05-08 15:27 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553717&group_id=103 Category: None Group: 2.1 beta >Status: Closed Resolution: Invalid Priority: 5 Submitted By: Simone Piunno (pioppo) Assigned to: Simone Piunno (pioppo) Summary: mail command interface doesn't work Initial Comment: sending a message to the -request address I can't execute any command and no error is reported. Try yourself writing to test21b2-request@ferrara.linux.it The version installed is a recent 2.1b2+ from CVS BTW: this bug-submitting page should have a "mail interface" category. Bye ---------------------------------------------------------------------- >Comment By: Simone Piunno (pioppo) Date: 2002-05-10 12:29 Message: Logged In: YES user_id=227443 it was my fault... sorry. ./config.status from 2.1b1 hadn't created the Makefile in Mailman/Commands. Now, after a full ./configure it works. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553717&group_id=103 From rcb@ucp.uchicago.edu Fri May 10 17:30:24 2002 From: rcb@ucp.uchicago.edu (Roy Bixler) Date: Fri, 10 May 2002 11:30:24 -0500 Subject: [Mailman-Developers] patch for using Bouncers/Catchall.py on Python 2.2.1 In-Reply-To: References: Message-ID: <20020510163024.GA17312@ucp.uchicago.edu> On Fri, May 10, 2002 at 12:00:04PM -0400, barry@zope.com (Barry A. Warsaw) wrote: > >>>>> "JWB" == John W Baxter writes: > > JWB> Interesting...my Python 2.2.1 on Mac OS X does include those > JWB> modules (and issues a deprecation warning upon import at the > JWB> interpreter command line). I didn't do anything special to > JWB> include them. > > And that module specifically imports the warnings module to silence > the deprecation warnings in Python 2.2.x. Did you generate this patch > because you saw those messages, or things were broken for you? I generated the patch because of the following: Python 2.2.1 (#10, May 3 2002, 17:45:45) [GCC 3.0.3] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> import regex Traceback (most recent call last): File "", line 1, in ? ImportError: No module named regex >>> import re >>> Python was compiled from source on a Solaris 8 machine. Since re is more modern, I thought I would try to patch Mailman rather than try to figure out why regex wasn't included in the Python build. -- Roy Bixler The University of Chicago Press rcb@ucp.uchicago.edu From noreply@sourceforge.net Fri May 10 20:54:46 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 10 May 2002 12:54:46 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-553385 ] Translation strings Message-ID: Bugs item #553385, was opened at 2002-05-07 20:45 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553385&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Translation strings Initial Comment: #: Mailman/Gui/ContentFilter.py:38 Minor typo; the entry reads: "Policies concerning concerning the content [...]" #: Mailman/Commands/cmd_set.py:186 msgid " %(status)s (%(how)s on %(date)s)" I'm not sure I fully understand what this is. status = delivery status? (disabled/enabled?) how = how it was disabled? date = the date it happened? How is the date written here? In english? According to the user's language setting? According to the locale? I believe this information is needed for many languages, to be able to translate this entry in the correct way... #: Mailman/Commands/cmd_set.py None of the commands should be translated, right? Should the various "set options" be translated? (e.g. 'ack', 'delivery', 'digest', etc.) If yes, then the output of the "set help" command would give the users a translated explanation to english commands. When they do "set show", the various options will also be translated, but english commands must be sent to the -request address, right? It is also currently not possible to translate the 'digest' option (there is no catalog entry for it). And why does the 'delivery' option have its own entries, when all the others have entries like this: "ack %(onoff)s" ? If no, then several cmd_set.py entries could probably be removed from the catalog, or they must be left blank so they default to their english value. ---------------------------------------------------------------------- >Comment By: Simone Piunno (pioppo) Date: 2002-05-10 21:54 Message: Logged In: YES user_id=227443 ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553385&group_id=103 From wheakory@isu.edu Fri May 10 20:37:42 2002 From: wheakory@isu.edu (Kory Wheatley) Date: Fri, 10 May 2002 13:37:42 -0600 Subject: [Mailman-Developers] Approved header option Message-ID: <3CDC2186.381C1CE3@isu.edu> In mailman 2.1b.1 How do you use the Approved:password to send your message to a moderated list. I'm the owner and I have the Emergency Moderation turned on and I what to send my message through. I don't want to use the Pending Administrative requests web interface to do this. I know in majordomo you can do this by adding "Approved:password" to the email message and sending it back through. How is this done in Mailman. -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From totschnig.michael@uqam.ca Sat May 11 16:46:46 2002 From: totschnig.michael@uqam.ca (totschnig.michael@uqam.ca) Date: Sat, 11 May 2002 11:46:46 -0400 Subject: [Mailman-Developers] bogue on sender filters customization page Message-ID: Hello, when tracking down a problem with the French translation I think I found a problem in the original message string #: Mailman/Gui/Privacy.py:223 msgid "" "Text to include in any\n" " rejection notice to\n" " be sent to moderated members who post to this list." shouldn't the URL be ?VARHELP=privacy/sender/member_moderation_action ^^^ Regards, Michael From marc_news@vasoftware.com Sat May 11 22:48:36 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sat, 11 May 2002 14:48:36 -0700 Subject: [Mailman-Developers] how to mass-set user options? In-Reply-To: <20020304211619.GU15098@merlins.org> References: <20020304102508.GF9799@merlins.org> <20020304211619.GU15098@merlins.org> Message-ID: <20020511214836.GC1311@merlins.org> > > 2) The new "nodupes" setting is really something you probably want as a > > default on all lists. I also had lists were people wanted notmetoo as a > > default too. > > Ben's fix for that is to have a bitfield per list that you can set and > > that states which options newly added users get. > > Now comes the question: how do I retroactively reset user options for a > given list of users without clicking on a web form? > > The idea would be to enable nodupes for a batch of users, although I've also > had the need to set a batch of users to notmetoo So, was there a way to do that, or do I need to write a wrapper with withlist? Thanks, Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From barry@zope.com Sun May 12 04:04:56 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 11 May 2002 23:04:56 -0400 Subject: [Mailman-Developers] how to mass-set user options? References: <20020304102508.GF9799@merlins.org> <20020304211619.GU15098@merlins.org> <20020511214836.GC1311@merlins.org> Message-ID: <15581.56280.796995.999969@anthem.wooz.org> >>>>> "MM" == Marc MERLIN writes: MM> So, was there a way to do that, or do I need to write a MM> wrapper with withlist? I'm afraid at the moment you'll need to write a withlist script. -Barry From noreply@sourceforge.net Sun May 12 07:00:49 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 11 May 2002 23:00:49 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-554345 ] New Feature: Support no web access Message-ID: Bugs item #554345, was opened at 2002-05-09 22:12 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554345&group_id=103 Category: Web/CGI Group: None >Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: Julian Orbach (julian_orbach) Assigned to: Nobody/Anonymous (nobody) Summary: New Feature: Support no web access Initial Comment: Our Mailman 2.0 server is behind a firewall. Some groups of users are entirely within the firewall, and they can use the web interface to unsubscribe, etc. Mailman can handle these lists fine. Other lists include some users inside the firewall, and some users outside the firewall. On these lists, I do not want the URL to the web interface to be published, as it will not be accessible for many users. I only want to publish instructions on how to edit options through the mail interface (or perhaps through another web interface in our DMZ which translates the requests to SMTP requests). However, the standard messages that get sent to subscribing users includes a reference to that URL. I would like to control this on a per list basis. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-12 02:00 Message: Logged In: YES user_id=12800 You can in MM2.1, if you have shell access to the Mailman installation. Simply add $prefix/lists/mylist/subscribeack.txt with the text you'd prefer to have. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554345&group_id=103 From noreply@sourceforge.net Sun May 12 07:10:07 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 11 May 2002 23:10:07 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-554287 ] smart_address_match and .us Message-ID: Bugs item #554287, was opened at 2002-05-09 17:54 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554287&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Christopher Kolar (ckolar) Assigned to: Nobody/Anonymous (nobody) Summary: smart_address_match and .us Initial Comment: I know that it is noted in Defaults.py that the smart address needs to be fixed for international TLDs, but this is also broken for .us TLDs as well. I just wanted it to be in the bug log that this needs to be fixed for all of those people. Thanks, --ck ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-12 02:10 Message: Logged In: YES user_id=12800 Near as I can tell, SMART_ADDRESS_MATCH isn't really used any where, except in functions that are also not used any where. Am I missing something or can all this cruft be removed now? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554287&group_id=103 From danny@terweij.nl Sun May 12 10:58:03 2002 From: danny@terweij.nl (Danny Terweij) Date: Sun, 12 May 2002 11:58:03 +0200 Subject: [Mailman-Developers] Cleaning the archive by a list-owner Message-ID: <006a01c1f99b$8286bd40$1e00a8c0@poema.yi.org> Hi, How can a list-owner clean out the archive? Delete messages? When not, can the developers program it? It would be nice. Groetjes Danny Terweij =20 From noreply@sourceforge.net Sun May 12 11:17:16 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 12 May 2002 03:17:16 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-555065 ] missing space Message-ID: Bugs item #555065, was opened at 2002-05-12 12:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=555065&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 4 Submitted By: Simone Piunno (pioppo) Assigned to: Nobody/Anonymous (nobody) Summary: missing space Initial Comment: I've a list with subscribe_policy = 1 (confirmation requested) and private_roster = 1 (only for subscribed people) When browsing the listinfo page from the web, I can see the following text: You will be sent email requesting confirmation, to prevent others from gratuitously subscribing you.This is also sa private list, which means that the list of members is not available to non-members. Note the missing space after the middle period. Attached is a proposed one-liner patch. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=555065&group_id=103 From danny@terweij.nl Sun May 12 11:19:35 2002 From: danny@terweij.nl (Danny Terweij) Date: Sun, 12 May 2002 12:19:35 +0200 Subject: [Mailman-Developers] Approvals does not working Message-ID: <007801c1f99e$843b1ca0$1e00a8c0@poema.yi.org> Hi, I have now several weeks mailman 2.1b1/2 running. I did asked it before, so here the question again : None of the lists and list owners/moderators and even me as site owner can not approve the messages staying at the Pending moderator requests. When you doing a accept or anything else and then "Submit all changes" it is doing nothing with the moderated mesages. After pressed the button is is in previous state. It is going bigger and bigger and de list-owners are complaining. No error found at the logfiles. If you can not believe it? personal mail me then you get the moderator password of my test list and see it your self. Even on some lists, not all lists, the list-owner can not a member changing at the membership options. So a list-owner/moderator can not unsub/nomail/and other options to be set or unset. Also here.. when pressing the button "Submit all changes" nothing happens. No error at the logfiles. So i have a trick found for list-owners to set users on nomail. Open the browser to : http://domain.com/mailman/admin/testlist Log in with the list-owner password. Then change the URL to : http://domain.com/mailman/listinfo/testlist (Not opening a new browser window, just stay in the same (for the cookie)) Fill in the members email-adres you want to set on nomail at: *********** To unsubscribe from testlist, get a password reminder, or change your subscription options enter your subscription email address: [ a.member@domain.com ] {unsubscribe or edit options} *********** Now press the button and you see the options (ALL!) for the member. Set the delivery to Disabled and "submit changed data". And the member is set to nomail by the list-owner. Oh, and even all the other options can be set! Greetings, Danny Terweij From david@midrange.com Sun May 12 16:23:44 2002 From: david@midrange.com (David Gibbs) Date: Sun, 12 May 2002 10:23:44 -0500 Subject: [Mailman-Developers] A couple of bugs ... Message-ID: Folks: I finally figured out what was causing my database error, a patch I had applied modified the version field in the database and was causing Mailman to not perform the necessary updates to the files. After I got past that, I started playing around with it in earnest... and noticed something... I ran the config_list command on a newly created list and got the following error ... [root@linux z]# ../bin/config_list -o testlist.txt testlist Traceback (most recent call last): File "../bin/config_list", line 268, in ? main() File "../bin/config_list", line 261, in main do_output(listname, outfile) File "../bin/config_list", line 113, in do_output do_list_categories(mlist, k, None, outfp) File "../bin/config_list", line 162, in do_list_categories lines = value.replace('\r', '').split('\n') AttributeError: replace Suggstions? david From danny@terweij.nl Sun May 12 16:33:26 2002 From: danny@terweij.nl (Danny Terweij) Date: Sun, 12 May 2002 17:33:26 +0200 Subject: [Mailman-Developers] A couple of bugs ... References: Message-ID: <000801c1f9ca$5d313320$1e00a8c0@poema.yi.org> David Gibbs heeft geschreven: > Folks: > I ran the config_list command on a newly created list and got the > following error ... > [root@linux z]# ../bin/config_list -o testlist.txt testlist > Traceback (most recent call last): [cut] > AttributeError: replace Same here, and reported it a few days ago. No replies yet. Danny Terweij From ida_b_s@hotmail.com Mon May 13 13:56:44 2002 From: ida_b_s@hotmail.com (Ida Berg Slang) Date: Mon, 13 May 2002 14:56:44 +0200 Subject: [Mailman-Developers] (no subject) Message-ID: Hello. I have a problem, because I am receiving emails from people that I suppose is originally for your organisation. It is questions and problems, that are filling up my emailaccount. Can you please help me with this problem? Thank you, Ida Berg Slang Ida_b_s@hotmail.com _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com From noreply@sourceforge.net Mon May 13 16:53:26 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 13 May 2002 08:53:26 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-555502 ] config_list fails with AttributeError Message-ID: Bugs item #555502, was opened at 2002-05-13 10:53 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=555502&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: config_list fails with AttributeError Initial Comment: I ran the config_list command on a newly created list and got the following error ... [root@linux z]# ../bin/config_list -o testlist.txt testlist Traceback (most recent call last): File "../bin/config_list", line 268, in ? main() File "../bin/config_list", line 261, in main do_output(listname, outfile) File "../bin/config_list", line 113, in do_output do_list_categories(mlist, k, None, outfp) File "../bin/config_list", line 162, in do_list_categories lines = value.replace('\r', '').split('\n') AttributeError: replace ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=555502&group_id=103 From danny@terweij.nl Mon May 13 17:09:44 2002 From: danny@terweij.nl (Danny Terweij) Date: Mon, 13 May 2002 18:09:44 +0200 Subject: [Mailman-Developers] I found it why list-admins can not do things Message-ID: <006d01c1fa98$992e35c0$1e00a8c0@poema.yi.org> Hi, My situation: Main site : poema.yi.org Mailman site: lnx.poema.yi.org lnx.poema.yi.org can not be connected directly, so i did a redirect on = the poema.yi.org apache (Virtual Host) site to poema.yi.org:81. Port 81 = is defined on the main internet/router as a port forwarding. So lnx.poema.yi.org is redirected to poema.yi.org:81 wich is defined as = port forwarding to internal-ip-lnx-machine:80..=20 Got it? If i use the browser and go to lnx.poema.yi.org/mailman/... it is not = converted to poema.yi.org:81 because i am on the internal network. All = stuff is working. But when a web visitor uses lnx.poema.yi.org (poema.yi.org:81), it is = not working. Whats is not working? Approvals and Membership options. So, what can i do to accept it? I played with : DEFAULT_EMAIL_HOST =3D 'lnx.poema.yi.org' DEFAULT_URL_HOST =3D 'lnx.poema.yi.org' DEFAULT_URL_PATTERN =3D 'http://%s/mailman/' # For backwards compatibility. Note: DEFAULT_URL_PATTERN must end in a = slash! DEFAULT_HOST_NAME =3D DEFAULT_EMAIL_HOST DEFAULT_URL =3D DEFAULT_URL_PATTERN % DEFAULT_URL_HOST So what is the best setting here for me?=20 I tried some things but wont work. btw, i have VIRTUAL_HOST_OVERVIEW =3D 0 , because i have no virtial = hosts on this machine (lnx). Danny Terweij Mailman 2.1B2 =20 From noreply@sourceforge.net Mon May 13 18:06:14 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 13 May 2002 10:06:14 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-554287 ] smart_address_match and .us Message-ID: Bugs item #554287, was opened at 2002-05-09 16:54 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554287&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Christopher Kolar (ckolar) Assigned to: Nobody/Anonymous (nobody) Summary: smart_address_match and .us Initial Comment: I know that it is noted in Defaults.py that the smart address needs to be fixed for international TLDs, but this is also broken for .us TLDs as well. I just wanted it to be in the bug log that this needs to be fixed for all of those people. Thanks, --ck ---------------------------------------------------------------------- >Comment By: Christopher Kolar (ckolar) Date: 2002-05-13 12:06 Message: Logged In: YES user_id=40678 Regardless, it is still a problem that someone@cpc.cps.k12.il.us gets bounced when someone@cps.k12.il.us is on the subscriber list. --chris ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-12 01:10 Message: Logged In: YES user_id=12800 Near as I can tell, SMART_ADDRESS_MATCH isn't really used any where, except in functions that are also not used any where. Am I missing something or can all this cruft be removed now? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554287&group_id=103 From danny@terweij.nl Mon May 13 18:48:28 2002 From: danny@terweij.nl (Danny Terweij) Date: Mon, 13 May 2002 19:48:28 +0200 Subject: [Mailman-Developers] admindb.py question ( or a bug/faillure ?) Message-ID: <00bf01c1faa6$63db0de0$1e00a8c0@poema.yi.org> Hi, I changed Defaults.py : DEFAULT_EMAIL_HOST =3D 'lnx.poema.yi.org' DEFAULT_URL_HOST =3D 'poema.yi.org:81' DEFAULT_URL_PATTERN =3D 'http://%s:81/mailman/' DEFAULT_HOST_NAME =3D 'poema.yi.org' DEFAULT_URL =3D 'http://poema.yi.org:81/mailman/' Then mailmanctl restart Then i checked the site : http://poema.yi.org:81/mailman/admindb/poema-test Logged in and looked at the source code of the webpage :
Where does this lnx.poema.yi.org is comming from? I did looked at admindb.py : Line number 172 admindburl =3D mlist.GetScriptURL('admindb', absolute=3D1) Where is it getting the url from? Not from the default settings at = Defaults.py (see above). Can any one tell me what the admindburl is holding for variable? Can i change it to : admindburl =3D 'http://poema.yi.org:81/mailman/' ( depends what the = variable is..)=20 Danny Terweij. =20 Groetjes Danny Terweij =20 From danny@terweij.nl Mon May 13 20:05:36 2002 From: danny@terweij.nl (Danny Terweij) Date: Mon, 13 May 2002 21:05:36 +0200 Subject: [Mailman-Developers] admindb.py question ( or a bug/faillure ?) References: <5.1.0.14.0.20020513105513.00ac2590@rlw.best.vwh.net> Message-ID: <01a001c1fab1$2ae52420$1e00a8c0@poema.yi.org> Hi, Did copy the settings also to mm_cfg.py Did change the admin.py to normal state. And same results, nothing happens when the submit button is pressed when approval is set. I changed my admindburl back to my setting and now i can approve the messages. Next step : Change a variable in ???.py to accept the member options. It is now getting to work here .. almost complete. But i see still at the page sources in my browser a lot of lnx.poema.yi.org links.. Can not find it where it is getting it from. Danny. ----- Original Message ----- From: "Bob Weissman" To: "Danny Terweij" Sent: Monday, May 13, 2002 7:57 PM Subject: Re: [Mailman-Developers] admindb.py question ( or a bug/faillure ?) > You are not supposed to change Defaults.py. You are supposed to override Defaults.py in mm_cfg.py instead. Perhaps something in mm_cfg.py is overriding your change in Defaults.py. > > - Bob > > At 10:48 AM 5/13/02, you wrote: > >Hi, > > > >I changed Defaults.py : > > > >DEFAULT_EMAIL_HOST = 'lnx.poema.yi.org' > >DEFAULT_URL_HOST = 'poema.yi.org:81' > >DEFAULT_URL_PATTERN = 'http://%s:81/mailman/' > >DEFAULT_HOST_NAME = 'poema.yi.org' > >DEFAULT_URL = 'http://poema.yi.org:81/mailman/' > > > >Then mailmanctl restart > > > >Then i checked the site : > > > >http://poema.yi.org:81/mailman/admindb/poema-test > > > >Logged in and looked at the source code of the webpage : > > > >Where does this lnx.poema.yi.org is comming from? > > > >I did looked at admindb.py : > > > >Line number 172 > >admindburl = mlist.GetScriptURL('admindb', absolute=1) > > > >Where is it getting the url from? Not from the default settings at Defaults.py (see above). > > > >Can any one tell me what the admindburl is holding for variable? > >Can i change it to : > >admindburl = 'http://poema.yi.org:81/mailman/' ( depends what the variable is..) > > > >Danny Terweij. > > > > > > > > > > > > > > > > > >Groetjes Danny Terweij > > > > > >_______________________________________________ > >Mailman-Developers mailing list > >Mailman-Developers@python.org > >http://mail.python.org/mailman-21/listinfo/mailman-developers > From danny@terweij.nl Mon May 13 20:54:32 2002 From: danny@terweij.nl (Danny Terweij) Date: Mon, 13 May 2002 21:54:32 +0200 Subject: [Mailman-Developers] Moderators are not getting approvals mails. Message-ID: <024f01c1fab8$0096e4e0$1e00a8c0@poema.yi.org> Hi, When a message is arrived at a list, and it is set according some filters and options to hold it, the list-admin(s) are getting a message there is a mail held to be approved. But! there is no mail send to the moderators? The moderators should be got a mail that there is a held message and the url where to handle this. The link for moderators is http://domain.com/mailman/admindb/[list-name] And they must be log in with the password set at the password section for moderators. (Or is it a option somewhere i missed?) Danny Terweij From dmick@utopia.West.Sun.COM Mon May 13 22:31:09 2002 From: dmick@utopia.West.Sun.COM (Dan Mick) Date: Mon, 13 May 2002 14:31:09 -0700 (PDT) Subject: [Mailman-Developers] A couple of bugs ... Message-ID: <200205132131.g4DLVmbH004569@utopia.West.Sun.COM> Category "contentfilter", variable "filter_mime_types", for me, has a 'list' type (i.e. its value is '[]'), but its type is advertised as mm_cfg.Text (4), which causes that newline replacement algorithm to bite it. I'm not sure if the assignment of type mm_cfg.Text is wrong, or if config_list needs to handle arrays of Text more gracefully. Barry? > Folks: > > I finally figured out what was causing my database error, a patch I had > applied modified the version field in the database and was causing Mailman > to not perform the necessary updates to the files. > > After I got past that, I started playing around with it in earnest... and > noticed something... > > I ran the config_list command on a newly created list and got the following > error ... > [root@linux z]# ../bin/config_list -o testlist.txt testlist > Traceback (most recent call last): > File "../bin/config_list", line 268, in ? > main() > File "../bin/config_list", line 261, in main > do_output(listname, outfile) > File "../bin/config_list", line 113, in do_output > do_list_categories(mlist, k, None, outfp) > File "../bin/config_list", line 162, in do_list_categories > lines = value.replace('\r', '').split('\n') > AttributeError: replace > > Suggstions? > > david > > > > > > > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman-21/listinfo/mailman-developers From noreply@sourceforge.net Mon May 13 22:37:05 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 13 May 2002 14:37:05 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-555627 ] subject prefic encoding Message-ID: Bugs item #555627, was opened at 2002-05-13 21:37 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=555627&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Norbert Bollow (bollow) Assigned to: Nobody/Anonymous (nobody) Summary: subject prefic encoding Initial Comment: In Mailman 2.1b2 on Python 2.1.3 with a mailing list that has German as its default language, the subject prefix gets encoded unneccessarily, e.g. [MNO] becomes =?iso-8859-1?q?=5BMNO=5D_?= . ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=555627&group_id=103 From danny@terweij.nl Mon May 13 23:06:16 2002 From: danny@terweij.nl (Danny Terweij) Date: Tue, 14 May 2002 00:06:16 +0200 Subject: [Mailman-Developers] error from list_admins Message-ID: <038001c1faca$67c53600$1e00a8c0@poema.yi.org> Traceback (most recent call last): File "/usr/local/mailman/bin/list_admins", line 96, in ? main() File "/usr/local/mailman/bin/list_admins", line 90, in main owners = COMMASPACE.join(mlist.owner) UnboundLocalError: local variable 'mlist' referenced before assignment Just a note for the dev guy's Danny Terweij From danny@terweij.nl Tue May 14 02:01:59 2002 From: danny@terweij.nl (Danny Terweij) Date: Tue, 14 May 2002 03:01:59 +0200 Subject: [Mailman-Developers] admindb.py question ( or a bug/faillure ?) References: <5.1.0.14.0.20020513105513.00ac2590@rlw.best.vwh.net> <01a001c1fab1$2ae52420$1e00a8c0@poema.yi.org> Message-ID: <049601c1fae2$f6d6a6e0$1e00a8c0@poema.yi.org> Hi, I did change the following to satisfy my list-admins/moderators to changes the Pending approvals and membership options. I replaced (admindb.py) all the "admindburl = .... " lines to # admindburl = mm_cfg.DEFAULT_URL + 'admindb/' + mlist.real_name And, i replaced (admin.py) all the "adminurl = .... " lines to # adminurl = mm_cfg.DEFAULT_URL + 'admin/' + mlist.real_name It is not a standard way, but it works on my situation. Thanx for the support on this.(figured it on my own, and have no programming skills!.. hmm... i lie.. C64 basic :-) ) The next "project"... translate the whole site to Dutch. I have mailed the Dutch translator, but no answers. So i do it on my own way (also not standard :( ) I know, i am now stuck with this version ... , when i am going to upgrade to Mm3 ... i must set all the damn things again :-( But hey, it is a hobby :-) Maybe i program at my own the "Send also to the moderators the approval/held messages by mail for approving, instead of admins only...". Danny Terweij (very happy at the moment!). ----- Original Message ----- From: "Danny Terweij" To: "Bob Weissman" Cc: Sent: Monday, May 13, 2002 9:05 PM Subject: Re: [Mailman-Developers] admindb.py question ( or a bug/faillure ?) > Hi, > > Did copy the settings also to mm_cfg.py > Did change the admin.py to normal state. > > And same results, nothing happens when the submit button is pressed when > approval is set. > > I changed my admindburl back to my setting and now i can approve the > messages. > > Next step : > Change a variable in ???.py to accept the member options. > It is now getting to work here .. almost complete. > But i see still at the page sources in my browser a lot of lnx.poema.yi.org > links.. > Can not find it where it is getting it from. > > Danny. > > > > ----- Original Message ----- > From: "Bob Weissman" > To: "Danny Terweij" > Sent: Monday, May 13, 2002 7:57 PM > Subject: Re: [Mailman-Developers] admindb.py question ( or a bug/faillure ?) > > > > You are not supposed to change Defaults.py. You are supposed to override > Defaults.py in mm_cfg.py instead. Perhaps something in mm_cfg.py is > overriding your change in Defaults.py. > > > > - Bob > > > > At 10:48 AM 5/13/02, you wrote: > > >Hi, > > > > > >I changed Defaults.py : > > > > > >DEFAULT_EMAIL_HOST = 'lnx.poema.yi.org' > > >DEFAULT_URL_HOST = 'poema.yi.org:81' > > >DEFAULT_URL_PATTERN = 'http://%s:81/mailman/' > > >DEFAULT_HOST_NAME = 'poema.yi.org' > > >DEFAULT_URL = 'http://poema.yi.org:81/mailman/' > > > > > >Then mailmanctl restart > > > > > >Then i checked the site : > > > > > >http://poema.yi.org:81/mailman/admindb/poema-test > > > > > >Logged in and looked at the source code of the webpage : > > > method="POST" > > > >Where does this lnx.poema.yi.org is comming from? > > > > > >I did looked at admindb.py : > > > > > >Line number 172 > > >admindburl = mlist.GetScriptURL('admindb', absolute=1) > > > > > >Where is it getting the url from? Not from the default settings at > Defaults.py (see above). > > > > > >Can any one tell me what the admindburl is holding for variable? > > >Can i change it to : > > >admindburl = 'http://poema.yi.org:81/mailman/' ( depends what the > variable is..) > > > > > >Danny Terweij. > > > > > > > > > > > > > > > > > > > > > > > > > > >Groetjes Danny Terweij > > > > > > > > >_______________________________________________ > > >Mailman-Developers mailing list > > >Mailman-Developers@python.org > > >http://mail.python.org/mailman-21/listinfo/mailman-developers > > > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman-21/listinfo/mailman-developers > From claw@kanga.nu Tue May 14 03:25:42 2002 From: claw@kanga.nu (J C Lawrence) Date: Mon, 13 May 2002 19:25:42 -0700 Subject: [Mailman-Developers] admindb.py question ( or a bug/faillure ?) In-Reply-To: Message from "Danny Terweij" of "Mon, 13 May 2002 19:48:28 +0200." <00bf01c1faa6$63db0de0$1e00a8c0@poema.yi.org> References: <00bf01c1faa6$63db0de0$1e00a8c0@poema.yi.org> Message-ID: <5000.1021343142@kanga.nu> On Mon, 13 May 2002 19:48:28 +0200 Danny Terweij wrote: > Logged in and looked at the source code of the webpage : action="http://lnx.poema.yi.org/mailman/admindb/poema-test" > method="POST" > Where does this lnx.poema.yi.org is comming from? >From ~mailman/lists//config.db. The value in Defaults.py (which you should never edit, change mm_cfg.py as instructed), is only used in creating new lists, not extant lists. You'll need to use the web UI or withlist to edit. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From noreply@sourceforge.net Tue May 14 07:04:59 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 13 May 2002 23:04:59 -0700 Subject: [Mailman-Developers] [ mailman-Patches-534577 ] Add SpamAssassin filter to mail pipeline Message-ID: Patches item #534577, was opened at 2002-03-25 16:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: James Henstridge (jhenstridge) Assigned to: Nobody/Anonymous (nobody) Summary: Add SpamAssassin filter to mail pipeline Initial Comment: This filter adds support for discarding or holding spam sent to the mailing list. It contacts a spamd daemon (from SpamAssassin -- http://spamassassin.taint.org) to score the message. If the score is above a certain threshold (default 10), the message is discarded and an entry is written to the vette log. If the score is above another lower threshold (default 5), the message is held for moderation. The SpamAssassin.py file should be installed in Mailman/Handlers/. The LIST_PIPELINE variable in Mailman/Handlers/HandlerAPI.py should be modified to include a 'SpamAssassin' item (I put it just after the existing 'SpamDetect' item). To change the defaults, the following can be added to the mm_cfg.py file: SPAMASSASSIN_HOST = 'host:port' # how to contact SA SPAMASSASSIN_DISCARD_SCORE = 10 SPAMASSASSIN_HOLD_SCORE = 5 If you don't want to discard messages, then DISCARD_SCORE can be set to something very high (1000 should do it). It looks the MM2.1 filter APIs have changed a bit, so this filter will need some modifications to work with that version. When I get round to upgrading, I might look into updating it. ---------------------------------------------------------------------- >Comment By: James Henstridge (jhenstridge) Date: 2002-05-14 14:04 Message: Logged In: YES user_id=146903 This version is essentially the same as the previous version, but adds compatibility with python > 1.5.2, which doesn't like you passing two arguments to socket.connect(). ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-04-27 14:17 Message: Logged In: YES user_id=146903 Just attached my updated version of the patch. This version requires SpamAssassin 2.20 (for the extra commands that the spamd daemon understands). It now displays a list of which rules were triggered for held messages, and can give messages from list members a bonus (defaults to 2), so that they are less likely to get held as spam. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-03-26 09:21 Message: Logged In: YES user_id=146903 There is a fairly easy optimisation for this filter that I missed when writing it. It calls str() on the message object twice. It would be quicker to call str() on the message once. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 From wheakory@isu.edu Tue May 14 15:22:38 2002 From: wheakory@isu.edu (Kory Wheatley) Date: Tue, 14 May 2002 08:22:38 -0600 Subject: [Mailman-Developers] Approved header option Message-ID: <3CE11DAE.73C88E9F@isu.edu> In mailman 2.1b.1 How do you use the Approved:password to send your message to a moderated list. I'm the owner and I have the Emergency Moderation turned on and I what to send my message through. I don't want to use the Pending Administrative requests web interface to do this. I know in majordomo you can do this by adding "Approved:password" to the email message and sending it back through. How is this done in Mailman. -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From jarrell@vt.edu Tue May 14 20:15:20 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Tue, 14 May 2002 15:15:20 -0400 Subject: [Mailman-Developers] [ mailman-Patches-534577 ] Add SpamAssassin filter to mail pipeline In-Reply-To: Message-ID: <5.1.0.14.2.20020514151416.06095a30@lennier.cc.vt.edu> At 11:04 PM 5/13/02 -0700, noreply@sourceforge.net wrote: >Patches item #534577, was opened at 2002-03-25 16:17 >You can respond by visiting: >http://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 > >Category: list administration >Group: Mailman 2.0.x >Status: Open >Resolution: None >Priority: 5 >Submitted By: James Henstridge (jhenstridge) >Assigned to: Nobody/Anonymous (nobody) >Summary: Add SpamAssassin filter to mail pipeline You know, I really think this needs to be made 2.1 clean and put into the dist; either in contrib, or even ready to go by just throwing a switch... From noreply@sourceforge.net Wed May 15 09:35:03 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 15 May 2002 01:35:03 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-556250 ] Icons not copied properly on new install Message-ID: Bugs item #556250, was opened at 2002-05-15 10:35 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=556250&group_id=103 Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Dario Lopez-Kästen (dlkita) Assigned to: Nobody/Anonymous (nobody) Summary: Icons not copied properly on new install Initial Comment: Using 2.1b2 on a minimal Solaris 8 installation, the install script fails to properly copy the icons from the misc dir in the source to the icons dir in the mailman install location. This is reproduceable (I installed 4 times). Looking in the Makefile gave no clues, mostly due to ignorance of makeifiles on my part. Haven't seen this mentioned anywhere, so I am not sure if this is my particular setup or if it is a general problem. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=556250&group_id=103 From noreply@sourceforge.net Wed May 15 10:07:17 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 15 May 2002 02:07:17 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-556260 ] err in INSTALL for qrunner autostarting Message-ID: Bugs item #556260, was opened at 2002-05-15 11:07 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=556260&group_id=103 Category: documentation Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Dario Lopez-Kästen (dlkita) Assigned to: Nobody/Anonymous (nobody) Summary: err in INSTALL for qrunner autostarting Initial Comment: There is what seems to be an error in the INSTALL document, the section that starts on line 327, about starting mailman automatically on reboot: around line 348, the document states: "For Unixes that don't support chkconfig, simply copy misc/mailman as above, then set up the following symbolic links, again as root: % cp misc/mailman /etc/init.d % cd /etc/rc.d/rc0.d ..... " The following is in error: - there is no misc/ directory in the installa location - if there where, following the instructions would undo the copying of scripts/mailman to /etc/init.d - the wording is somewhat ambiguous and may lead to misunderstanding. I propose the following change to the documentation: "For Unixes that don't support chkconfig, simply copy scripts/mailman as above: % cp scripts/mailman /etc/init.d/mailman then set up the following symbolic links, again as root: % cd /etc/rc.d/rc0.d ..... " ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=556260&group_id=103 From jra@baylink.com Wed May 15 19:51:50 2002 From: jra@baylink.com (Jay R. Ashworth) Date: Wed, 15 May 2002 14:51:50 -0400 Subject: [Mailman-Developers] Passwords In-Reply-To: <5.1.0.14.2.20020514151416.06095a30@lennier.cc.vt.edu>; from Ron Jarrell on Tue, May 14, 2002 at 03:15:20PM -0400 References: <5.1.0.14.2.20020514151416.06095a30@lennier.cc.vt.edu> Message-ID: <20020515145150.18594@scfn.thpl.lib.fl.us> Ok, stupid question time again. What's the latest word on a direct "unsubscribe" link that does *not* require a password? Is that in 2.1? Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") From donal.hunt2@mail.dcu.ie Wed May 15 19:50:10 2002 From: donal.hunt2@mail.dcu.ie (Donal Hunt) Date: Wed, 15 May 2002 19:50:10 +0100 Subject: [Mailman-Developers] Message Pipeline Message-ID: <3CE2ADE2.436FFE76@mail.dcu.ie> Hey there... I'm doing some modifications to the Mailman pipeline at the moment - adding a module that I want that does some modifications to messages as they get processed. I'm pretty happy with my code so far but wanted to check do I return the modified message or just make the changes and return? eg at the end do: return msg Regards Donal DCU From donal.hunt2@mail.dcu.ie Wed May 15 21:52:04 2002 From: donal.hunt2@mail.dcu.ie (Donal Hunt) Date: Wed, 15 May 2002 21:52:04 +0100 Subject: [Mailman-Developers] Re: Message Pipeline References: <3CE2ADE2.436FFE76@mail.dcu.ie> Message-ID: <3CE2CA74.9DEF9BD3@mail.dcu.ie> Just to answer my own mail... Nope - you don't need to put a "return msg" at the end of the "process" method. Later Donal DCU Donal Hunt wrote: > > Hey there... > > I'm doing some modifications to the Mailman pipeline at the moment - > adding a module that I want that does some modifications to messages as > they get processed. > > I'm pretty happy with my code so far but wanted to check do I return the > modified message or just make the changes and return? eg at the end do: > > return msg > > Regards > > Donal > DCU From dmick@utopia.West.Sun.COM Thu May 16 05:15:36 2002 From: dmick@utopia.West.Sun.COM (Dan Mick) Date: Wed, 15 May 2002 21:15:36 -0700 (PDT) Subject: [Mailman-Developers] MimeDel.py: after filtering, munge text/plain's back together Message-ID: <200205160416.g4G4GHbH003979@utopia.West.Sun.COM> I've been playing with MimeDel (Content filtering), and have come to the conclusion that two things need to happen: 1) there needs to be a way to set "only allow text" or "only allow text/plain" without enumerating each type you *don't* want, and 2) at the end of filtering, there needs to be a check to see if all the remaining parts can profitably be recombined into one part, at least for text/plain. Here's a hack at doing #2 (so that, for instance, messages with HTML alternatives end up being one big text/plain message, even with headers and footers turned on). #1 takes a new attribute and some GUI stuff, so I'll try to sell that back to Barry directly. Note: this diff is hand-hacked (as I have my partial #1 solution in there too) so you may have to hand-apply this if you want to play with it. Comments welcome. Index: MimeDel.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Handlers/MimeDel.py,v retrieving revision 2.1 diff -u -r2.1 MimeDel.py --- MimeDel.py 18 Apr 2002 20:46:53 -0000 2.1 +++ MimeDel.py 16 May 2002 04:13:32 -0000 @@ -91,12 +92,16 @@ # Now perhaps convert all text/html to text/plain if mlist.convert_html_to_plaintext and mm_cfg.HTML_TO_PLAIN_TEXT_COMMAND: changedp += to_plaintext(msg) + # Now, scan through all parts, and if only text/plain left, fuse + # them all back together into one payload + collapse_textplain(msg) + if changedp: msg['X-Content-Filtered-By'] = 'Mailman/MimeDel %s' % VERSION @@ -138,6 +146,23 @@ newpayload.append(subpart) msg.set_payload(newpayload) +def collapse_textplain(msg): + if not msg.is_multipart(): + return + for subpart in msg.get_payload(): + if subpart.get_type() != 'text/plain': + return + # ok, all parts are text/plain; munge 'em together + newpayload = "" + for subpart in msg.get_payload(): + if len(newpayload): + newpayload += '\n' + newpayload += subpart.get_payload() + if newpayload[-1] != '\n': + newpayload += '\n' + msg.set_payload(newpayload) + msg.set_type("text/plain") From dmick@utopia.West.Sun.COM Thu May 16 05:27:57 2002 From: dmick@utopia.West.Sun.COM (Dan Mick) Date: Wed, 15 May 2002 21:27:57 -0700 (PDT) Subject: [Mailman-Developers] MimeDel.py: after filtering, munge text/plain's back together Message-ID: <200205160428.g4G4ScbH004284@utopia.West.Sun.COM> > 2) at the end of filtering, there needs to be a check to see if > all the remaining parts can profitably be recombined into > one part, at least for text/plain. a) obviously this is wrong for multiple real text attachments b) maybe a better answer is "don't add headers and footers until MimeDel runs (i.e. maybe MimeDel should come earlier in the pipeline) Hmm. From barry@zope.com Thu May 16 05:35:44 2002 From: barry@zope.com (Barry A. Warsaw) Date: Thu, 16 May 2002 00:35:44 -0400 Subject: [Mailman-Developers] MimeDel.py: after filtering, munge text/plain's back together References: <200205160416.g4G4GHbH003979@utopia.West.Sun.COM> Message-ID: <15587.14112.594284.731224@anthem.wooz.org> Thanks Dan. I've been totally stuffed with customer work so I've sadly been ignoring mm-dev traffic. Sorry folks. I do hope to do some catchup work this weekend. BTW, if anybody's in NYC this Saturday, let me know. My band's going to be at Acme in Manhattan for a one set hit-and-run and it'd be cool if you stopped by and said hi! Cheers, -Barry From jonc@nc.rr.com Sun May 12 19:05:21 2002 From: jonc@nc.rr.com (Jon Carnes) Date: Sun, 12 May 2002 14:05:21 -0400 Subject: [Mailman-Developers] HowTo: [Mailman-Users] Cleaning the archive by a list-owner In-Reply-To: <006a01c1f99b$8286bd40$1e00a8c0@poema.yi.org> References: <006a01c1f99b$8286bd40$1e00a8c0@poema.yi.org> Message-ID: <200205121801.OAA04685@salsa.haht.com> Straight Mailman (unmodified) won't let you do this. I have some simple scripts that are password protected that do it for my admins. They were a piece of cake to write. Your sysadmin would have to install them for you. For the sysadmin to modify the archives... - edit ~mailman/archives/private/.mbox/.mbox - delete/modify any emails you want (normally delete older mail) - delete the old archive html files... rm -rf ~mailman/archives/private//.* - recreate the archive html files... cd ~mailman bin/arch \ archives/private/.mbox/.mbox === The email for the list is stored in mbox format (straight text) in a file in the archive directory. You can easily edit this mailbox and then re-run the archives so that your changes are pushed out to the HTML area. If you want to find the top of an email based on date: F_DATE="12 May 2002" grep -n "^From: " | grep $F_DATE | top -1 This gives you first line of an email that came in on that date - and it prints out the line number in the file for that line... To print out a file starting at a given line and continueing on to the end: F_NAME="~mailman/archive/private/mylist.mbox/mylist.mbox START=4093 sed -n "$START, \$ p" $F_NAME > $F_NAME.bak === There are several ways to automate this, the easiest is via email, but html is not too much harder - especially if you are willing to allow simple CGI's. I leave this up to your imagination! Take care, Jon --- Original Message: Sunday 12 May 2002 05:58 am --- > Hi, > > How can a list-owner clean out the archive? Delete messages? > When not, can the developers program it? > It would be nice. > > > Groetjes Danny Terweij From shiva@sewingwitch.com Wed May 15 05:22:06 2002 From: shiva@sewingwitch.com (Kenneth Porter) Date: 14 May 2002 21:22:06 -0700 Subject: [Mailman-Developers] Plussed addresses Message-ID: <1021436526.20227.46.camel@obi-wan.kenlabs.com> I'd like to use a "plussed" address in mailing lists (eg. shiva+mailmain-developers@sewingwitch.com) and I'm wondering if anyone has proposed changing the mailman filtering to match a plussed member name with the unplussed equivalent? In other words, I'd like to subscribe to a list using the plussed address, but post with the unplussed address. This sorta fits under the List Membership items in the wishlist (http://www.gnu.org/software/mailman/todo.html). From pioppo@ferrara.linux.it Wed May 15 21:20:24 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Wed, 15 May 2002 22:20:24 +0200 Subject: [Mailman-Developers] a translation checker Message-ID: <20020515202024.GA3315@abulafia.casa> ---------------------- multipart/mixed attachment Hi everyone, I'm trying to write a translation checker, a script that walks all files of a given Mailman translation, searching for inconsistencies such as wrong variable references, missing tags and so on. I'm doing this because I'm lazy and periodically reviewing and validating a translation is a boring process :) In attach you can find an early prototype, feel free to mail me complaints, suggestions and requests. If you think it's worth, I could try to generalize and do better exception handling. At the moment I have 2 problems and I need your advice: 1. What is the best regexp to use instead of /%\(([^)]+)\)[0-9]*[sd]/ to search for any Python %(variable)s? 2. Do you know of any existing parser I can use to read mailman.po? Cheers, Simone -- Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo ---------------------- multipart/mixed attachment #!/usr/bin/python # # transcheck - (c) 2002 by Simone Piunno # # This program is free software; you can redistribute it and/or modify it # under the terms of the version 2.0 of the GNU General Public License as # published by the Free Software Foundation. # # This program is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY # or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License # for more details. # # You should have received a copy of the GNU General Public License along # with this program; if not, write to the Free Software Foundation, Inc., 59 # Temple Place - Suite 330, Boston, MA 02111-1307, USA. """ Check a given Mailman translation making sure that variables and tags referenced in translation are the same variables and tags in the original templates and catalog. Usage: cd $MAILMAN_DIR /some/where/transcheck Where is your country code (e.g. 'it' for Italy) """ import sys import re import os MMTag = re.compile("<(MM-[^>]+)>"); PythonTag = re.compile("%\(([^)]+)\)[0-9]*[sd]"); def check_file(fileIT, fileEN, html=0): """check a translated template against the original one search also tags if html is not zero""" dict = {} errs = [] it = open(fileIT) while 1: line = it.readline() if not line: break list = PythonTag.findall(line) if html: list = list + MMTag.findall(line) for key in list: if dict.has_key(key): dict[key] = dict[key] + 1 else: dict[key] = 1 it.close() en = open(fileEN) while 1: line = en.readline() if not line: break list = PythonTag.findall(line) if html: list = list + MMTag.findall(line) for key in list: if dict.has_key(key): dict[key] = dict[key] - 1 else: errs.append( "Tag \"%(tag)s\" was not found in %(file)s" % { 'tag' : key, 'file' : fileIT } ) en.close() for key in dict.keys(): if dict[key] < 0: errs.append( "There are more \"%(tag)s\" tags in %(en)s than in %(it)s" % { 'tag' : key, 'it' : fileIT, 'en' : fileEN } ) if dict[key] > 0: errs.append( "There are more \"%(tag)s\" tags in %(it)s than in %(en)s" % { 'tag' : key, 'it' : fileIT, 'en' : fileEN } ) return errs def check_po(file): status = "IDLE" f = open(file) while 1: line = f.readline() if not line: break # here I should parse the .po file f.close() try: lang = sys.argv[1] except: print "Usage: transcheck " sys.exit(1) isHtml = re.compile("\.html$"); isTxt = re.compile("\.txt$"); for file in os.listdir("templates/" + lang + "/"): fileEN = "templates/en/" + file fileIT = "templates/" + lang + "/" + file errlist = [] if isHtml.search(file): print "HTML checking " + fileIT + "... ", errlist = check_file(fileIT, fileEN, 1) else: if isTxt.search(file): print "TXT checking " + fileIT + "... ", errlist = check_file(fileIT, fileEN, 0) else: continue if errlist: print "FAILED" for err in errlist: print " - " + err else: print "OK" file = "messages/" + lang + "/LC_MESSAGES/mailman.po" print "PO checking " + file + "... ", errlist = check_po(file) if errlist: print "FAILED" for err in errlist: print " - " + err else: print "OK" ---------------------- multipart/mixed attachment-- From ntmatador@netscape.net Thu May 16 19:13:36 2002 From: ntmatador@netscape.net (ntmatador@netscape.net) Date: Thu, 16 May 2002 14:13:36 -0400 Subject: [Mailman-Developers] Customization of mailman HTML pages... Message-ID: <68252CB6.378EF768.0339E2EE@netscape.net> I just recently setup a mailman mailing list server (FreeBSD) for a college but I am interested in changing the way that the auto-generated HTML pages look, especially for the archives part. Does anyone have any idea how I can go about in doing this or if it is possible? If it is already customizable, what files do I need to edit to do this? Thank you for the help in advance... Eduardo __________________________________________________________________ Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/ From noreply@sourceforge.net Thu May 16 17:39:54 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 16 May 2002 09:39:54 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-224744 ] disable List-Post for broadcast list Message-ID: Feature Requests item #224744, was opened at 2000-12-06 10:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=224744&group_id=103 Category: configuring/installing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Don Porter (dgp) Assigned to: Nobody/Anonymous (nobody) Summary: disable List-Post for broadcast list Initial Comment: There are problems using Mailman for "broadcast lists" -- those lists where only a few people are authorized to post messages to the list. For those lists, it is desirable to remove all references to posting messages in the instructions seen by list subscribers. The general list information page can be rewritten to achieve this, but the welcome message also includes these instructions and cannot be customized. With more recent releases of Mailman, the problem is made worse with the addition of a List-Post: header, which indicates to subscribers that their posts are welcome. They are not. Mailman needs additional configurability to suppress these invitations to post to the list to better support broadcast lists. ---------------------------------------------------------------------- Comment By: Bob Weissman (bweissman) Date: 2002-05-16 09:39 Message: Logged In: YES user_id=546505 I have a working patch for this for Mailman 2.0.10. It adds a new attribute "add_extra_list_headers" to each mailing list, with default 1 (Yes). The toggle for this appears on the main admin page for each list. This controls 5 of the 6 List-* headers: Id, Help, Unsubscribe, Subscribe, and Post. It does not control List- Archive, on the assumption that is still useful for archived lists. I wrote it this way because I have lists which I do not want subscribers self-administering (they are sync-ed with a master membership database for my organization). It would be a simple matter to change this to add one parameter per header, but I didn't need that. Anybody want this? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-10-11 11:59 Message: Logged In: NO I fully agree with this, and have the same difficulties. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2001-03-02 16:13 Message: Logged In: YES user_id=34209 I think the addition of a 'read-only list' would be a good idea, myself. Moved to feature request. Patches welcome, of course (forgive me if there is already a patch for this, I'm trying to catch up ;) ---------------------------------------------------------------------- Comment By: Dustin Mitchell (djmitche) Date: 2001-02-01 11:52 Message: This is a much-needed feature for our installation as well. Perhaps the addition of a 'Read-Only List?' configuration option? I'm willing to draw up and submit a patch for this, but I'll wait until I hear desire from a developer before I do this. Dustin ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2000-12-07 08:53 Message: See also http://mail.python.org/pipermail/mailman-users/2000-September/006431.html ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=224744&group_id=103 From noreply@sourceforge.net Fri May 17 10:43:09 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 17 May 2002 02:43:09 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-557127 ] Foreign charset subjects in archive Message-ID: Feature Requests item #557127, was opened at 2002-05-17 13:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=557127&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Michael Bravo (mbravo) Assigned to: Nobody/Anonymous (nobody) Summary: Foreign charset subjects in archive Initial Comment: Encoded subjects in archive should be demangled for proper viewing. Example: # [Developers] =?koi8-r?B?5MXNz87T1NLBw8nPzs7ZxSDQzM/dwcTLyQ==?= John Doe It's completely unreadable in this way. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=557127&group_id=103 From noreply@sourceforge.net Fri May 17 11:03:52 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 17 May 2002 03:03:52 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-557131 ] newlist alias output error Message-ID: Bugs item #557131, was opened at 2002-05-17 10:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=557131&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Neil Darlow (ndarlow) Assigned to: Nobody/Anonymous (nobody) Summary: newlist alias output error Initial Comment: I had a problem with Mailman-2.0.10 not responding to confirmation e-mail submissions. I found that there was no newline between newlist's -request and -owner aliases output (they were concatenated). This led to anything sent to the -request alias being silently ignored. Separating the aliases restored correct operation of confirmation processing. Regards, Neil Darlow M.Sc. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=557131&group_id=103 From noreply@sourceforge.net Fri May 17 11:25:33 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 17 May 2002 03:25:33 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-557131 ] newlist alias output error Message-ID: Bugs item #557131, was opened at 2002-05-17 10:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=557131&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Neil Darlow (ndarlow) Assigned to: Nobody/Anonymous (nobody) Summary: newlist alias output error Initial Comment: I had a problem with Mailman-2.0.10 not responding to confirmation e-mail submissions. I found that there was no newline between newlist's -request and -owner aliases output (they were concatenated). This led to anything sent to the -request alias being silently ignored. Separating the aliases restored correct operation of confirmation processing. Regards, Neil Darlow M.Sc. ---------------------------------------------------------------------- >Comment By: Neil Darlow (ndarlow) Date: 2002-05-17 10:25 Message: Logged In: YES user_id=39443 On further investigation this doesn't appear to be caused by newlist but copy'n'paste of the aliases output. It appears that if the -request alias is exactly one screen width and copy'n'paste is performed on the aliases then aliases are concatenated. It's just something to watch out for. Regards, Neil Darlow M.Sc. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=557131&group_id=103 From donal.hunt2@mail.dcu.ie Fri May 17 17:56:40 2002 From: donal.hunt2@mail.dcu.ie (Donal Hunt) Date: Fri, 17 May 2002 17:56:40 +0100 Subject: [Mailman-Developers] GLOBAL_PIPELINE Message-ID: <3CE53648.FE5F09EC@mail.dcu.ie> Quick question... Looking at the end of the pipeline, the last three processes are 'AfterDelivery', 'Acknowledge', and 'ToOutgoing'. From reading the comments in the 'AfterDelivery' and 'Acknowledge' source files I would have thought they should come after 'ToOutgoing'. Am i missing something in my logic?? Also should there be a "," after the 'ToOutgoing' entry below?? (just noticed that now). On a related note - I'm using a modified version of Personalize.py but I'm not too sure about where in the pipeline I should add it. Suggestions? All it does it split up the delivery so each envelope contains an email for exactly one subscriber. Thanks in advance Donal DCU ----- GLOBAL_PIPELINE = [ # These are the modules that do tasks common to all delivery paths. 'SpamDetect', 'Approve', 'Replybot', 'Moderate', 'MimeDel', 'Hold', 'Emergency', 'Tagger', 'CalcRecips', 'AvoidDuplicates', 'Cleanse', 'CookHeaders', # And now we send the message to the digest mbox file, and to the arch and # news queues. Runners will provide further processing of the message, # specific to those delivery paths. 'ToDigest', 'ToArchive', 'ToUsenet', # Now we'll do a few extra things specific to the member delivery # (outgoing) path, finally leaving the message in the outgoing queue. 'AfterDelivery', 'Acknowledge', 'ToOutgoing', ] From donal.hunt2@mail.dcu.ie Fri May 17 20:34:13 2002 From: donal.hunt2@mail.dcu.ie (Donal Hunt) Date: Fri, 17 May 2002 20:34:13 +0100 Subject: [Mailman-Developers] Web Interface Message-ID: <3CE55B35.31458049@mail.dcu.ie> I'm messing about with adding extra tabs to the admin pages, but running into some trouble... I've created a file in the $prefix/Mailman/Gui/ directory - lets call it NewTab.py... I also added the class name (defined in NewTab.py) to mm_cfg.py (copying the default setting from Defaults.py). However I think i've missed a link somewhere when reading through the source as things aren't working as expected. Do I need to define anything else / create other files?? Thanks again Donal From donal.hunt2@mail.dcu.ie Fri May 17 21:35:28 2002 From: donal.hunt2@mail.dcu.ie (Donal Hunt) Date: Fri, 17 May 2002 21:35:28 +0100 Subject: [Mailman-Developers] Re: Web Interface References: <3CE55B35.31458049@mail.dcu.ie> Message-ID: <3CE56990.632C6429@mail.dcu.ie> Solved this one as well... I needed to add the line from NewTab import NewTab into $prefix/Mailman/Gui/__init__.py d'oh!!! Later D. Donal Hunt wrote: > > I'm messing about with adding extra tabs to the admin pages, but running > into some trouble... > > I've created a file in the $prefix/Mailman/Gui/ directory - lets call it > NewTab.py... I also added the class name (defined in NewTab.py) to > mm_cfg.py (copying the default setting from Defaults.py). > > However I think i've missed a link somewhere when reading through the > source as things aren't working as expected. Do I need to define > anything else / create other files?? > > Thanks again > > Donal From barry@zope.com Fri May 17 22:11:40 2002 From: barry@zope.com (Barry A. Warsaw) Date: Fri, 17 May 2002 17:11:40 -0400 Subject: [Mailman-Developers] GLOBAL_PIPELINE References: <3CE53648.FE5F09EC@mail.dcu.ie> Message-ID: <15589.29196.884737.565046@anthem.wooz.org> >>>>> "DH" == Donal Hunt writes: DH> Looking at the end of the pipeline, the last three processes DH> are 'AfterDelivery', 'Acknowledge', and 'ToOutgoing'. From DH> reading the comments in the 'AfterDelivery' and 'Acknowledge' DH> source files I would have thought they should come after DH> 'ToOutgoing'. Am i missing something in my logic?? You're probably correct. Technically, I think the To* modules should be the last things in GLOBAL_PIPELINE and the out qrunner's own internal pipeline should call AfterDelivery and Acknowledge. But in practice I doubt it matters. DH> Also should there be a "," after the 'ToOutgoing' entry DH> below?? (just noticed that now). It's optional! That's actually one of the cool things about Python; the trailing element in a list (or dict or tuple) can have a comma after it. Makes rearranging the list elements so much nicer for cut-n-paste. The one exception is for tuples with only one element: they /must/ have the trailing comma: tupleone = (1,) because (1) is syntactically ambiguous. DH> On a related note - I'm using a modified version of DH> Personalize.py but I'm not too sure about where in the DH> pipeline I should add it. Suggestions? All it does it split DH> up the delivery so each envelope contains an email for exactly DH> one subscriber. Are you looking at the current cvs? The Personalize.py module is gone now, SMTPDirect.py having subsumed all its functionality for performance reasons. -Barry From barry@zope.com Fri May 17 22:50:28 2002 From: barry@zope.com (Barry A. Warsaw) Date: Fri, 17 May 2002 17:50:28 -0400 Subject: [Mailman-Developers] Replybot change proposed Message-ID: <15589.31524.461549.684799@anthem.wooz.org> I propose that the Replybot not send responses to any message marked "Precedence: bulk" unless there is a corresponding "X-Ack: yes" header. I also propose that the -request robot discard all similarly formatted messages. I think this will drastically cut down on the number of bogus replybot storms, and vulnerability of robot addresses being subscribed. There's not much we can do about broken replybots, but we can at least guard against properly written ones. Does anybody have any objections? -Barry From chuqui@plaidworks.com Fri May 17 23:17:33 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Fri, 17 May 2002 15:17:33 -0700 Subject: [Mailman-Developers] Replybot change proposed In-Reply-To: <15589.31524.461549.684799@anthem.wooz.org> Message-ID: On 5/17/02 2:50 PM, "Barry A. Warsaw" wrote: > Does anybody have any objections? Go for it, d00d. Bots really should not respond to stuff not labelled first class, to protect themselves from all of the bots that do... -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ Stress is when you wake up screaming and you realize you haven't fallen asleep yet. From jarrell@vt.edu Fri May 17 23:31:36 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Fri, 17 May 2002 18:31:36 -0400 (EDT) Subject: [Mailman-Developers] Hmm... More on header mangling... Message-ID: <200205172231.g4HMVaW12750@babylon5.cc.vt.edu> In-ter-esting. Got a note that was sent to a yahoogroup, and to one of my mailman lists simultaneously. Mailman did the "mangle the header line prematurely ending the headers" trick to it. But for once I can see what the header looked like originally! In the yahoo group note it came out as: X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t( ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[#:{)FXyiAS7(8t( ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[ rcpt to: rcpt to: data X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#; 3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t( ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[From rontest-bounces@babylon5.cc.vt.edu Fri May 17 18:24:55 2002 Delivery-Date: Fri, 17 May 2002 18:24:55 -0400 Return-Path: rontest-bounces@babylon5.cc.vt.edu Received: from babylon5.cc.vt.edu (babylon5.cc.vt.edu [128.173.14.193]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g4HMOte384118 for ; Fri, 17 May 2002 18:24:55 -0400 (EDT) Received: from babylon5.cc.vt.edu (localhost [127.0.0.1]) by babylon5.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g4HMOt612075 for ; Fri, 17 May 2002 18:24:55 -0400 (EDT) Date: Fri, 17 May 2002 18:24:55 -0400 (EDT) From: rontest-bounces@babylon5.cc.vt.edu Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) by babylon5.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g4HMOr612070 for ; Fri, 17 May 2002 18:24:53 -0400 (EDT) Received: from dagger.cc.vt.edu (IDENT:mirapoint@dagger-lb.cc.vt.edu [10.1.1.11]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g4HMOqe383213; Fri, 17 May 2002 18:24:52 -0400 (EDT) Received: from babylon5.cc.vt.edu (babylon5.cc.vt.edu [128.173.14.193]) by dagger.cc.vt.edu (Mirapoint Messaging Server MOS 3.1.0.54-GA) with ESMTP id AKR05504; Fri, 17 May 2002 18:08:34 -0400 (EDT) Message-Id: <200205172208.AKR05504@dagger.cc.vt.edu> X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#; 3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t( ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[ List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Help: Sender: rontest-bounces@babylon5.cc.vt.edu Errors-To: rontest-bounces@babylon5.cc.vt.edu Test of header processing. _______________________________________________ rontest mailing list - rontest@babylon5.cc.vt.edu http://babylon5.cc.vt.edu/mailman/listinfo/rontest Note the break in the "X-Face" header... I'm off to the code.. Or, perhaps, noting just now that it's after six on a friday and I'm still in the office, perhaps I'm off to the code on Monday :-)... From barry@zope.com Fri May 17 23:02:30 2002 From: barry@zope.com (Barry A. Warsaw) Date: Fri, 17 May 2002 18:02:30 -0400 Subject: [Mailman-Developers] Re: [Mailman-Users] Approved header option References: <3CE11DAE.73C88E9F@isu.edu> Message-ID: <15589.32246.921963.605043@anthem.wooz.org> >>>>> "KW" == Kory Wheatley writes: KW> In mailman 2.1b.1 How do you use the Approved:password to send KW> your message to a moderated list. I'm the owner and I have the KW> Emergency Moderation turned on and I what to send my message KW> through. I don't want to use the Pending Administrative KW> requests web interface to do this. I know in majordomo you can KW> do this by adding "Approved:password" to the email message and KW> sending it back through. How is this done in Mailman. Same way! Did you try it? :) Note that Mailman accepts "Approved: password" or "Approve: password" because I can never remember what the defacto standard is. :) -Barry From marc_news@vasoftware.com Sat May 18 02:47:53 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Fri, 17 May 2002 18:47:53 -0700 Subject: [Mailman-Developers] Bug between mailman 2.0/2.1 and outlook reference field. Message-ID: <20020518014753.GJ10075@merlins.org> Ok, so the problem is that outlook generates reference headers like this: References: <004001c1fe06$3f5be350$a3c5e80c@MoeA> <011c01c1fe07$6d8edd30$647ba8c0@C1912731A> Note that there is no space between the first and second items. I haven't checked in the RFCs, but I'm fairly sure it's invalid. Unfortunately, mailman kind of chockes on it. It fails to parse it and throws some of the headers in the body ----- Forwarded message from test-owner@svlug.org ----- From: test-owner@somedomain.tld To: test-owner@somedomain.tld X-List-Administrivia: yes Subject: Test post from someuser@vasw.com requires approval X-Spam-Status: No, hits=1.5 required=7.0 tests=NO_REAL_NAME,FROM_AND_TO_SAME version=2.20 X-Spam-Level: * As list administrator, your authorization is requested for the following mailing list posting: List: Test@lists.somedomain.tld From: someuser@vasw.com Subject: (no subject) Reason: Message has implicit destination At your convenience, visit: http://lists.somedomain.tld/lists/admindb/test to approve or deny the request. From: someuser@vasw.com Bcc: >From someuser@sf.net Fri May 17 18:15:25 2002 Date: Fri, 17 May 2002 18:15:25 -0700 From: Marc MERLIN To: test@lists.somedomain.tld Subject: testing reference field References: <004001c1fe06$3f5be350$a3c5e80c@MoeA> <011c01c1fe07$6d8edd30$647ba8c0@C1912731A> test 2 ----- End forwarded message ----- The HTML approve window shows this: Message Headers: ---------------------------------------------------------------------------- Received: from nat-hdqt.vasoftware.com ([198.186.202.17] helo=magic.hdqt.vasoftware.com) by mail.svlug.org with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 178sss-000750-00 for ; Fri, 17 May 2002 18:19:46 -0700 Received: from localhost ([127.0.0.1]) by magic.hdqt.vasoftware.com with smtp (Exim 3.31-VA-mm2 #1 (Debian)) id 178sqy-00026C-00; Fri, 17 May 2002 18:17:54 -0700 Message-Id: From: merlin@vasw.com Bcc: Date: Fri, 17 May 2002 18:17:54 -0700 ---------------------------------------------------------------------------- Message Excerpt: ---------------------------------------------------------------------------- >From merlin@sf.net Fri May 17 18:15:25 2002 Date: Fri, 17 May 2002 18:15:25 -0700 From: Marc MERLIN To: test@lists.somedomain.tld Subject: testing reference field References: <004001c1fe06$3f5be350$a3c5e80c@MoeA> <011c01c1fe07$6d8edd30$647ba8c0@C1912731A> test 2 ---------------------------------------------------------------------------- -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From philb@philb.us Sat May 18 23:15:37 2002 From: philb@philb.us (Phil Barnett) Date: Sat, 18 May 2002 18:15:37 -0400 Subject: [Mailman-Developers] Replybot change proposed In-Reply-To: <15589.31524.461549.684799@anthem.wooz.org> References: <15589.31524.461549.684799@anthem.wooz.org> Message-ID: On Friday 17 May 2002 05:50 pm, you wrote: > I propose that the Replybot not send responses to any message marked > "Precedence: bulk" unless there is a corresponding "X-Ack: yes" > header. > > I also propose that the -request robot discard all similarly > formatted messages. > > I think this will drastically cut down on the number of bogus > replybot storms, and vulnerability of robot addresses being > subscribed. > > There's not much we can do about broken replybots, but we can at > least guard against properly written ones. > > Does anybody have any objections? Makes sense to me. From barry@zope.com Sat May 18 03:39:52 2002 From: barry@zope.com (Barry A. Warsaw) Date: Fri, 17 May 2002 22:39:52 -0400 Subject: [Mailman-Developers] Replybot change proposed References: <15589.31524.461549.684799@anthem.wooz.org> Message-ID: <15589.48888.47214.762556@anthem.wooz.org> >> I propose that the Replybot not send responses to any message >> marked "Precedence: bulk" unless there is a corresponding >> "X-Ack: yes" header. Thanks all, the code's checked in now. -Barry From barry@zope.com Sat May 18 03:50:11 2002 From: barry@zope.com (Barry A. Warsaw) Date: Fri, 17 May 2002 22:50:11 -0400 Subject: [Mailman-Developers] Hmm... More on header mangling... References: <200205172231.g4HMVaW12750@babylon5.cc.vt.edu> Message-ID: <15589.49507.42796.641846@anthem.wooz.org> >>>>> "RJ" == Ron Jarrell writes: RJ> Mailman did the "mangle the header line prematurely ending the RJ> headers" trick to it. But for once I can see what the header RJ> looked like originally! Confirmed (and sorry about that hold warning you probably got Ron ;). Now I just need to figure out why! -Barry From jarrell@vt.edu Sat May 18 06:29:11 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Sat, 18 May 2002 01:29:11 -0400 Subject: [Mailman-Developers] Hmm... More on header mangling... In-Reply-To: <15589.49507.42796.641846@anthem.wooz.org> References: <200205172231.g4HMVaW12750@babylon5.cc.vt.edu> Message-ID: <5.1.0.14.2.20020518012552.00a84180@lennier.cc.vt.edu> At 10:50 PM 5/17/02 -0400, Barry A. Warsaw wrote: > >>>>> "RJ" == Ron Jarrell writes: > > RJ> Mailman did the "mangle the header line prematurely ending the > RJ> headers" trick to it. But for once I can see what the header > RJ> looked like originally! > >Confirmed (and sorry about that hold warning you probably got Ron ;). Which had me confused as hell for about 30 seconds, trying to figure out how one of my tests ended up routed through wooz.org! :-) >Now I just need to figure out why! Note that my "three line header" idea got shot to hell when I chopped the third line of and it still acquired the extra new line. It's showing up that way in the pickle, so it's either email's parseheaders (I'm thinking there might be some subtle error with a "too long" line and how it's interacting with "NL.join") or with the pickling process. Since the extra nl is in the pickle, everyone downstream in the pipeline just inhereits the problem. (Why do I seem to always find the truly strange problems?) From chuqui@plaidworks.com Sat May 18 06:52:29 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Fri, 17 May 2002 22:52:29 -0700 Subject: [Mailman-Developers] Hmm... More on header mangling... In-Reply-To: <5.1.0.14.2.20020518012552.00a84180@lennier.cc.vt.edu> Message-ID: On 5/17/02 10:29 PM, "Ron Jarrell" wrote: > (Why do I seem to always find the truly strange problems?) Because anyone can find the easy ones? -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ IMHO: Jargon. Acronym for In My Humble Opinion. Used to flag as an opinion something that is clearly from context an opinion to everyone except the mentally dense. Opinions flagged by IMHO are actually rarely humble. IMHO. (source: third unabridged dictionary of chuqui-isms). From donal.hunt2@mail.dcu.ie Sat May 18 16:17:36 2002 From: donal.hunt2@mail.dcu.ie (Donal Hunt) Date: Sat, 18 May 2002 16:17:36 +0100 Subject: [Mailman-Developers] Auto response on -admin and -owner addresses [Mailman Message-ID: <3CE67090.3DA8E9EF@mail.dcu.ie> Hey there... This doesn't seem to be working at present on my box... I've set the relevant option in the lists web interface but when someone sends mail to -owner or -admin, the sender doesn't get an auto-response back... The list owner/admin gets the mail just fine though... I'm using a fairly recent of Mailman CVS and had a quick look through the check-ins/bug reports and didn't see anything relevant. If it's just me I'll upgrade to latest CVS and see if that fixes it. :-) Regards Donal From rodolfo@pilas.net Sat May 18 18:24:53 2002 From: rodolfo@pilas.net (Rodolfo Pilas) Date: 18 May 2002 14:24:53 -0300 Subject: [Mailman-Developers] gate_news Message-ID: <1021742714.967.6.camel@julieta> Please, help me. I need to know how to stop this message asap, because I am receiving many reports from my crontab. Thanks. -----Mensaje reenviado----- From: Rodolfo Pilas To: mailman-users@python.org Subject: [Mailman-Users] gate_news Date: 17 May 2002 21:22:30 -0300 Since some hours ago I have problems with gate_news script, see it: mailman@> /usr/bin/python -S /usr/lib/mailman/cron/gate_news Traceback (most recent call last): File "/usr/lib/mailman/cron/gate_news", line 249, in ? main() File "/usr/lib/mailman/cron/gate_news", line 230, in main process_lists(lock) File "/usr/lib/mailman/cron/gate_news", line 164, in process_lists mlist = MailList.MailList(listname, lock=0) File "/usr/lib/mailman/Mailman/MailList.py", line 98, in __init__ self.Load() File "/usr/lib/mailman/Mailman/MailList.py", line 504, in Load dict, e = self.__load(file) File "/usr/lib/mailman/Mailman/MailList.py", line 479, in __load dict = loadfunc(fp) cPickle.UnpicklingError: invalid load key, '<'. mailman@> I use mailman v. 2.1a3 You can also see: http://www.espaciolibre.net/cgi-bin/listinfo because the listinfo shows the same error. Can you help me? -- Rodolfo Pilas Quien los puso a estos tipos donde estan, rodolfo@pilas.net Quien los deja seguir en su lugar, http://rodolfo.pilas.net Quien los baja ahora de su altar, Yahoo ID: ysidorito Quien les paga para que hagan lo que haran http://xtralinux.org -=# Apocalipsis Now % Cuarteto de Nos #=- Public GnuPG key: http://www.keyserver.net 1024D/57153363 2001-06-02 key fingerprint = DAAE 3246 3F7D A420 B7A0 48A5 D120 C773 5715 3363 ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py -- Rodolfo Pilas Quien los puso a estos tipos donde estan, rodolfo@pilas.net Quien los deja seguir en su lugar, http://rodolfo.pilas.net Quien los baja ahora de su altar, Yahoo ID: ysidorito Quien les paga para que hagan lo que haran http://xtralinux.org -=# Apocalipsis Now % Cuarteto de Nos #=- Public GnuPG key: http://www.keyserver.net 1024D/57153363 2001-06-02 key fingerprint = DAAE 3246 3F7D A420 B7A0 48A5 D120 C773 5715 3363 From jwblist@olympus.net Sat May 18 20:47:36 2002 From: jwblist@olympus.net (John W Baxter) Date: Sat, 18 May 2002 12:47:36 -0700 Subject: [Mailman-Developers] Replybot change proposed In-Reply-To: References: <15589.31524.461549.684799@anthem.wooz.org> Message-ID: > >> I propose that the Replybot not send responses to any message marked >> "Precedence: bulk" unless there is a corresponding "X-Ack: yes" >> header. Should that be expanded by adding "Precedence: junk" ? --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA From rlw@rlw.best.vwh.net Sat May 18 21:01:46 2002 From: rlw@rlw.best.vwh.net (Bob Weissman) Date: Sat, 18 May 2002 13:01:46 -0700 Subject: [Mailman-Developers] Replybot change proposed In-Reply-To: References: <15589.31524.461549.684799@anthem.wooz.org> Message-ID: <5.1.0.14.0.20020518130108.02e9f9b0@rlw.best.vwh.net> At 12:47 PM 5/18/02, John W Baxter wrote: >>> I propose that the Replybot not send responses to any message marked >>> "Precedence: bulk" unless there is a corresponding "X-Ack: yes" >>> header. > >Should that be expanded by adding "Precedence: junk" ? And "Precedence: list"? From barry@zope.com Sun May 19 18:23:30 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sun, 19 May 2002 13:23:30 -0400 Subject: [Mailman-Developers] Replybot change proposed References: <15589.31524.461549.684799@anthem.wooz.org> <5.1.0.14.0.20020518130108.02e9f9b0@rlw.best.vwh.net> Message-ID: <15591.57234.821586.88763@anthem.wooz.org> >>>>> "BW" == Bob Weissman writes: BW> And "Precedence: list"? >>>>> "JWB" == John W Baxter writes: JWB> Should that be expanded by adding "Precedence: junk" ? Probably so. I wonder if /any/ value for Precedence: should prevent replybot from responding? -Barry From rlw@rlw.best.vwh.net Sun May 19 18:46:44 2002 From: rlw@rlw.best.vwh.net (Bob Weissman) Date: Sun, 19 May 2002 10:46:44 -0700 Subject: [Mailman-Developers] Replybot change proposed In-Reply-To: <15591.57234.821586.88763@anthem.wooz.org> References: <15589.31524.461549.684799@anthem.wooz.org> <5.1.0.14.0.20020518130108.02e9f9b0@rlw.best.vwh.net> Message-ID: <5.1.0.14.0.20020519104420.00a89020@rlw.best.vwh.net> At 10:23 AM 5/19/02, Barry A. Warsaw wrote: >>>>>> "BW" == Bob Weissman writes: > BW> And "Precedence: list"? >>>>>> "JWB" == John W Baxter writes: > JWB> Should that be expanded by adding "Precedence: junk" ? >Probably so. I wonder if /any/ value for Precedence: should prevent >replybot from responding? > >-Barry I don't think so. The values "first-class" and "special-delivery" probably deserve responses. Any numerical value greater than or equal to zero does, too. - Bob From barry@zope.com Sun May 19 18:52:05 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sun, 19 May 2002 13:52:05 -0400 Subject: [Mailman-Developers] Replybot change proposed References: <15589.31524.461549.684799@anthem.wooz.org> <5.1.0.14.0.20020518130108.02e9f9b0@rlw.best.vwh.net> <5.1.0.14.0.20020519104420.00a89020@rlw.best.vwh.net> Message-ID: <15591.58949.540504.710470@anthem.wooz.org> >>>>> "BW" == Bob Weissman writes: BW> I don't think so. The values "first-class" and BW> "special-delivery" probably deserve responses. Any numerical BW> value greater than or equal to zero does, too. Are there any rfcs or even defacto documents describing the semantics of Precedence? Best I could find was RFC 2076, which is less that confidence inspiring. ;) -Barry From chuqui@plaidworks.com Sun May 19 18:59:38 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Sun, 19 May 2002 10:59:38 -0700 Subject: [Mailman-Developers] Replybot change proposed In-Reply-To: <15591.57234.821586.88763@anthem.wooz.org> Message-ID: On 5/19/02 10:23 AM, "Barry A. Warsaw" wrote: > Probably so. I wonder if /any/ value for Precedence: should prevent > replybot from responding? There are precedence values for first class and urgent. I've actually seen them used. I'd be wary of assuming here, except where it's standard or fairly well-set that it's a bot or program of some sort. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ Someday, we'll look back on this, laugh nervously and change the subject. From chuqui@plaidworks.com Sun May 19 19:28:54 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Sun, 19 May 2002 11:28:54 -0700 Subject: [Mailman-Developers] Replybot change proposed In-Reply-To: <15591.58949.540504.710470@anthem.wooz.org> Message-ID: On 5/19/02 10:52 AM, "Barry A. Warsaw" wrote: > Are there any rfcs or even defacto documents describing the semantics > of Precedence? I believe 822/821 defines its existance, but not its content. The best defacto definitions for content come from the sendmail definitions, which everyone else more or less borrows. Here's the relevant piece from the sendmail operations manual: When the name is found in a "Precedence:" field, the message class is set to num. Higher numbers mean higher precedence. Numbers less than zero have the special property that if an error occurs during pro- cessing the body of the message will not be returned; this is expected to be used for "bulk" mail such as through mailing lists. The default precedence is zero. For example, our list of precedences is: Pfirst-class=0 Pspecial-delivery=100 Plist=-30 Pbulk=-60 Pjunk=-100 People writing mailing list exploders are encouraged to use "Precedence: list". Older versions of sendmail (which discarded all error returns for negative prece- dences) didn't recognize this name, giving it a default precedence of zero. This allows list main- tainers to see error returns on both old and new ver- sions of sendmail. Note their use of "our list of..." -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ Someday, we'll look back on this, laugh nervously and change the subject. From noreply@sourceforge.net Mon May 20 11:16:02 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 20 May 2002 03:16:02 -0700 Subject: [Mailman-Developers] [ mailman-Patches-558208 ] Unescaped HTML in subject lines Message-ID: Patches item #558208, was opened at 2002-05-20 10:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=558208&group_id=103 Category: Pipermail Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Tristan Roddis (tristan_roddis) Assigned to: Nobody/Anonymous (nobody) Summary: Unescaped HTML in subject lines Initial Comment: Currently (in 2.0.x and up to 2.1b2), then the archive index pages do not escape HTML in the subject lines of posts. This exposes the possibility of malicious or annoying list members being able to invoke cross site javascript on the index pages, or simply corrupt the archive display by adding HTML fragments (e.g. ' without a corresponding ') The fix is extremely simple, just edit the file /home/mailman/Mailman/Archiver/HyperArch.py so that the function write_index_entry() (which starts at or near line 882 in v2.06) so that its last line reads as follows: print index_entry_template % (urllib.quote (article.filename), html_quote (subject), article.sequence, author) [i.e. add the crucial html_quote() function around the subject] Hope that helps, -Tristan. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=558208&group_id=103 From noreply@sourceforge.net Mon May 20 14:26:01 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 20 May 2002 06:26:01 -0700 Subject: [Mailman-Developers] [ mailman-Patches-558208 ] Unescaped HTML in subject lines Message-ID: Patches item #558208, was opened at 2002-05-20 06:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=558208&group_id=103 Category: Pipermail Group: Mailman 2.0.x >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Tristan Roddis (tristan_roddis) Assigned to: Nobody/Anonymous (nobody) Summary: Unescaped HTML in subject lines Initial Comment: Currently (in 2.0.x and up to 2.1b2), then the archive index pages do not escape HTML in the subject lines of posts. This exposes the possibility of malicious or annoying list members being able to invoke cross site javascript on the index pages, or simply corrupt the archive display by adding HTML fragments (e.g. ' without a corresponding ') The fix is extremely simple, just edit the file /home/mailman/Mailman/Archiver/HyperArch.py so that the function write_index_entry() (which starts at or near line 882 in v2.06) so that its last line reads as follows: print index_entry_template % (urllib.quote (article.filename), html_quote (subject), article.sequence, author) [i.e. add the crucial html_quote() function around the subject] Hope that helps, -Tristan. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-20 09:26 Message: Logged In: YES user_id=12800 I believe this report is out of date. All known cross-site scripting attacks have been fixed as of MM2.0.10 and I don't believe MM2.1b2 is vulnerable. I double checked the code in each version and indeed both versions make sure to quote any html in subjects. Can you please double check the latest versions (2.0.10 and 2.1cvs). ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=558208&group_id=103 From noreply@sourceforge.net Mon May 20 14:47:23 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 20 May 2002 06:47:23 -0700 Subject: [Mailman-Developers] [ mailman-Patches-558208 ] Unescaped HTML in subject lines Message-ID: Patches item #558208, was opened at 2002-05-20 10:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=558208&group_id=103 Category: Pipermail Group: Mailman 2.0.x Status: Closed Resolution: Out of Date Priority: 5 Submitted By: Tristan Roddis (tristan_roddis) Assigned to: Nobody/Anonymous (nobody) Summary: Unescaped HTML in subject lines Initial Comment: Currently (in 2.0.x and up to 2.1b2), then the archive index pages do not escape HTML in the subject lines of posts. This exposes the possibility of malicious or annoying list members being able to invoke cross site javascript on the index pages, or simply corrupt the archive display by adding HTML fragments (e.g. ' without a corresponding ') The fix is extremely simple, just edit the file /home/mailman/Mailman/Archiver/HyperArch.py so that the function write_index_entry() (which starts at or near line 882 in v2.06) so that its last line reads as follows: print index_entry_template % (urllib.quote (article.filename), html_quote (subject), article.sequence, author) [i.e. add the crucial html_quote() function around the subject] Hope that helps, -Tristan. ---------------------------------------------------------------------- >Comment By: Tristan Roddis (tristan_roddis) Date: 2002-05-20 13:47 Message: Logged In: YES user_id=549463 I've just had a look, and the offending line is still there in the file HyperArch.py for both versions (line number 882 in 2.10, and line 862 from both the mailman2.1b2.tar archive and the latest CVS). Note that there was never this problem with the subject lines for each individual article - it's only the index pages that are missing the HTML quoting function. HTH, -T. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-20 13:26 Message: Logged In: YES user_id=12800 I believe this report is out of date. All known cross-site scripting attacks have been fixed as of MM2.0.10 and I don't believe MM2.1b2 is vulnerable. I double checked the code in each version and indeed both versions make sure to quote any html in subjects. Can you please double check the latest versions (2.0.10 and 2.1cvs). ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=558208&group_id=103 From noreply@sourceforge.net Mon May 20 16:10:07 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 20 May 2002 08:10:07 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558208 ] Unescaped HTML in subject lines Message-ID: Bugs item #558208, was opened at 2002-05-20 06:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558208&group_id=103 >Category: None >Group: None >Status: Open Resolution: Out of Date Priority: 5 Submitted By: Tristan Roddis (tristan_roddis) Assigned to: Nobody/Anonymous (nobody) Summary: Unescaped HTML in subject lines Initial Comment: Currently (in 2.0.x and up to 2.1b2), then the archive index pages do not escape HTML in the subject lines of posts. This exposes the possibility of malicious or annoying list members being able to invoke cross site javascript on the index pages, or simply corrupt the archive display by adding HTML fragments (e.g. ' without a corresponding ') The fix is extremely simple, just edit the file /home/mailman/Mailman/Archiver/HyperArch.py so that the function write_index_entry() (which starts at or near line 882 in v2.06) so that its last line reads as follows: print index_entry_template % (urllib.quote (article.filename), html_quote (subject), article.sequence, author) [i.e. add the crucial html_quote() function around the subject] Hope that helps, -Tristan. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-20 11:10 Message: Logged In: YES user_id=12800 I'm re-opening this but moving it to the bugs tracker. I believe MM2.0.10 is vulnerable to this attack and the fix is simple. MM2.1b2 is not vulnerable because if you look at line 859 in HyperArch.py, you'll see that the subject and author fields are always CGIescape()'d. ---------------------------------------------------------------------- Comment By: Tristan Roddis (tristan_roddis) Date: 2002-05-20 09:47 Message: Logged In: YES user_id=549463 I've just had a look, and the offending line is still there in the file HyperArch.py for both versions (line number 882 in 2.10, and line 862 from both the mailman2.1b2.tar archive and the latest CVS). Note that there was never this problem with the subject lines for each individual article - it's only the index pages that are missing the HTML quoting function. HTH, -T. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-20 09:26 Message: Logged In: YES user_id=12800 I believe this report is out of date. All known cross-site scripting attacks have been fixed as of MM2.0.10 and I don't believe MM2.1b2 is vulnerable. I double checked the code in each version and indeed both versions make sure to quote any html in subjects. Can you please double check the latest versions (2.0.10 and 2.1cvs). ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558208&group_id=103 From noreply@sourceforge.net Mon May 20 16:10:42 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 20 May 2002 08:10:42 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558208 ] Unescaped HTML in subject lines Message-ID: Bugs item #558208, was opened at 2002-05-20 06:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558208&group_id=103 >Category: Pipermail >Group: 2.0.x >Status: Closed >Resolution: Fixed >Priority: 7 Submitted By: Tristan Roddis (tristan_roddis) Assigned to: Nobody/Anonymous (nobody) Summary: Unescaped HTML in subject lines Initial Comment: Currently (in 2.0.x and up to 2.1b2), then the archive index pages do not escape HTML in the subject lines of posts. This exposes the possibility of malicious or annoying list members being able to invoke cross site javascript on the index pages, or simply corrupt the archive display by adding HTML fragments (e.g. ' without a corresponding ') The fix is extremely simple, just edit the file /home/mailman/Mailman/Archiver/HyperArch.py so that the function write_index_entry() (which starts at or near line 882 in v2.06) so that its last line reads as follows: print index_entry_template % (urllib.quote (article.filename), html_quote (subject), article.sequence, author) [i.e. add the crucial html_quote() function around the subject] Hope that helps, -Tristan. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-20 11:10 Message: Logged In: YES user_id=12800 Fixed in MM2.0.11 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-20 11:10 Message: Logged In: YES user_id=12800 I'm re-opening this but moving it to the bugs tracker. I believe MM2.0.10 is vulnerable to this attack and the fix is simple. MM2.1b2 is not vulnerable because if you look at line 859 in HyperArch.py, you'll see that the subject and author fields are always CGIescape()'d. ---------------------------------------------------------------------- Comment By: Tristan Roddis (tristan_roddis) Date: 2002-05-20 09:47 Message: Logged In: YES user_id=549463 I've just had a look, and the offending line is still there in the file HyperArch.py for both versions (line number 882 in 2.10, and line 862 from both the mailman2.1b2.tar archive and the latest CVS). Note that there was never this problem with the subject lines for each individual article - it's only the index pages that are missing the HTML quoting function. HTH, -T. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-20 09:26 Message: Logged In: YES user_id=12800 I believe this report is out of date. All known cross-site scripting attacks have been fixed as of MM2.0.10 and I don't believe MM2.1b2 is vulnerable. I double checked the code in each version and indeed both versions make sure to quote any html in subjects. Can you please double check the latest versions (2.0.10 and 2.1cvs). ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558208&group_id=103 From barry@zope.com Mon May 20 19:05:21 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 20 May 2002 14:05:21 -0400 Subject: [Mailman-Developers] RELEASED Mailman 2.0.11 Message-ID: <15593.15073.61526.436079@anthem.wooz.org> I'm announcing the release of Mailman 2.0.11 which fixes two cross-site scripting exploits, one reported by "office" in the admin login page, and another reported by Tristan Roddis in the Pipermail index summaries. It is recommended that all sites upgrade their 2.0.x systems to this version. As usual, I've made both full source tarballs and patches available. See http://sourceforge.net/project/showfiles.php?group_id=103 for links to download all the patches and the source tarball. If you decide to install the patches, please do read the release notes first: http://sourceforge.net/project/shownotes.php?release_id=63042 See also: http://www.gnu.org/software/mailman http://www.list.org http://mailman.sf.net Cheers, -Barry From noreply@sourceforge.net Mon May 20 21:02:23 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 20 May 2002 13:02:23 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-558419 ] List-specific external handlers for MIME Message-ID: Feature Requests item #558419, was opened at 2002-05-20 20:02 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=558419&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel Keshet (dkesh) Assigned to: Nobody/Anonymous (nobody) Summary: List-specific external handlers for MIME Initial Comment: The MIME-handler should be able to hand off selected MIME types to an external handler, specified on a per-list basis, instead of deleting them. That way, site admins could write filters that post attachments to a website or filter them appropriately. The external handler could submit back new content to be included in the mail, e.g. a website to visit for the attachment or a warning that an attachment had been removed. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=558419&group_id=103 From marc_news@vasoftware.com Mon May 20 23:02:30 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Mon, 20 May 2002 15:02:30 -0700 Subject: [Mailman-Developers] bounce processor doesn't seem to work with digest bounces ? Message-ID: <20020520220230.GR31629@merlins.org> This bounce didn't get handled by mailman even though it went to svlug-bounces+peter.tower=fiserv.com@svlug.org (see Received lines), peter.tower@fiserv.com is subscribed to the list, and I'm pretty sure VERP bounce processing is working otherwise. Any ideas? From marc_news@vasoftware.com Tue May 21 01:17:12 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Mon, 20 May 2002 17:17:12 -0700 Subject: [Mailman-Developers] bounce processor doesn't seem to work with digest bounces ? In-Reply-To: <20020520220230.GR31629@merlins.org> References: <20020520220230.GR31629@merlins.org> Message-ID: <20020521001712.GY31629@merlins.org> On Mon, May 20, 2002 at 03:02:30PM -0700, Marc MERLIN wrote: > This bounce didn't get handled by mailman even though it went > to svlug-bounces+peter.tower=fiserv.com@svlug.org (see Received lines), > peter.tower@fiserv.com is subscribed to the list, and I'm pretty sure VERP > bounce processing is working otherwise. Ok, I'm stupid, we all knew that. Since I'm told some of you have your crystal balls out for repair, I'll include the actual bounce :-) (body truncated on purpose. Thanks for the heads up Dan) >From svlug-bounces@svlug.org Mon May 20 12:04:14 2002 Received: from svlug.svlug.org ([198.186.203.43]:2811 helo=mail.svlug.org) by mail2.merlins.org with esmtp (Cipher TLSv1:DES-CBC3-SHA:168) (Exim 4.04 #136 (Debian)) id 179sRw-00052N-00 for ; Mon, 20 May 2002 12:04:04 -0700 Received: from localhost ([127.0.0.1] helo=svlug.svlug.org) by mail.svlug.org with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 179sQU-0003AU-00 for ; Mon, 20 May 2002 12:02:34 -0700 Received: from firewall245.fiserv.com ([12.2.10.245] helo=missive-n0.fiserv.net) by mail.svlug.org with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 179sPP-00033e-00 for ; Mon, 20 May 2002 12:01:27 -0700 Received: from fiserv.com (root@localhost) by missive-n0.fiserv.net (8.8.8/8.8.7) with ESMTP id OAA10946 for ; Mon, 20 May 2002 14:03:19 -0500 (CDT) Received: from fwmke3 ([10.46.3.1]) by fiserv.com (Missive-4.0.2.0) with SMTP; Mon, 20 May 2002 14:03:03 -0500 Hop-Count: 1 Date: Mon, 20 May 2002 14:03:19 -0500 From: "master, post" To: Message-ID: <3830425@fiserv-missive1.fiserv.net> MIME-Version: 1.0 Sender: svlug-bounces@svlug.org Errors-To: svlug-bounces@lists.svlug.org Subject: Undeliverable mail Content-Type: multipart/mixed; boundary="=Bndry=--13CE94877" X-Spam-Status: No, hits=6.1 required=7.0 tests=TO_EMPTY,TO_MALFORMED,AMAZING version=2.20 X-Spam-Level: ****** Status: RO Content-Length: 8612 Lines: 243 --=Bndry=--13CE94877 Content-Type: text/plain; charset=US-ASCII Attached is your mail message which could not be delivered, or may have encountered some trouble in the delivery process. --=Bndry=--13CE94877 Content-Type: message/rfc822 Content-Disposition: inline Received: from localhost ([127.0.0.1] helo=svlug.svlug.org) by mail.svlug.org with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 179sOw-0003H3-01 for ; Mon, 20 May 2002 12:00:58 -0700 Date: Mon, 20 May 2002 12:00:58 -0700 From: svlug-request@svlug.org Subject: svlug Digest, Vol 84, Issue 1 To: svlug@svlug.org Message-ID: X-BeenThere: svlug@lists.svlug.org X-Mailman-Version: 2.1b2+ Precedence: bulk List-Help: List-Archive: List-Unsubscribe: , List-Subscribe: , List-Post: List-Id: discussion list for the Silicon Valley Linux Users Group. Sender: svlug-bounces+peter.tower=fiserv.com@svlug.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=Bndry=--33CE94877" --=Bndry=--33CE94877 Content-Type: text/plain; charset=US-ASCII Content-Description: svlug Digest, Vol 84, Issue 1 Send svlug mailing list submissions to svlug@lists.svlug.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.svlug.org/lists/listinfo/svlug or, via email, send a message with subject or body 'help' to svlug-request@lists.svlug.org You can reach the person managing the list at svlug-owner@lists.svlug.org When replying, please edit your Subject line so it is more specific than "Re: Contents of svlug digest..." -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From noreply@sourceforge.net Tue May 21 03:31:25 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 20 May 2002 19:31:25 -0700 Subject: [Mailman-Developers] [ mailman-Patches-558515 ] sendmail.py patch for security Message-ID: Patches item #558515, was opened at 2002-05-21 02:31 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=558515&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Peter D. Gray (pdg999) Assigned to: Nobody/Anonymous (nobody) Summary: sendmail.py patch for security Initial Comment: This is an updated Sendmail.py which avoids popen etc and is therefore (hopefully) secure. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=558515&group_id=103 From les@2pi.org Tue May 21 05:17:02 2002 From: les@2pi.org (Les Niles) Date: Mon, 20 May 2002 21:17:02 -0700 Subject: [Mailman-Developers] MimeDel.py: after filtering, munge text/plain's back together In-Reply-To: <200205160416.g4G4GHbH003979@utopia.West.Sun.COM> (message from Dan Mick on Wed, 15 May 2002 21:15:36 -0700 (PDT)) References: <200205160416.g4G4GHbH003979@utopia.West.Sun.COM> Message-ID: <200205210417.VAA13407@mutiny.2pi.org> On Wed, 15 May 2002 21:15:36 -0700 (PDT) Dan Mick wrote: >I've been playing with MimeDel (Content filtering), and have >come to the conclusion that two things need to happen: > >1) there needs to be a way to set "only allow text" or "only >allow text/plain" without enumerating each type you *don't* want, >and >... >Comments welcome. Not-text: "[^t]|t[^e]|te[^x]|tex[^t]|text[^/]" or something like that. -les From jarrell@vt.edu Tue May 21 11:17:31 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Tue, 21 May 2002 06:17:31 -0400 Subject: [Mailman-Developers] bounce processor doesn't seem to work with digest bounces ? In-Reply-To: <20020521001712.GY31629@merlins.org> References: <20020520220230.GR31629@merlins.org> <20020520220230.GR31629@merlins.org> Message-ID: <5.1.0.14.2.20020521061602.00a75d80@lennier.cc.vt.edu> At 05:17 PM 5/20/02 -0700, Marc wrote: >From: "master, post" >To: I'd have to go look at the code again, but doesn't the bounce processor read the headers? And this To header is a big fat null, which might well have confused the hell out of it... From noreply@sourceforge.net Tue May 21 13:01:05 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 21 May 2002 05:01:05 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558633 ] Blocked queue after fight with Majordomo Message-ID: Bugs item #558633, was opened at 2002-05-21 12:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Nigel Metheringham (nigel) Assigned to: Nobody/Anonymous (nobody) Summary: Blocked queue after fight with Majordomo Initial Comment: On Mailman 2.0.8 (was honestly going to upgrade today!). It appears that a couple of messages were boucing between the mailman request addresses and a Majordomo server, with more error transcript being added to the message on each bounce. This then appeared to completely block the qrunner. Removing the 2 huge messages from the qfiles directory fixed it. Broken message qfiles attached. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id=103 From noreply@sourceforge.net Tue May 21 13:03:11 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 21 May 2002 05:03:11 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558633 ] Blocked queue after fight with Majordomo Message-ID: Bugs item #558633, was opened at 2002-05-21 12:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Nigel Metheringham (nigel) Assigned to: Nobody/Anonymous (nobody) Summary: Blocked queue after fight with Majordomo Initial Comment: On Mailman 2.0.8 (was honestly going to upgrade today!). It appears that a couple of messages were boucing between the mailman request addresses and a Majordomo server, with more error transcript being added to the message on each bounce. This then appeared to completely block the qrunner. Removing the 2 huge messages from the qfiles directory fixed it. Broken message qfiles attached. ---------------------------------------------------------------------- >Comment By: Nigel Metheringham (nigel) Date: 2002-05-21 12:03 Message: Logged In: YES user_id=31288 and other file ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id=103 From smw@pixel.citadel.org Mon May 20 20:52:59 2002 From: smw@pixel.citadel.org (Steve Williams) Date: Mon, 20 May 2002 15:52:59 -0400 Subject: [Mailman-Developers] Usenet Gateway question... Message-ID: <200205201952.g4KJqxM23432@pixel.citadel.org> I'm currently using 2.0.1 and I'm having an interesting usenet issue. I've recently had to switch ISP's and now my stupid newsfeed requires authentication. Is there any way in Mailman to allow for that, or is there the possibility of a quick-fix? I've done a lot of customizations to it so I'm kind of trying to avoid upgrading (in case someone tells me that's the solution) unless I really have to. I apologize if this has already been asked. I checked the archives but didn't see anything, however given the amount of data I was wading through I admit the possibility that I missed it. Thanks in advance, -Steve From J.Landman@ru.ac.za Tue May 21 08:53:02 2002 From: J.Landman@ru.ac.za (John Landman) Date: Tue, 21 May 2002 09:53:02 +0200 Subject: [Mailman-Developers] Printing mailman subscriber list Message-ID: <006101c2009c$89852de0$8250e792@ru.ac.za> Is there a developer out there interested in adding the facility to print the list of subscribers in a MailMan list? Or, if this has been done where's the patch? the system in use here claims to be 2.0.5. Yours -> John Landman don't be irreplaceable - if you can't be replaced, you can't be promoted. - Dilbert ______________________________________________________________ -- Department of Geography , Rhodes University, P O Box 94, Grahamstown, 6140 South Africa ________________________________________ /|||||||||||||\ humans are a resource not a cost - a peter drucker principle |||||||||||||||||||| Internet: J.Landman@ru.ac.za |||||||||||||@|| Telephone: +27 46 603 8325 Fax: +27 46 636 1199 \||||||||||||||/ __________________________________________ everyone one day will get one break sometime once The views expressed above are not necessarily those of Rhodes University and if any other opinions are expressed I don't know whose they are From david@midrange.com Tue May 21 15:15:59 2002 From: david@midrange.com (David Gibbs) Date: Tue, 21 May 2002 09:15:59 -0500 (CDT) Subject: [Mailman-Developers] Python Unicode codecs for Chinese? Message-ID: <34596.208.248.38.130.1021990559.squirrel@webmail.midrange.com> Folks: I just resynced my mailman sandbox, reconfigured, and got the following message ... configure: warning: ***** Python Unicode codecs for Chinese not found. ***** Chinese emails generated by or manipulated in Mailman will not ***** be sent in the correct encoding and may be unreadable. ***** Please uncompress and install the Chinese codecs from: ***** http://sourceforge.net/projects/python-codecs/ ***** ***** Note: Everything else will work just fine. ... however, when I go to the URL mentioned, I end up with a alpha project with no released files and no home page. Is this supposed to be what I get? david From dmick@utopia.West.Sun.COM Tue May 21 20:43:04 2002 From: dmick@utopia.West.Sun.COM (Dan Mick) Date: Tue, 21 May 2002 12:43:04 -0700 (PDT) Subject: [Mailman-Developers] MimeDel.py: after filtering, munge text/plain's back together Message-ID: <200205211943.g4LJhnOl019978@utopia.West.Sun.COM> I like this version for #2 much better; it handles any payload type (at least theoretically) with the desirable text/plain as a side effect. I'm not happy about the \n hack but I don't see a way around it. Again, this is a manually-hacked diff, but now it's only one block insertion, so should be easier to play with. Comments still welcome. The syslog() is, of course, optional. I left the nested if()'s for ease of debugging. @@ -91,12 +92,27 @@ # Now perhaps convert all text/html to text/plain if mlist.convert_html_to_plaintext and mm_cfg.HTML_TO_PLAIN_TEXT_COMMAND: changedp += to_plaintext(msg) + + # If we're left with only two parts, an empty body and one attachment, + # recast the message to one of just that part + + if len(msg.get_payload()) == 2: + if msg.get_payload(0).get_payload() == '': + type = msg.get_payload(1).get_type() + syslog('post', "collapsing message %s type %s", + msg['Message-ID'], type) + newpayload = msg.get_payload(1).get_payload() + if type == 'text/plain' and newpayload[-1] != '\n': + newpayload += '\n' + msg.set_payload(newpayload) + msg.set_type(type) + if changedp: msg['X-Content-Filtered-By'] = 'Mailman/MimeDel %s' % VERSION > I've been playing with MimeDel (Content filtering), and have > come to the conclusion that two things need to happen: > > 1) there needs to be a way to set "only allow text" or "only > allow text/plain" without enumerating each type you *don't* want, > and > > 2) at the end of filtering, there needs to be a check to see if > all the remaining parts can profitably be recombined into > one part, at least for text/plain. > > Here's a hack at doing #2 (so that, for instance, messages > with HTML alternatives end up being one big text/plain message, > even with headers and footers turned on). > > #1 takes a new attribute and some GUI stuff, so I'll try to sell > that back to Barry directly. > > Note: this diff is hand-hacked (as I have my partial #1 > solution in there too) so you may have to hand-apply this > if you want to play with it. > > Comments welcome. > > > > > Index: MimeDel.py > =================================================================== > RCS file: /cvsroot/mailman/mailman/Mailman/Handlers/MimeDel.py,v > retrieving revision 2.1 > diff -u -r2.1 MimeDel.py > --- MimeDel.py 18 Apr 2002 20:46:53 -0000 2.1 > +++ MimeDel.py 16 May 2002 04:13:32 -0000 > > @@ -91,12 +92,16 @@ > # Now perhaps convert all text/html to text/plain > if mlist.convert_html_to_plaintext and mm_cfg.HTML_TO_PLAIN_TEXT_COMMAND: > changedp += to_plaintext(msg) > + # Now, scan through all parts, and if only text/plain left, fuse > + # them all back together into one payload > + collapse_textplain(msg) > + > if changedp: > msg['X-Content-Filtered-By'] = 'Mailman/MimeDel %s' % VERSION > > > @@ -138,6 +146,23 @@ > newpayload.append(subpart) > msg.set_payload(newpayload) > > +def collapse_textplain(msg): > + if not msg.is_multipart(): > + return > + for subpart in msg.get_payload(): > + if subpart.get_type() != 'text/plain': > + return > + # ok, all parts are text/plain; munge 'em together > + newpayload = "" > + for subpart in msg.get_payload(): > + if len(newpayload): > + newpayload += '\n' > + newpayload += subpart.get_payload() > + if newpayload[-1] != '\n': > + newpayload += '\n' > + msg.set_payload(newpayload) > + msg.set_type("text/plain") > > > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman-21/listinfo/mailman-developers From noreply@sourceforge.net Tue May 21 21:18:26 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 21 May 2002 13:18:26 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558848 ] Upgrade to 2.0.11 breaks admindb page Message-ID: Bugs item #558848, was opened at 2002-05-21 16:18 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558848&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: nathan hruby (nhruby) Assigned to: Nobody/Anonymous (nobody) Summary: Upgrade to 2.0.11 breaks admindb page Initial Comment: Hey, just upgraded to 2.0.11 from 2.0.5. Upgraded by applying the patches (in correct order :) to go from 2.0.5 to .2.0.22. All patches applied cleanly to the 2.0.5 source with no errors. reran the config.guess and re-ran make install, everything went off without a hitch, after restarting sendmail, httpd and cron after the upgrade procedure and checking the test list the admindb webpage dies with an error. All other pages work fine. Here's the traceback: May 21 16:32:19 2002 admin(9971): @@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@ admin(9971): [----- Mailman Version: 2.0.11 -----] admin(9971): [----- Traceback ------] admin(9971): Traceback (innermost last): admin(9971): File "/home/mailman/scripts/driver", line 96, in run_main admin(9971): main() admin(9971): File "/home/mailman/Mailman/Cgi/ admindb.py", line 110, in main admin(9971): if len(cgidata.keys()): admin(9971): NameError: cgidata admin(9971): [----- Python Information -----] admin(9971): sys.version = 1.5.2 (#1, Aug 25 2000, 09:33:37) [GCC 2.96 20000731 (experimental)] admin(9971): sys.executable = /usr/bin/python admin(9971): sys.prefix = /usr admin(9971): sys.exec_prefix= /usr admin(9971): sys.path = /usr admin(9971): sys.platform = linux-i386 admin(9971): [----- Environment Variables -----] admin(9971): DOCUMENT_ROOT: /var/www/html admin(9971): SERVER_ADDR: 128.192.51.21 admin(9971): QUERY_STRING: admin(9971): SERVER_PORT: 80 admin(9971): PATH_TRANSLATED: /var/www/html/ testlist admin(9971): REMOTE_ADDR: 128.192.51.220 admin(9971): HTTP_UA_OS: MacOS admin(9971): HTTP_ACCEPT_LANGUAGE: en admin(9971): GATEWAY_INTERFACE: CGI/1.1 admin(9971): SERVER_NAME: nuttybar.drama.uga.edu admin(9971): HTTP_CONNECTION: Keep-Alive admin(9971): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 5.14; Mac_PowerPC) admin(9971): HTTP_ACCEPT: */* admin(9971): REQUEST_URI: /mailman/admindb/ testlist admin(9971): HTTP_UA_CPU: PPC admin(9971): HTTP_EXTENSION: Security/Remote- Passphrase admin(9971): SCRIPT_FILENAME: /home/mailman/ cgi-bin/admindb admin(9971): PATH_INFO: /testlist admin(9971): HTTP_HOST: nuttybar.drama.uga.edu admin(9971): REQUEST_METHOD: GET admin(9971): SERVER_SIGNATURE:
Apache/1.3.14 Server at nuttybar.drama.uga.edu Port 80
admin(9971): SCRIPT_NAME: /mailman/admindb admin(9971): SERVER_ADMIN: root@localhost admin(9971): SERVER_SOFTWARE: Apache/1.3.14 (Unix) (Red-Hat/Linux) admin(9971): PYTHONPATH: /home/mailman admin(9971): HTTP_COOKIE: testlist:admin= 280200000069c3aeea3c73280000003034623331306 1396165613462396165353062636 633393934393139363738333237323539303864 admin(9971): SERVER_PROTOCOL: HTTP/1.1 admin(9971): REMOTE_PORT: 56839 admin(9971): HTTP_REFERER: http:// nuttybar.drama.uga.edu/mailman/admin/testlist ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558848&group_id=103 From noreply@sourceforge.net Tue May 21 21:41:04 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 21 May 2002 13:41:04 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558848 ] Upgrade to 2.0.11 breaks admindb page Message-ID: Bugs item #558848, was opened at 2002-05-21 16:18 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558848&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: nathan hruby (nhruby) Assigned to: Nobody/Anonymous (nobody) Summary: Upgrade to 2.0.11 breaks admindb page Initial Comment: Hey, just upgraded to 2.0.11 from 2.0.5. Upgraded by applying the patches (in correct order :) to go from 2.0.5 to .2.0.22. All patches applied cleanly to the 2.0.5 source with no errors. reran the config.guess and re-ran make install, everything went off without a hitch, after restarting sendmail, httpd and cron after the upgrade procedure and checking the test list the admindb webpage dies with an error. All other pages work fine. Here's the traceback: May 21 16:32:19 2002 admin(9971): @@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@ admin(9971): [----- Mailman Version: 2.0.11 -----] admin(9971): [----- Traceback ------] admin(9971): Traceback (innermost last): admin(9971): File "/home/mailman/scripts/driver", line 96, in run_main admin(9971): main() admin(9971): File "/home/mailman/Mailman/Cgi/ admindb.py", line 110, in main admin(9971): if len(cgidata.keys()): admin(9971): NameError: cgidata admin(9971): [----- Python Information -----] admin(9971): sys.version = 1.5.2 (#1, Aug 25 2000, 09:33:37) [GCC 2.96 20000731 (experimental)] admin(9971): sys.executable = /usr/bin/python admin(9971): sys.prefix = /usr admin(9971): sys.exec_prefix= /usr admin(9971): sys.path = /usr admin(9971): sys.platform = linux-i386 admin(9971): [----- Environment Variables -----] admin(9971): DOCUMENT_ROOT: /var/www/html admin(9971): SERVER_ADDR: 128.192.51.21 admin(9971): QUERY_STRING: admin(9971): SERVER_PORT: 80 admin(9971): PATH_TRANSLATED: /var/www/html/ testlist admin(9971): REMOTE_ADDR: 128.192.51.220 admin(9971): HTTP_UA_OS: MacOS admin(9971): HTTP_ACCEPT_LANGUAGE: en admin(9971): GATEWAY_INTERFACE: CGI/1.1 admin(9971): SERVER_NAME: nuttybar.drama.uga.edu admin(9971): HTTP_CONNECTION: Keep-Alive admin(9971): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 5.14; Mac_PowerPC) admin(9971): HTTP_ACCEPT: */* admin(9971): REQUEST_URI: /mailman/admindb/ testlist admin(9971): HTTP_UA_CPU: PPC admin(9971): HTTP_EXTENSION: Security/Remote- Passphrase admin(9971): SCRIPT_FILENAME: /home/mailman/ cgi-bin/admindb admin(9971): PATH_INFO: /testlist admin(9971): HTTP_HOST: nuttybar.drama.uga.edu admin(9971): REQUEST_METHOD: GET admin(9971): SERVER_SIGNATURE:
Apache/1.3.14 Server at nuttybar.drama.uga.edu Port 80
admin(9971): SCRIPT_NAME: /mailman/admindb admin(9971): SERVER_ADMIN: root@localhost admin(9971): SERVER_SOFTWARE: Apache/1.3.14 (Unix) (Red-Hat/Linux) admin(9971): PYTHONPATH: /home/mailman admin(9971): HTTP_COOKIE: testlist:admin= 280200000069c3aeea3c73280000003034623331306 1396165613462396165353062636 633393934393139363738333237323539303864 admin(9971): SERVER_PROTOCOL: HTTP/1.1 admin(9971): REMOTE_PORT: 56839 admin(9971): HTTP_REFERER: http:// nuttybar.drama.uga.edu/mailman/admin/testlist ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-21 16:41 Message: Logged In: YES user_id=12800 Please compare the Mailman/Cgi/admindb.py file against the file at the top of the 2.0 maintainence branch: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/mailman/mailman/Mailman/Cgi/admindb.py?rev=1.36.2.7&only_with_tag=Release_2_0_11&content-type=text/plain It sounds like there was a problem with the upgrade or the install after upgrade (I know you didn't get any errors, but still, I can't see why this exception would otherwise happen!) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558848&group_id=103 From noreply@sourceforge.net Tue May 21 21:47:14 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 21 May 2002 13:47:14 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558633 ] Blocked queue after fight with Majordomo Message-ID: Bugs item #558633, was opened at 2002-05-21 08:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Nigel Metheringham (nigel) Assigned to: Nobody/Anonymous (nobody) Summary: Blocked queue after fight with Majordomo Initial Comment: On Mailman 2.0.8 (was honestly going to upgrade today!). It appears that a couple of messages were boucing between the mailman request addresses and a Majordomo server, with more error transcript being added to the message on each bounce. This then appeared to completely block the qrunner. Removing the 2 huge messages from the qfiles directory fixed it. Broken message qfiles attached. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-21 16:47 Message: Logged In: YES user_id=12800 Heh, I think this is a general problem when you get two email robots talking to each other! In MM2.1cvs the robot will refuse to respond to a message marked Precedence: bulk|junk|list -- but it looks like that wouldn't have even helped in this case (since the Majordomo server isnt' setting that header ;/ ) The only other solution I can think of is to add a config variable which is a blacklist of known addresses (regexps) that Mailman should not respond too. You'd still get into the robot infloop the first time, but at least you'd have a hope of avoiding subsequent replybot storms for the same address. ---------------------------------------------------------------------- Comment By: Nigel Metheringham (nigel) Date: 2002-05-21 08:03 Message: Logged In: YES user_id=31288 and other file ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id=103 From noreply@sourceforge.net Tue May 21 21:56:08 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 21 May 2002 13:56:08 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558848 ] Upgrade to 2.0.11 breaks admindb page Message-ID: Bugs item #558848, was opened at 2002-05-21 16:18 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558848&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: nathan hruby (nhruby) Assigned to: Nobody/Anonymous (nobody) Summary: Upgrade to 2.0.11 breaks admindb page Initial Comment: Hey, just upgraded to 2.0.11 from 2.0.5. Upgraded by applying the patches (in correct order :) to go from 2.0.5 to .2.0.22. All patches applied cleanly to the 2.0.5 source with no errors. reran the config.guess and re-ran make install, everything went off without a hitch, after restarting sendmail, httpd and cron after the upgrade procedure and checking the test list the admindb webpage dies with an error. All other pages work fine. Here's the traceback: May 21 16:32:19 2002 admin(9971): @@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@ admin(9971): [----- Mailman Version: 2.0.11 -----] admin(9971): [----- Traceback ------] admin(9971): Traceback (innermost last): admin(9971): File "/home/mailman/scripts/driver", line 96, in run_main admin(9971): main() admin(9971): File "/home/mailman/Mailman/Cgi/ admindb.py", line 110, in main admin(9971): if len(cgidata.keys()): admin(9971): NameError: cgidata admin(9971): [----- Python Information -----] admin(9971): sys.version = 1.5.2 (#1, Aug 25 2000, 09:33:37) [GCC 2.96 20000731 (experimental)] admin(9971): sys.executable = /usr/bin/python admin(9971): sys.prefix = /usr admin(9971): sys.exec_prefix= /usr admin(9971): sys.path = /usr admin(9971): sys.platform = linux-i386 admin(9971): [----- Environment Variables -----] admin(9971): DOCUMENT_ROOT: /var/www/html admin(9971): SERVER_ADDR: 128.192.51.21 admin(9971): QUERY_STRING: admin(9971): SERVER_PORT: 80 admin(9971): PATH_TRANSLATED: /var/www/html/ testlist admin(9971): REMOTE_ADDR: 128.192.51.220 admin(9971): HTTP_UA_OS: MacOS admin(9971): HTTP_ACCEPT_LANGUAGE: en admin(9971): GATEWAY_INTERFACE: CGI/1.1 admin(9971): SERVER_NAME: nuttybar.drama.uga.edu admin(9971): HTTP_CONNECTION: Keep-Alive admin(9971): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 5.14; Mac_PowerPC) admin(9971): HTTP_ACCEPT: */* admin(9971): REQUEST_URI: /mailman/admindb/ testlist admin(9971): HTTP_UA_CPU: PPC admin(9971): HTTP_EXTENSION: Security/Remote- Passphrase admin(9971): SCRIPT_FILENAME: /home/mailman/ cgi-bin/admindb admin(9971): PATH_INFO: /testlist admin(9971): HTTP_HOST: nuttybar.drama.uga.edu admin(9971): REQUEST_METHOD: GET admin(9971): SERVER_SIGNATURE:
Apache/1.3.14 Server at nuttybar.drama.uga.edu Port 80
admin(9971): SCRIPT_NAME: /mailman/admindb admin(9971): SERVER_ADMIN: root@localhost admin(9971): SERVER_SOFTWARE: Apache/1.3.14 (Unix) (Red-Hat/Linux) admin(9971): PYTHONPATH: /home/mailman admin(9971): HTTP_COOKIE: testlist:admin= 280200000069c3aeea3c73280000003034623331306 1396165613462396165353062636 633393934393139363738333237323539303864 admin(9971): SERVER_PROTOCOL: HTTP/1.1 admin(9971): REMOTE_PORT: 56839 admin(9971): HTTP_REFERER: http:// nuttybar.drama.uga.edu/mailman/admin/testlist ---------------------------------------------------------------------- >Comment By: nathan hruby (nhruby) Date: 2002-05-21 16:56 Message: Logged In: YES user_id=19736 Damn you're quick :) Fixed by moving the following block of code starting at line 110 in mailman/Cgi/admindb.py over 5 spaces to the left... --- CUT_N_PASTE cgidata = cgi.FieldStorage() try: Auth.authenticate(mlist, cgidata) except Auth.NotLoggedInError, e: Auth.loginpage(mlist, 'admindb', e.message) return -- CUT_N_PASTE perhaps there is something screwy with the patches in the downlaod manager? ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-21 16:41 Message: Logged In: YES user_id=12800 Please compare the Mailman/Cgi/admindb.py file against the file at the top of the 2.0 maintainence branch: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/mailman/mailman/Mailman/Cgi/admindb.py?rev=1.36.2.7&only_with_tag=Release_2_0_11&content-type=text/plain It sounds like there was a problem with the upgrade or the install after upgrade (I know you didn't get any errors, but still, I can't see why this exception would otherwise happen!) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558848&group_id=103 From noreply@sourceforge.net Tue May 21 23:01:07 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 21 May 2002 15:01:07 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558896 ] allow multiple values for invoking group Message-ID: Bugs item #558896, was opened at 2002-05-21 18:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558896&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Nalin Dahyabhai (nsdahya1) Assigned to: Nobody/Anonymous (nobody) Summary: allow multiple values for invoking group Initial Comment: When building binary packages (for example, when you don't know ahead of time which MTA is going to be used, and the different MTAs run under different GIDs), it's sometimes useful to be able to specify multiple unprivileged GIDs which are to be allowed to run the wrapped scripts. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558896&group_id=103 From noreply@sourceforge.net Tue May 21 23:11:50 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 21 May 2002 15:11:50 -0700 Subject: [Mailman-Developers] [ mailman-Patches-558898 ] allow multiple values for invoking group Message-ID: Patches item #558898, was opened at 2002-05-21 18:11 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=558898&group_id=103 Category: command line scripts Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Nalin Dahyabhai (nsdahya1) Assigned to: Nobody/Anonymous (nobody) Summary: allow multiple values for invoking group Initial Comment: Per bug #558896, a patch which converts the allowed gid into an array of allowed gids which can be set at compile-time. Might not be complete enough, but it seems to work for me. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=558898&group_id=103 From noreply@sourceforge.net Tue May 21 23:43:35 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 21 May 2002 15:43:35 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558909 ] Auto-responsder doesn't send response. Message-ID: Bugs item #558909, was opened at 2002-05-21 23:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558909&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Donal Hunt (redgiant) Assigned to: Nobody/Anonymous (nobody) Summary: Auto-responsder doesn't send response. Initial Comment: Auto-response mail never gets sent on -admin and -owner addresses. Set the autorespond_admin and autorespond_admin_text properties on the auto-responder page of the admin page for the list. Sending mail to either -admin@host or -owner@host results in the admin receiving the email but no auto-response is sent to the sender. Found on Mailman CVS (May 9th). Up to my eyes at present so haven't got a chance to dig deeper yet. Will do so middle of next week if needed. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558909&group_id=103 From nb@thinkcoach.com Tue May 21 23:13:08 2002 From: nb@thinkcoach.com (Norbert Bollow) Date: Wed, 22 May 2002 00:13:08 +0200 Subject: [Mailman-Developers] [ mailman-Bugs-558633 ] Blocked queue after fight with Majordomo In-Reply-To: (noreply@sourceforge.net) References: Message-ID: <200205212213.g4LMD8a01244@quill.local> > Heh, I think this is a general problem when you get two > email robots talking to each other! In MM2.1cvs the robot > will refuse to respond to a message marked Precedence: > bulk|junk|list -- but it looks like that wouldn't have even > helped in this case (since the Majordomo server isnt' > setting that header ;/ ) Rate limiting can do a lot to prevent things from getting out of hand. For example, respond at most ten times to essentially the same request from the same email address. On any given day, when Mailman gets the tenth message from the same email address without valid commands, it could reply "This is the tenth message of this type today from you. It order to avoid problems like mail loops between email robots, any further messages of this type will be ignored today. Please try again tomorrow." And then any further messages from that address with no valid commands will be just discarded. Similarly, Mailman would reply only to ten subscription requests for the same list from the same user on any given day. And only to ten unsubscription requests for the same list from the same user on any given day. And only to ten requests to change the subscription options in the same way. Etc. Since most loops (with the exception of some bounce loops) iterate more quickly than ten times per day, this will kill most loops between robots before they create serious problems. Greetings, Norbert. -- A founder of the http://DotGNU.org project and Steering Committee member Norbert Bollow, Weidlistr.18, CH-8624 Gruet (near Zurich, Switzerland) Tel +41 1 972 20 59 Fax +41 1 972 20 69 http://norbert.ch List hosting with GNU Mailman on your own domain name http://cisto.com From barry@zope.com Wed May 22 01:26:22 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 21 May 2002 20:26:22 -0400 Subject: [Mailman-Developers] Replybot change proposed References: <15591.58949.540504.710470@anthem.wooz.org> Message-ID: <15594.58798.401990.177430@anthem.wooz.org> >>>>> "CVR" == Chuq Von Rospach writes: CVR> I believe 822/821 defines its existance, but not its CVR> content. The best defacto definitions for content come from CVR> the sendmail definitions, which everyone else more or less CVR> borrows. CVR> Here's the relevant piece from the sendmail operations CVR> manual: That actually helps a lot, thanks Chuq. Note this also tells me that we should be setting "Precedence: list" in our outgoing messages instead of "Precedence: bulk". Any objections? -Barry From chuqui@plaidworks.com Wed May 22 02:40:04 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Tue, 21 May 2002 18:40:04 -0700 Subject: [Mailman-Developers] Replybot change proposed In-Reply-To: <15594.58798.401990.177430@anthem.wooz.org> Message-ID: On 5/21/02 5:26 PM, "Barry A. Warsaw" wrote: > Note this also tells me that we should be setting "Precedence: list" > in our outgoing messages instead of "Precedence: bulk". Any > objections? I would send out list messages Precedence: list, admin messages as bulk. If the password reminder is hooked up to the bounce processor, send it out first class, otherwise send it out bulk. (why? Because some sites don't send bounces to list/bulk mail, so the only way to do bounce hacking on those is to send a first class message, and the password message is perfect, if we do site-wide bounce processing on it...) -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ Very funny, Scotty. Now beam my clothes down here, will you? From barry@zope.com Wed May 22 03:10:27 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 21 May 2002 22:10:27 -0400 Subject: [Mailman-Developers] Replybot change proposed References: <15594.58798.401990.177430@anthem.wooz.org> Message-ID: <15594.65043.331875.393933@anthem.wooz.org> >>>>> "CVR" == Chuq Von Rospach writes: >> Note this also tells me that we should be setting "Precedence: >> list" in our outgoing messages instead of "Precedence: bulk". >> Any objections? CVR> I would send out list messages Precedence: list, admin CVR> messages as bulk. Okay, I'm with you there. CVR> If the password reminder is hooked up to the bounce CVR> processor, send it out first class, otherwise send it out CVR> bulk. (why? Because some sites don't send bounces to CVR> list/bulk mail, so the only way to do bounce hacking on those CVR> is to send a first class message, and the password message is CVR> perfect, if we do site-wide bounce processing on it...) That's a little surprising. The sendmail docs you quoted say: [...] Numbers less than zero have the special property that if an error occurs during pro- cessing the body of the message will not be returned; this is expected to be used for "bulk" mail such as through mailing lists. which tells me that Precedence: bulk still gets a bounce returned, but the body of the original message won't be included. That's fine, since we don't need the body to process the bounce. Maybe you're describing the behavior of other MTAs? I'm inclined to send password reminders out as "Precedence: bulk", although I /think/ it wouldn't be hard to do whatever we wanted here. -Barry From chuqui@plaidworks.com Wed May 22 03:17:23 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Tue, 21 May 2002 19:17:23 -0700 Subject: [Mailman-Developers] Replybot change proposed In-Reply-To: <15594.65043.331875.393933@anthem.wooz.org> Message-ID: On 5/21/02 7:10 PM, "Barry A. Warsaw" wrote: > That's a little surprising. The sendmail docs you quoted say: I didn't say they were CORRECT. I merely noted some sites do this. I think it's wrong -- but if you never send a first class piece of email, they never return a bounce, so you can't correct it. A royal waste of resources.... > I'm inclined to send password reminders out as "Precedence: bulk", > although I /think/ it wouldn't be hard to do whatever we wanted here. Which is fine. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ IMHO: Jargon. Acronym for In My Humble Opinion. Used to flag as an opinion something that is clearly from context an opinion to everyone except the mentally dense. Opinions flagged by IMHO are actually rarely humble. IMHO. (source: third unabridged dictionary of chuqui-isms). From barry@zope.com Wed May 22 03:19:54 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 21 May 2002 22:19:54 -0400 Subject: [Mailman-Developers] Replybot change proposed References: <15594.65043.331875.393933@anthem.wooz.org> Message-ID: <15595.74.787716.125228@anthem.wooz.org> >>>>> "CVR" == Chuq Von Rospach writes: >> I'm inclined to send password reminders out as "Precedence: >> bulk", although I /think/ it wouldn't be hard to do whatever we >> wanted here. CVR> Which is fine. Cool. Let's leave it this way for now. Should be easy to change later if we decide we want it first-class after all. -Barry From noreply@sourceforge.net Wed May 22 03:38:12 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 21 May 2002 19:38:12 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558633 ] Blocked queue after fight with Majordomo Message-ID: Bugs item #558633, was opened at 2002-05-21 08:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Nigel Metheringham (nigel) Assigned to: Nobody/Anonymous (nobody) Summary: Blocked queue after fight with Majordomo Initial Comment: On Mailman 2.0.8 (was honestly going to upgrade today!). It appears that a couple of messages were boucing between the mailman request addresses and a Majordomo server, with more error transcript being added to the message on each bounce. This then appeared to completely block the qrunner. Removing the 2 huge messages from the qfiles directory fixed it. Broken message qfiles attached. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-21 22:38 Message: Logged In: YES user_id=12800 Norbert Bollow gives this very good idea: Rate limiting can do a lot to prevent things from getting out of hand. For example, respond at most ten times to essentially the same request from the same email address. On any given day, when Mailman gets the tenth message from the same email address without valid commands, it could reply "This is the tenth message of this type today from you. It order to avoid problems like mail loops between email robots, any further messages of this type will be ignored today. Please try again tomorrow." And then any further messages from that address with no valid commands will be just discarded. Similarly, Mailman would reply only to ten subscription requests for the same list from the same user on any given day. And only to ten unsubscription requests for the same list from the same user on any given day. And only to ten requests to change the subscription options in the same way. Etc. Since most loops (with the exception of some bounce loops) iterate more quickly than ten times per day, this will kill most loops between robots before they create serious problems. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-21 16:47 Message: Logged In: YES user_id=12800 Heh, I think this is a general problem when you get two email robots talking to each other! In MM2.1cvs the robot will refuse to respond to a message marked Precedence: bulk|junk|list -- but it looks like that wouldn't have even helped in this case (since the Majordomo server isnt' setting that header ;/ ) The only other solution I can think of is to add a config variable which is a blacklist of known addresses (regexps) that Mailman should not respond too. You'd still get into the robot infloop the first time, but at least you'd have a hope of avoiding subsequent replybot storms for the same address. ---------------------------------------------------------------------- Comment By: Nigel Metheringham (nigel) Date: 2002-05-21 08:03 Message: Logged In: YES user_id=31288 and other file ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id=103 From barry@zope.com Wed May 22 03:38:48 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 21 May 2002 22:38:48 -0400 Subject: [Mailman-Developers] [ mailman-Bugs-558633 ] Blocked queue after fight with Majordomo References: <200205212213.g4LMD8a01244@quill.local> Message-ID: <15595.1208.470139.147279@anthem.wooz.org> >>>>> "NB" == Norbert Bollow writes: NB> Rate limiting can do a lot to prevent things from getting NB> out of hand. It's an excellent point. I've added your comments to the bug report so I don't forget. Thanks, -Barry From noreply@sourceforge.net Wed May 22 04:03:03 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 21 May 2002 20:03:03 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-558896 ] allow multiple values for invoking group Message-ID: Feature Requests item #558896, was opened at 2002-05-21 18:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=558896&group_id=103 >Category: None >Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nalin Dahyabhai (nsdahya1) Assigned to: Nobody/Anonymous (nobody) Summary: allow multiple values for invoking group Initial Comment: When building binary packages (for example, when you don't know ahead of time which MTA is going to be used, and the different MTAs run under different GIDs), it's sometimes useful to be able to specify multiple unprivileged GIDs which are to be allowed to run the wrapped scripts. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-21 23:03 Message: Logged In: YES user_id=12800 I'm changing this to a feature request. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=558896&group_id=103 From noreply@sourceforge.net Wed May 22 04:15:24 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 21 May 2002 20:15:24 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558988 ] bad performance for big queue dirs Message-ID: Bugs item #558988, was opened at 2002-05-22 03:15 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558988&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Norbert Bollow (bollow) Assigned to: Nobody/Anonymous (nobody) Summary: bad performance for big queue dirs Initial Comment: Many filesystems (e.g. the popular ext2) have horrible performance when there are many files in the same directory. The queue system should be modified to avoid this situation. As a test case, try adding 20,000 test address in such a way that Mailman will try to send a welcome message to each of them. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558988&group_id=103 From wheakory@isu.edu Wed May 22 06:37:58 2002 From: wheakory@isu.edu (Kory Wheatley) Date: Tue, 21 May 2002 23:37:58 -0600 Subject: [Mailman-Developers] Mailman problem with Python upgrade Message-ID: <3CEB2EB5.C28DCFE5@isu.edu> I've install mailman 2.0.11 on Red Hat 7.2 and it was working fine until I upgrade to Python 2.1. Once I upgraded to this version everything seemed fine for 5 hours. I was able to receive messages from my mailing lists at our University. The Web Interface administrator options for the lists all worked fine. Then messages started piling in "qfiles" and it would not send anymore messages out. I moved them out of the queue and started moving them back in one at a time and then again the messages seemed to be sent properly, but then they started piling back up in the qfiles directory again . Here is the errors I received in the "error" logfile. I'm not totally efficient on Python yet, so I would like some help I would appreciate it. (Quite a few messages on CORRUPTED ARCHIVES and module regex not found) ERROR LOG FILE May 21 10:20:01 2002 qrunner(31161): Traceback (most recent call last): May 21 10:20:01 2002 qrunner(31161): File "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail May 21 10:20:01 2002 qrunner(31161): import HyperArch May 21 10:20:01 2002 qrunner(31161): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? May 21 10:20:01 2002 qrunner(31161): from Mailman import EncWord May 21 10:20:01 2002 qrunner(31161): File "/home/mailman/Mailman/EncWord.py", line 21, in ? May 21 10:20:01 2002 qrunner(31161): import base64 May 21 10:20:01 2002 qrunner(31161): File "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? May 21 10:20:01 2002 qrunner(31161): import binascii May 21 10:20:01 2002 qrunner(31161): ImportError: No module named binascii May 21 10:20:01 2002 (31161) CORRUPT ARCHIVE FOR LIST: libstaff May 21 10:20:02 2002 qrunner(31161): Traceback (most recent call last): May 21 10:20:02 2002 qrunner(31161): File "/home/mailman/Mailman/Archiver/Archiver.py", line 220, in ArchiveMail May 21 10:20:02 2002 qrunner(31161): h = HyperArch.HyperArchive(self) May 21 10:20:02 2002 qrunner(31161): AttributeError: 'Mailman.Archiver.HyperArch' module has no attribute 'HyperArchive' May 21 10:20:02 2002 (31161) CORRUPT ARCHIVE FOR LIST: relief May 21 10:20:02 2002 qrunner(31161): Traceback (most recent call last): May 21 10:20:02 2002 qrunner(31161): File "/home/mailman/Mailman/Archiver/Archiver.py", line 220, in ArchiveMail May 21 10:20:02 2002 qrunner(31161): h = HyperArch.HyperArchive(self) May 21 10:20:02 2002 qrunner(31161): AttributeError: 'Mailman.Archiver.HyperArch' module has no attribute 'HyperArchive' May 21 10:20:02 2002 (31161) CORRUPT ARCHIVE FOR LIST: ultimate May 21 10:22:01 2002 qrunner(31203): Traceback (most recent call last): May 21 10:22:01 2002 qrunner(31203): File "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail May 21 10:22:01 2002 qrunner(31203): import HyperArch May 21 10:22:01 2002 qrunner(31203): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? May 21 10:22:01 2002 qrunner(31203): from Mailman import EncWord May 21 10:22:01 2002 qrunner(31203): File "/home/mailman/Mailman/EncWord.py", line 21, in ? May 21 10:22:01 2002 qrunner(31203): import base64 May 21 10:22:01 2002 qrunner(31203): File "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? May 21 10:22:01 2002 qrunner(31203): import binascii May 21 10:22:01 2002 qrunner(31203): ImportError: No module named binascii May 21 10:22:01 2002 (31203) CORRUPT ARCHIVE FOR LIST: korymail May 21 10:28:01 2002 qrunner(31258): Traceback (most recent call last): May 21 10:28:01 2002 qrunner(31258): File "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail May 21 10:28:01 2002 qrunner(31258): import HyperArch May 21 10:28:01 2002 qrunner(31258): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? May 21 10:28:01 2002 qrunner(31258): from Mailman import EncWord May 21 10:28:01 2002 qrunner(31258): File "/home/mailman/Mailman/EncWord.py", line 21, in ? May 21 10:28:01 2002 qrunner(31258): import base64 May 21 10:28:01 2002 qrunner(31258): File "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? May 21 10:28:01 2002 qrunner(31258): import binascii May 21 10:28:01 2002 qrunner(31258): ImportError: No module named binascii May 21 10:28:01 2002 (31258) CORRUPT ARCHIVE FOR LIST: ccaus May 21 10:34:00 2002 qrunner(31303): Traceback (most recent call last): May 21 10:34:00 2002 qrunner(31303): File "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail May 21 10:34:01 2002 qrunner(31303): import HyperArch May 21 10:34:01 2002 qrunner(31303): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? May 21 10:34:01 2002 qrunner(31303): from Mailman import EncWord May 21 10:34:01 2002 qrunner(31303): File "/home/mailman/Mailman/EncWord.py", line 21, in ? May 21 10:34:01 2002 qrunner(31303): import base64 May 21 10:34:01 2002 qrunner(31303): File "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? May 21 10:34:01 2002 qrunner(31303): import binascii May 21 10:34:01 2002 qrunner(31303): ImportError: No module named binascii 3:26:01 2002 qrunner(32122): Traceback (most recent call last): May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/cron/qrunner", line 283, in ? May 21 13:26:01 2002 qrunner(32122): kids = main(lock) May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/cron/qrunner", line 253, in main May 21 13:26:01 2002 qrunner(32122): keepqueued = dispose_message(mlist, msg, msgdata) May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/cron/qrunner", line 121, in dispose_message May 21 13:26:01 2002 qrunner(32122): if BouncerAPI.ScanMessages(mlist, mimemsg): May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 57, in ScanMessages May 21 13:26:01 2002 qrunner(32122): mod = __import__('Mailman.Bouncers.'+modname) May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/Mailman/Bouncers/Catchall.py", line 34, in ? May 21 13:26:01 2002 qrunner(32122): import regsub May 21 13:26:01 2002 qrunner(32122): File "/usr/lib/python2.1/regsub.py", line 20, in ? May 21 13:26:01 2002 qrunner(32122): import regex May 21 13:26:01 2002 qrunner(32122): ImportError : No module named regex Kory Wheatley Idaho State University From marc_news@vasoftware.com Wed May 22 07:14:59 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Tue, 21 May 2002 23:14:59 -0700 Subject: [Mailman-Developers] confirmation strings don't seem to work with mm 2.1b2+ Message-ID: <20020522061253.GB865@merlins.org> I'm using a CVS tree updated last week. I got this mail (because my spamassassin is boucing the mails, and the list mostly gets spams). No big deal, except that the URL tells me the confirmation string is incorrect and even if I re-enter it in the "Otherwise, re-enter your confirmation string." page, it still doesn't work. What can I do to help debug this/provide more info? ----- Forwarded message from web-team-request@svlug.org ----- From: web-team-request@svlug.org To: merlin@svlug.org X-List-Administrivia: yes Subject: confirm 834fdd960d02e8e77409e82c626b698f96fb434a X-Spam-Status: No, hits=0.6 required=7.0 tests=NO_REAL_NAME version=2.20 X-Spam-Level: Your membership in the mailing list web-team has been disabled due to excessive bounces. You will not get any more messages from this list until you re-enable your membership. You will receive 3 more reminders like this before your membership in the list is deleted. To re-enable your membership, you can simply respond to this message (leaving the Subject: line intact), or visit the confirmation page at http://lists.svlug.org/lists/confirm/web-team/834fdd960d02e8e77409e82c626b698f96fb434a You can also visit your membership page at http://lists.svlug.org/lists/options/web-team/merlin%40svlug.org (...) ----- End forwarded message ----- -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From noreply@sourceforge.net Wed May 22 16:40:17 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 22 May 2002 08:40:17 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558633 ] Blocked queue after fight with Majordomo Message-ID: Bugs item #558633, was opened at 2002-05-21 13:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Nigel Metheringham (nigel) Assigned to: Nobody/Anonymous (nobody) Summary: Blocked queue after fight with Majordomo Initial Comment: On Mailman 2.0.8 (was honestly going to upgrade today!). It appears that a couple of messages were boucing between the mailman request addresses and a Majordomo server, with more error transcript being added to the message on each bounce. This then appeared to completely block the qrunner. Removing the 2 huge messages from the qfiles directory fixed it. Broken message qfiles attached. ---------------------------------------------------------------------- Comment By: Donal Hunt (redgiant) Date: 2002-05-22 16:40 Message: Logged In: YES user_id=551025 It actually gets worse! I finally figured out what has been crashing my machine for the past few days... and it's related to this bug i think. To reproduce: Create a moderated mailing list. eg test@hostanme.com Send a mail from your mailman user (eg su to mailman id and type: echo "test" | mail -s "test" test@hostname.com (where test@hostname.com is your moderated mailing list)) The mail gets sent to the mailing list and held for approval (mailman@hostname.com isn't a subscriber). A message gets sent back to mailman@hostname.com saying the message is held for approval (which mailman tries to post to the mailman list). At this stage stuff starts to stop working on the machine (smtp, telnet and syslogd mainly). What I've got from stracing syslogd (I originally thought it was a syslogd problem) and a mail from root are below: The thing is not that mailman is going to be sending mails to lists locally, but more someone could spoof a mail and DOS your machine. not nice!!! From what I've seen (evidence below) - there isn't a fight between the two lists 0 but i may be wrong. Quick fix: set "respond_to_post_requests" to No. System info: Suse Linux 7.0, Syslogd 1.3-3, Mailman 2.1b (cvs - may 9th) If this has been fixed already or is a seperate bug I apologise in advance for the long comment. ----------------------------------------------------------------------------------------------- : Command died with status 1: "/usr/local/mailman/mail/wrapper post mailman" Reporting-MTA: dns; hostname.dcu.ie Arrival-Date: Wed, 22 May 2002 16:02:45 +0100 (IST) Final-Recipient: rfc822; mailman@hostname.dcu.ie Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; Command died with status 1: "/usr/local/mailman/mail/wrapper post mailman" Received: from hostname.dcu.ie (localhost [127.0.0.1]) by hostname.dcu.ie (Postfix) with ESMTP id DB02D5DFEA for ; Wed, 22 May 2002 16:02:45 +0100 (IST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Your message to Test2 awaits moderator approval From: test2-bounces@hostname.dcu.ie To: mailman@hostname.dcu.ie Message-ID: Date: Wed, 22 May 2002 16:02:44 +0100 X-BeenThere: test2@hostname.dcu.ie X-Mailman-Version: 2.1b2+ Precedence: bulk List-Id: X-List-Administrivia: yes Sender: test2-bounces@hostname.dcu.ie Errors-To: test2-bounces@hostname.dcu.ie ----------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------- writev(1, [{"May 22 02:36:40", 15}, {" ", 1}, {"hostname", 7}, {" ", 1}, {"local[6728]: fatal: execvp /usr/"..., 85}, {"\r\n", 2}], 6) = ?ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) --- time(NULL) = 1022032087 rt_sigaction(SIGALRM, {0x405304, [], SA_RESTART}, {0x405304, [], SA_RESTART}, 8) = 0 alarm(30) = 0 sigreturn() = ? (mask now []) writev(1, [{"May 22 02:36:40", 15}, {" ", 1}, {"hostname", 7}, {" ", 1},{"local[6728]: fatal: execvp /usr/"..., 85}, {"\r\n", 2}], 6) = ?ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) --- time(NULL) = 1022032117 rt_sigaction(SIGALRM, {0x405304, [], SA_RESTART}, {0x405304, [],SA_RESTART}, 8) = 0 alarm(30) = 0 sigreturn() = ? (mask now []) writev(1, [{"May 22 02:36:40", 15}, {" ", 1}, {"linux28", 7}, {" ", 1}, {"local[6728]: fatal: execvp /usr/"..., 85}, {"\r\n", 2}], 6 <200205212213.g4LMD8a01244@quill.local> Message-ID: <20020522132253.16048@scfn.thpl.lib.fl.us> I seem to have managed to get CVS installed and running (and finally ironed out my DNS issues), but for some reason, my installation thinks it has no name: invitation messages come from "MAILER-DAEMON" with no domain, and the List headers are for "test1@" Defaults.py *has* a default email host and URL host... but they didn't get picked up on the build for some reason; I had to key them in manually. Is there somewhere else they are? Do I have to reinstall *again*? I'm losing my hair here... Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") From claw@kanga.nu Wed May 22 19:11:39 2002 From: claw@kanga.nu (J C Lawrence) Date: Wed, 22 May 2002 11:11:39 -0700 Subject: [Mailman-Developers] Another stupid question In-Reply-To: Message from "Jay R. Ashworth" of "Wed, 22 May 2002 13:22:53 EDT." <20020522132253.16048@scfn.thpl.lib.fl.us> References: <200205212213.g4LMD8a01244@quill.local> <20020522132253.16048@scfn.thpl.lib.fl.us> Message-ID: <32385.1022091099@kanga.nu> On Wed, 22 May 2002 13:22:53 -0400 Jay R Ashworth wrote: > I seem to have managed to get CVS installed and running (and finally > ironed out my DNS issues), but for some reason, my installation thinks > it has no name: invitation messages come from "MAILER-DAEMON" with no > domain, and the List headers are for "test1@" Odds are good this is an MTA config problem. Send mail from both the CLI (`mail`) and telnetting to localhost. See what default host is given on From: etc and then fix as appropriate. Make sure you try with unqualified addresses (ie UID only), with partially qualified domains, and FQDNs to see the exact behaviour. > Do I have to reinstall *again*? Almost certainly not. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From jra@baylink.com Wed May 22 20:02:31 2002 From: jra@baylink.com (Jay R. Ashworth) Date: Wed, 22 May 2002 15:02:31 -0400 Subject: [Mailman-Developers] Another stupid question In-Reply-To: <32385.1022091099@kanga.nu>; from J C Lawrence on Wed, May 22, 2002 at 11:11:39AM -0700 References: <200205212213.g4LMD8a01244@quill.local> <20020522132253.16048@scfn.thpl.lib.fl.us> <32385.1022091099@kanga.nu> Message-ID: <20020522150231.37782@scfn.thpl.lib.fl.us> On Wed, May 22, 2002 at 11:11:39AM -0700, J C Lawrence wrote: > On Wed, 22 May 2002 13:22:53 -0400 > Jay R Ashworth wrote: > > I seem to have managed to get CVS installed and running (and finally > > ironed out my DNS issues), but for some reason, my installation thinks > > it has no name: invitation messages come from "MAILER-DAEMON" with no > > domain, and the List headers are for "test1@" > > Odds are good this is an MTA config problem. Send mail from both the > CLI (`mail`) and telnetting to localhost. See what default host is > given on From: etc and then fix as appropriate. Make sure you try with > unqualified addresses (ie UID only), with partially qualified domains, > and FQDNs to see the exact behaviour. It would appear not. Sending mail from the Mailman machine using mutt sends messages with the headers just as they might be expected to be. It appears that mailman doesn't know it's name... Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") From claw@kanga.nu Wed May 22 20:53:24 2002 From: claw@kanga.nu (J C Lawrence) Date: Wed, 22 May 2002 12:53:24 -0700 Subject: [Mailman-Developers] Another stupid question In-Reply-To: Message from "Jay R. Ashworth" of "Wed, 22 May 2002 15:02:31 EDT." <20020522150231.37782@scfn.thpl.lib.fl.us> References: <200205212213.g4LMD8a01244@quill.local> <20020522132253.16048@scfn.thpl.lib.fl.us> <32385.1022091099@kanga.nu> <20020522150231.37782@scfn.thpl.lib.fl.us> Message-ID: <2252.1022097204@kanga.nu> On Wed, 22 May 2002 15:02:31 -0400 Jay R Ashworth wrote: > On Wed, May 22, 2002 at 11:11:39AM -0700, J C Lawrence wrote: >> On Wed, 22 May 2002 13:22:53 -0400 Jay R Ashworth >> wrote: > It would appear not. Sending mail from the Mailman machine using mutt > sends messages with the headers just as they might be expected to be. Which demonstrates nothing except that you have mutt well configured. Do the tests I outlined and it will reveal how your MTA handles unqualified and fully qualified From: headers. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From noreply@sourceforge.net Thu May 23 00:51:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 22 May 2002 16:51:18 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558909 ] Auto-responsder doesn't send response. Message-ID: Bugs item #558909, was opened at 2002-05-21 18:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558909&group_id=103 Category: mail delivery Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Donal Hunt (redgiant) Assigned to: Nobody/Anonymous (nobody) Summary: Auto-responsder doesn't send response. Initial Comment: Auto-response mail never gets sent on -admin and -owner addresses. Set the autorespond_admin and autorespond_admin_text properties on the auto-responder page of the admin page for the list. Sending mail to either -admin@host or -owner@host results in the admin receiving the email but no auto-response is sent to the sender. Found on Mailman CVS (May 9th). Up to my eyes at present so haven't got a chance to dig deeper yet. Will do so middle of next week if needed. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-22 19:51 Message: Logged In: YES user_id=12800 Fixed in cvs. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558909&group_id=103 From noreply@sourceforge.net Thu May 23 00:56:46 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 22 May 2002 16:56:46 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-559417 ] "arch" utility spews output Message-ID: Bugs item #559417, was opened at 2002-05-22 16:56 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559417&group_id=103 Category: Pipermail Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Ian Clarke (sanity) Assigned to: Nobody/Anonymous (nobody) Summary: "arch" utility spews output Initial Comment: When I run the "arch" utility to rebuild my archives, it prints out loads of "figuring article archives", which is somewhat confusing to the new user. Would it be possible to have a more sensible status report so that people aren't confused when they rebuild a large archive? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559417&group_id=103 From noreply@sourceforge.net Thu May 23 03:08:24 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 22 May 2002 19:08:24 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558988 ] bad performance for big queue dirs Message-ID: Bugs item #558988, was opened at 2002-05-21 23:15 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558988&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Norbert Bollow (bollow) Assigned to: Nobody/Anonymous (nobody) Summary: bad performance for big queue dirs Initial Comment: Many filesystems (e.g. the popular ext2) have horrible performance when there are many files in the same directory. The queue system should be modified to avoid this situation. As a test case, try adding 20,000 test address in such a way that Mailman will try to send a welcome message to each of them. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-22 22:08 Message: Logged In: YES user_id=12800 I think you have a valid complaint, but I'm loathe to change something so fundamental this late in the game. I'll leave this bug report open because if we can recommend some other, more big queue friendly filesystem (reiserfs? I don't know) then we should document this. Don't MTAs have the same problem? Do they all implement multiple subdirectories for queued messages? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558988&group_id=103 From barry@zope.com Thu May 23 03:27:58 2002 From: barry@zope.com (Barry A. Warsaw) Date: Wed, 22 May 2002 22:27:58 -0400 Subject: [Mailman-Developers] Another stupid question References: <200205212213.g4LMD8a01244@quill.local> <20020522132253.16048@scfn.thpl.lib.fl.us> Message-ID: <15596.21422.676846.100564@anthem.wooz.org> >>>>> "JRA" == Jay R Ashworth writes: JRA> Defaults.py *has* a default email host and URL host... but JRA> they didn't get picked up on the build for some reason; I had JRA> to key them in manually. Is there somewhere else they are? Did you key those in /after/ you created your test list? If so, and if DEFAULT_EMAIL_HOST was the empty string at the time you created your list, then I can see how your list's host_name attribute would be the empty string. Remember that changing DEFAULT_EMAIL_HOST after the fact doesn't update your list configs. So, you need to fix host_name (and probably web_page_url). Only the former can be changed on the General admin page. Both of course can be changed via withlist. Both DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST are calculated by configure, so look at your configure output to see if it got the right values or not. If not, then you need to look seriously at your DNS setup, or your Python installation. socket.getfqdn() better return the fully qualified domain name for your machine, or you've got problems, but they ain't in Mailman. JRA> Do I have to reinstall *again*? You should almost /never/ have to completely reinstall. At worst you might have to re-run configure and "make install", and perhaps do a little fixup with withlist (if your configure screwed up and you didn't catch it until your created some lists). JRA> I'm losing my hair here... i-think-i'm-going-bald-ly y'rs, -Barry From jra@baylink.com Thu May 23 04:21:17 2002 From: jra@baylink.com (Jay R. Ashworth) Date: Wed, 22 May 2002 23:21:17 -0400 Subject: [Mailman-Developers] Another stupid question In-Reply-To: <15596.21422.676846.100564@anthem.wooz.org>; from "Barry A. Warsaw" on Wed, May 22, 2002 at 10:27:58PM -0400 References: <200205212213.g4LMD8a01244@quill.local> <20020522132253.16048@scfn.thpl.lib.fl.us> <15596.21422.676846.100564@anthem.wooz.org> Message-ID: <20020522232117.65350@scfn.thpl.lib.fl.us> On Wed, May 22, 2002 at 10:27:58PM -0400, Barry A. Warsaw wrote: > >>>>> "JRA" == Jay R Ashworth writes: > JRA> Defaults.py *has* a default email host and URL host... but > JRA> they didn't get picked up on the build for some reason; I had > JRA> to key them in manually. Is there somewhere else they are? > > Did you key those in /after/ you created your test list? If so, and > if DEFAULT_EMAIL_HOST was the empty string at the time you created > your list, then I can see how your list's host_name attribute would be > the empty string. Remember that changing DEFAULT_EMAIL_HOST after the > fact doesn't update your list configs. Can't remember it if I don't know it. Thanks. > So, you need to fix host_name (and probably web_page_url). Only the > former can be changed on the General admin page. Both of course can > be changed via withlist. Or I can remove the list and reinstantiate it, right? > Both DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST are calculated by > configure, so look at your configure output to see if it got the right > values or not. If not, then you need to look seriously at your DNS > setup, or your Python installation. socket.getfqdn() better return > the fully qualified domain name for your machine, or you've got > problems, but they ain't in Mailman. They came up empty. Hostname had been set to a name with an underscore in it, which didn't DNS. > JRA> Do I have to reinstall *again*? > > You should almost /never/ have to completely reinstall. At worst you > might have to re-run configure and "make install", and perhaps do a > little fixup with withlist (if your configure screwed up and you > didn't catch it until your created some lists). Nah; it'll be easier to reinstall. No real lists yet. > JRA> I'm losing my hair here... > > i-think-i'm-going-bald-ly y'rs, Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") From barry@zope.com Thu May 23 04:33:16 2002 From: barry@zope.com (Barry A. Warsaw) Date: Wed, 22 May 2002 23:33:16 -0400 Subject: [Mailman-Developers] Another stupid question References: <200205212213.g4LMD8a01244@quill.local> <20020522132253.16048@scfn.thpl.lib.fl.us> <15596.21422.676846.100564@anthem.wooz.org> <20020522232117.65350@scfn.thpl.lib.fl.us> Message-ID: <15596.25340.94700.118624@anthem.wooz.org> >>>>> "JRA" == Jay R Ashworth writes: JRA> Can't remember it if I don't know it. Thanks. Ah cool. It's an important point that should go in the site admin document . >> So, you need to fix host_name (and probably web_page_url). >> Only the former can be changed on the General admin page. Both >> of course can be changed via withlist. JRA> Or I can remove the list and reinstantiate it, right? Yup, if you've got nothing important in the list. JRA> They came up empty. Hostname had been set to a name with an JRA> underscore in it, which didn't DNS. Ah, okay. JRA> Nah; it'll be easier to reinstall. JRA> No real lists yet. Just fix mm_cfg.py and blow away the list. You should be good then. >> JRA> I'm losing my hair here... >> i-think-i'm-going-bald-ly y'rs, JRA> :) -Barry From jwblist@olympus.net Thu May 23 05:35:43 2002 From: jwblist@olympus.net (John W Baxter) Date: Wed, 22 May 2002 21:35:43 -0700 Subject: [Mailman-Developers] Another stupid question In-Reply-To: <20020522232117.65350@scfn.thpl.lib.fl.us> References: <200205212213.g4LMD8a01244@quill.local> <20020522132253.16048@scfn.thpl.lib.fl.us> <15596.21422.676846.100564@anthem.wooz.org> <20020522232117.65350@scfn.thpl.lib.fl.us> Message-ID: At 23:21 -0400 5/22/2002, Jay R. Ashworth wrote: >On Wed, May 22, 2002 at 10:27:58PM -0400, Barry A. Warsaw wrote: ... >> So, you need to fix host_name (and probably web_page_url). Only the >> former can be changed on the General admin page. Both of course can >> be changed via withlist. > >Or I can remove the list and reinstantiate it, right? Yes, but if you are at the stage of the list's lifetime when that is appropriate, then it would seem that this list is a good one on which to practice using bin/withlist. Unless you're already comfortable with it. --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA From wheakory@isu.edu Thu May 23 07:52:56 2002 From: wheakory@isu.edu (Kory Wheatley) Date: Thu, 23 May 2002 00:52:56 -0600 Subject: [Mailman-Developers] Python and Mailman problem Message-ID: <3CEC91C8.F9173162@isu.edu> Critical trying to run Python 2.1 on my production mailman 2.0.11 Univeristy Mailing Lists. I had to revert back to Python1.5.2 Does Python 2.1 work with Mailman 2.0.11. Details & and error messages below. Does anyone know the solution of this problem below? I've install mailman 2.0.11 on Red Hat 7.2 and it was working fine until I upgrade to Python 2.1. Once I upgraded to this version everything seemed fine for 5 hours. I was able to receive messages from my mailing lists at our University. The Web Interface administrator options for the lists all worked fine. Then messages started piling in "qfiles" and it would not send anymore messages out. I moved them out of the queue and started moving them back in one at a time and then again the messages seemed to be sent properly, but then they started piling back up in the qfiles directory again . Here is the errors I received in the "error" logfile. I'm not totally efficient on Python yet, so I would like some help I would appreciate it. (Quite a few messages on CORRUPTED ARCHIVES and module regex not found) ERROR LOG FILE May 21 10:20:01 2002 (31161) CORRUPT ARCHIVE FOR LIST: libstaff May 21 10:20:02 2002 qrunner(31161): Traceback (most recent call last): May 21 10:20:02 2002 qrunner(31161): File "/home/mailman/Mailman/Archiver/Archiver.py", line 220, in ArchiveMail May 21 10:20:02 2002 qrunner(31161): h = HyperArch.HyperArchive(self) May 21 10:20:02 2002 qrunner(31161): AttributeError: 'Mailman.Archiver.HyperArch' module has no attribute 'HyperArchive' May 21 10:20:02 2002 (31161) CORRUPT ARCHIVE FOR LIST: relief May 21 10:20:02 2002 qrunner(31161): Traceback (most recent call last): May 21 10:20:02 2002 qrunner(31161): File "/home/mailman/Mailman/Archiver/Archiver.py", line 220, in ArchiveMail May 21 10:20:02 2002 qrunner(31161): h = HyperArch.HyperArchive(self) May 21 10:20:02 2002 qrunner(31161): AttributeError: 'Mailman.Archiver.HyperArch' module has no attribute 'HyperArchive' May 21 10:20:02 2002 (31161) CORRUPT ARCHIVE FOR LIST: ultimate May 21 10:22:01 2002 qrunner(31203): Traceback (most recent call last): May 21 10:22:01 2002 qrunner(31203): File "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail May 21 10:22:01 2002 qrunner(31203): import HyperArch May 21 10:22:01 2002 qrunner(31203): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? May 21 10:22:01 2002 qrunner(31203): from Mailman import EncWord May 21 10:22:01 2002 qrunner(31203): File "/home/mailman/Mailman/EncWord.py", line 21, in ? May 21 10:22:01 2002 qrunner(31203): import base64 May 21 10:22:01 2002 qrunner(31203): File "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? May 21 10:22:01 2002 qrunner(31203): import binascii May 21 10:22:01 2002 qrunner(31203): ImportError: No module named binascii May 21 10:22:01 2002 (31203) CORRUPT ARCHIVE FOR LIST: korymail May 21 10:28:01 2002 qrunner(31258): Traceback (most recent call last): May 21 10:28:01 2002 qrunner(31258): File "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail May 21 10:28:01 2002 qrunner(31258): import HyperArch May 21 10:28:01 2002 qrunner(31258): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? May 21 10:28:01 2002 qrunner(31258): from Mailman import EncWord May 21 10:28:01 2002 qrunner(31258): File "/home/mailman/Mailman/EncWord.py", line 21, in ? May 21 10:28:01 2002 qrunner(31258): import base64 May 21 10:28:01 2002 qrunner(31258): File "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? May 21 10:28:01 2002 qrunner(31258): import binascii May 21 10:28:01 2002 qrunner(31258): ImportError: No module named binascii 3:26:01 2002 qrunner(32122): Traceback (most recent call last): May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/cron/qrunner", line 283, in ? May 21 13:26:01 2002 qrunner(32122): kids = main(lock) May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/cron/qrunner", line 253, in main May 21 13:26:01 2002 qrunner(32122): keepqueued = dispose_message(mlist, msg, msgdata) May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/cron/qrunner", line 121, in dispose_message May 21 13:26:01 2002 qrunner(32122): if BouncerAPI.ScanMessages(mlist, mimemsg): May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 57, in ScanMessages May 21 13:26:01 2002 qrunner(32122): mod = __import__('Mailman.Bouncers.'+modname) May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/Mailman/Bouncers/Catchall.py", line 34, in ? May 21 13:26:01 2002 qrunner(32122): import regsub May 21 13:26:01 2002 qrunner(32122): File "/usr/lib/python2.1/regsub.py", line 20, in ? May 21 13:26:01 2002 qrunner(32122): import regex May 21 13:26:01 2002 qrunner(32122): ImportError : No module named regex Kory Wheatley Idaho State University From noreply@sourceforge.net Thu May 23 10:50:08 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 23 May 2002 02:50:08 -0700 Subject: [Mailman-Developers] [ mailman-Patches-444879 ] Archive indexer control to improve index Message-ID: Patches item #444879, was opened at 2001-07-26 18:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Archive indexer control to improve index Initial Comment: This patch is applicable to Mailman 2.0.6 release and supercedes ealier patches 401669 and 402422. This patch should improve the quality of search results returned by search engines such as htdig (http://www.htdig.org) where the seach engine's index builder responds to strings embedded in the html pages that are the subject of the indexing. The changes in this patch: 1. allow strings for enabling and disabling indexing to be defined in mm_cfg.py. 2. embeds those strings in the pages generated as the html version of a list's archive. By default nothing in the html changes. To get the desired effect, you must define ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in mm_cfg.py You probably want to run this patch as follows: cd patch -p1 < See also the associated patch for integrating the htdig search software with mailman's internal archiver ouput. ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:50 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:53 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch should apply without problems to MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:43 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:14 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002. Corrects problem noted or 5 Mar 2002 by nobody ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-05 21:41 Message: Logged In: NO When applying this patch I get an error with Hunk 1 and Defaults.py is not updated. This happens with the a clean download of the latest cvs installation (5 Mar 2002). Any ideas what the problem is? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:53 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:48 Message: Logged In: YES user_id=75166 indexing-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:07 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:03 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.7 ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 From noreply@sourceforge.net Thu May 23 10:59:58 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 23 May 2002 02:59:58 -0700 Subject: [Mailman-Developers] [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Integration of Mailman & htdig for archi Initial Comment: This patch is applicable to Mailman 2.0.6 release that has had search enhancement patch 444879 patch installed - if your Defaults.py has the ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in it then you've got that patch. It replaces earlier patches 401670 and 402423 and is mainly to correct some problems arising from fixes introduced into Mailman by bug fix releases since the 402423 patch. This patch integrates htdig with Mailman and provides: 1. per list search facility with a search form on the list's TOC page. 2. maintenance of privacy of private archives which requires the user to establish their credentials via the normal private archive access before any access via htdig is allowed. 3. a common base URL for both public and private archive access via htsearch results so that htdig indices are unaffected by changingan archive from private to public and vice versa. All access to archives via htdig is controlled by a new wrapped cgi- bin script called htdig.py. 4. a new cron activated script and extra crontab entry which runs htdig regularly to maintain the per list search indices. 5. automatic creation, deletion and maintenance of htdig configuration files and such. Beyond installing htdig and telling Mailman where it is via mm_cfg you do not have to do any other setup. Well not quite you do have to set up a single per installation symlink to allow htdig to find the automatically generated per list htdig configuration files. You probably want to run this patch as follows: cd patch -p1 < ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:59 Message: Logged In: YES user_id=75166 htdig-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 This version removes an incompatibility with Python 2.2 which caused warning messages to be generated when any of the family cron/nightly_htdig scripts were run. Some guidance on file access permissions for some htdig database files needed by rundig have been added to installation notes. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:59 Message: Logged In: YES user_id=75166 htdig-2.0.10-0.1.patch is a revised version of the patch that is compatible with MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:46 Message: Logged In: YES user_id=75166 htdig-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:22 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002 Known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:56 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:58 Message: Logged In: YES user_id=75166 htdig-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 17:33 Message: Logged In: YES user_id=75166 The htdig-2.0.8-0.1.patch version of the patch resolves a problem that can arise with htdig indexing if the web_page_url for a list uses other than the http addressing (some folks want to use https). While specified as for MM 2.0.8 the revised patch should work OK with 2.0.7, 2.0.6 and probably back as far as 2.0.3. If you do not have the requirement for using other than http addressing in you lists web_page_urls it probably isn't worth the trouble of upgrading to this patch level. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:08 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:00 Message: Logged In: YES user_id=75166 This patch should also apply without problems to Mm 2.0.7 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-09 11:54 Message: Logged In: YES user_id=75166 The htdig-2.0.6-03.patch version of the patch makes some previously hard-coded things configurable and enhances the capability to run the htdig searches and indexing on a different machine to the one delivering Mailman and Mailman's web UI. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 From noreply@sourceforge.net Thu May 23 11:16:52 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 23 May 2002 03:16:52 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-559558 ] can't make moderated list unmoderated Message-ID: Bugs item #559558, was opened at 2002-05-23 10:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559558&group_id=103 Category: security/privacy Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Benjamin Geer (beroul) Assigned to: Nobody/Anonymous (nobody) Summary: can't make moderated list unmoderated Initial Comment: With Mailman 2.0.8, I made a list moderated (by setting "Must posts be approved by an administrator?" in Privacy Options) to "Yes". A few weeks later, I changed my mind and set this to "No". However, whenever someone tries to post to the list, I still receive a message from Mailman, saying that the posting requires approval (the subject line says "Posting to a restricted list by sender requires approval"). ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559558&group_id=103 From webmaster@isu.edu Wed May 22 23:48:21 2002 From: webmaster@isu.edu (Webmaster) Date: Wed, 22 May 2002 16:48:21 -0600 Subject: [Mailman-Developers] Python Upgrade problem with mailman Message-ID: <3CEC2035.4DF7A459@isu.edu> Very critical does anyone know if Pytnon 2.1 will work with mailman 2.0.11, (problems with my production mailing lists) Explanation below: I've install mailman 2.0.11 on Red Hat 7.2 and it was working fine until I upgrade to Python 2.1. Once I upgraded to this version everything seemed fine for 5 hours. I was able to receive messages from my mailing lists at our University. The Web Interface administrator options for the lists all worked fine. Then messages started piling in "qfiles" and it would not send anymore messages out. I moved them out of the queue and started moving them back in one at a time and then again the messages seemed to be sent properly, but then they started piling back up in the qfiles directory again . Here is the errors I received in the "error" logfile. I'm not totally efficient on Python yet, so I would like some help I would appreciate it. (Quite a few messages on CORRUPTED ARCHIVES and module regex not found) ERROR LOG FILE > May 21 10:20:01 2002 qrunner(31161): Traceback (most recent call last): > May 21 10:20:01 2002 qrunner(31161): File > "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail > May 21 10:20:01 2002 qrunner(31161): import HyperArch > May 21 10:20:01 2002 qrunner(31161): File > "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? > May 21 10:20:01 2002 qrunner(31161): from Mailman import EncWord > May 21 10:20:01 2002 qrunner(31161): File > "/home/mailman/Mailman/EncWord.py", line 21, in ? > May 21 10:20:01 2002 qrunner(31161): import base64 > May 21 10:20:01 2002 qrunner(31161): File > "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? > May 21 10:20:01 2002 qrunner(31161): import binascii > May 21 10:20:01 2002 qrunner(31161): ImportError: No module named > binascii > May 21 10:20:01 2002 (31161) CORRUPT ARCHIVE FOR LIST: libstaff > May 21 10:20:02 2002 qrunner(31161): Traceback (most recent call last): > May 21 10:20:02 2002 qrunner(31161): File > "/home/mailman/Mailman/Archiver/Archiver.py", line 220, in ArchiveMail > May 21 10:20:02 2002 qrunner(31161): h = > HyperArch.HyperArchive(self) > May 21 10:20:02 2002 qrunner(31161): AttributeError: > 'Mailman.Archiver.HyperArch' module has no attribute 'HyperArchive' > May 21 10:20:02 2002 (31161) CORRUPT ARCHIVE FOR LIST: relief > May 21 10:20:02 2002 qrunner(31161): Traceback (most recent call last): > May 21 10:20:02 2002 qrunner(31161): File > "/home/mailman/Mailman/Archiver/Archiver.py", line 220, in ArchiveMail > May 21 10:20:02 2002 qrunner(31161): h = > HyperArch.HyperArchive(self) > May 21 10:20:02 2002 qrunner(31161): AttributeError: > 'Mailman.Archiver.HyperArch' module has no attribute 'HyperArchive' > May 21 10:20:02 2002 (31161) CORRUPT ARCHIVE FOR LIST: ultimate > May 21 10:22:01 2002 qrunner(31203): Traceback (most recent call last): > May 21 10:22:01 2002 qrunner(31203): File > "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail > May 21 10:22:01 2002 qrunner(31203): import HyperArch > May 21 10:22:01 2002 qrunner(31203): File > "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? > May 21 10:22:01 2002 qrunner(31203): from Mailman import EncWord > May 21 10:22:01 2002 qrunner(31203): File > "/home/mailman/Mailman/EncWord.py", line 21, in ? > May 21 10:22:01 2002 qrunner(31203): import base64 > May 21 10:22:01 2002 qrunner(31203): File > "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? > May 21 10:22:01 2002 qrunner(31203): import binascii > May 21 10:22:01 2002 qrunner(31203): ImportError: No module named > binascii > 3:26:01 2002 qrunner(32122): Traceback (most recent call last): > May 21 13:26:01 2002 qrunner(32122): File > "/home/mailman/cron/qrunner", line 283, in ? > May 21 13:26:01 2002 qrunner(32122): kids = main(lock) > May 21 13:26:01 2002 qrunner(32122): File > "/home/mailman/cron/qrunner", line 253, in main > May 21 13:26:01 2002 qrunner(32122): keepqueued = > dispose_message(mlist, msg, msgdata) > May 21 13:26:01 2002 qrunner(32122): File > "/home/mailman/cron/qrunner", line 121, in dispose_message > May 21 13:26:01 2002 qrunner(32122): if > BouncerAPI.ScanMessages(mlist, mimemsg): > May 21 13:26:01 2002 qrunner(32122): File > "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 57, in ScanMessages > > May 21 13:26:01 2002 qrunner(32122): mod = > __import__('Mailman.Bouncers.'+modname) > May 21 13:26:01 2002 qrunner(32122): File > "/home/mailman/Mailman/Bouncers/Catchall.py", line 34, in ? > May 21 13:26:01 2002 qrunner(32122): import regsub > May 21 13:26:01 2002 qrunner(32122): File > "/usr/lib/python2.1/regsub.py", line 20, in ? > May 21 13:26:01 2002 qrunner(32122): import regex > May 21 13:26:01 2002 qrunner(32122): ImportError : No module named > regex -- ################################################## Webmaster Idaho State University Computing & Communications webmaster@isu.edu ################################################## From Nigel.Metheringham@dev.InTechnology.co.uk Thu May 23 09:33:53 2002 From: Nigel.Metheringham@dev.InTechnology.co.uk (Nigel Metheringham) Date: 23 May 2002 09:33:53 +0100 Subject: [Mailman-Developers] [ mailman-Bugs-558988 ] bad performance for big queue dirs In-Reply-To: References: Message-ID: <1022142837.7936.9.camel@gaspode.localnet> > Many filesystems (e.g. the popular ext2) have horrible > performance when there are many files in the same > directory. The queue system should be modified to > avoid this situation. As a test case, try adding > 20,000 test address in such a way that Mailman will try > to send a welcome message to each of them. Isn't this optomising for a rather uncommon case. Typically the qfiles directory holds a couple of minutes of transactions plus messages awaiting moderation. [Actually that comment is somewhat Mailman 2.0.x centric although I think it will hold for later versions] > Don't MTAs have the same problem? Do they all implement > multiple subdirectories for queued messages? It is done in some MTAs - exim for example (as an option) - frankly for many cases the additional overhead of searching n directories outweighs the advantages of faster per message access *unless* you typically run huge queues (in which case there are other advantages like splitting the queue run). Nigel. -- [ Nigel Metheringham Nigel.Metheringham@InTechnology.co.uk ] [ - Comments in this message are my own and not ITO opinion/policy - ] From jra@baylink.com Thu May 23 15:52:08 2002 From: jra@baylink.com (Jay R. Ashworth) Date: Thu, 23 May 2002 10:52:08 -0400 Subject: [Mailman-Developers] Another stupid question In-Reply-To: <15596.25340.94700.118624@anthem.wooz.org>; from "Barry A. Warsaw" on Wed, May 22, 2002 at 11:33:16PM -0400 References: <200205212213.g4LMD8a01244@quill.local> <20020522132253.16048@scfn.thpl.lib.fl.us> <15596.21422.676846.100564@anthem.wooz.org> <20020522232117.65350@scfn.thpl.lib.fl.us> <15596.25340.94700.118624@anthem.wooz.org> Message-ID: <20020523105208.34783@scfn.thpl.lib.fl.us> On Wed, May 22, 2002 at 11:33:16PM -0400, Barry A. Warsaw wrote: > >>>>> "JRA" == Jay R Ashworth writes: > JRA> Can't remember it if I don't know it. Thanks. > > Ah cool. It's an important point that should go in the site admin > document . Yeah, yeah; just as soon as I rush the rush job that I'm rushing to rush now. Did you ever actually set up that list? > JRA> Or I can remove the list and reinstantiate it, right? > > Yup, if you've got nothing important in the list. Nope. > JRA> No real lists yet. > > Just fix mm_cfg.py and blow away the list. You should be good then. Cool. > >> JRA> I'm losing my hair here... > >> i-think-i'm-going-bald-ly y'rs, > > JRA> > > Cheers, - j -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") From barry@zope.com Thu May 23 16:02:11 2002 From: barry@zope.com (Barry A. Warsaw) Date: Thu, 23 May 2002 11:02:11 -0400 Subject: [Mailman-Developers] Another stupid question References: <200205212213.g4LMD8a01244@quill.local> <20020522132253.16048@scfn.thpl.lib.fl.us> <15596.21422.676846.100564@anthem.wooz.org> <20020522232117.65350@scfn.thpl.lib.fl.us> <15596.25340.94700.118624@anthem.wooz.org> <20020523105208.34783@scfn.thpl.lib.fl.us> Message-ID: <15597.1139.601956.607569@anthem.wooz.org> >>>>> "JRA" == Jay R Ashworth writes: JRA> Yeah, yeah; just as soon as I rush the rush job that I'm JRA> rushing to rush now. Did you ever actually set up that list? Now /that's/ the spirit! (of radio?) I actually did set the list up, but I haven't advertised it enough. I will try to get a wider announcement out about it asap. -Barry From jra@baylink.com Thu May 23 16:05:35 2002 From: jra@baylink.com (Jay R. Ashworth) Date: Thu, 23 May 2002 11:05:35 -0400 Subject: [Mailman-Developers] Another stupid question In-Reply-To: ; from John W Baxter on Wed, May 22, 2002 at 09:35:43PM -0700 References: <200205212213.g4LMD8a01244@quill.local> <20020522132253.16048@scfn.thpl.lib.fl.us> <15596.21422.676846.100564@anthem.wooz.org> <20020522232117.65350@scfn.thpl.lib.fl.us> Message-ID: <20020523110535.51128@scfn.thpl.lib.fl.us> On Wed, May 22, 2002 at 09:35:43PM -0700, John W Baxter wrote: > At 23:21 -0400 5/22/2002, Jay R. Ashworth wrote: > >On Wed, May 22, 2002 at 10:27:58PM -0400, Barry A. Warsaw wrote: > ... > >> So, you need to fix host_name (and probably web_page_url). Only the > >> former can be changed on the General admin page. Both of course can > >> be changed via withlist. > > > >Or I can remove the list and reinstantiate it, right? > > Yes, but if you are at the stage of the list's lifetime when that is > appropriate, then it would seem that this list is a good one on which to > practice using bin/withlist. Unless you're already comfortable with it. That's actaully an excellent point which both I and Barry missed. Thanks. Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") From jra@baylink.com Thu May 23 16:06:15 2002 From: jra@baylink.com (Jay R. Ashworth) Date: Thu, 23 May 2002 11:06:15 -0400 Subject: [Mailman-Developers] Another stupid question In-Reply-To: <15597.1139.601956.607569@anthem.wooz.org>; from "Barry A. Warsaw" on Thu, May 23, 2002 at 11:02:11AM -0400 References: <200205212213.g4LMD8a01244@quill.local> <20020522132253.16048@scfn.thpl.lib.fl.us> <15596.21422.676846.100564@anthem.wooz.org> <20020522232117.65350@scfn.thpl.lib.fl.us> <15596.25340.94700.118624@anthem.wooz.org> <20020523105208.34783@scfn.thpl.lib.fl.us> <15597.1139.601956.607569@anthem.wooz.org> Message-ID: <20020523110615.11693@scfn.thpl.lib.fl.us> On Thu, May 23, 2002 at 11:02:11AM -0400, Barry A. Warsaw wrote: > >>>>> "JRA" == Jay R Ashworth writes: > JRA> Yeah, yeah; just as soon as I rush the rush job that I'm > JRA> rushing to rush now. Did you ever actually set up that list? > > Now /that's/ the spirit! (of radio?) Telvision, in my case. > I actually did set the list up, but I haven't advertised it enough. I > will try to get a wider announcement out about it asap. Did you sign me on? -- j -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") From rcb@ucp.uchicago.edu Thu May 23 16:52:08 2002 From: rcb@ucp.uchicago.edu (Roy Bixler) Date: Thu, 23 May 2002 10:52:08 -0500 Subject: [Mailman-Developers] Python and Mailman problem In-Reply-To: <3CEC91C8.F9173162@isu.edu> References: <3CEC91C8.F9173162@isu.edu> Message-ID: <20020523155208.GA20316@ucp.uchicago.edu> On Thu, May 23, 2002 at 12:52:56AM -0600, Kory Wheatley wrote: > Critical trying to run Python 2.1 on my production mailman 2.0.11 > Univeristy Mailing Lists. I had to revert back to Python1.5.2 > Does Python 2.1 work with Mailman 2.0.11. I got it to work with Python 2.2.1 but this one was built from source on Solaris 8 and I remember having to uncomment a lot of modules at the Modules/Setup file before the build. Also, I needed to patch the Mailman/Bouncers/Catchall.py file because 'regex' didn't seem to be there to include (maybe I missed something but anyway I didn't think it worthwhile to figure out how to get 'regex' included if it's obsolete and only one module of Mailman needs it.) I posted the patch to the Mailman developers' list earlier this month but I can send it if you can't find it and are interested. R. From chuqui@plaidworks.com Thu May 23 16:53:55 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Thu, 23 May 2002 08:53:55 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558988 ] bad performance for big queue dirs In-Reply-To: <1022142837.7936.9.camel@gaspode.localnet> Message-ID: On 5/23/02 1:33 AM, "Nigel Metheringham" wrote: > Isn't this optomising for a rather uncommon case. Typically the qfiles > directory holds a couple of minutes of transactions plus messages > awaiting moderation. Not on a large site, no. But 2.1 changes the queueing enough that I'd put this on hold until we see if it's still a problem in 2.1. I certainly don't think it should be examined in 2.0.x, and we don't have any real info on whether 2.1 needs tweaking for really large/high-volume sites. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ No! No! Dead girl, OFF the table! -- Shrek From nb@thinkcoach.com Thu May 23 17:42:18 2002 From: nb@thinkcoach.com (Norbert Bollow) Date: Thu, 23 May 2002 18:42:18 +0200 Subject: [Mailman-Developers] [ mailman-Bugs-558988 ] bad performance for big queue dirs In-Reply-To: <1022142837.7936.9.camel@gaspode.localnet> (message from Nigel Metheringham on 23 May 2002 09:33:53 +0100) References: <1022142837.7936.9.camel@gaspode.localnet> Message-ID: <200205231642.g4NGgIx18033@quill.local> > > Many filesystems (e.g. the popular ext2) have horrible > > performance when there are many files in the same > > directory. The queue system should be modified to > > avoid this situation. As a test case, try adding > > 20,000 test address in such a way that Mailman will try > > to send a welcome message to each of them. > > Isn't this optomising for a rather uncommon case. It may be an uncommon case, but if/when it happens, processing the queue becomes so slow that it's a real problem. I've just taken some timings: Adding 20,000 test addresses took about 40 minutes. (They're all addresses at a remote machine where the the whole domain is forwarded to /dev/null ). I consider this to be acceptable. Now the welcome messages are going out, at a rate of one message every 6.6 seconds. This is on inexpensive hardware (a Cobalt RaQ3) but the server is otherwise idle. At this rate, it would take more than 36 hours to send them all out. I consider this to be unacceptably slow (but it's not catastrophic unless it's normal for your server to put ten or more messages into the virgin queue per minute on the avarage). What I'm really concerned about is the possiblity of a similar thing happening on the bounces queue. On a busy system, you can easily have bounces coming in with a rate greater than 10 bounces per minute. Temporary network problems can easily result in you getting a large number of bounces at the same time. This could put so many bounces into the queue that processing bounces becomes slower than the rate at which new bounces arrive. Then the bounce-handler is permanently screwed. Greetings, Norbert. -- A founder of the http://DotGNU.org project and Steering Committee member Norbert Bollow, Weidlistr.18, CH-8624 Gruet (near Zurich, Switzerland) Tel +41 1 972 20 59 Fax +41 1 972 20 69 http://norbert.ch List hosting with GNU Mailman on your own domain name http://cisto.com From jon@csh.rit.edu Thu May 23 18:02:16 2002 From: jon@csh.rit.edu (Jon Parise) Date: Thu, 23 May 2002 13:02:16 -0400 Subject: [Mailman-Developers] bin/arch and large mbox Message-ID: <20020523170216.GC11670@csh.rit.edu> I'm in the process of integrating a large set of old ezmlm archives with my existing Mailman archives. After converting the ezmlm archives to mbox format, I've been merging the archives together into a single listname.mbox file and then running bin/arch to rebuild the indexes. Everything has been going well until I hit a large mbox archive (~11MB). bin/arch only gets through the first 200 or so messages before it decides to finish up. This leaves me with only three weeks of archive indexes (from the year 2000, at that). The bin/arch usage text alludes to bin/arch having issues with large mbox'es, and it seems as though I'm experiencing one of them. =) Something like "bin/arch -s 0 -e 500 listname" doesn't seem to help. Any thoughts on how to proceed? -- Jon Parise (jon@csh.rit.edu) . Information Technology (2001) http://www.csh.rit.edu/~jon/ : Computer Science House Member From noreply@sourceforge.net Thu May 23 16:56:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 23 May 2002 08:56:55 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558848 ] Upgrade to 2.0.11 breaks admindb page Message-ID: Bugs item #558848, was opened at 2002-05-21 16:18 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558848&group_id=103 Category: configuring/installing Group: 2.0.x >Status: Closed Resolution: None Priority: 5 Submitted By: nathan hruby (nhruby) Assigned to: Nobody/Anonymous (nobody) Summary: Upgrade to 2.0.11 breaks admindb page Initial Comment: Hey, just upgraded to 2.0.11 from 2.0.5. Upgraded by applying the patches (in correct order :) to go from 2.0.5 to .2.0.22. All patches applied cleanly to the 2.0.5 source with no errors. reran the config.guess and re-ran make install, everything went off without a hitch, after restarting sendmail, httpd and cron after the upgrade procedure and checking the test list the admindb webpage dies with an error. All other pages work fine. Here's the traceback: May 21 16:32:19 2002 admin(9971): @@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@ admin(9971): [----- Mailman Version: 2.0.11 -----] admin(9971): [----- Traceback ------] admin(9971): Traceback (innermost last): admin(9971): File "/home/mailman/scripts/driver", line 96, in run_main admin(9971): main() admin(9971): File "/home/mailman/Mailman/Cgi/ admindb.py", line 110, in main admin(9971): if len(cgidata.keys()): admin(9971): NameError: cgidata admin(9971): [----- Python Information -----] admin(9971): sys.version = 1.5.2 (#1, Aug 25 2000, 09:33:37) [GCC 2.96 20000731 (experimental)] admin(9971): sys.executable = /usr/bin/python admin(9971): sys.prefix = /usr admin(9971): sys.exec_prefix= /usr admin(9971): sys.path = /usr admin(9971): sys.platform = linux-i386 admin(9971): [----- Environment Variables -----] admin(9971): DOCUMENT_ROOT: /var/www/html admin(9971): SERVER_ADDR: 128.192.51.21 admin(9971): QUERY_STRING: admin(9971): SERVER_PORT: 80 admin(9971): PATH_TRANSLATED: /var/www/html/ testlist admin(9971): REMOTE_ADDR: 128.192.51.220 admin(9971): HTTP_UA_OS: MacOS admin(9971): HTTP_ACCEPT_LANGUAGE: en admin(9971): GATEWAY_INTERFACE: CGI/1.1 admin(9971): SERVER_NAME: nuttybar.drama.uga.edu admin(9971): HTTP_CONNECTION: Keep-Alive admin(9971): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 5.14; Mac_PowerPC) admin(9971): HTTP_ACCEPT: */* admin(9971): REQUEST_URI: /mailman/admindb/ testlist admin(9971): HTTP_UA_CPU: PPC admin(9971): HTTP_EXTENSION: Security/Remote- Passphrase admin(9971): SCRIPT_FILENAME: /home/mailman/ cgi-bin/admindb admin(9971): PATH_INFO: /testlist admin(9971): HTTP_HOST: nuttybar.drama.uga.edu admin(9971): REQUEST_METHOD: GET admin(9971): SERVER_SIGNATURE:
Apache/1.3.14 Server at nuttybar.drama.uga.edu Port 80
admin(9971): SCRIPT_NAME: /mailman/admindb admin(9971): SERVER_ADMIN: root@localhost admin(9971): SERVER_SOFTWARE: Apache/1.3.14 (Unix) (Red-Hat/Linux) admin(9971): PYTHONPATH: /home/mailman admin(9971): HTTP_COOKIE: testlist:admin= 280200000069c3aeea3c73280000003034623331306 1396165613462396165353062636 633393934393139363738333237323539303864 admin(9971): SERVER_PROTOCOL: HTTP/1.1 admin(9971): REMOTE_PORT: 56839 admin(9971): HTTP_REFERER: http:// nuttybar.drama.uga.edu/mailman/admin/testlist ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-23 11:56 Message: Logged In: YES user_id=12800 I just looked at the 2.0.4 -> 2.0.5 patch and it looks okay to me. That's the patch that should contain the fixed indentation for those lines. Hmm... ---------------------------------------------------------------------- Comment By: nathan hruby (nhruby) Date: 2002-05-21 16:56 Message: Logged In: YES user_id=19736 Damn you're quick :) Fixed by moving the following block of code starting at line 110 in mailman/Cgi/admindb.py over 5 spaces to the left... --- CUT_N_PASTE cgidata = cgi.FieldStorage() try: Auth.authenticate(mlist, cgidata) except Auth.NotLoggedInError, e: Auth.loginpage(mlist, 'admindb', e.message) return -- CUT_N_PASTE perhaps there is something screwy with the patches in the downlaod manager? ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-21 16:41 Message: Logged In: YES user_id=12800 Please compare the Mailman/Cgi/admindb.py file against the file at the top of the 2.0 maintainence branch: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/mailman/mailman/Mailman/Cgi/admindb.py?rev=1.36.2.7&only_with_tag=Release_2_0_11&content-type=text/plain It sounds like there was a problem with the upgrade or the install after upgrade (I know you didn't get any errors, but still, I can't see why this exception would otherwise happen!) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558848&group_id=103 From doko@cs.tu-berlin.de Thu May 23 21:01:49 2002 From: doko@cs.tu-berlin.de (Matthias Klose) Date: Thu, 23 May 2002 22:01:49 +0200 Subject: [Mailman-Developers] MM2.1 CVS: broken configure script Message-ID: <15597.19117.177260.314225@gargle.gargle.HOWL> mailman checks for the installation directories during configury. IMO this wrongly assumes, that - the build machine is the target machine - the directories already exist during configuration - you don't use a temporary installation directory 2.1b2 works ok. Found this while making experimental Debian packages. Matthias ./configure --prefix=/usr/lib/mailman \ --with-var-prefix=/var/lib/mailman \ --with-username=list \ --with-groupname=list \ --with-mail-gid=daemon --with-cgi-gid=www-data creating cache ./config.cache checking for --with-python... no checking for python... /usr/bin/python checking Python interpreter... /usr/bin/python checking Python version... 2.1.3 checking for a BSD compatible install... /usr/bin/install -c checking whether make sets ${MAKE}... yes checking for true... /bin/true checking for --without-gcc... no checking for gcc... gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking whether #! works in shell scripts... yes checking for --with-var-prefix... /var/lib/mailman checking for --with-username... list checking for list UID... 38 checking for --with-groupname... list checking for list GID... 38 checking permissions on /var/lib/mailman... configure: error: ***** Installation directory /var/lib/mailman is not configured properly! ***** Directory doesn't exist: /var/lib/mailman make: *** [configure-stamp] Error 1 From mhz@altlinux.org Thu May 23 22:52:19 2002 From: mhz@altlinux.org (Mikhail Zabaluev) Date: Fri, 24 May 2002 01:52:19 +0400 Subject: [Mailman-Developers] to punish not to pardon [mailman-developers-bounces@python.org: The results of your email commands] Message-ID: <20020523215219.GK12869@mhz.mikhail.zabaluev.name> ---------------------- multipart/mixed attachment Hello, How should I interpret the bounce from Mailman, attached below? Have I been unsubscribed or not? -- Stay tuned, MhZ JID: mookid@jabber.org ___________ All possibility of understanding is rooted in the ability to say no. -- Susan Sontag ---------------------- multipart/mixed attachment An embedded message was scrubbed... From: mailman-developers-bounces@python.org Subject: The results of your email commands Date: Thu, 23 May 2002 17:13:24 -0400 Size: 3437 Url: http://mail.python.org/pipermail-21/mailman-developers/attachments/69fba005/attachment.txt ---------------------- multipart/mixed attachment-- From marc_news@vasoftware.com Fri May 24 05:56:50 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Thu, 23 May 2002 21:56:50 -0700 Subject: [Mailman-Developers] mailman-cvs broke config_list Message-ID: <20020524045650.GZ865@merlins.org> I updated to CVS a few days ago and I'm now getting this: Traceback (most recent call last): File "/var/local/mailman/bin/config_list", line 270, in ? main() File "/var/local/mailman/bin/config_list", line 262, in main do_output(listname, outfile) File "/var/local/mailman/bin/config_list", line 114, in do_output do_list_categories(mlist, k, None, outfp) File "/var/local/mailman/bin/config_list", line 163, in do_list_categories lines = value.replace('\r', '').split('\n') AttributeError: replace -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From noreply@sourceforge.net Fri May 24 15:29:47 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 24 May 2002 07:29:47 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-560127 ] qrunner segfaults on specific message Message-ID: Bugs item #560127, was opened at 2002-05-24 10:29 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560127&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Douglas Paul (dwpaul) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner segfaults on specific message Initial Comment: I received the following bounce message to the -admin account on a mailing list I run. When qrunner tries to process this message, it segfaults, and leaves its locks. When subsequent qrunner passes occur, it just complains that it can't get the lock. Removing the locks just causes it to segfault again. The only solution I've found it to simply remove the message from the queue. This originally happened with Mailman 2.0.8, but I upgraded to 2.0.11 and it still occurred. I was able to reproduce the problem by mailing the contents of the message to the -admin address again. The .msg and .db files are attached. Version Info: Mailman 2.0.8 / 2.0.11 Python 1.5.2 (#1, Jan 19 2000, 19:01:15) [GCC 2.95.1 19990816 (release)] on linux-armv4l Linux elemental 2.4.17-rmk5 #7 Mon Feb 18 18:12:50 EST 2002 armv4l unknown Sendmail 8.9.3 ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560127&group_id=103 From dmick@utopia.West.Sun.COM Fri May 24 20:54:08 2002 From: dmick@utopia.West.Sun.COM (Dan Mick) Date: Fri, 24 May 2002 12:54:08 -0700 Subject: [Mailman-Developers] mailman-cvs broke config_list References: <20020524045650.GZ865@merlins.org> Message-ID: <3CEE9A60.AF491BC7@utopia.west.sun.com> Yeah, I sent this a couple of weeks ago, but Barry missed it I guess: HEY BARRY!!!! :) Subject: Re: [Mailman-Developers] A couple of bugs ... Date: Mon, 13 May 2002 14:31:09 -0700 (PDT) From: Dan Mick To: mailman-developers@python.org, david@midrange.com Category "contentfilter", variable "filter_mime_types", for me, has a 'list' type (i.e. its value is '[]'), but its type is advertised as mm_cfg.Text (4), which causes that newline replacement algorithm to bite it. I'm not sure if the assignment of type mm_cfg.Text is wrong, or if config_list needs to handle arrays of Text more gracefully. Barry? Marc MERLIN wrote: > > I updated to CVS a few days ago and I'm now getting this: > > Traceback (most recent call last): > File "/var/local/mailman/bin/config_list", line 270, in ? > main() > File "/var/local/mailman/bin/config_list", line 262, in main > do_output(listname, outfile) > File "/var/local/mailman/bin/config_list", line 114, in do_output > do_list_categories(mlist, k, None, outfp) > File "/var/local/mailman/bin/config_list", line 163, in do_list_categories > lines = value.replace('\r', '').split('\n') > AttributeError: replace > > -- > Microsoft is to operating systems & security .... > .... what McDonalds is to gourmet cooking > > Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman-21/listinfo/mailman-developers From jon@csh.rit.edu Fri May 24 21:41:52 2002 From: jon@csh.rit.edu (Jon Parise) Date: Fri, 24 May 2002 16:41:52 -0400 Subject: [Mailman-Developers] Odd options wording Message-ID: <20020524204151.GD23346@csh.rit.edu> On the subscriber's options screen in Mailman 2.1b2+, this text existis: "Conceal yourself from subscriber list? When someone views the list membership, your email address is normally shown (in an obscured fashion to thwart spam harvesters). If you do not want your email address to show up on this membership roster, select No for this option." It sounds like that "No" should be changed to a "Yes" for the statements to agree and make sense. -- Jon Parise (jon@csh.rit.edu) . Information Technology (2001) http://www.csh.rit.edu/~jon/ : Computer Science House Member From david@midrange.com Fri May 24 22:01:53 2002 From: david@midrange.com (David Gibbs) Date: Fri, 24 May 2002 16:01:53 -0500 (CDT) Subject: [Mailman-Developers] Re: mailman-cvs broke config_list Message-ID: <16909.208.248.38.130.1022274113.squirrel@webmail.midrange.com> > I updated to CVS a few days ago and I'm now getting this: > Traceback (most recent call last): > File "/var/local/mailman/bin/config_list", line 270, in ? > main() > File "/var/local/mailman/bin/config_list", line 262, in main > do_output(listname, outfile) > File "/var/local/mailman/bin/config_list", line 114, in do_output > do_list_categories(mlist, k, None, outfp) > File "/var/local/mailman/bin/config_list", line 163, in do_list_categories > lines = value.replace('\r', '').split('\n') > AttributeError: replace I logged that as bug 555502 on Sourceforge on the 13th. david From noreply@sourceforge.net Fri May 24 23:26:11 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 24 May 2002 15:26:11 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-560344 ] List Configuration Missing Basic Options Message-ID: Bugs item #560344, was opened at 2002-05-24 18:26 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560344&group_id=103 Category: security/privacy Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: rich cowan (leftlink) Assigned to: Nobody/Anonymous (nobody) Summary: List Configuration Missing Basic Options Initial Comment: Some feedback on mailman, which I have now been using for about 5 months: -- The list type information is really misplaced in the mailman interface. If I want to decide if a list should be announcement-only, moderated, or unmoderated, this info should not be under a "privacy" section; it should be part of the fundamental general settings. --The bug tracker should really have a category for "list setup/administration". This is very distinct from configuring the software on the server. --So I'm requesting that this bug be moved to a new bug category, in fact. And that the "must posts be preapproved by an administrator" question be renamed to "what is the type of this list"? and that there be 3 choices rather than two: * all posts must be approved by an administrator * all posts must be from the administrator * posts do not need to be approved -rich p.s. see http://democracygroups.org/mailinglisthowto.html for some definitions ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560344&group_id=103 From barry@zope.com Sat May 25 07:44:15 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 25 May 2002 02:44:15 -0400 Subject: [Mailman-Developers] mailman-cvs broke config_list References: <20020524045650.GZ865@merlins.org> <3CEE9A60.AF491BC7@utopia.west.sun.com> Message-ID: <15599.12991.551810.771492@anthem.wooz.org> >>>>> "DM" == Dan Mick writes: DM> I'm not sure if the assignment of type mm_cfg.Text is wrong, DM> or if config_list needs to handle arrays of Text more DM> gracefully. Barry? Actually, config_list had to be taught about the transformations that can happen to attribute values coming from and going to the web interface. I'll spare you guys the details. Sigh. ;) Anyway, I think I have some patches that fix this, but please take a close look at your config_list -o output and your list's configuration after using config_list -i. I might have screwed up somewhere. -Barry From noreply@sourceforge.net Sat May 25 07:45:15 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 24 May 2002 23:45:15 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-555502 ] config_list fails with AttributeError Message-ID: Bugs item #555502, was opened at 2002-05-13 11:53 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=555502&group_id=103 Category: command line scripts Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: config_list fails with AttributeError Initial Comment: I ran the config_list command on a newly created list and got the following error ... [root@linux z]# ../bin/config_list -o testlist.txt testlist Traceback (most recent call last): File "../bin/config_list", line 268, in ? main() File "../bin/config_list", line 261, in main do_output(listname, outfile) File "../bin/config_list", line 113, in do_output do_list_categories(mlist, k, None, outfp) File "../bin/config_list", line 162, in do_list_categories lines = value.replace('\r', '').split('\n') AttributeError: replace ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-25 02:45 Message: Logged In: YES user_id=12800 This should be fixed in cvs now. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=555502&group_id=103 From barry@zope.com Sat May 25 08:06:51 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 25 May 2002 03:06:51 -0400 Subject: [Mailman-Developers] /bin/list_admins error References: <00c501c1f617$e1ea6480$1e00a8c0@poema.yi.org> Message-ID: <15599.14347.754631.889875@anthem.wooz.org> >>>>> "DT" == Danny Terweij writes: DT> Traceback (most recent call last): | File "/usr/local/mailman/bin/list_admins", line 96, in ? | main() | File "/usr/local/mailman/bin/list_admins", line 90, in main | owners = COMMASPACE.join(mlist.owner) DT> UnboundLocalError: local variable 'mlist' referenced before DT> assignment This is caused when you give a bogus list name to list_admins. Fixing it now. -Barry From noreply@sourceforge.net Sat May 25 08:11:20 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 25 May 2002 00:11:20 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-560344 ] List "styles" should be supported. Message-ID: Feature Requests item #560344, was opened at 2002-05-24 18:26 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=560344&group_id=103 >Category: None >Group: None Status: Open Resolution: None Priority: 5 Submitted By: rich cowan (leftlink) Assigned to: Nobody/Anonymous (nobody) >Summary: List "styles" should be supported. Initial Comment: Some feedback on mailman, which I have now been using for about 5 months: -- The list type information is really misplaced in the mailman interface. If I want to decide if a list should be announcement-only, moderated, or unmoderated, this info should not be under a "privacy" section; it should be part of the fundamental general settings. --The bug tracker should really have a category for "list setup/administration". This is very distinct from configuring the software on the server. --So I'm requesting that this bug be moved to a new bug category, in fact. And that the "must posts be preapproved by an administrator" question be renamed to "what is the type of this list"? and that there be 3 choices rather than two: * all posts must be approved by an administrator * all posts must be from the administrator * posts do not need to be approved -rich p.s. see http://democracygroups.org/mailinglisthowto.html for some definitions ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-25 03:11 Message: Logged In: YES user_id=12800 Thanks for the url, interesting article. As to the specific bug report, the problem is that there really needs to be a way to specify a "style" of a mailing list. Currently, setting up an announce-only list means twiddling a bunch of disparate variables. That's not good, but it'll have to do for MM2.1. So I'd actually categorize this as a feature request, and in fact, will move it to that tracker. Mailing lists should support common high-level styles or types. I'm also changing the Summary: of this bug accordingly. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=560344&group_id=103 From noreply@sourceforge.net Sat May 25 08:14:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 25 May 2002 00:14:30 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-560127 ] qrunner segfaults on specific message Message-ID: Bugs item #560127, was opened at 2002-05-24 10:29 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560127&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Douglas Paul (dwpaul) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner segfaults on specific message Initial Comment: I received the following bounce message to the -admin account on a mailing list I run. When qrunner tries to process this message, it segfaults, and leaves its locks. When subsequent qrunner passes occur, it just complains that it can't get the lock. Removing the locks just causes it to segfault again. The only solution I've found it to simply remove the message from the queue. This originally happened with Mailman 2.0.8, but I upgraded to 2.0.11 and it still occurred. I was able to reproduce the problem by mailing the contents of the message to the -admin address again. The .msg and .db files are attached. Version Info: Mailman 2.0.8 / 2.0.11 Python 1.5.2 (#1, Jan 19 2000, 19:01:15) [GCC 2.95.1 19990816 (release)] on linux-armv4l Linux elemental 2.4.17-rmk5 #7 Mon Feb 18 18:12:50 EST 2002 armv4l unknown Sendmail 8.9.3 ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-25 03:14 Message: Logged In: YES user_id=12800 I've no idea why you get a core dump, but by definition it must be a bug in Python. No Python script should ever be able to crash the interpreter. I can't find anything wrong with the files you uploaded. Is there any chance you can 1) run gdb on the resulting core file to get a stack trace; 2) upgrade your Python to something newer than 1.5.2? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560127&group_id=103 From david@midrange.com Sat May 25 12:05:13 2002 From: david@midrange.com (David Gibbs) Date: Sat, 25 May 2002 06:05:13 -0500 Subject: [Mailman-Developers] 'make install' error in cvs Message-ID: I just updated cvs and ran 'make install', and got the following error ... make[1]: Entering directory `/root/mailman-2.1-beta/mailman/misc' for p in email-2.0.4 JapaneseCodecs-1.4.5 KoreanCodecs-2.0.4; \ do \ gunzip -c $p.tar.gz | tar xf -; \ (cd $p ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/bin/python2 setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib); \ done File "/usr/local/mailman/pythonlib/email/_compat22.py", line 21 yield self ^ SyntaxError: invalid syntax ^C [ I killed it at this point ] interrupted make[1]: *** [install-packages] Error 1 make: *** [doinstall] Interrupt Ideas? david From barry@zope.com Sat May 25 17:04:46 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 25 May 2002 12:04:46 -0400 Subject: [Mailman-Developers] 'make install' error in cvs References: Message-ID: <15599.46622.916006.160232@anthem.wooz.org> >>>>> "DG" == David Gibbs writes: DG> I just updated cvs and ran 'make install', and got the DG> following error ... DG> make[1]: Entering directory DG> `/root/mailman-2.1-beta/mailman/misc' for p in email-2.0.4 DG> JapaneseCodecs-1.4.5 KoreanCodecs-2.0.4; \ do \ DG> gunzip -c $p.tar.gz | tar xf -; \ (cd $p ; DG> PYTHONPATH=/usr/local/mailman/pythonlib /usr/bin/python2 | setup.py --quiet install --install-lib | /usr/local/mailman/pythonlib --install-purelib | /usr/local/mailman/pythonlib); \ | done DG> File "/usr/local/mailman/pythonlib/email/_compat22.py", line DG> 21 yield self ^ | SyntaxError: invalid syntax | ^C [ I killed it at this point ] | interrupted | make[1]: *** [install-packages] Error 1 | make: *** [doinstall] Interrupt DG> Ideas? Yup, it's part of the (in)compatibility hacks to make the email package work with both python2.1 and python2.2. Question: why did you "kill it at this point"? Did the installation process hang for you? I believe that if you just ignore this error everything should still work for you. You can verify this by cd'ing to /root/mailman-2.1-beta/mailman/misc/email-2.0.4 and typing: % PYTHONPATH=/usr/local/mailman/pythonlib python test.py If you see no errors, you're good to go. Let me know if you do get errors. I'll have to figure out a way to get distutils to not try to compile the _compat22.py file. :( -Barry From noreply@sourceforge.net Sat May 25 17:20:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 25 May 2002 09:20:30 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-560127 ] qrunner segfaults on specific message Message-ID: Bugs item #560127, was opened at 2002-05-24 10:29 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560127&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Douglas Paul (dwpaul) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner segfaults on specific message Initial Comment: I received the following bounce message to the -admin account on a mailing list I run. When qrunner tries to process this message, it segfaults, and leaves its locks. When subsequent qrunner passes occur, it just complains that it can't get the lock. Removing the locks just causes it to segfault again. The only solution I've found it to simply remove the message from the queue. This originally happened with Mailman 2.0.8, but I upgraded to 2.0.11 and it still occurred. I was able to reproduce the problem by mailing the contents of the message to the -admin address again. The .msg and .db files are attached. Version Info: Mailman 2.0.8 / 2.0.11 Python 1.5.2 (#1, Jan 19 2000, 19:01:15) [GCC 2.95.1 19990816 (release)] on linux-armv4l Linux elemental 2.4.17-rmk5 #7 Mon Feb 18 18:12:50 EST 2002 armv4l unknown Sendmail 8.9.3 ---------------------------------------------------------------------- >Comment By: Douglas Paul (dwpaul) Date: 2002-05-25 12:20 Message: Logged In: YES user_id=552731 Unfortunately, my Python doesn't have any symbols, but here's what I get from a backtrace. It looks to me like it's trying to allocate a lot of memory, and a bug in glibc is making it crash: (gdb) backtrace #0 chunk_alloc (ar_ptr=0x4015bbe4, nb=40) at malloc.c:2814 #1 0x400c86fc in __libc_malloc (bytes=1075166260) at malloc.c:2643 #2 0xbfffdc10 in ?? () I also get this strange message, too: warning: core file may not match specified executable file. Core was generated by `'. Program terminated with signal 11, Segmentation fault. This system was running with glibc 2.1.2. I tried running it on in a chrooted environment I'm building to upgrade my system (glibc 2.2.5, Python 2.2) and it does work fine. Unless there's any other information you'd like me to find, I think I'll just upgrade my Python to 2.2. It's definitely not a bug in Mailman. Thanks for the quick response. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-25 03:14 Message: Logged In: YES user_id=12800 I've no idea why you get a core dump, but by definition it must be a bug in Python. No Python script should ever be able to crash the interpreter. I can't find anything wrong with the files you uploaded. Is there any chance you can 1) run gdb on the resulting core file to get a stack trace; 2) upgrade your Python to something newer than 1.5.2? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560127&group_id=103 From barry@zope.com Sat May 25 17:37:40 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 25 May 2002 12:37:40 -0400 Subject: [Mailman-Developers] Re: [Mailman-Users] Python Upgrade problem with mailman References: <3CEC2035.4DF7A459@isu.edu> Message-ID: <15599.48596.696959.311568@anthem.wooz.org> >>>>> "W" == Webmaster writes: W> Very critical does anyone know if Pytnon 2.1 will work with W> mailman 2.0.11, (problems with my production mailing lists) Yes, it definitely works. python.org/zope.org runs MM2.0.11 with Python 2.1.3. It really looks like your Python installation is hosed. Did you upgrade it by building it from source? -Barry From david@midrange.com Sat May 25 18:17:12 2002 From: david@midrange.com (David Gibbs) Date: Sat, 25 May 2002 12:17:12 -0500 Subject: [Mailman-Developers] Re: 'make install' error in cvs References: <15599.46622.916006.160232@anthem.wooz.org> Message-ID: "Barry A. Warsaw" wrote in message news:15599.46622.916006.160232@anthem.wooz.org... > Yup, it's part of the (in)compatibility hacks to make the email > package work with both python2.1 and python2.2. Ok > Question: why did you "kill it at this point"? Did the installation > process hang for you? No, but on the workstation I was at I didn't have good scrollback. :( > I believe that if you just ignore this error everything should still > work for you. You can verify this by cd'ing to > /root/mailman-2.1-beta/mailman/misc/email-2.0.4 and typing: > % PYTHONPATH=/usr/local/mailman/pythonlib python test.py > If you see no errors, you're good to go. Let me know if you do get > errors. Got this ... [root@linux email-2.0.4]# pwd /root/mailman-2.1-beta/mailman/misc/email-2.0.4 [root@linux email-2.0.4]# PYTHONPATH=/usr/local/mailman/pythonlib python test.py Traceback (innermost last): File "test.py", line 7, in ? import unittest ImportError: No module named unittest david From barry@zope.com Sat May 25 19:53:30 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 25 May 2002 14:53:30 -0400 Subject: [Mailman-Developers] Re: 'make install' error in cvs References: <15599.46622.916006.160232@anthem.wooz.org> Message-ID: <15599.56746.159531.510@anthem.wooz.org> >>>>> "DG" == David Gibbs writes: DG> Got this ... DG> [root@linux email-2.0.4]# pwd DG> /root/mailman-2.1-beta/mailman/misc/email-2.0.4 [root@linux DG> email-2.0.4]# PYTHONPATH=/usr/local/mailman/pythonlib python DG> test.py Traceback (innermost last): | File "test.py", line 7, in ? | import unittest DG> ImportError: No module named unittest You must use at least Python 2.1 (with 2.1.3 or 2.2.1 recommended). Still, something's weird because unittest came with Python 2.0 IIRC. You sure that the first python on your path isn't 1.5.2? -Barry From nb@thinkcoach.com Sat May 25 20:18:18 2002 From: nb@thinkcoach.com (Norbert Bollow) Date: Sat, 25 May 2002 21:18:18 +0200 Subject: [Mailman-Developers] Re: [Mailman-Users] Mailman does everything except send mail In-Reply-To: <15599.47311.371744.228560@anthem.wooz.org> (barry@zope.com) References: <20020515130106.A20160@itn.co.uk> <1021464374.7916.128.camel@atlas> <15589.33377.455777.828959@anthem.wooz.org> <1021969996.14022.44.camel@atlas> <15599.47311.371744.228560@anthem.wooz.org> Message-ID: <200205251918.g4PJIId09263@quill.local> barry@zope.com (Barry A. Warsaw) wrote on mailman-users: > MM2.1's qrunner will take almost no resources to just leave it > running. Is there a way to start say a hundred of them on the same box (in order to service a hundred separate Mailman installations) so that most of the memory is shared? Greetings, Norbert. -- A founder of the http://DotGNU.org project and Steering Committee member Norbert Bollow, Weidlistr.18, CH-8624 Gruet (near Zurich, Switzerland) Tel +41 1 972 20 59 Fax +41 1 972 20 69 http://norbert.ch List hosting with GNU Mailman on your own domain name http://cisto.com From barry@zope.com Sat May 25 20:59:20 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 25 May 2002 15:59:20 -0400 Subject: [Mailman-Developers] Re: [Mailman-Users] Mailman does everything except send mail References: <20020515130106.A20160@itn.co.uk> <1021464374.7916.128.camel@atlas> <15589.33377.455777.828959@anthem.wooz.org> <1021969996.14022.44.camel@atlas> <15599.47311.371744.228560@anthem.wooz.org> <200205251918.g4PJIId09263@quill.local> Message-ID: <15599.60696.21874.961842@anthem.wooz.org> >>>>> "NB" == Norbert Bollow writes: >> MM2.1's qrunner will take almost no resources to just leave it >> running. NB> Is there a way to start say a hundred of them on the same box NB> (in order to service a hundred separate Mailman installations) NB> so that most of the memory is shared? You can start lots of them, even multiple ones to service the same queue. They won't collide and don't need to lock any resource. But each is a separate Python process, in the current scheme of things. If the qrunners were I/O bound, you might see some gains by multithreading them, but I haven't implemented that at all (and it won't help if they're cpu bound). -Barry From david@midrange.com Sat May 25 21:21:13 2002 From: david@midrange.com (David Gibbs) Date: Sat, 25 May 2002 15:21:13 -0500 Subject: [Mailman-Developers] Re: 'make install' error in cvs In-Reply-To: <15599.56746.159531.510@anthem.wooz.org> References: <15599.46622.916006.160232@anthem.wooz.org> Message-ID: <5.1.1.2.2.20020525152022.01f39b08@linux.midrange.com> At 01:53 PM 5/25/2002, Barry A. Warsaw wrote: >You must use at least Python 2.1 (with 2.1.3 or 2.2.1 recommended). >Still, something's weird because unittest came with Python 2.0 IIRC. Gah! My bad. I have two pythons installed ... python, which a 1.x, and python2, which is 2.1. Here's the real results ... [root@linux email-2.0.4]# pwd /root/mailman-2.1-beta/mailman/misc/email-2.0.4 [root@linux email-2.0.4]# PYTHONPATH=/usr/local/mailman/pythonlib python2 test.py ...........................................................................................F...................... ====================================================================== FAIL: test_parseaddr_empty (test_email.TestMiscellaneous) ---------------------------------------------------------------------- Traceback (most recent call last): File "test/test_email.py", line 1189, in test_parseaddr_empty self.assertEqual(Utils.parseaddr('<>'), ('', '')) File "/tmp/32444-i386/install/usr/lib/python2.1/unittest.py", line 273, in failUnlessEqual raise self.failureException, (msg or '%s != %s' % (first, second)) AssertionError: ('', None) != ('', '') ---------------------------------------------------------------------- Ran 114 tests in 2.118s FAILED (failures=1) [root@linux email-2.0.4]# python2 -V Python 2.1.1 -- | Internet: david@midrange.com | WWW: http://david.fallingrock.net | AIM: MidrangeMan | | If you can't fly, run; if you can't run, walk; | if you can't walk, crawl. | -mlk From marc_news@vasoftware.com Sat May 25 21:09:27 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sat, 25 May 2002 13:09:27 -0700 Subject: [Mailman-Developers] compile error in mailman cvs? Message-ID: <20020525200923.GB25230@merlins.org> I just synced my tree, and: make[1]: Entering directory `/var/local/src/mailman-cvs/misc' for p in email-2.0.4 JapaneseCodecs-1.4.5 KoreanCodecs-2.0.4; \ do \ gunzip -c $p.tar.gz | tar xf -; \ (cd $p ; PYTHONPATH=/var/local/mailman/pythonlib /usr/bin/python setup.py --quiet install --install-lib /var/local/mailman/pythonlib --install-purelib /var/local/mailman/pythonlib); \ done File "/var/local/mailman/pythonlib/email/_compat22.py", line 21 yield self ^ SyntaxError: invalid syntax File "/var/local/mailman/pythonlib/japanese/mappings/jis_x_0208.py", line 6234 "\x6d\x ^ Syntax Barry? Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From danny@terweij.nl Sat May 25 21:32:37 2002 From: danny@terweij.nl (Danny Terweij) Date: Sat, 25 May 2002 22:32:37 +0200 Subject: [Mailman-Developers] Wrong domain choosed when creating a new list (mm2.1b2) Message-ID: <009101c2042b$4f7b9840$1e00a8c0@onsnet.org> Hi, These are my mm_cfg settings: DEFAULT_EMAIL_HOST = 'lnx.p-s.nl' DEFAULT_URL_HOST = 'www.p-s.nl' DEFAULT_URL_PATTERN = 'http://%s:81/mailman/' DEFAULT_HOST_NAME = DEFAULT_URL_HOST DEFAULT_URL = DEFAULT_URL_PATTERN % DEFAULT_URL_HOST VIRTUAL_HOST_OVERVIEW = 0 When i do creating a new list : ./newlist [root@lnx bin]# ./newlist Enter the name of the list: testlist-1 Enter the email of the person running the list: danny@terweij.nl Initial testlist-1 password: [aliases shown] Hit enter to notify testlist-1 owner... When i hit it and check my mailbox of danny@terweij.nl : mailman-admin@www.p-s.nl wrote: > The mailing list `testlist-1' has just been created for you. The > following is some basic information about your mailing list. It is using DEFAULT_URL_HOST or DEFAULT_HOST_NAME instead of DEFAULT_EMAIL_HOST. (in my case... the lists are not runing on www.p-s.nl, but on www.p-s.nl : 81 redirected internaly to my linux host lnx.p-s.nl) Where can i change this? Danny. From barry@zope.com Sat May 25 21:37:01 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 25 May 2002 16:37:01 -0400 Subject: [Mailman-Developers] Re: 'make install' error in cvs References: <15599.46622.916006.160232@anthem.wooz.org> <5.1.1.2.2.20020525152022.01f39b08@linux.midrange.com> Message-ID: <15599.62957.309119.239507@anthem.wooz.org> >>>>> "DG" == David Gibbs writes: | Python 2.1.1 Try upgrading to Python 2.1.3. It should go smoothly as it's only a bug fix release. -Barry From barry@zope.com Sat May 25 21:39:28 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 25 May 2002 16:39:28 -0400 Subject: [Mailman-Developers] compile error in mailman cvs? References: <20020525200923.GB25230@merlins.org> Message-ID: <15599.63104.7788.808839@anthem.wooz.org> >>>>> "MM" == Marc MERLIN writes: MM> I just synced my tree, and: | make[1]: Entering directory `/var/local/src/mailman-cvs/misc' | for p in email-2.0.4 JapaneseCodecs-1.4.5 KoreanCodecs-2.0.4; \ | do \ | gunzip -c $p.tar.gz | tar xf -; \ | (cd $p ; PYTHONPATH=/var/local/mailman/pythonlib /usr/bin/python setup.py --quiet install --install-lib /var/local/mailman/pythonlib --install-purelib /var/local/mailman/pythonlib); \ | done | File "/var/local/mailman/pythonlib/email/_compat22.py", line 21 | yield self | ^ This one you /should/ be able to ignore (I'm still trying to figure out how to get distutils not to try to compile _compat22.py if you're running Python 2.1). | SyntaxError: invalid syntax | File "/var/local/mailman/pythonlib/japanese/mappings/jis_x_0208.py", line 6234 | "\x6d\x | ^ | Syntax Gah, I've no clue about this one. Is there a possibility that your Python wasn't built with Unicode support? -Barry From satyap@satya.virtualave.net Sat May 25 22:16:33 2002 From: satyap@satya.virtualave.net (Satya) Date: Sat, 25 May 2002 14:16:33 -0700 (PDT) Subject: [Mailman-Developers] Re: [Mailman-Users] Mailman does everything except send mail In-Reply-To: <15599.60696.21874.961842@anthem.wooz.org> Message-ID: On May 25, 2002 at 15:59, Barry A. Warsaw wrote: [qrunners] >You can start lots of them, even multiple ones to service the same >queue. They won't collide and don't need to lock any resource. So on a busy server, starting multiple qrunners from cron would help with the stale lockfile and associated issues? -- Satya. 2 + 2 = 5 for extremely large values of 2. From marc_news@vasoftware.com Sat May 25 22:23:01 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sat, 25 May 2002 14:23:01 -0700 Subject: [Mailman-Developers] compile error in mailman cvs? In-Reply-To: <15599.63104.7788.808839@anthem.wooz.org> References: <20020525200923.GB25230@merlins.org> <15599.63104.7788.808839@anthem.wooz.org> Message-ID: <20020525212257.GD25230@merlins.org> On Sat, May 25, 2002 at 04:39:28PM -0400, Barry A. Warsaw wrote: > | done > | File "/var/local/mailman/pythonlib/email/_compat22.py", line 21 > | yield self > | ^ > > This one you /should/ be able to ignore (I'm still trying to figure > out how to get distutils not to try to compile _compat22.py if you're > running Python 2.1). Ok, I upgraed and it seems to run fine > | SyntaxError: invalid syntax > | File "/var/local/mailman/pythonlib/japanese/mappings/jis_x_0208.py", line 6234 > | "\x6d\x > | ^ > | Syntax > > Gah, I've no clue about this one. Is there a possibility that your > Python wasn't built with Unicode support? Can't really tell, what's the magic flag? (help says -U though) Python 2.1.1 svlug:/var/local/src/mailman-cvs# python -h usage: python [option] ... [-c cmd | file | -] [arg] ... Options and arguments (and corresponding environment variables): -d : debug output from parser (also PYTHONDEBUG=x) -i : inspect interactively after running script, (also PYTHONINSPECT=x) and force prompts, even if stdin does not appear to be a terminal -O : optimize generated bytecode (a tad; also PYTHONOPTIMIZE=x) -OO : remove doc-strings in addition to the -O optimizations -S : don't imply 'import site' on initialization -t : issue warnings about inconsistent tab usage (-tt: issue errors) -u : unbuffered binary stdout and stderr (also PYTHONUNBUFFERED=x) -U : Unicode literals: treats '...' literals like u'...' -v : verbose (trace import statements) (also PYTHONVERBOSE=x) -x : skip first line of source, allowing use of non-Unix forms of #!cmd -h : print this help message and exit -V : print the Python version number and exit -W arg : warning control (arg is action:message:category:module:lineno) -c cmd : program passed in as string (terminates option list) file : program read from script file - : program read from stdin (default; interactive mode if a tty) arg ...: arguments passed to program in sys.argv[1:] Other environment variables: PYTHONSTARTUP: file executed on interactive startup (no default) PYTHONPATH : ':'-separated list of directories prefixed to the default module search path. The result is sys.path. PYTHONHOME : alternate directory (or :). The default module search path uses /python2.1. PYTHONCASEOK : ignore case in 'import' statements (Windows). svlug:/var/local/src/mailman-cvs# python -v # /usr/lib/python2.1/site.pyc matches /usr/lib/python2.1/site.py import site # precompiled from /usr/lib/python2.1/site.pyc # /usr/lib/python2.1/os.pyc matches /usr/lib/python2.1/os.py import os # precompiled from /usr/lib/python2.1/os.pyc import posix # builtin # /usr/lib/python2.1/posixpath.pyc matches /usr/lib/python2.1/posixpath.py import posixpath # precompiled from /usr/lib/python2.1/posixpath.pyc # /usr/lib/python2.1/stat.pyc matches /usr/lib/python2.1/stat.py import stat # precompiled from /usr/lib/python2.1/stat.pyc # /usr/lib/python2.1/UserDict.pyc matches /usr/lib/python2.1/UserDict.py import UserDict # precompiled from /usr/lib/python2.1/UserDict.pyc Python 2.1.1 (#1, Nov 11 2001, 18:19:24) [GCC 2.95.4 20011006 (Debian prerelease)] on linux2 Type "copyright", "credits" or "license" for more information. import readline # dynamically loaded from /usr/lib/python2.1/lib-dynload/readline.so Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From nb@thinkcoach.com Sat May 25 22:47:48 2002 From: nb@thinkcoach.com (Norbert Bollow) Date: Sat, 25 May 2002 23:47:48 +0200 Subject: [Mailman-Developers] Re: [Mailman-Users] Mailman does everything except send mail In-Reply-To: (message from Satya on Sat, 25 May 2002 14:16:33 -0700 (PDT)) References: Message-ID: <200205252147.g4PLlmW10286@quill.local> > [qrunners] > >You can start lots of them, even multiple ones to service the same > >queue. They won't collide and don't need to lock any resource. > > So on a busy server, starting multiple qrunners from cron would help > with the stale lockfile and associated issues? Barry was speaking about Mailman 2.1 there, you don't start the qrunners from cron in Mailman 2.1 In Mailman 2.0.x when you start a second qrunner for the same Mailman installation, the new qrunner will just exit. This doesn't help you. (In the possibly-pretty-unique situation that I have, with _many_ Mailman 2.0.x installs per server, it's a bad idea to start those multiple qrunners directly from cron.) Greetings, Norbert. -- A founder of the http://DotGNU.org project and Steering Committee member Norbert Bollow, Weidlistr.18, CH-8624 Gruet (near Zurich, Switzerland) Tel +41 1 972 20 59 Fax +41 1 972 20 69 http://norbert.ch List hosting with GNU Mailman on your own domain name http://cisto.com From david@midrange.com Sun May 26 00:07:28 2002 From: david@midrange.com (David Gibbs) Date: Sat, 25 May 2002 18:07:28 -0500 Subject: [Mailman-Developers] Re: Re: 'make install' error in cvs References: <15599.46622.916006.160232@anthem.wooz.org><5.1.1.2.2.20020525152022.01f39b08@linux.midrange.com> <15599.62957.309119.239507@anthem.wooz.org> Message-ID: "Barry A. Warsaw" wrote in message news:15599.62957.309119.239507@anthem.wooz.org... > | Python 2.1.1 > Try upgrading to Python 2.1.3. It should go smoothly as it's only a > bug fix release. Got 2.2.1 ... seems to work fine so far. david From marc_news@vasoftware.com Sun May 26 00:40:36 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sat, 25 May 2002 16:40:36 -0700 Subject: [Mailman-Developers] 'make install' error in cvs In-Reply-To: <15599.46622.916006.160232@anthem.wooz.org> References: <15599.46622.916006.160232@anthem.wooz.org> Message-ID: <20020525234032.GE25230@merlins.org> On Sat, May 25, 2002 at 12:04:46PM -0400, Barry A. Warsaw wrote: > DG> File "/usr/local/mailman/pythonlib/email/_compat22.py", line > DG> 21 yield self ^ > | SyntaxError: invalid syntax > | ^C [ I killed it at this point ] > | interrupted > | make[1]: *** [install-packages] Error 1 > | make: *** [doinstall] Interrupt > > DG> Ideas? > > Yup, it's part of the (in)compatibility hacks to make the email > package work with both python2.1 and python2.2. Duh, that will teach me to post before finishing ot catch up on my folder backlog. > Question: why did you "kill it at this point"? Did the installation > process hang for you? As far as I'm concerned, I paniced and killed it. > I believe that if you just ignore this error everything should still > work for you. You can verify this by cd'ing to > /root/mailman-2.1-beta/mailman/misc/email-2.0.4 and typing: > > % PYTHONPATH=/usr/local/mailman/pythonlib python test.py > > If you see no errors, you're good to go. Let me know if you do get > errors. > http://mail.python.org/mailman-21/listinfo/mailman-developers svlug:/var/local/src/mailman-cvs/misc/email-2.0.4# PYTHONPATH=/var/local/mailman/pythonlib python test.py ...........................................................................................F...................... ====================================================================== FAIL: test_parseaddr_empty (test_email.TestMiscellaneous) ---------------------------------------------------------------------- Traceback (most recent call last): File "test/test_email.py", line 1189, in test_parseaddr_empty self.assertEqual(Utils.parseaddr('<>'), ('', '')) File "/usr/lib/python2.1/unittest.py", line 273, in failUnlessEqual raise self.failureException, (msg or '%s != %s' % (first, second)) AssertionError: ('', None) != ('', '') ---------------------------------------------------------------------- Ran 114 tests in 1.585s FAILED (failures=1) I then upgraded from python 2.1 to python 2.2 and got: svlug:/var/local/src/mailman-cvs/misc/email-2.0.4# PYTHONPATH=/var/local/mailman/pythonlib python test.py .................................................................................................................. ---------------------------------------------------------------------- Ran 114 tests in 1.409s OK The unicode error also went away but I have this instaed now: make[1]: Entering directory `/var/local/src/mailman-cvs/misc' for p in email-2.0.4 JapaneseCodecs-1.4.5 KoreanCodecs-2.0.4; \ do \ gunzip -c $p.tar.gz | tar xf -; \ (cd $p ; PYTHONPATH=/var/local/mailman/pythonlib /usr/bin/python setup.py --quiet install --install-lib /var/local/mailman/pythonlib --install-purelib /var/local/mailman/pythonlib); \ done Traceback (most recent call last): File "setup.py", line 11, in ? from distutils.core import setup ImportError: No module named distutils.core Traceback (most recent call last): File "setup.py", line 5, in ? from distutils.core import setup, Extension ImportError: No module named distutils.core Traceback (most recent call last): File "setup.py", line 5, in ? from distutils.core import setup, Extension ImportError: No module named distutils.core make[1]: *** [install-packages] Error 1 although it does complete and install Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From donal.hunt2@mail.dcu.ie Sun May 26 16:55:42 2002 From: donal.hunt2@mail.dcu.ie (Donal Hunt) Date: Sun, 26 May 2002 16:55:42 +0100 Subject: [Mailman-Developers] Help on a code sample... Message-ID: <3CF1057E.28C64E26@mail.dcu.ie> Hi there, I've written the following example handler for Mailman but have a bug that I can't for the life of me understand why it's happening... It's based on Personalize.py (yes, I'm aware it's deprecated, but it works for me. :-)) Basically. The email gets encrypted correctly for the first person (and sent to them), but the second person gets person one's mail encrypted!! Basically "valu"e doesn't get reset back to the actual unencrypted email contents (msg). I'm sure I'm missing something stupid in my loop (to do the multi-part stuff). If someone spots it I'ld really appreciate a mail. Thanks in advance. Donal DCU ----------------------------------------------------- def process(mlist, msg, msgdata): if getattr(mlist, 'crypto_processing') <> 1: return if not msgdata.get('decrypted'): return # Make a copy for each recipient, and re-queue the copies to the incoming # queue. Set the pipeline for the copies to just Decorate and # ToOutgoing. The normal queue on the original copy should take care of # everything else. newpipeline = ['Decorate', 'ToOutgoing'] inq = get_switchboard(mm_cfg.INQUEUE_DIR) # Save the original To: line originalto = msg['To'] # Create a separate message for each recipient savedmsg = msg for member in msgdata.get('recips', []): msg = savedmsg syslog('error', 'msg: %s' % msg) r_code = 1 metadatacopy = msgdata.copy() metadatacopy['pipeline'] = newpipeline metadatacopy['recips'] = [member] metadatacopy['encrypted'] = 1 del msg['To'] name = mlist.getMemberName(member) if name: msg['To'] = '%s (%s)' % (member, name) else: msg['To'] = member # Walk the message tree and tree to encrypt text/plain parts. for part in msg.walk(): if part.get_type('text/plain') == 'text/plain': # text/plain message part - encrypt it. value = part.get_payload() if not value: pass else: try: syslog('error', 'value **2**: %s' % value) (r_code,result) = IBE.encrypt_msg(value, mlist.getMemberCPAddress(member)) syslog('error', 'result: %s' % result) if r_code == 1: part.set_payload("""Error occurred during encryption of this message / message part.\n\n Error msg:\n"""+result) else: part.set_payload(result) del metadatacopy['decrypted'] except Exception, e: syslog('error', 'Error in encrypt_msg, IBE.py: %s' % e) else: # Non text/plain msg part. Ignore. pass inq.enqueue(msg, metadatacopy, listname=mlist.internal_name()) # Restore the original To: line del msg['To'] msg['To'] = originalto # Don't let the normal ToOutgoing processing actually send the original # copy. del msgdata['recips'] ----------------------------------------------------- From cday@permanently.misplaced.net Sun May 26 20:36:54 2002 From: cday@permanently.misplaced.net (Chad Day) Date: Sun, 26 May 2002 15:36:54 -0400 Subject: [Mailman-Developers] Interfacing with MySQL? Message-ID: <20020526153654.B216@permanently.misplaced.net> I've looked on SourceForge for a patch and didn't find anything, but I'm sure this has probably come up before.. couldn't find it in the archives either. Has anyone written a patch that will allow mailman to interface with MySQL for login verification? I have a bunch of user info in a mysql database and I want to tie these 2 together, and not have the user have to keep a seperate password (or have the ability to change them, throwing them out of sync).. Can anyone help me out? Thanks, Chad From lac@strakt.com Sun May 26 06:43:42 2002 From: lac@strakt.com (Laura Creighton) Date: Sun, 26 May 2002 07:43:42 +0200 Subject: [Mailman-Developers] from python-list@python.org ... for those of you not subscribed to there Message-ID: <200205260543.g4Q5hgSZ021858@ratthing-b246.strakt.com> (Message spamfixes:2) Date: Sat, 25 May 2002 22:18:12 EDT To: cc: "'Sean 'Shaleh' Perry'" , "'Python Mailing List'" From: Matt Curtin Subject: Meta: Shibboleth (was: RE: Off Topic, But List Related) Return-Path: python-list-admin@python.org Delivery-Date: Sun May 26 04:25:35 2002 MIME-Version: 1.0 In-Reply-To: <007101c20458$335f1e20$388e7aa5@adirondacker> References: <007101c20458$335f1e20$388e7aa5@adirondacker> X-Mailer: VM 6.92 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid X-Attribution: Matt X-URL: http://www.interhack.net/people/cmcurtin/ X-message-flag: Thank you for using LookOut, the most insecure mailer available ***! X-Accept-Language: en-US, en, ru, de, fr X-Face: L"IcL.b%SDN]0Kql2b`e.}+i05V9fi\yX#H1+Xl)3!+n/3?5`%-SA-HDgPk9 ***uTk<3dv^J5DCgal)-E{`zN#*o6F|y>r)\< List-Post: List-Subscribe: , List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: On 25 May 2002, Peter F. Ferris presumably wrote: Hi, I'm the architect of Shibboleth, the privacy- and security-aware mailing list manager Peter mentioned. I'd like to clear up a few things, just to make sure there are no misconceptions. > perhaps you should read the white paper. [...] > The only addresses that would be gleaned would be those typed in the > message body by the user. Shibboleth addresses this problem by standardizing all addresses. If we have a set of lists dedicated to discussion of python, we might designate that list "family" as "python". All subscribers to any of the python lists would then have a standardized address form of python+nym@example.com Assuming that the local MTA uses + as the separator character between account and token for delivery. (I believe that qmail installations will use - by default, and the character is settable in most Unix MTAs.) Thus, if my nym is cmcurtin and I'm a subscriber, my posts would wind up in the archives (and posted through the lists) as python+cmcurtin@example.com. No one would ever know my address(es) unless I include them in signature blocks and whatnot. This means that all mail in connection with a list, or even person-to-person stuff that started on a list is run through Shibboleth. Mailing lists follow the same form, e.g., "Python Technical Discussion" might be python+tech@example.com, "Python Advocacy" might be python+perlsucks@example.com, and "Python Questions" might be python+help@example.com. Shibboleth performs a series of tests to detect whether a message has come from an "insider" (someone legitimately subscribed to one of the lists). If not, Shibboleth will return a "user unknown" bounce to the sender, e.g., an outsider (e.g., spammer) mailing python+cmcurtin@example.com would get a user unknown bounce, where an insider mailing python+cmcurtin@example.com would have the message delivered to me through the python list-supporting Shibboleth installation. (These tests also include provisions for handling of PGP signatures, reusable passwords in X-Password headers, E?SMTP/MTA path analysis for address forgery detection and some other useful stuff for enforcing the only-insiders-can-talk-to-insiders policy option.) We actually built the system so that groups that wanted privacy and security on a public network would be able to get it. Spam became a problem after the project was underway. Spam, email-worms, etc., are all handled remarkably well in practice on existing Shibboleth installations. That is, I know of no cases where any spam has been posted to a Shibboleth mailing list, or where any worm has propagated through a Shibboleth-run list or to a user whose address was published through participation in a Shibboleth list. (I know Peter from one such list family, and our lack of spam, malware, and other outsider-originated annoyances is likely what prompted his mention of Shibboleth. But I can't speak for him obviously. :-) Peter refers to a white paper, which isn't quite correct. The URI he gave is for a formal technical paper that is part of the Proceedings of the 9th USENIX Security Symposium. You can pick up the paper as it was presented at the conference from the USENIX site, of course. Shibboleth is implemented in that other language ;-) but I would be delighted to see its functionality become options in a more general-purpose and widely-used mailing list manager like Mailman. I'm presently too buried to perform the porting work myself, but if someone would like to do some fun coding, I would be happy to advise and to provide feedback on getting some of the more useful features of Shibboleth incorporated into another system. Happy hacking! -- Matt Curtin Interhack Corp +1 614 545 HACK http://web.interhack.com/ Author, Developing Trust: Online Privacy and Security (Apress, 2001) Knight, Lambda Calculus | Certum quod factum. --Giovanni Battista Vico -- http://mail.python.org/mailman/listinfo/python-list From barry@zope.com Mon May 27 20:16:43 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 27 May 2002 15:16:43 -0400 Subject: [Mailman-Developers] [ mailman-Bugs-558988 ] bad performance for big queue dirs References: <1022142837.7936.9.camel@gaspode.localnet> <200205231642.g4NGgIx18033@quill.local> Message-ID: <15602.34331.731926.488668@anthem.wooz.org> >>>>> "NB" == Norbert Bollow writes: NB> Now the welcome messages are going out, at a rate of one NB> message every 6.6 seconds. This is on inexpensive hardware (a NB> Cobalt RaQ3) but the server is otherwise idle. At this rate, NB> it would take more than 36 hours to send them all out. I NB> consider this to be unacceptably slow (but it's not NB> catastrophic unless it's normal for your server to put ten or NB> more messages into the virgin queue per minute on the NB> avarage). There are a lot of unknowns here though. For example, we don't know if your rate limits are caused by MTA or network throttles. If your server is idle then i/o is suspect but we don't know if creating more outgoing qrunner processes would help you (by splitting up the queue hash space among parallel processes). Is your MTA spooling to the same filesystem that Mailman is spooling off of? If your MTA is throttling and it's running synchronously with the outgoing qrunner then Mailman may just be sitting around blocked on output to your MTA. Or maybe your disk subsystem can't take the pressure of Mailman reading off of it while your MTA is writing to it. What happens if you put them on different disks and/or controllers? And what effect does using some other filesystem (e.g. reiserfs) have on throughput? NB> What I'm really concerned about is the possiblity of a similar NB> thing happening on the bounces queue. On a busy system, you NB> can easily have bounces coming in with a rate greater than 10 NB> bounces per minute. Temporary network problems can easily NB> result in you getting a large number of bounces at the same NB> time. This could put so many bounces into the queue that NB> processing bounces becomes slower than the rate at which new NB> bounces arrive. Then the bounce-handler is permanently NB> screwed. I don't think we can correlate your outgoing queue draining behavior with any supposed behavior of the internal bounce queue draining. -Barry From chuqui@plaidworks.com Tue May 28 02:55:16 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Mon, 27 May 2002 18:55:16 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558988 ] bad performance for big queue dirs In-Reply-To: <15602.34331.731926.488668@anthem.wooz.org> Message-ID: On 5/27/02 12:16 PM, "Barry A. Warsaw" wrote: > NB> Now the welcome messages are going out, at a rate of one > NB> message every 6.6 seconds. This is on inexpensive hardware (a > NB> Cobalt RaQ3) but the server is otherwise idle. > There are a lot of unknowns here though. For example, we don't know > if your rate limits are caused by MTA or network throttles. If it's a cobalt, ti's probably sendmail. If it's sendmail, it's probably the DNS-on-accept delays that sendmail has (unless you turn on deliverymode=defer, which disables relay checks). So I'm willing to bet there's a lot of DNS delay here. You can get around this by setting up a special incoming port attached only to localhost so that nobody else can use it, and then you can use the defer mode on that port safely, and speed things up hugely. Then you need to look at disk I/O and whether you're MTA is thrashing because of access contention on the mqueeu directory(s). I'd put the chance of qfile issues really low on the list of things to check here. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ IMHO: Jargon. Acronym for In My Humble Opinion. Used to flag as an opinion something that is clearly from context an opinion to everyone except the mentally dense. Opinions flagged by IMHO are actually rarely humble. IMHO. (source: third unabridged dictionary of chuqui-isms). From noreply@sourceforge.net Tue May 28 03:17:50 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 27 May 2002 19:17:50 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558633 ] Blocked queue after fight with Majordomo Message-ID: Bugs item #558633, was opened at 2002-05-21 08:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id=103 Category: mail delivery Group: 2.0.x >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nigel Metheringham (nigel) Assigned to: Nobody/Anonymous (nobody) Summary: Blocked queue after fight with Majordomo Initial Comment: On Mailman 2.0.8 (was honestly going to upgrade today!). It appears that a couple of messages were boucing between the mailman request addresses and a Majordomo server, with more error transcript being added to the message on each bounce. This then appeared to completely block the qrunner. Removing the 2 huge messages from the qfiles directory fixed it. Broken message qfiles attached. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-27 22:17 Message: Logged In: YES user_id=12800 I have implemented something like what Norbert suggested for MM2.1b3. I won't fix this for MM2.0.x. ---------------------------------------------------------------------- Comment By: Donal Hunt (redgiant) Date: 2002-05-22 11:40 Message: Logged In: YES user_id=551025 It actually gets worse! I finally figured out what has been crashing my machine for the past few days... and it's related to this bug i think. To reproduce: Create a moderated mailing list. eg test@hostanme.com Send a mail from your mailman user (eg su to mailman id and type: echo "test" | mail -s "test" test@hostname.com (where test@hostname.com is your moderated mailing list)) The mail gets sent to the mailing list and held for approval (mailman@hostname.com isn't a subscriber). A message gets sent back to mailman@hostname.com saying the message is held for approval (which mailman tries to post to the mailman list). At this stage stuff starts to stop working on the machine (smtp, telnet and syslogd mainly). What I've got from stracing syslogd (I originally thought it was a syslogd problem) and a mail from root are below: The thing is not that mailman is going to be sending mails to lists locally, but more someone could spoof a mail and DOS your machine. not nice!!! From what I've seen (evidence below) - there isn't a fight between the two lists 0 but i may be wrong. Quick fix: set "respond_to_post_requests" to No. System info: Suse Linux 7.0, Syslogd 1.3-3, Mailman 2.1b (cvs - may 9th) If this has been fixed already or is a seperate bug I apologise in advance for the long comment. ----------------------------------------------------------------------------------------------- : Command died with status 1: "/usr/local/mailman/mail/wrapper post mailman" Reporting-MTA: dns; hostname.dcu.ie Arrival-Date: Wed, 22 May 2002 16:02:45 +0100 (IST) Final-Recipient: rfc822; mailman@hostname.dcu.ie Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; Command died with status 1: "/usr/local/mailman/mail/wrapper post mailman" Received: from hostname.dcu.ie (localhost [127.0.0.1]) by hostname.dcu.ie (Postfix) with ESMTP id DB02D5DFEA for ; Wed, 22 May 2002 16:02:45 +0100 (IST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Your message to Test2 awaits moderator approval From: test2-bounces@hostname.dcu.ie To: mailman@hostname.dcu.ie Message-ID: Date: Wed, 22 May 2002 16:02:44 +0100 X-BeenThere: test2@hostname.dcu.ie X-Mailman-Version: 2.1b2+ Precedence: bulk List-Id: X-List-Administrivia: yes Sender: test2-bounces@hostname.dcu.ie Errors-To: test2-bounces@hostname.dcu.ie ----------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------- writev(1, [{"May 22 02:36:40", 15}, {" ", 1}, {"hostname", 7}, {" ", 1}, {"local[6728]: fatal: execvp /usr/"..., 85}, {"\r\n", 2}], 6) = ?ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) --- time(NULL) = 1022032087 rt_sigaction(SIGALRM, {0x405304, [], SA_RESTART}, {0x405304, [], SA_RESTART}, 8) = 0 alarm(30) = 0 sigreturn() = ? (mask now []) writev(1, [{"May 22 02:36:40", 15}, {" ", 1}, {"hostname", 7}, {" ", 1},{"local[6728]: fatal: execvp /usr/"..., 85}, {"\r\n", 2}], 6) = ?ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) --- time(NULL) = 1022032117 rt_sigaction(SIGALRM, {0x405304, [], SA_RESTART}, {0x405304, [],SA_RESTART}, 8) = 0 alarm(30) = 0 sigreturn() = ? (mask now []) writev(1, [{"May 22 02:36:40", 15}, {" ", 1}, {"linux28", 7}, {" ", 1}, {"local[6728]: fatal: execvp /usr/"..., 85}, {"\r\n", 2}], 6 References: Message-ID: <200205272301.58914.philb@philb.us> Why is this being repeatedly mailed over and over again, redundantly? On Monday 27 May 2002 10:17 pm, noreply@sourceforge.net wrote: > Bugs item #558633, was opened at 2002-05-21 08:01 > You can respond by visiting: > http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&gr >oup_id=103 > > Category: mail delivery > Group: 2.0.x > > >Status: Closed > >Resolution: Fixed > > Priority: 5 > Submitted By: Nigel Metheringham (nigel) > Assigned to: Nobody/Anonymous (nobody) > Summary: Blocked queue after fight with Majordomo > > Initial Comment: > On Mailman 2.0.8 (was honestly going to upgrade today!). > > It appears that a couple of messages were boucing > between the mailman request addresses and a Majordomo > server, > with more error transcript being added to the message > on each bounce. This then appeared to completely > block the qrunner. Removing the 2 huge messages > from the qfiles directory fixed it. > > > Broken message qfiles attached. > > > --------------------------------------------------------------------- >- > > >Comment By: Barry A. Warsaw (bwarsaw) > > Date: 2002-05-27 22:17 > > Message: > Logged In: YES > user_id=12800 > > I have implemented something like what Norbert suggested for > MM2.1b3. I won't fix this for MM2.0.x. > > --------------------------------------------------------------------- >- > > Comment By: Donal Hunt (redgiant) > Date: 2002-05-22 11:40 > > Message: > Logged In: YES > user_id=551025 > > It actually gets worse! > I finally figured out what has been crashing my machine for the past > few days... and it's related to this bug i think. > > To reproduce: > > Create a moderated mailing list. eg test@hostanme.com > Send a mail from your mailman user (eg su to mailman id and type: > > echo "test" | mail -s "test" test@hostname.com (where > test@hostname.com is your moderated mailing list)) > > The mail gets sent to the mailing list and held for approval > (mailman@hostname.com isn't a subscriber). A message gets sent back > to mailman@hostname.com saying the message is held for approval > (which mailman tries to post to the mailman list). > > At this stage stuff starts to stop working on the machine (smtp, > telnet and syslogd mainly). What I've got from stracing syslogd (I > originally thought it was a syslogd problem) and a mail from root are > below: > > The thing is not that mailman is going to be sending mails to lists > locally, but more someone could spoof a mail and DOS your machine. > not nice!!! From what I've seen (evidence below) - there isn't a > fight between the two lists 0 but i may be wrong. > > Quick fix: set "respond_to_post_requests" to No. > > System info: Suse Linux 7.0, Syslogd 1.3-3, Mailman 2.1b (cvs - may > 9th) > > If this has been fixed already or is a seperate bug I apologise in > advance for the long comment. > > --------------------------------------------------------------------- >-------------------------- : Command died > with status 1: > "/usr/local/mailman/mail/wrapper post mailman" > > > > > Reporting-MTA: dns; hostname.dcu.ie > Arrival-Date: Wed, 22 May 2002 16:02:45 +0100 (IST) > > Final-Recipient: rfc822; mailman@hostname.dcu.ie > Action: failed > Status: 5.0.0 > Diagnostic-Code: X-Postfix; Command died with status 1: > "/usr/local/mailman/mail/wrapper post mailman" > > > > > Received: from hostname.dcu.ie (localhost [127.0.0.1]) > by hostname.dcu.ie (Postfix) with ESMTP id DB02D5DFEA > for ; Wed, 22 May 2002 16:02:45 > +0100 (IST) MIME-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > Subject: Your message to Test2 awaits moderator approval > From: test2-bounces@hostname.dcu.ie > To: mailman@hostname.dcu.ie > Message-ID: > Date: Wed, 22 May 2002 16:02:44 +0100 > X-BeenThere: test2@hostname.dcu.ie > X-Mailman-Version: 2.1b2+ > Precedence: bulk > List-Id: > X-List-Administrivia: yes > Sender: test2-bounces@hostname.dcu.ie > Errors-To: test2-bounces@hostname.dcu.ie > --------------------------------------------------------------------- >-------------------------- > > --------------------------------------------------------------------- >-------------------------- writev(1, [{"May 22 02:36:40", 15}, {" ", > 1}, {"hostname", 7}, {" ", 1}, {"local[6728]: fatal: execvp > /usr/"..., 85}, {"\r\n", 2}], 6) = ?ERESTARTSYS (To be restarted) > --- SIGALRM (Alarm clock) --- > time(NULL) = 1022032087 > rt_sigaction(SIGALRM, {0x405304, [], SA_RESTART}, {0x405304, [], > SA_RESTART}, 8) = 0 alarm(30) = 0 > sigreturn() = ? (mask now []) > writev(1, [{"May 22 02:36:40", 15}, {" ", 1}, {"hostname", 7}, {" ", > 1},{"local[6728]: fatal: execvp /usr/"..., 85}, {"\r\n", 2}], 6) = > ?ERESTARTSYS (To be restarted) > --- SIGALRM (Alarm clock) --- > time(NULL) = 1022032117 > rt_sigaction(SIGALRM, {0x405304, [], SA_RESTART}, {0x405304, > [],SA_RESTART}, 8) = 0 alarm(30) = 0 > sigreturn() = ? (mask now []) > writev(1, [{"May 22 02:36:40", 15}, {" ", 1}, {"linux28", 7}, {" ", > 1}, {"local[6728]: fatal: execvp /usr/"..., 85}, {"\r\n", 2}], 6 > --------------------------------------------------------------------- >-------------------------- > > --------------------------------------------------------------------- >- > > Comment By: Barry A. Warsaw (bwarsaw) > Date: 2002-05-21 22:38 > > Message: > Logged In: YES > user_id=12800 > > Norbert Bollow gives this very good idea: > > Rate limiting can do a lot to prevent things from getting > out of hand. For example, respond at most ten times to > essentially the same request from the same email address. > > On any given day, when Mailman gets the tenth message from the > same email address without valid commands, it could reply "This > is the tenth message of this type today from you. It order to > avoid problems like mail loops between email robots, any further > messages of this type will be ignored today. Please try again > tomorrow." And then any further messages from that address with > no valid commands will be just discarded. > > Similarly, Mailman would reply only to ten subscription requests > for the same list from the same user on any given day. And only > to ten unsubscription requests for the same list from the same > user on any given day. And only to ten requests to change the > subscription options in the same way. Etc. > > Since most loops (with the exception of some bounce loops) > iterate more quickly than ten times per day, this will kill most > loops between robots before they create serious problems. > > > --------------------------------------------------------------------- >- > > Comment By: Barry A. Warsaw (bwarsaw) > Date: 2002-05-21 16:47 > > Message: > Logged In: YES > user_id=12800 > > Heh, I think this is a general problem when you get two > email robots talking to each other! In MM2.1cvs the robot > will refuse to respond to a message marked Precedence: > bulk|junk|list -- but it looks like that wouldn't have even > helped in this case (since the Majordomo server isnt' > setting that header ;/ ) > > The only other solution I can think of is to add a config > variable which is a blacklist of known addresses (regexps) > that Mailman should not respond too. You'd still get into > the robot infloop the first time, but at least you'd have a > hope of avoiding subsequent replybot storms for the same > address. > > > --------------------------------------------------------------------- >- > > Comment By: Nigel Metheringham (nigel) > Date: 2002-05-21 08:03 > > Message: > Logged In: YES > user_id=31288 > > and other file > > --------------------------------------------------------------------- >- > > You can respond by visiting: > http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&gr >oup_id=103 > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman-21/listinfo/mailman-developers From barry@zope.com Tue May 28 04:16:25 2002 From: barry@zope.com (Barry A. Warsaw) Date: Mon, 27 May 2002 23:16:25 -0400 Subject: [Mailman-Developers] [ mailman-Bugs-558633 ] Blocked queue after fight with Majordomo References: <200205272301.58914.philb@philb.us> Message-ID: <15602.63113.984700.154399@anthem.wooz.org> >>>>> "PB" == Phil Barnett writes: PB> Why is this being repeatedly mailed over and over again, PB> redundantly? Check the messages carefully. Each new copy should have something different, a new comment, a changed status, etc. -Barry From noreply@sourceforge.net Tue May 28 05:55:42 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 27 May 2002 21:55:42 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-560127 ] qrunner segfaults on specific message Message-ID: Bugs item #560127, was opened at 2002-05-24 10:29 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560127&group_id=103 Category: mail delivery >Group: Unreproducible >Status: Closed Resolution: None Priority: 5 Submitted By: Douglas Paul (dwpaul) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner segfaults on specific message Initial Comment: I received the following bounce message to the -admin account on a mailing list I run. When qrunner tries to process this message, it segfaults, and leaves its locks. When subsequent qrunner passes occur, it just complains that it can't get the lock. Removing the locks just causes it to segfault again. The only solution I've found it to simply remove the message from the queue. This originally happened with Mailman 2.0.8, but I upgraded to 2.0.11 and it still occurred. I was able to reproduce the problem by mailing the contents of the message to the -admin address again. The .msg and .db files are attached. Version Info: Mailman 2.0.8 / 2.0.11 Python 1.5.2 (#1, Jan 19 2000, 19:01:15) [GCC 2.95.1 19990816 (release)] on linux-armv4l Linux elemental 2.4.17-rmk5 #7 Mon Feb 18 18:12:50 EST 2002 armv4l unknown Sendmail 8.9.3 ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-28 00:55 Message: Logged In: YES user_id=12800 The backtrace is useless because the stack is trashed., but thanks anyway! :) I'm not sure what to blame, although i have a sneaking suspicion that it's bugs in Python 1.5.2's pickle or marshal code. I can't reproduce it with the files you've given, so I can't be sure. At this point, upgrading to Python 2.2.1 is probably your best bet. If you still get crashes after the upgrade, please open a new bug report. You'll definitely want to use MM2.0.11 with Python 2.2.1. ---------------------------------------------------------------------- Comment By: Douglas Paul (dwpaul) Date: 2002-05-25 12:20 Message: Logged In: YES user_id=552731 Unfortunately, my Python doesn't have any symbols, but here's what I get from a backtrace. It looks to me like it's trying to allocate a lot of memory, and a bug in glibc is making it crash: (gdb) backtrace #0 chunk_alloc (ar_ptr=0x4015bbe4, nb=40) at malloc.c:2814 #1 0x400c86fc in __libc_malloc (bytes=1075166260) at malloc.c:2643 #2 0xbfffdc10 in ?? () I also get this strange message, too: warning: core file may not match specified executable file. Core was generated by `'. Program terminated with signal 11, Segmentation fault. This system was running with glibc 2.1.2. I tried running it on in a chrooted environment I'm building to upgrade my system (glibc 2.2.5, Python 2.2) and it does work fine. Unless there's any other information you'd like me to find, I think I'll just upgrade my Python to 2.2. It's definitely not a bug in Mailman. Thanks for the quick response. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-25 03:14 Message: Logged In: YES user_id=12800 I've no idea why you get a core dump, but by definition it must be a bug in Python. No Python script should ever be able to crash the interpreter. I can't find anything wrong with the files you uploaded. Is there any chance you can 1) run gdb on the resulting core file to get a stack trace; 2) upgrade your Python to something newer than 1.5.2? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=560127&group_id=103 From noreply@sourceforge.net Tue May 28 05:58:21 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 27 May 2002 21:58:21 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-559558 ] can't make moderated list unmoderated Message-ID: Bugs item #559558, was opened at 2002-05-23 06:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559558&group_id=103 Category: security/privacy Group: 2.0.x >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Benjamin Geer (beroul) Assigned to: Nobody/Anonymous (nobody) Summary: can't make moderated list unmoderated Initial Comment: With Mailman 2.0.8, I made a list moderated (by setting "Must posts be approved by an administrator?" in Privacy Options) to "Yes". A few weeks later, I changed my mind and set this to "No". However, whenever someone tries to post to the list, I still receive a message from Mailman, saying that the posting requires approval (the subject line says "Posting to a restricted list by sender requires approval"). ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-28 00:58 Message: Logged In: YES user_id=12800 Check the member_postings_only and postings variables for other options that could be affecting your settings. I'm closing this bug report because the list is likely working as expected. However, in MM2.0.x the interaction of these three variables is definitely confusing, so for more help please contact mailman-users@python.org. Note that this have greatly improved in MM2.1. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559558&group_id=103 From noreply@sourceforge.net Tue May 28 05:59:21 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 27 May 2002 21:59:21 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-559417 ] "arch" utility spews output Message-ID: Bugs item #559417, was opened at 2002-05-22 19:56 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559417&group_id=103 Category: Pipermail Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Ian Clarke (sanity) Assigned to: Nobody/Anonymous (nobody) >Summary: "arch" utility spews output Initial Comment: When I run the "arch" utility to rebuild my archives, it prints out loads of "figuring article archives", which is somewhat confusing to the new user. Would it be possible to have a more sensible status report so that people aren't confused when they rebuild a large archive? ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-28 00:59 Message: Logged In: YES user_id=12800 What's confusing about these messages? Is it just the sheer volume of output that bothers you? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=559417&group_id=103 From noreply@sourceforge.net Tue May 28 06:00:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 27 May 2002 22:00:19 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-558988 ] bad performance for big queue dirs Message-ID: Bugs item #558988, was opened at 2002-05-21 23:15 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558988&group_id=103 >Category: mail delivery >Group: 2.1 beta >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Norbert Bollow (bollow) Assigned to: Nobody/Anonymous (nobody) Summary: bad performance for big queue dirs Initial Comment: Many filesystems (e.g. the popular ext2) have horrible performance when there are many files in the same directory. The queue system should be modified to avoid this situation. As a test case, try adding 20,000 test address in such a way that Mailman will try to send a welcome message to each of them. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-28 01:00 Message: Logged In: YES user_id=12800 Closing as won't fix for MM2.1. If it's a valid problem backed up by more experience and research, we'll address it in subsequent releases. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-22 22:08 Message: Logged In: YES user_id=12800 I think you have a valid complaint, but I'm loathe to change something so fundamental this late in the game. I'll leave this bug report open because if we can recommend some other, more big queue friendly filesystem (reiserfs? I don't know) then we should document this. Don't MTAs have the same problem? Do they all implement multiple subdirectories for queued messages? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558988&group_id=103 From noreply@sourceforge.net Tue May 28 06:02:04 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 27 May 2002 22:02:04 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-557131 ] newlist alias output error Message-ID: Bugs item #557131, was opened at 2002-05-17 06:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=557131&group_id=103 >Category: command line scripts >Group: 2.0.x >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Neil Darlow (ndarlow) Assigned to: Nobody/Anonymous (nobody) Summary: newlist alias output error Initial Comment: I had a problem with Mailman-2.0.10 not responding to confirmation e-mail submissions. I found that there was no newline between newlist's -request and -owner aliases output (they were concatenated). This led to anything sent to the -request alias being silently ignored. Separating the aliases restored correct operation of confirmation processing. Regards, Neil Darlow M.Sc. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-28 01:02 Message: Logged In: YES user_id=12800 Probably a function of your terminal as well. I tend to cut and paste with XEmacs so it's never a problem for me. :) MM2.1 should be better since (hopefully) you won't have to actually cut and paste the output. ---------------------------------------------------------------------- Comment By: Neil Darlow (ndarlow) Date: 2002-05-17 06:25 Message: Logged In: YES user_id=39443 On further investigation this doesn't appear to be caused by newlist but copy'n'paste of the aliases output. It appears that if the -request alias is exactly one screen width and copy'n'paste is performed on the aliases then aliases are concatenated. It's just something to watch out for. Regards, Neil Darlow M.Sc. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=557131&group_id=103 From noreply@sourceforge.net Tue May 28 06:05:52 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 27 May 2002 22:05:52 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-556260 ] err in INSTALL for qrunner autostarting Message-ID: Bugs item #556260, was opened at 2002-05-15 05:07 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=556260&group_id=103 Category: documentation Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Dario Lopez-Kästen (dlkita) Assigned to: Nobody/Anonymous (nobody) Summary: err in INSTALL for qrunner autostarting Initial Comment: There is what seems to be an error in the INSTALL document, the section that starts on line 327, about starting mailman automatically on reboot: around line 348, the document states: "For Unixes that don't support chkconfig, simply copy misc/mailman as above, then set up the following symbolic links, again as root: % cp misc/mailman /etc/init.d % cd /etc/rc.d/rc0.d ..... " The following is in error: - there is no misc/ directory in the installa location - if there where, following the instructions would undo the copying of scripts/mailman to /etc/init.d - the wording is somewhat ambiguous and may lead to misunderstanding. I propose the following change to the documentation: "For Unixes that don't support chkconfig, simply copy scripts/mailman as above: % cp scripts/mailman /etc/init.d/mailman then set up the following symbolic links, again as root: % cd /etc/rc.d/rc0.d ..... " ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-28 01:05 Message: Logged In: YES user_id=12800 Thanks for the suggestion. I've made the change to the INSTALL file for MM2.1b3. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=556260&group_id=103 From noreply@sourceforge.net Tue May 28 06:08:28 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 27 May 2002 22:08:28 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-556250 ] Icons not copied properly on new install Message-ID: Bugs item #556250, was opened at 2002-05-15 04:35 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=556250&group_id=103 Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Dario Lopez-Kästen (dlkita) Assigned to: Nobody/Anonymous (nobody) Summary: Icons not copied properly on new install Initial Comment: Using 2.1b2 on a minimal Solaris 8 installation, the install script fails to properly copy the icons from the misc dir in the source to the icons dir in the mailman install location. This is reproduceable (I installed 4 times). Looking in the Makefile gave no clues, mostly due to ignorance of makeifiles on my part. Haven't seen this mentioned anywhere, so I am not sure if this is my particular setup or if it is a general problem. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-28 01:08 Message: Logged In: YES user_id=12800 I can't reproduce this on my Linux system. Could there be some assumption of GNU make in the misc/Makefile.in? But if so, wouldn't that affect other targets? Can anybody else on Solaris 8 verify this bug, please? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=556250&group_id=103 From noreply@sourceforge.net Tue May 28 06:18:11 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 27 May 2002 22:18:11 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-555065 ] missing space Message-ID: Bugs item #555065, was opened at 2002-05-12 06:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=555065&group_id=103 Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Accepted Priority: 4 Submitted By: Simone Piunno (pioppo) Assigned to: Nobody/Anonymous (nobody) Summary: missing space Initial Comment: I've a list with subscribe_policy = 1 (confirmation requested) and private_roster = 1 (only for subscribed people) When browsing the listinfo page from the web, I can see the following text: You will be sent email requesting confirmation, to prevent others from gratuitously subscribing you.This is also sa private list, which means that the list of members is not available to non-members. Note the missing space after the middle period. Attached is a proposed one-liner patch. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-28 01:18 Message: Logged In: YES user_id=12800 Thanks! ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=555065&group_id=103 From noreply@sourceforge.net Tue May 28 06:52:35 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 27 May 2002 22:52:35 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-554290 ] request: invite text and message subject Message-ID: Bugs item #554290, was opened at 2002-05-09 17:59 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554290&group_id=103 Category: (un)subscribing Group: 2.1 beta >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Christopher Kolar (ckolar) Assigned to: Nobody/Anonymous (nobody) Summary: request: invite text and message subject Initial Comment: Glad to see the invite functionality appearing in 2.1 I have two comments. 1. I would like to be able to invite people and include a custome text message (as on yahoogroups). That way I can invite them and remind them "I am inviting you to join this list because you gave me your email address at the conference and you said you might be interested." 2. The subject line of the invitation makes it look a lot like spam. I would make it something like: Subject: Invitation to join LISTNAME@HOSTNAME - confirm I have see this done where it is padded with spaces so that the ugly confirmation code will not appear in the window of most email readers, the invitee doesn't really need to sent it anyway. The link is awesome thought. Thanks for adding this. --chris ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-28 01:52 Message: Logged In: YES user_id=12800 1. I have a hack to prepend a custom message on invitations (and subscriptions as it turns out). I'll check this in shortly. 2. I'm not going to change this, but I suggest setting VERP_CONFIRMATIONS to 1 in mm_cfg.py. In that case, the subject will be much more human friendly, while the envelope sender actually contains the magic confirmation cookie. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=554290&group_id=103 From noreply@sourceforge.net Tue May 28 07:11:36 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 27 May 2002 23:11:36 -0700 Subject: [Mailman-Developers] [ mailman-Patches-502668 ] new mlist option send_reminder_frequency Message-ID: Patches item #502668, was opened at 2002-01-12 13:11 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=502668&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Matthias Klose (doko) Assigned to: Nobody/Anonymous (nobody) Summary: new mlist option send_reminder_frequency Initial Comment: For announcement mailing lists, which get only one or two mails each year, a monthly password reminder is too much. The list administrator can toggle the send_reminder once each year, but that's error prone. The attached patch adds a list specific option send_reminder_frequency with the values monthly (default), yearly and quaterly. the mailpasswds script is changed to ask for this option. I didn't yet figure out, how to update existing lists ... ---------------------------------------------------------------------- >Comment By: Matthias Klose (doko) Date: 2002-05-28 06:11 Message: Logged In: YES user_id=60903 Here is the updated alternative patch not introducing a new option, but extending the send_reminders option (updated to current CVS). ---------------------------------------------------------------------- Comment By: Matthias Klose (doko) Date: 2002-01-16 20:08 Message: Logged In: YES user_id=60903 Here is an alternative patch not introducing a new option, but extending the send_reminders option. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=502668&group_id=103 From noreply@sourceforge.net Tue May 28 10:06:20 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 28 May 2002 02:06:20 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-457242 ] Search Archives Message-ID: Feature Requests item #457242, was opened at 2001-08-31 14:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=457242&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Search Archives Initial Comment: How about a search feature for the archives? Len Leshin ---------------------------------------------------------------------- Comment By: Kenneth Porter (scratchmonkey) Date: 2002-05-28 09:06 Message: Logged In: YES user_id=29401 A related discussion came up on the Evolution list (http://www.ximian.com/) and it was suggested that a simple read-only NNTP server allow access to the archives. NNTP defines some server-side search facilities that could facilitate this. An existing NNTP server might already be able to do this, in which case what's needed is a cookbook article on how to set it up. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=457242&group_id=103 From danovaro@publinet.it Tue May 28 15:09:34 2002 From: danovaro@publinet.it (stefano danovaro) Date: Tue, 28 May 2002 16:09:34 +0200 (CEST) Subject: [Mailman-Developers] problems subscribing via some webmail interface Message-ID: <1022594974.3cf38f9e2139f@webmail.publinet.it> hello, I have mailman version 2.1b2+. Some users that use some webmail interfaces are experiencing problems with the subscription process. It seems that the reply to the confirmation request message arrives to mailman encoded with base64 and so the subscription fails. Is there a solution ? thanks, Stefano From nb@cisto.com Tue May 28 15:46:49 2002 From: nb@cisto.com (Norbert Bollow) Date: Tue, 28 May 2002 16:46:49 +0200 Subject: [Mailman-Developers] [ mailman-Bugs-558988 ] bad performance for big queue dirs In-Reply-To: (message from Chuq Von Rospach on Mon, 27 May 2002 18:55:16 -0700) References: Message-ID: <200205281446.g4SEkn703942@quill.local> Chuq Von Rospach wrote: > > NB> Now the welcome messages are going out, at a rate of one > > NB> message every 6.6 seconds. This is on inexpensive hardware (a > > NB> Cobalt RaQ3) but the server is otherwise idle. > > > There are a lot of unknowns here though. For example, we don't know > > if your rate limits are caused by MTA or network throttles. Trust me, they aren't. Whenever Mailman would pass one of the messages to the MTA, it would go out almost instantanously. > If it's a cobalt, it's probably sendmail. It's qmail with a couple of patches, including big_concurrency, which isn't relevant for this test because the MTA gets one message per 6.6 seconds only. > Then you need to look at disk I/O and whether you're MTA is thrashing > because of access contention on the mqueeu directory(s). I'd put the chance > of qfile issues really low on the list of things to check here. Well, I deleted those almost 40000 files from welcome messages (as I didn't have 36 hours of patience :-), added 20000 real subscribers (_witout_sending_them_welcome_messages_) and it all works ok now. This issue is certainly related to the size of Mailman's queues, in this case the virgin queue. If it's not a matter of filesystem (in)efficiency, then it must be Python or Mailman doing something that scales extremely badly with queue size. Greetings, Norbert. -- A founder of the http://DotGNU.org project and Steering Committee member Norbert Bollow, Weidlistr.18, CH-8624 Gruet (near Zurich, Switzerland) Tel +41 1 972 20 59 Fax +41 1 972 20 69 http://norbert.ch List hosting with GNU Mailman on your own domain name http://cisto.com From jra@baylink.com Tue May 28 16:54:00 2002 From: jra@baylink.com (Jay R. Ashworth) Date: Tue, 28 May 2002 11:54:00 -0400 Subject: [Mailman-Developers] [ mailman-Bugs-558988 ] bad performance for big queue dirs In-Reply-To: <15602.34331.731926.488668@anthem.wooz.org>; from "Barry A. Warsaw" on Mon, May 27, 2002 at 03:16:43PM -0400 References: <1022142837.7936.9.camel@gaspode.localnet> <200205231642.g4NGgIx18033@quill.local> <15602.34331.731926.488668@anthem.wooz.org> Message-ID: <20020528115400.24976@scfn.thpl.lib.fl.us> On Mon, May 27, 2002 at 03:16:43PM -0400, Barry A. Warsaw wrote: > There are a lot of unknowns here though. For example, we don't know > if your rate limits are caused by MTA or network throttles. If your > server is idle then i/o is suspect but we don't know if creating more > outgoing qrunner processes would help you (by splitting up the queue > hash space among parallel processes). Is your MTA spooling to the > same filesystem that Mailman is spooling off of? If your MTA is > throttling and it's running synchronously with the outgoing qrunner > then Mailman may just be sitting around blocked on output to your > MTA. Or maybe your disk subsystem can't take the pressure of Mailman > reading off of it while your MTA is writing to it. What happens if > you put them on different disks and/or controllers? And what effect > does using some other filesystem (e.g. reiserfs) have on throughput? Hmmm... suggestion for future point releases: having some instrumentation that would make it easier to decide where the throttles *are* would be Really Useful. Mailman has lots of *configuration* knobs, but few *runtime* knobs, that I've seen, and almost *no* meters. It's a Subsystem; it needs that stuff. Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") From jra@baylink.com Tue May 28 16:59:37 2002 From: jra@baylink.com (Jay R. Ashworth) Date: Tue, 28 May 2002 11:59:37 -0400 Subject: [Mailman-Developers] [ mailman-Bugs-558633 ] Blocked queue after fight with Majordomo In-Reply-To: <15602.63113.984700.154399@anthem.wooz.org>; from "Barry A. Warsaw" on Mon, May 27, 2002 at 11:16:25PM -0400 References: <200205272301.58914.philb@philb.us> <15602.63113.984700.154399@anthem.wooz.org> Message-ID: <20020528115937.55951@scfn.thpl.lib.fl.us> On Mon, May 27, 2002 at 11:16:25PM -0400, Barry A. Warsaw wrote: > >>>>> "PB" == Phil Barnett writes: > PB> Why is this being repeatedly mailed over and over again, > PB> redundantly? > > Check the messages carefully. Each new copy should have something > different, a new comment, a changed status, etc. Yeah, and unlike BugZilla, sourceFnords' thing puts the mods at the *bottom* of the message... Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") From barry@zope.com Tue May 28 17:01:38 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 28 May 2002 12:01:38 -0400 Subject: [Mailman-Developers] [ mailman-Bugs-558988 ] bad performance for big queue dirs References: <1022142837.7936.9.camel@gaspode.localnet> <200205231642.g4NGgIx18033@quill.local> <15602.34331.731926.488668@anthem.wooz.org> <20020528115400.24976@scfn.thpl.lib.fl.us> Message-ID: <15603.43490.20601.27780@anthem.wooz.org> >>>>> "JRA" == Jay R Ashworth writes: JRA> Hmmm... suggestion for future point releases: having some JRA> instrumentation that would make it easier to decide where the JRA> throttles *are* would be Really Useful. Mailman has lots of JRA> *configuration* knobs, but few *runtime* knobs, that I've JRA> seen, and almost *no* meters. JRA> It's a Subsystem; it needs that stuff. I couldn't agree more if you paid me to add it. :) -Barry From danny@terweij.nl Wed May 29 00:34:40 2002 From: danny@terweij.nl (Danny Terweij) Date: Wed, 29 May 2002 01:34:40 +0200 Subject: [Mailman-Developers] Re: HowTo: [Mailman-Users] Cleaning the archive by a list-owner References: <006a01c1f99b$8286bd40$1e00a8c0@poema.yi.org> <200205121801.OAA04685@salsa.haht.com> Message-ID: <009701c206a0$3e1cbd00$1e00a8c0@onsnet.org> Jon Carnes Wrote a while ago: Hi, Jon, all readers... I did work something out, but it is for me very difficult to create. I deleted my created scripts because it looks ugly and it wont do what i want. When editing the mbox, and there is a new message processed .. it screws up all the stuff. I'll think it is better to use MySQL for storing messages. Then it is easy to create a protected webpage in PHP to read the messages and delete/edit them. And after all doing a new bin/arch listname to read the messages from the sql database and generate the html output.... I am now not seeing any clue to create a webpage/script for deleting/editing messages. (Because i do not know where to start). My mbox files are over 300mb in size. It is not easy to read the file in and proccess some stuff in the file .. my linux box is not fast enough and it has 96mb memory and 172mb swap size. So i need another concept. I am not a good programmer, so please give me more example code to play with. > Straight Mailman (unmodified) won't let you do this. > I have some simple scripts that are password protected that do it for > my admins. They were a piece of cake to write. Your sysadmin would > have to install them for you. > For the sysadmin to modify the archives... > - edit ~mailman/archives/private/.mbox/.mbox > - delete/modify any emails you want (normally delete older mail) > - delete the old archive html files... > rm -rf ~mailman/archives/private//.* > - recreate the archive html files... > cd ~mailman > bin/arch \ > archives/private/.mbox/.mbox > The email for the list is stored in mbox format (straight text) in a > file in the archive directory. You can easily edit this mailbox and > then re-run the archives so that your changes are pushed out to the > HTML area. > If you want to find the top of an email based on date: > F_DATE="12 May 2002" > grep -n "^From: " | grep $F_DATE | top -1 > This gives you first line of an email that came in on that date - and > it prints out the line number in the file for that line... > To print out a file starting at a given line and continueing on to > the end: F_NAME="~mailman/archive/private/mylist.mbox/mylist.mbox > START=4093 > sed -n "$START, \$ p" $F_NAME > $F_NAME.bak > === > There are several ways to automate this, the easiest is via email, > but html is not too much harder - especially if you are willing to > allow simple CGI's. I leave this up to your imagination! Take care, > > Jon > > --- Original Message: Sunday 12 May 2002 05:58 am --- >> Hi, >> >> How can a list-owner clean out the archive? Delete messages? >> When not, can the developers program it? >> It would be nice. >> >> >> Groetjes Danny Terweij From jpmg@eng.cam.ac.uk Wed May 29 11:19:25 2002 From: jpmg@eng.cam.ac.uk (jpmg@eng.cam.ac.uk) Date: Wed, 29 May 2002 11:19:25 +0100 Subject: [Mailman-Developers] (2.0.11) Mailman/Cgi/admindb.py should notice CGIEXT Message-ID: <200205291019.4833@tweedle.eng.cam.ac.uk> *** admindb.py.dist Mon Apr 1 19:47:46 2002 --- admindb.py Wed May 29 11:16:39 2002 *************** *** 43,49 **** link = mm_cfg.DEFAULT_URL if link[-1] <> '/': link = link + '/' ! link = link + 'admin' doc.AddItem(Link(link, 'list of available mailing lists.')) print doc.Format(bgcolor="#ffffff") --- 43,49 ---- link = mm_cfg.DEFAULT_URL if link[-1] <> '/': link = link + '/' ! link = link + Utils.ScriptURL('admin') doc.AddItem(Link(link, 'list of available mailing lists.')) print doc.Format(bgcolor="#ffffff") From noreply@sourceforge.net Wed May 29 21:15:24 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 29 May 2002 13:15:24 -0700 Subject: [Mailman-Developers] [ mailman-Patches-562061 ] Poor grammar: templates/subscribeack.txt Message-ID: Patches item #562061, was opened at 2002-05-29 21:15 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=562061&group_id=103 Category: None Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Dominic Hargreaves (therealdom) Assigned to: Nobody/Anonymous (nobody) Summary: Poor grammar: templates/subscribeack.txt Initial Comment: This file contains the phrase: "You may also have your password mailed to you automatically off of the Web page noted above." This is incorrect, and should read: "You may also have your password mailed to you automatically from the Web page noted above." The attached trivial patch fixes this. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=562061&group_id=103 From jpmg@eng.cam.ac.uk Thu May 30 12:29:12 2002 From: jpmg@eng.cam.ac.uk (jpmg@eng.cam.ac.uk) Date: Thu, 30 May 2002 12:29:12 +0100 (BST) Subject: [Mailman-Developers] (2.0.11 patch) explicit references to mailman-owner instead of MAILMAN_OWNER Message-ID: <17702.200205301129@tigger.eng.cam.ac.uk> There are a few places where mailman-2.0.11 makes explicit reference to 'mailman-owner' + mlist.host_name where I believe it should use the MAILMAN_OWNER variable (else why bother pretending that the latter is usefully administrator-configurable?). [ I've ignored the one in scripts/answer_majordomo_mail as I don't believe that script can run anyway (does the Utils.SendTextToUser function exist?) ] *** bin/newlist.orig Sat Mar 3 05:58:19 2001 --- bin/newlist Thu May 30 11:23:42 2002 *************** *** 204,214 **** 'admin_url' : mlist.GetScriptURL('admin', absolute=1), 'listinfo_url': mlist.GetScriptURL('listinfo', absolute=1), 'requestaddr' : "%s-request@%s" % (listname, mlist.host_name), ! 'hostname' : mlist.host_name, }) msg = Message.UserNotification( owner_mail, ! 'mailman-owner@' + mlist.host_name, 'Your new mailing list: ' + listname, text) HandlerAPI.DeliverToUser(mlist, msg) --- 204,214 ---- 'admin_url' : mlist.GetScriptURL('admin', absolute=1), 'listinfo_url': mlist.GetScriptURL('listinfo', absolute=1), 'requestaddr' : "%s-request@%s" % (listname, mlist.host_name), ! 'mailman-owner' : mm_cfg.MAILMAN_OWNER, }) msg = Message.UserNotification( owner_mail, ! mm_cfg.MAILMAN_OWNER, 'Your new mailing list: ' + listname, text) HandlerAPI.DeliverToUser(mlist, msg) *** templates/newlist.txt.orig Fri Jun 19 20:37:07 1998 --- templates/newlist.txt Thu May 30 11:23:50 2002 *************** *** 32,35 **** your admin password. You can also use your password to change member's options, including digestification, delivery disabling, etc. ! Please address all questions to mailman-owner@%(hostname)s. --- 32,35 ---- your admin password. You can also use your password to change member's options, including digestification, delivery disabling, etc. ! Please address all questions to %(mailman-owner)s. ------------------------ On a separate note, I _think_ that the email address "mailman@site" is only ever used in one place, namely Mailman/MailCommandHandler.py , where it's purpose doesn't seem noticeably distinct from the MAILMAN_OWNER account. Is there any good reason not to do the following patch, and simplify the installation of mailman such that the only non-list-related alias that it requires is the one specified by MAILMAN_OWNER in the mm_cfg.py file? *** Mailman/MailCommandHandler.py.orig Tue Aug 1 23:03:23 2000 --- Mailman/MailCommandHandler.py Thu May 30 11:27:52 2002 *************** *** 406,413 **** return lists = Utils.list_names() lists.sort() ! self.AddToResponse("\nPublic mailing lists run by mailman@%s" ! % self.host_name, trunc=0) for listname in lists: if listname == self._internal_name: listob = self --- 406,413 ---- return lists = Utils.list_names() lists.sort() ! self.AddToResponse("\nPublic mailing lists run by %s" ! % mm_cfg.MAILMAN_OWNER, trunc=0) for listname in lists: if listname == self._internal_name: listob = self ------------------------- -patrick. From noreply@sourceforge.net Thu May 30 16:50:34 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 30 May 2002 08:50:34 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-553128 ] cant use alternate port Message-ID: Bugs item #553128, was opened at 2002-05-06 22:48 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553128&group_id=103 Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Invalid >Priority: 1 Submitted By: Christopher Donald Wiegand (cdwiegand) Assigned to: Nobody/Anonymous (nobody) Summary: cant use alternate port Initial Comment: I have to use port 81 for my webserver (due to a NAT issue on the firewall, as port 80 is already in use). I have adjusted DEFAULT_URL_HOST, and have also tried adjusting DEFAULT_URL_PATTERN, and in most places this works, however, when a list has it's archive made private, it does not include the :81 I appended to the variable... This *appears* to be a bug with Mailman 2.1b1. Also affects the submit button when you reject/ignore/approve moderated items from the list admin menu. ---------------------------------------------------------------------- >Comment By: Christopher Donald Wiegand (cdwiegand) Date: 2002-05-30 09:50 Message: Logged In: YES user_id=9059 Never mind - I adjusted apache, and it's working fine now :). I guess this was a feature of the virtual hosts. Too bad you can't turn that off... ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=553128&group_id=103 From terri@zone12.com Thu May 30 21:04:05 2002 From: terri@zone12.com (Terri Oda) Date: Thu, 30 May 2002 16:04:05 -0400 Subject: [Mailman-Developers] Adding to the FAQ & other documentation Message-ID: <5.1.0.14.0.20020530153155.02fcf4e0@pop.ncf.carleton.ca> I'm starting to merge in a bunch of old archives to linuxchix's current archives (under 2.0.10), and I ran in to a problem. Searching the mailing lists let me know that I wasn't the only one with the problem, but didn't give me the answer. Here's a good description of the problem from a nice guy who sadly had to tell me he hadn't found the answer either, but there were a decent number of similar stories on the mailing list: http://mail.python.org/pipermail/mailman-users/2002-May/019594.html In my case, it was just refusing to build with the old archives inserted, so I was just keeping the same HTML pages even though the mbox file had been changed. So, recalling that From lines could be a problem, I started going through the big archive file and discovered that right near the beginning, there's a message with two From lines. I remove one, and voila! the entire thing rebuilds. I'm happy now, but in the interest of saving other people some effort and hairpulling... could a few lines about this be added to the FAQ (http://list.org/faq.html, I'd guess) and wherever else it's appropriate? I'd be quite happy to do this myself if someone can tell me how and what I need to do to get access. :) Here's the quickly-written version: --- Q: How do I rebuild the HTML pages for the archives? A: Run /bin/arch to rebuild the HTML. If it says "Pickling archive state into /archives/private//pipermail.pck" but doesn't make any changes, (see http://mail.python.org/pipermail/mailman-users/2002-May/019594.html for a longer description of the problem) you may have a slightly corrupted mbox file which can't be read correctly by the archive generator. Take a look at the mbox file (Typically: /archives/private/.mbox/.mbox) and make sure that each message is separated by one blank line and begins with one and only one line of the form From . --- On the subject of documentation... Mary set this up so that it automatically subs in the appropriate list name to our FAQ. http://www.linuxchix.org/content/docs/faqs/technical.html?listname=grrltalk Has anyone ever thought about having a help page like this set up as part of mailman? I know it'd be nice to believe that the pages are clear enough as is, but I know sometimes a longer explanation can help people out. Terri From danovaro@publinet.it Fri May 31 08:31:51 2002 From: danovaro@publinet.it (stefano danovaro) Date: Fri, 31 May 2002 09:31:51 +0200 (CEST) Subject: [Mailman-Developers] problems subscribing via some webmail interface Message-ID: <1022830311.3cf726e773fa1@webmail.publinet.it> hello, I have mailman version 2.1b2+. Some users that use some webmail interfaces are experiencing problems with the subscription process. It seems that the reply to the confirmation request message arrives to mailman encoded with base64 and so the subscription fails. Is there a solution ? thanks, Stefano From frank@manbox.de Fri May 31 09:15:36 2002 From: frank@manbox.de (frank) Date: Fri, 31 May 2002 10:15:36 +0200 Subject: [Mailman-Developers] aliases and virtuser-support for sendmail Message-ID: Hello, I have no idea of python-coding, but I thought for some experienced person here it should be no problem to add the feature to mailman that it writes also to sendmails' aliases and virtuser-files when setting up a mailing list. I installed mailman version 2.1b2+ and loved this very much because of it's language features. Btw.: I also translated almost completely the German language version (as this was done only half way) and corrected there a lot of bugs. So if somebody wants to have the file - pls. mail me. The only thing to work with mailman would be now that it can write to those files - so that it needs no manual intervention when setting up a mailing list. I would appreciate very much if somebody could help me! Thanks in advance... Frank From dmick@utopia.West.Sun.COM Fri May 31 09:25:19 2002 From: dmick@utopia.West.Sun.COM (Dan Mick) Date: Fri, 31 May 2002 01:25:19 -0700 (PDT) Subject: [Mailman-Developers] aliases and virtuser-support for sendmail Message-ID: <200205310826.g4V8QCOl012652@utopia.West.Sun.COM> > I have no idea of python-coding, but I thought for some experienced person > here it should be no problem to add the feature to mailman that it writes > also to sendmails' aliases and virtuser-files when setting up a mailing > list. See README.SENDMAIL and the contrib/ files it refers to. (This is in MM 2.1, of course). I don't use it, but I'm sure David does, and I'm sure it works. From noreply@sourceforge.net Fri May 31 22:14:50 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 31 May 2002 14:14:50 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-563091 ] digest an option in confirm cgi Message-ID: Bugs item #563091, was opened at 2002-05-31 15:14 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=563091&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Christopher Donald Wiegand (cdwiegand) Assigned to: Nobody/Anonymous (nobody) Summary: digest an option in confirm cgi Initial Comment: I have a list that has the digest option turned off (via the cgi). However, when I confirm a subscription to this list via the cgi link in the email, the page gives me the option of turning digests on (even though it is not an option when first subscribing to the list). Also, I would recommend that on that same confirmation page, the subscribe button be directly below the fields, and the cancel button on the side. I almost accidentally cancelled my confirmation... ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=563091&group_id=103 From jon@latchkey.com Fri May 31 22:54:10 2002 From: jon@latchkey.com (Jon Scott Stevens) Date: Fri, 31 May 2002 14:54:10 -0700 Subject: [Mailman-Developers] problems subscribing via some webmail interface In-Reply-To: <1022830311.3cf726e773fa1@webmail.publinet.it> Message-ID: on 5/31/02 12:31 AM, "stefano danovaro" wrote: > hello, > I have mailman version 2.1b2+. > Some users that use some webmail interfaces are experiencing problems with the > subscription process. It seems that the reply to the confirmation request > message arrives to mailman encoded with base64 and so the subscription fails. > Is there a solution ? > > thanks, > Stefano I have heard several complaints along these lines as well. Even with 2.0.11. Shouldn't mailman just look in the subject? Seems safer. -jon From fwang2@yahoo.com Fri May 31 17:53:07 2002 From: fwang2@yahoo.com (Oliver Wang) Date: Fri, 31 May 2002 09:53:07 -0700 (PDT) Subject: [Mailman-Developers] bin/arch woes in 2.1b2 Message-ID: <20020531165307.79569.qmail@web11206.mail.yahoo.com> Hi, I am testing out 2.1b2 and try importing some mbox with foreign characters by "bin/arch", and it broke down in the middle with following errors. Any ideas what is wrong? thanks /oliver main() File "bin/arch", line 148, in main archiver.processUnixMailbox(fp, Article, start, end) File "/var/mailman/Mailman/Archiver/pipermail.py", line 545, in processUnixMailbox m = mbox.next() File "/usr/lib/python2.2/mailbox.py", line 33, in next return self.factory(_Subfile(self.fp, start, stop)) File "/var/mailman/Mailman/Mailbox.py", line 77, in scrubber return mailbox.scrub(msg) File "/var/mailman/Mailman/Mailbox.py", line 97, in scrub return self._scrubber(self._mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 114, in process url = save_attachment(mlist, part, filter_html=0) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 217, in save_attachment decodedpayload = msg.get_payload(decode=1) File "/var/mailman/pythonlib/email/Message.py", line 162, in get_payload return Utils._bdecode(payload) File "/var/mailman/pythonlib/email/Utils.py", line 66, in _bdecode value = base64.decodestring(s) File "/usr/lib/python2.2/base64.py", line 44, in decodestring return binascii.a2b_base64(s) binascii.Error: Incorrect padding __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com From v.borstlap@firstfind.nl Fri May 31 11:27:28 2002 From: v.borstlap@firstfind.nl (Valentijn Borstlap) Date: Fri, 31 May 2002 12:27:28 +0200 Subject: [Mailman-Developers] Help ! Message-ID: <009701c2088d$c3b0ccb0$0200a8c0@valentijn> Hi, I tested mailman a while ago. But now I don't use it. It seems that my postfix program isn't working ok. Do you have some idea's on how I can uninstall mailman? Thanx in advance! Valentijn Borstlap ----------------------------------------------------------------------- FirstFind E-Consults Schrevenweg 5-17 8024 HB ZWOLLE T: 038-4530752 F: 038-4530761 U: firstfind.nl E: v.borstlap@firstfind.nl ----------------------------------------------------------------------- ***************************************************** Voorbehoud FirstFind E-Consults: Aan de inhoud van dit e-mailbericht kunnen geen rechten worden ontleend, tenzij dit expliciet in dit bericht is verwoord. De informatie verzonden met dit e-mailbericht is uitsluitend bestemd voor de geadresseerde. Indien het wordt ontvangen door iemand anders, wordt verzocht het te retourneren aan de afzender. *****************************************************