From 4tunecookie@totalise.co.uk Mon Sep 2 01:08:01 2002 From: 4tunecookie@totalise.co.uk (4tune Cookie) Date: Mon, 2 Sep 2002 01:08:01 +0100 Subject: [Mailman-Developers] jaguar brings out the best.. Message-ID: <0B80B822-BE08-11D6-92E5-000393994FF4@totalise.co.uk> Dear bwarsaw, ; ) excellent to see another fan of X is in a position to help, have tried installing mailman but to no success, a fink package would be superb or even better, configured to use with Postfix. tried on x10.1.3-5, os 10.2 not yet will have anotyher go and see where i get stuck again i will assist in anyway i can, i have postfix running at the moment. cookie. g4-dp-768mb-120gb-dvdR-dvdRAM From pioppo@ferrara.linux.it Mon Sep 2 19:59:44 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Mon, 2 Sep 2002 20:59:44 +0200 Subject: [Mailman-Developers] reply-to in digest Message-ID: <20020902185944.GC1926@ferrara.linux.it> Hi, One of my users is complaining because digested messages have no Reply-To: header. He says the behaviour changed from 2.0 to 2.1. Is this change intentional? More info: - the list has reply_goes_to_list = 1 - Reply-To: is ok for non-digest members - running 2.1b3+ -- Adde parvum parvo magnus acervus erit. Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From claw@kanga.nu Mon Sep 2 21:11:26 2002 From: claw@kanga.nu (J C Lawrence) Date: Mon, 02 Sep 2002 13:11:26 -0700 Subject: [Mailman-Developers] reply-to in digest In-Reply-To: Message from Simone Piunno of "Mon, 02 Sep 2002 20:59:44 +0200." <20020902185944.GC1926@ferrara.linux.it> References: <20020902185944.GC1926@ferrara.linux.it> Message-ID: <21638.1030997486@kanga.nu> On Mon, 2 Sep 2002 20:59:44 +0200 Simone Piunno wrote: > One of my users is complaining because digested messages have no > Reply-To: header. He says the behaviour changed from 2.0 to 2.1. Is > this change intentional? Yes. Digest messages should never be replied to. Tell the user to burst his digests and reply to the individual messages. -- 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 pioppo@ferrara.linux.it Mon Sep 2 21:19:58 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Mon, 2 Sep 2002 22:19:58 +0200 Subject: [Mailman-Developers] reply-to in digest In-Reply-To: <21638.1030997486@kanga.nu> References: <20020902185944.GC1926@ferrara.linux.it> <21638.1030997486@kanga.nu> Message-ID: <20020902201958.GB2679@ferrara.linux.it> On Mon, Sep 02, 2002 at 01:11:26PM -0700, J C Lawrence wrote: > > One of my users is complaining because digested messages have no > > Reply-To: header. He says the behaviour changed from 2.0 to 2.1. Is > > this change intentional? > > Yes. Digest messages should never be replied to. Tell the user to > burst his digests and reply to the individual messages. Sorry, let me rephrase: this is what he wants to do! He wants to reply to individual messages, but they lack the Reply-To. Many good MUAs (at least mutt and pine - he uses the latter) allows you to view the attached messages as they were arrived normally, non digested (this is the beauty of MIME digests), but replying doesn't work correctly if reply-to is not present in each single message. -- Adde parvum parvo magnus acervus erit. Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From dgc@uchicago.edu Tue Sep 3 18:23:30 2002 From: dgc@uchicago.edu (David Champion) Date: Tue, 3 Sep 2002 12:23:30 -0500 Subject: [Mailman-Developers] Re: i18n support for Archiver In-Reply-To: <3D6B9EAB.B8F33FAE@nleaudio.com> References: <20020827035826.M37023@nleaudio.com> <26111.1030435874@kanga.nu> <3D6B9EAB.B8F33FAE@nleaudio.com> Message-ID: <20020903172330.GB15192@dust.uchicago.edu> * On 2002.08.27, in <3D6B9EAB.B8F33FAE@nleaudio.com>, * "Bob Puff@NLE" wrote: > > Easier to use one of the extended CDROM formats which supports long > > filenames > > A few months ago I went through this with a customer who wanted a copy > of the archives on CDROM from their list. The extended filenames work > fine under Windows, but not under the MacOS. They have a different > format for their extended filenames. The only common denominator I > found was the 8.3 dos filenames. For UNIX, you want Rock Ridge extensions. For MS, you want Joliet. For MacOS, you want HFS. Combinations of these are commonly called "hybrid". I haven't used Toast on the Mac, but I'd wager that it'll take care of this. So does mkisofs (formerly mkhybrid) from the cdrtools software (formerly cdrecord). Mkisofs runs on most UNIXes, and will create a single-file hybrid ISO-9660+extensions CD-ROM image track suitable for burning to disc with any CD-R[W] software. Sincec cdrecord is included with it, you might find it easiest to use; maybe not. Search for "cdrecord schily -psychopath" in Google. It's a first hit, so it's okay to feel lucky. At one time not so long ago, VMS and HP-UX still required 8.3 filenaming, but I suspect they've both gone RR by now. Solaris 9 now ships with mkisofs and Sun's own cd-recording program, cdrw. I'd recommend something like: shell$ cd /path/to/image/root shell$ mkisofs -o /tmp/image.iso -V "Name of CD-ROM" -J -r -h . -J adds Joliet records. -r uses "rationalized" Rock Ridge extensions (uids are mapped to 0, permissions normalized). -h adds HFS extensions Mkisofs also lets you emplace El Torito, Sparc, and Apple boot images, if that's important, and hide certain files from Joliet users or HFS users exclusively. So, anyway, with tools like that I don't see the added value of switching to 8.3 filenames. :) -- -D. We establised a fine coffee. What everybody can say Sun Project, APC/UCCO TASTY! It's fresh, so-mild, with some special coffee's University of Chicago bitter and sourtaste. "LET'S HAVE SUCH A COFFEE! NOW!" dgc@uchicago.edu Please love CAFE MIAMI. Many thanks. From Dan.Mick@sun.com Tue Sep 3 19:40:53 2002 From: Dan.Mick@sun.com (Dan Mick) Date: Tue, 03 Sep 2002 11:40:53 -0700 Subject: [Mailman-Developers] Re: i18n support for Archiver References: <20020827035826.M37023@nleaudio.com> <26111.1030435874@kanga.nu> <3D6B9EAB.B8F33FAE@nleaudio.com> <20020903172330.GB15192@dust.uchicago.edu> Message-ID: <3D750235.6080904@sun.com> David Champion wrote: > Search for "cdrecord schily -psychopath" in Google. HAHAHAHAHahahahahahahahahahahaha! Oh, that's brilliant! Thank you David; I love Joerg's software, but that just hit home... From Dale@Newfield.org Tue Sep 3 22:00:30 2002 From: Dale@Newfield.org (Dale Newfield) Date: Tue, 3 Sep 2002 17:00:30 -0400 (EDT) Subject: [Mailman-Developers] (More) pristine archives In-Reply-To: <15726.36493.78699.947964@geddy.zope.com> Message-ID: On Thu, 29 Aug 2002, Barry A. Warsaw wrote: > DN> Wouldn't that abort be triggered by a call to .UnLock() > DN> without a call to .Save()? I would think that all calls to > DN> .Lock() and any calls to .UnLock() without a prior call to > DN> .Save() should abort any current transaction. > > What about the qrunners that don't lock the list because they only > need read access to the data? That's why I think we need an explicit > abort, even if it's no-op'd for the old-style persistence. If it's read-only, I don't see the problem unless you need the data it is reading to remain unchanged (locked) for some span of time. Transactions are only related to changes made to the database. A read-only MailList would always be able to read, and at any given point in time the information returned would be that most recently committed. (I.E., If one process is reading and another modifying, the reading process will see the data from before the modifications until the writing process commits, then the reading process would see *all* those mods (no need to worry about incomplete changes--that's the point of an all-or-nothing transaction).) > Ah, so the problem probably isn't the transaction boundaries, but that > Mailman assumes that each list's persistence is completely independent > of other lists. Right. > I think the one place where you'll get hosed by this is in the cgi's > where "global" operations loop through all the lists (yes, this sucks > and is inefficient, but its the best we can currently do). I was hoping that these loops were always read-only, or that they could be serialized so that only one MailList is ever locked at a time. > I'm not sure how to get around this, except through some kind of > elaborate nested transaction support. Which is a road we really don't want to go down--Even if some random SQL implementation supported that, SQL doesn't support it in the standard. > Hmm. I'm going to have to think about this some more. I'm off line > right now so can't look at code details. OK. I'm going to go ahead and continue my development hoping that there's no show-stopper here. We do need to continue this conversation, but I also want to actually get stuff working :-) -Dale From dgc@uchicago.edu Wed Sep 4 00:30:26 2002 From: dgc@uchicago.edu (David Champion) Date: Tue, 3 Sep 2002 18:30:26 -0500 Subject: [Mailman-Developers] Re: i18n support for Archiver In-Reply-To: <3D750235.6080904@sun.com> References: <20020827035826.M37023@nleaudio.com> <26111.1030435874@kanga.nu> <3D6B9EAB.B8F33FAE@nleaudio.com> <20020903172330.GB15192@dust.uchicago.edu> <3D750235.6080904@sun.com> Message-ID: <20020903233026.GJ15192@dust.uchicago.edu> * On 2002.09.03, in <3D750235.6080904@sun.com>, * "Dan Mick" wrote: > > Oh, that's brilliant! Thank you David; I love Joerg's software, > but that just hit home... I rely on his CD software, and for the most part it's quite good, but it was just too funny to let lie when I found him claiming that under some circumstances you need his make clone to compile cdrecord, and his tar clone to unpack his make source. You just have to wonder why -- until you realize you'd probably regret finding out. -- -D. We establised a fine coffee. What everybody can say Sun Project, APC/UCCO TASTY! It's fresh, so-mild, with some special coffee's University of Chicago bitter and sourtaste. "LET'S HAVE SUCH A COFFEE! NOW!" dgc@uchicago.edu Please love CAFE MIAMI. Many thanks. From barry@zope.com Wed Sep 4 13:08:13 2002 From: barry@zope.com (Barry A. Warsaw) Date: Wed, 4 Sep 2002 08:08:13 -0400 Subject: [Mailman-Developers] (More) pristine archives References: <15726.36493.78699.947964@geddy.zope.com> Message-ID: <15733.63405.157076.576891@anthem.wooz.org> >>>>> "DN" == Dale Newfield writes: >> What about the qrunners that don't lock the list because they >> only need read access to the data? That's why I think we need >> an explicit abort, even if it's no-op'd for the old-style >> persistence. DN> If it's read-only, I don't see the problem unless you need the DN> data it is reading to remain unchanged (locked) for some span DN> of time. No, I was just thinking about read consistency here. I think you basically want the read state frozen at the start of the _dispose() method, which will either start with a Load() or a Lock(). It might be a bad thing (unless it isn't ) for the state to change during _dispose(), even if the list is only reading its data. DN> Transactions are only related to changes made to the database. DN> A read-only MailList would always be able to read, and at any DN> given point in time the information returned would be that DN> most recently committed. (I.E., If one process is reading and DN> another modifying, the reading process will see the data from DN> before the modifications until the writing process commits, DN> then the reading process would see *all* those mods (no need DN> to worry about incomplete changes--that's the point of an DN> all-or-nothing transaction).) Part of the point is also to provide consistent state for read-only data. In ZODB for example, it's possible to get read-conflicts if the state of the objects aren't consistent. E.g. you read obj1 from transaction1, which has a reference to obj2. Before you read obj2, process2 has modified obj2 in transaction2. Now process1 reads obj2. Inconsistent state and a read-conflict occurs. (Aside: ZODB4 will likely have multiversion consistency control which assures that process1 will read obj2's state as it existed in transaction1). This works in Mailman by doing a Load/Lock at the top of _dispose to sync the in-memory state with the on-disk state for the duration of the method. >> I think the one place where you'll get hosed by this is in the >> cgi's where "global" operations loop through all the lists >> (yes, this sucks and is inefficient, but its the best we can >> currently do). DN> I was hoping that these loops were always read-only, or that DN> they could be serialized so that only one MailList is ever DN> locked at a time. I believe they're serialized (they do write state), /except/ for the "parent" list for the process. E.g. I visit list1 to change my password, but click on "set globally". list1 remains locked while I cycle through the other lists, locking them in turn and making those changes. We may have to rewrite a few of these loops. >> I'm not sure how to get around this, except through some kind >> of elaborate nested transaction support. DN> Which is a road we really don't want to go down--Even if some DN> random SQL implementation supported that, SQL doesn't support DN> it in the standard. Ok. >> Hmm. I'm going to have to think about this some more. I'm off >> line right now so can't look at code details. DN> OK. I'm going to go ahead and continue my development hoping DN> that there's no show-stopper here. We do need to continue DN> this conversation, but I also want to actually get stuff DN> working :-) +1 :) Let us know how it goes. -Barry From barry@python.org Wed Sep 4 13:39:03 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 4 Sep 2002 08:39:03 -0400 Subject: [Mailman-Developers] reply-to in digest References: <20020902185944.GC1926@ferrara.linux.it> Message-ID: <15733.65255.495021.904355@anthem.wooz.org> >>>>> "SP" == Simone Piunno writes: >> Yes. Digest messages should never be replied to. Tell the >> user to burst his digests and reply to the individual messages. SP> Sorry, let me rephrase: this is what he wants to do! SP> He wants to reply to individual messages, but they lack the SP> Reply-To. This is because RFC 1153 specifies the exact list of headers that should be copied to digest messages, and that list doesn't include Reply-To. OTOH, I think the list specified by RFC 1153 is incomplete (e.g. it doesn't include MIME headers), so adding Reply-To to the list of overrides seems fine to me. -Barry From noreply@sourceforge.net Wed Sep 4 20:46:33 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 04 Sep 2002 12:46:33 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-604701 ] apparent duplicate file Message-ID: Bugs item #604701, was opened at 2002-09-04 12:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604701&group_id=103 Category: documentation Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Ross Boylan (rboylan) Assigned to: Nobody/Anonymous (nobody) Summary: apparent duplicate file Initial Comment: doc/posting-flow-chart and posting-flow-chart.png appear to be the same file in the same format, though they have slightly different lengths. If they are the same, I suggest eliminating one. I also suggest using the .png extension if it is a png file. Finally, both should be marked as binary, but that is a more general problem for which I will submit a separate bug. This is based on the latest from cvs ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604701&group_id=103 From noreply@sourceforge.net Wed Sep 4 20:56:49 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 04 Sep 2002 12:56:49 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-604704 ] certain files not marked as binary Message-ID: Bugs item #604704, was opened at 2002-09-04 12:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604704&group_id=103 Category: documentation Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Ross Boylan (rboylan) Assigned to: Nobody/Anonymous (nobody) Summary: certain files not marked as binary Initial Comment: Based on the latest code from cvs and inspection of the relevant Entries files, it seems that some items in the doc subdirectories (specifically, in IPC7 and LISA-98 all the gz files) are not marked as binary. They should be. doc/posting-flow-chart.ps *is* marked as binary. I believe that ps files can be treated as text. In an earlier bug I said that the posting-flowchart graphics were not marked as binary; that was incorrect. It's only the material in the subdirectories that is not marked as binary. A spot check of one of the files with gzip says its still OK, so the error may not be too significant. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604704&group_id=103 From noreply@sourceforge.net Thu Sep 5 02:26:45 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 04 Sep 2002 18:26:45 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-604841 ] simulate bounce Message-ID: Bugs item #604841, was opened at 2002-09-04 21:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604841&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Justin (returnthis) Assigned to: Nobody/Anonymous (nobody) Summary: simulate bounce Initial Comment: It would be great to add a "simulate invalid address" to the authorization page. e.g. along with the Defer/Accept/Reject/Discard options. This would simply send an invalid address message back to the sender. Usually used for spam emails with members only posting. Would greatly reduce spam as the invalid address would be removed by most automated spamming systems. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604841&group_id=103 From mradamlacey@hotmail.com Thu Sep 5 02:08:53 2002 From: mradamlacey@hotmail.com (Adam Lacey) Date: Wed, 04 Sep 2002 20:08:53 -0500 Subject: [Mailman-Developers] trying to tweak adminstrative options Message-ID: Apologize in advance if this isnt the mailing to help me, but if anyone can I would appreciate it. I am running mailman to manage lists. It works fine as intended, however I want to restrict access to certain adminstrative features (message size, etc). However I want to keep access to other adminstrative features (membership management, desrciptions, greeting message, etc.). I thought if I could find where the pages for the list administration options are created, I could simply remove the options that I dont want the list administrators access to, and if I wanted to change those options, I could simply edit via the command line (config_list). However, I dont know the structure of the program, or if there is a semi-easy solution. Could anybody shed some light on where that particular content is made, where I could edit it, or if I can. Thanks for the help _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com From mradamlacey@hotmail.com Thu Sep 5 02:08:54 2002 From: mradamlacey@hotmail.com (Adam Lacey) Date: Wed, 04 Sep 2002 20:08:54 -0500 Subject: [Mailman-Developers] trying to tweak adminstrative options Message-ID: Apologize in advance if this isnt the mailing to help me, but if anyone can I would appreciate it. I am running mailman to manage lists. It works fine as intended, however I want to restrict access to certain adminstrative features (message size, etc). However I want to keep access to other adminstrative features (membership management, desrciptions, greeting message, etc.). I thought if I could find where the pages for the list administration options are created, I could simply remove the options that I dont want the list administrators access to, and if I wanted to change those options, I could simply edit via the command line (config_list). However, I dont know the structure of the program, or if there is a semi-easy solution. Could anybody shed some light on where that particular content is made, where I could edit it, or if I can. Thanks for the help _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com From noreply@sourceforge.net Thu Sep 5 02:49:22 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 04 Sep 2002 18:49:22 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-604704 ] certain files not marked as binary Message-ID: Bugs item #604704, was opened at 2002-09-04 15:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604704&group_id=103 Category: documentation Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ross Boylan (rboylan) Assigned to: Nobody/Anonymous (nobody) Summary: certain files not marked as binary Initial Comment: Based on the latest code from cvs and inspection of the relevant Entries files, it seems that some items in the doc subdirectories (specifically, in IPC7 and LISA-98 all the gz files) are not marked as binary. They should be. doc/posting-flow-chart.ps *is* marked as binary. I believe that ps files can be treated as text. In an earlier bug I said that the posting-flowchart graphics were not marked as binary; that was incorrect. It's only the material in the subdirectories that is not marked as binary. A spot check of one of the files with gzip says its still OK, so the error may not be too significant. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-04 21:49 Message: Logged In: YES user_id=12800 Actually, the two png files are unreadable, so I'm removing them. I'm also unmarking posting-flow-chart.ps as binary, and marking the others as binary. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604704&group_id=103 From noreply@sourceforge.net Thu Sep 5 02:50:23 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 04 Sep 2002 18:50:23 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-604701 ] apparent duplicate file Message-ID: Bugs item #604701, was opened at 2002-09-04 15:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604701&group_id=103 Category: documentation Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ross Boylan (rboylan) Assigned to: Nobody/Anonymous (nobody) Summary: apparent duplicate file Initial Comment: doc/posting-flow-chart and posting-flow-chart.png appear to be the same file in the same format, though they have slightly different lengths. If they are the same, I suggest eliminating one. I also suggest using the .png extension if it is a png file. Finally, both should be marked as binary, but that is a more general problem for which I will submit a separate bug. This is based on the latest from cvs ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-04 21:50 Message: Logged In: YES user_id=12800 Both the pngs were unreadable, so I removed them. Use the .ps file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604701&group_id=103 From dev@anabasis.net Thu Sep 5 08:13:42 2002 From: dev@anabasis.net (Lawrence Weeks) Date: Thu, 5 Sep 2002 02:13:42 -0500 Subject: [Mailman-Developers] Moving a list from one virtual host to another Message-ID: <20020905021342.A7161@xenophon.anabasis.net> There doesn't appear to be any utility or admin page option to do this in 2.1b3. In playing around, it seems that changing the host_name and web_page_url members on a list object do the job. Is that accurate, so long as I then update the virtual domain alias map as well? Thanks. Larry -- Lawrence Weeks "Audaces fortuna juvat." dev@anabasis.net From noreply@sourceforge.net Thu Sep 5 07:22:19 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 04 Sep 2002 23:22:19 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-602077 ] make install fails with import error Message-ID: Bugs item #602077, was opened at 2002-08-29 16:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=602077&group_id=103 Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Goeran Zaengerlein (timetrack) Assigned to: Nobody/Anonymous (nobody) Summary: make install fails with import error Initial Comment: I tried to install Mailman 2.1b3 and I followed the installation instruction exactly but make install fails with the following message: --- snip --- Compiling /usr/local/mailman/Mailman/versions.py ... Traceback (most recent call last): File "bin/update", line 44, in ? import paths ImportError: No module named paths make: *** [update] Error 1 --- snap --- SuSE 7.2 Python 2.2.1 gcc 2.95.3 The problem was already described here: http://mail.python.org/pipermail/mailman-users/2002- July/020991.html but no solution has been posted as far as I could see... Any idea what I did wrong? ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-05 02:22 Message: Logged In: YES user_id=12800 Did you install Python via RPM? If so, be sure you have the python-devel package installed. I don't know why this is, but I've seen reports of this problem when folks only have the python package installed. Installing the python-devel or installing Python from source seems to solve this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=602077&group_id=103 From noreply@sourceforge.net Thu Sep 5 06:05:50 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 04 Sep 2002 22:05:50 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-604895 ] MySQL (or other DB) Hook Inclusion Message-ID: Feature Requests item #604895, was opened at 2002-09-05 05:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=604895&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Christopher R. Allen (bigfatpipe) Assigned to: Nobody/Anonymous (nobody) Summary: MySQL (or other DB) Hook Inclusion Initial Comment: It would be great if some or all of the configurable information about a list could be managed through a database environment such as MySQL. I'm not familliar with Python code structure, but as a perl geek my brain says that DBI support would be awesome, with local administrators responsible for site- specific configuration and Python-equivilant-to-DBI implementations. Such a DB environment would go several steps towards feature req. no. 456071 (Unified User Access), as the DB could be used to maintain user account data across multiple subscriptions. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=604895&group_id=103 From noreply@sourceforge.net Thu Sep 5 03:59:43 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 04 Sep 2002 19:59:43 -0700 Subject: [Mailman-Developers] [ mailman-Patches-602084 ] options.py lists_of_member optimization Message-ID: Patches item #602084, was opened at 2002-08-29 16:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=602084&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: options.py lists_of_member optimization Initial Comment: Call lists_of_member() and apply globalopts only if called for, i.e., if globalopts is not empty. Empirically, this is a lot faster (if no global options requested), with ca. 5K lists. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-04 22:59 Message: Logged In: YES user_id=12800 Cute! Accepted, thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=602084&group_id=103 From noreply@sourceforge.net Thu Sep 5 04:00:01 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 04 Sep 2002 20:00:01 -0700 Subject: [Mailman-Developers] [ mailman-Patches-602084 ] options.py lists_of_member optimization Message-ID: Patches item #602084, was opened at 2002-08-29 16:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=602084&group_id=103 Category: Web UI Group: Mailman 2.1 >Status: Closed Resolution: Accepted Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: options.py lists_of_member optimization Initial Comment: Call lists_of_member() and apply globalopts only if called for, i.e., if globalopts is not empty. Empirically, this is a lot faster (if no global options requested), with ca. 5K lists. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-04 22:59 Message: Logged In: YES user_id=12800 Cute! Accepted, thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=602084&group_id=103 From noreply@sourceforge.net Thu Sep 5 03:30:50 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 04 Sep 2002 19:30:50 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-604701 ] apparent duplicate file Message-ID: Bugs item #604701, was opened at 2002-09-04 15:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604701&group_id=103 Category: documentation Group: 2.1 beta Status: Closed Resolution: Fixed Priority: 5 Submitted By: Ross Boylan (rboylan) Assigned to: Nobody/Anonymous (nobody) Summary: apparent duplicate file Initial Comment: doc/posting-flow-chart and posting-flow-chart.png appear to be the same file in the same format, though they have slightly different lengths. If they are the same, I suggest eliminating one. I also suggest using the .png extension if it is a png file. Finally, both should be marked as binary, but that is a more general problem for which I will submit a separate bug. This is based on the latest from cvs ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-04 22:30 Message: Logged In: YES user_id=12800 I don't mean they're unreadable, I mean they're unreadable! For me the font was so small I couldn't read the text. :) ---------------------------------------------------------------------- Comment By: Ross Boylan (rboylan) Date: 2002-09-04 22:13 Message: Logged In: YES user_id=300987 That's odd; I have no trouble reading them. Perhaps you are on a system that does some cr/lf translation that mine doesn't? I'm on Linux. running cvs 1.11.2. Of course, if that was the problem, setting the mode to binary should fix it. But I don't know if cvs client picks up on a mode change on the server. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-04 21:50 Message: Logged In: YES user_id=12800 Both the pngs were unreadable, so I removed them. Use the .ps file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604701&group_id=103 From noreply@sourceforge.net Thu Sep 5 03:13:11 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 04 Sep 2002 19:13:11 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-604701 ] apparent duplicate file Message-ID: Bugs item #604701, was opened at 2002-09-04 12:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604701&group_id=103 Category: documentation Group: 2.1 beta Status: Closed Resolution: Fixed Priority: 5 Submitted By: Ross Boylan (rboylan) Assigned to: Nobody/Anonymous (nobody) Summary: apparent duplicate file Initial Comment: doc/posting-flow-chart and posting-flow-chart.png appear to be the same file in the same format, though they have slightly different lengths. If they are the same, I suggest eliminating one. I also suggest using the .png extension if it is a png file. Finally, both should be marked as binary, but that is a more general problem for which I will submit a separate bug. This is based on the latest from cvs ---------------------------------------------------------------------- >Comment By: Ross Boylan (rboylan) Date: 2002-09-04 19:13 Message: Logged In: YES user_id=300987 That's odd; I have no trouble reading them. Perhaps you are on a system that does some cr/lf translation that mine doesn't? I'm on Linux. running cvs 1.11.2. Of course, if that was the problem, setting the mode to binary should fix it. But I don't know if cvs client picks up on a mode change on the server. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-04 18:50 Message: Logged In: YES user_id=12800 Both the pngs were unreadable, so I removed them. Use the .ps file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=604701&group_id=103 From noreply@sourceforge.net Thu Sep 5 03:51:35 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 04 Sep 2002 19:51:35 -0700 Subject: [Mailman-Developers] [ mailman-Patches-602087 ] observe configure srcdir Message-ID: Patches item #602087, was opened at 2002-08-29 16:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=602087&group_id=103 >Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: observe configure srcdir Initial Comment: (2nd try, hopefully with attached file this time.) These patches to Makefile.in in several directories make the --srcdir configure option work. Which can be very useful if you have a multi-platform build system. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-04 22:50 Message: Logged In: YES user_id=12800 In CGI_PROGS in the src/Makefile.in patch, where did "login" sneak in from? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=602087&group_id=103 From barry@python.org Thu Sep 5 03:25:33 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 4 Sep 2002 22:25:33 -0400 Subject: [Mailman-Developers] trying to tweak adminstrative options References: Message-ID: <15734.49309.801739.923286@anthem.wooz.org> >>>>> "AL" == Adam Lacey writes: AL> I thought if I could find where the pages for the list AL> administration options are created, I could simply remove the AL> options that I dont want the list administrators access to, AL> and if I wanted to change those options, I could simply edit AL> via the command line (config_list). AL> However, I dont know the structure of the program, or if there AL> is a semi-easy solution. Could anybody shed some light on AL> where that particular content is made, where I could edit it, AL> or if I can. There's no trivially easy solution, but you could hack the code. I think this would work (for MM2.1): find the attributes you want to disable in the Mailman/Gui/*.py files and comment them out. They won't show up in the admin interface and you'd have to use bin/withlist (or bin/config_list) to modify them. Note that this is a fairly heavy handed approach because this will affect all the lists on your server. -Barry From noreply@sourceforge.net Thu Sep 5 03:50:58 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 04 Sep 2002 19:50:58 -0700 Subject: [Mailman-Developers] [ mailman-Patches-602087 ] observe configure srcdir Message-ID: Patches item #602087, was opened at 2002-08-29 16:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=602087&group_id=103 Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: observe configure srcdir Initial Comment: (2nd try, hopefully with attached file this time.) These patches to Makefile.in in several directories make the --srcdir configure option work. Which can be very useful if you have a multi-platform build system. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-04 22:50 Message: Logged In: YES user_id=12800 In CGI_PROGS in the src/Makefile.in patch, where did "login" sneak in from? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=602087&group_id=103 From barry@python.org Thu Sep 5 03:33:42 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 4 Sep 2002 22:33:42 -0400 Subject: [Mailman-Developers] jaguar brings out the best.. References: <0B80B822-BE08-11D6-92E5-000393994FF4@totalise.co.uk> Message-ID: <15734.49798.365987.230012@anthem.wooz.org> >>>>> "4tunecookie" == <4tunecookie@totalise.co.uk> writes: 4tunecookie> Dear bwarsaw, ; ) 4tunecookie> excellent to see another fan of X is in a position to 4tunecookie> help, OSX rocks. 4tunecookie> have tried installing mailman but to no success, a 4tunecookie> fink package would be superb or even better, 4tunecookie> configured to use with Postfix. I'm not up on fink, but I'd like to hear more about what "no success" means. What did you try and what were the symptoms of it not working? Where there installation problems? 4tunecookie> tried on x10.1.3-5, os 10.2 not yet 4tunecookie> will have anotyher go and see where i get stuck again Cool. Please let us know how far along you get so we can help you out. Also, let me know if there's any recommendations specific to OSX we can give. I'd be happy to put together a README.OSX with details. 4tunecookie> i will assist in anyway i can, i have postfix running 4tunecookie> at the moment. Cool. -Barry From barry@python.org Thu Sep 5 03:39:03 2002 From: barry@python.org (Barry A. Warsaw) Date: Wed, 4 Sep 2002 22:39:03 -0400 Subject: [Mailman-Developers] Forget password form and unsubscribe without password References: <3D6EF881.CA59B84D@isu.edu> <20020830165342.GA560@ostraya.zone12.com> Message-ID: <15734.50119.243559.842067@anthem.wooz.org> >>>>> "TO" == Terri Oda writes: TO> I suspect putting the two boxes on one page would be a good TO> exercise for someone trying to learn python, if you're picky TO> about having them together. :) And of course, MM2.1 has this already on the member's log in page (plus password-less unsub by confirmation. :). -Barry From noreply@sourceforge.net Thu Sep 5 16:45:11 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 05 Sep 2002 08:45:11 -0700 Subject: [Mailman-Developers] [ mailman-Patches-602087 ] observe configure srcdir Message-ID: Patches item #602087, was opened at 2002-08-29 20:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=602087&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: observe configure srcdir Initial Comment: (2nd try, hopefully with attached file this time.) These patches to Makefile.in in several directories make the --srcdir configure option work. Which can be very useful if you have a multi-platform build system. ---------------------------------------------------------------------- >Comment By: Donn Cave (donnc) Date: 2002-09-05 15:45 Message: Logged In: YES user_id=42839 I'm sorry - that's a local modification, of course, and I shouldn't have included it with this patch. I have hacked in another authentication system for our Kerberos realm, cf. http://www.mail- archive.com/mailman-developers@python.org/msg03713.html ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-05 02:50 Message: Logged In: YES user_id=12800 In CGI_PROGS in the src/Makefile.in patch, where did "login" sneak in from? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=602087&group_id=103 From noreply@sourceforge.net Thu Sep 5 17:55:58 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 05 Sep 2002 09:55:58 -0700 Subject: [Mailman-Developers] [ mailman-Patches-605146 ] Expand "addrs" to "addresses" Message-ID: Patches item #605146, was opened at 2002-09-05 12:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605146&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jon Parise (parise) Assigned to: Nobody/Anonymous (nobody) Summary: Expand "addrs" to "addresses" Initial Comment: The attached patch expands the abbreviated "addrs" text to the full "addresses" word. I think this looks more professional. Because this changes the gettext string, however, localization updates will have to be made. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605146&group_id=103 From barry@zope.com Thu Sep 5 19:06:59 2002 From: barry@zope.com (Barry A. Warsaw) Date: Thu, 5 Sep 2002 14:06:59 -0400 Subject: [Mailman-Developers] New `spambayes' project on SourceForge Message-ID: <15735.40259.117828.402419@anthem.wooz.org> There's been a ton of press about applying Bayesian classifiers to spam detection lately, spurred on by Paul Graham's recent paper "A Plan for Spam" http://www.paulgraham.com/spam.html Tim Peters has done an incredible amount of work on our Python implementation of this idea. Some of the reasons why I think Tim's work is so cool is that he's brought along his deep knowledge of speech recognition's related issues, and his obsessive devotion to reducing the amount of spam I ultimately have to delete . In order to encourage more participation from the wider open source community, we've moved the code from a backwater of the Python cvs tree to its own project on SourceForge. The hope is that more people will be able to contribute to ideas, testing, and integration of the basic algorithms with other systems such as mail daemons, mailing list managers, and mail clients. The project is called "spambayes" (for lack of creativity on our part :) and is hosted here: http://sf.net/projects/spambayes If you're interested in becoming a developer on the project, let me know. Otherwise you can of course get anonymous checkouts of the code. There are also two mailing lists related to the spambayes project. The first is a general discussion list: http://mail.python.org/mailman-21/listinfo/spambayes and the other is a list for cvs checkin message notices: http://mail.python.org/mailman-21/listinfo/spambayes-checkins Feel free to join those lists (and help be a guinea pig for Mailman 2.1 :). Enjoy, -Barry PS to Python-devers: the code has been removed from nondist/sandbox/spambayes, so you won't be able to hack on it there. Also, please move discussion about this from python-dev@python.org to spambayes@python.org From barry@python.org Thu Sep 5 14:25:55 2002 From: barry@python.org (Barry A. Warsaw) Date: Thu, 5 Sep 2002 09:25:55 -0400 Subject: [Mailman-Developers] Moving a list from one virtual host to another References: <20020905021342.A7161@xenophon.anabasis.net> Message-ID: <15735.23395.984720.652644@anthem.wooz.org> >>>>> "LW" == Lawrence Weeks writes: LW> There doesn't appear to be any utility or admin page option to LW> do this in 2.1b3. In playing around, it seems that changing LW> the host_name and web_page_url members on a list object do the LW> job. Is that accurate, so long as I then update the virtual LW> domain alias map as well? Thanks. Yes, that should be all you need to do. Hmm, I think bin/fix_url.py should probably include a switch to look up a virtual domain in the VIRTUAL_HOSTS map. -Barry From noreply@sourceforge.net Thu Sep 5 20:58:00 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 05 Sep 2002 12:58:00 -0700 Subject: [Mailman-Developers] [ mailman-Patches-605234 ] Stylesheet support for archives Message-ID: Patches item #605234, was opened at 2002-09-05 15:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605234&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Fred L. Drake, Jr. (fdrake) Assigned to: Nobody/Anonymous (nobody) Summary: Stylesheet support for archives Initial Comment: This patch adds a stylesheet reference to the pipermail archives, and copies in an empty stylesheet the first time the list is opened and the file doesn't already exist. The patch modifies two files in the Mailman.Archiver package, and the stylesheet should be copied into templates/en/. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605234&group_id=103 From noreply@sourceforge.net Thu Sep 5 21:00:49 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 05 Sep 2002 13:00:49 -0700 Subject: [Mailman-Developers] [ mailman-Patches-605234 ] Stylesheet support for archives Message-ID: Patches item #605234, was opened at 2002-09-05 15:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605234&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Fred L. Drake, Jr. (fdrake) >Assigned to: Barry A. Warsaw (bwarsaw) Summary: Stylesheet support for archives Initial Comment: This patch adds a stylesheet reference to the pipermail archives, and copies in an empty stylesheet the first time the list is opened and the file doesn't already exist. The patch modifies two files in the Mailman.Archiver package, and the stylesheet should be copied into templates/en/. ---------------------------------------------------------------------- >Comment By: Fred L. Drake, Jr. (fdrake) Date: 2002-09-05 16:00 Message: Logged In: YES user_id=3066 Barry volunteered to integrate and test. Yay! ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605234&group_id=103 From JasonR.Mastaler Thu Sep 5 21:01:37 2002 From: JasonR.Mastaler (JasonR.Mastaler) Date: Thu, 05 Sep 2002 14:01:37 -0600 Subject: [Mailman-Developers] Re: New `spambayes' project on SourceForge References: <15735.40259.117828.402419@anthem.wooz.org> Message-ID: barry@zope.com (Barry A. Warsaw) writes: > There are also two mailing lists related to the spambayes project. > The first is a general discussion list: > > http://mail.python.org/mailman-21/listinfo/spambayes > > and the other is a list for cvs checkin message notices: > > http://mail.python.org/mailman-21/listinfo/spambayes-checkins These lists have now been added to Gmane (http://gmane.org) as well: spambayes@python.org <==> news://news.gmane.org/gmane.mail.spam.spambayes.general spambayes-checkins@python.org <==> news://news.gmane.org/gmane.mail.spam.spambayes.cvs -- (http://tmda.net/) From pioppo@ferrara.linux.it Thu Sep 5 21:08:14 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Thu, 5 Sep 2002 22:08:14 +0200 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list Message-ID: <20020905200814.GE2024@ferrara.linux.it> Hi, I run a bunch of lists with reply_goes_to_list=1 (yeah, I know that reply-to munging is considered harmful but I consider more important to keep discussions inside the lists and anyway this has been our standard configuration for ages and now people expect this behaviour) The problem is that sometimes a non-subscriber sends a question to the list and subscribers think he is also a subscriber and do not CC him. I think it would be nice to use the multi-valued reply-to this way: 1. if the user sent a message with reply-to, then add the list address to the reply-to (or overwrite reply-to with the list address if the original reply-to is subscribed to the list, just to remove duplicate mails) 2. if the user sent a message without reply-to, then create a new reply-to including: a. the original from or sender (which is the best?) if it's not subscribed to the list b. the list address Probably this could be a 4th option for the reply_goes_to_list setting. I'm willing to provide a patch if you like the idea, but I don't know which address to use for the "2a" case. -- Adde parvum parvo magnus acervus erit. Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From noreply@sourceforge.net Thu Sep 5 22:15:36 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 05 Sep 2002 14:15:36 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-605263 ] Bad var in ListAdmin._UpdateRecords() Message-ID: Bugs item #605263, was opened at 2002-09-05 14:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605263&group_id=103 Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Les Niles (lniles) Assigned to: Nobody/Anonymous (nobody) Summary: Bad var in ListAdmin._UpdateRecords() Initial Comment: ListAdmin._UpdateRecords() (in the CVS head, and as far as I can tell all the way back to its inception) refers to "mlist", which raises a NameError when updating some lists. Syntactically it would seem that this should be "self" instead, and experimentally that solves the problem. Here's the patch: *** ListAdmin.py.~1~ Wed Sep 4 23:25:26 2002 --- ListAdmin.py Thu Sep 5 00:38:24 2002 *************** *** 539,545 **** # pre-2.1a2 compatibility when, addr, passwd, digest = info fullname = '' ! lang = mlist.preferred_language elif len(info) == 5: # pre-2.1a4 compatibility when, addr, passwd, digest, lang = info --- 539,545 ---- # pre-2.1a2 compatibility when, addr, passwd, digest = info fullname = '' ! lang = self.preferred_language elif len(info) == 5: # pre-2.1a4 compatibility when, addr, passwd, digest, lang = info ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605263&group_id=103 From wheakory@isu.edu Thu Sep 5 23:12:53 2002 From: wheakory@isu.edu (Kory Wheatley) Date: Thu, 05 Sep 2002 16:12:53 -0600 Subject: [Mailman-Developers] SMTPDirect.py using sleep command Message-ID: <3D77D6E5.52B56E31@isu.edu> Using Mailman 2.0.13 on Red Hat 7.2 I've got a Mailman mailing list that contains 14,000 subscribers, on a Linux box that's using sendmail has the delivery agent that sends all of the messages to one mail host, because all 14,000 subscribers have an email account on our mail server. This Linux box is only used to deliver our Mailman mailing to our Mail server which is a HPUX 11 server, using sendmail as the routing agent. We sent a message to the 14,000 recipient Mailman mailing list the other day and it put the load on our Unix Box that contains our mail server to the roof What I have done to maybe slow down the delivery to sendmail that creates the queue files then delivers them to our mail server is in the Mailman SMTPDirect.py I have used the sleep command to sleep after delivering so that our mail server can catch up before the next batch is delivered, this way its not being bombarded. Now here is where I would appreciate help, I'm not a experienced Python programmer and maybe what I did below is stupid and will not work (using the time.sleep(25) command), but please look at the code and if it will not work please let me know what I can code that will work that will slow down the delivery to our mail server. ------------CODE-------------------- def deliver(envsender, msgtext, recips, failures): refused = {} # Gather statistics on how long each SMTP dialog takes. ## t0 = time.time() try: conn = smtplib.SMTP(mm_cfg.SMTPHOST, mm_cfg.SMTPPORT) try: # make sure the connect happens, which won't be done by the # constructor if SMTPHOST is false time.sleep(25) refused = conn.sendmail(envsender, recips, msgtext) finally: ## t1 = time.time() ## syslog('smtp', 'smtp for %d recips, completed in %.3f seconds' % ## (len(recips), (t1-t0))) conn.quit() except smtplib.SMTPRecipientsRefused, e: refused = e.recipients # MTA not responding, or other socket problems, or any other kind of # SMTPException. In that case, nothing got delivered except (socket.error, smtplib.SMTPException), e: ------------END----------------- From noreply@sourceforge.net Fri Sep 6 14:09:02 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 06 Sep 2002 06:09:02 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-605557 ] language support Message-ID: Bugs item #605557, was opened at 2002-09-06 15:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605557&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Emilio Delgado (popemiko) Assigned to: Nobody/Anonymous (nobody) Summary: language support Initial Comment: Bug in Mailman version 2.1b3 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 "/var/lib/mailman/scripts/driver", line 82, in run_main main() File "/var/lib/mailman/Mailman/Cgi/create.py", line 60, in main request_creation(doc) File "/var/lib/mailman/Mailman/Cgi/create.py", line 376, in request_creation [_(Utils.GetLanguageDescr(L)) for L in langs], File "/var/lib/mailman/Mailman/Utils.py", line 599, in GetLanguageDescr return mm_cfg.LC_DESCRIPTIONS[lang][0] KeyError: admlogin_files Python information: Variable Value sys.version 2.2 (#1, Feb 24 2002, 16:21:58) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux-i386 Environment variables: Variable Value HTTP_REFERER http://192.168.1.15/mailman/admin SERVER_SOFTWARE Apache-AdvancedExtranetServer/1.3.23 (Mandrake Linux/4.1mdk) mod_ssl/2.8.7 OpenSSL/0.9.6c PHP/4.1.2 PYTHONPATH /var/lib/mailman SCRIPT_FILENAME /var/lib/mailman/cgi-bin/create SERVER_ADMIN root@localhost SCRIPT_NAME /mailman/create SCRIPT_URI http://infor.unibertsitatea.net/mailman/create SERVER_SIGNATURE Apache-AdvancedExtranetServer/1.3.23 Server at infor.unibertsitatea.net Port 80 REQUEST_METHOD GET HTTP_HOST 192.168.1.15 SCRIPT_URL /mailman/create SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/create HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 HTTP_ACCEPT_CHARSET ISO-8859-1, utf-8;q=0.66, *;q=0.66 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204 HTTP_CONNECTION keep-alive SERVER_NAME infor.unibertsitatea.net REMOTE_ADDR 192.168.1.15 REMOTE_PORT 1281 HTTP_ACCEPT_LANGUAGE en-us SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 DOCUMENT_ROOT /var/www/html HTTP_ACCEPT_ENCODING gzip, deflate, compress;q=0.9 SERVER_ADDR 192.168.1.15 HTTP_KEEP_ALIVE 300 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605557&group_id=103 From noreply@sourceforge.net Sat Sep 7 08:03:12 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 07 Sep 2002 00:03:12 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-605933 ] subscribe by invite dies on dup user Message-ID: Bugs item #605933, was opened at 2002-09-07 07:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605933&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) Summary: subscribe by invite dies on dup user Initial Comment: Playing with the "invite" feature, I invited myself, knowing I was already on the list. If you reply by email, it properly bounces back a "you're already subscribed" error. Click the web link, however, and fill out the form (which, btw mistakenly said that the moderater had to approve it on an open list; I don't remember if that's hardcoded or dynamic, but I *thought* it was dynamic) and when you submit it you get a traceback... the cgi-form really ought to catch this condition gracefully... Traceback (most recent call last): File "/home/mailman/scripts/driver", line 82, in run_main main() File "/home/mailman/Mailman/Cgi/confirm.py", line 110, in main subscription_confirm(mlist, doc, cookie, cgidata) File "/home/mailman/Mailman/Cgi/confirm.py", line 314, in subscription_confirm op, addr, pw, digest, lang = mlist.ProcessConfirmation( File "/home/mailman/Mailman/MailList.py", line 1072, in ProcessConfirmation self.ApprovedAddMember(userdesc) File "/home/mailman/Mailman/MailList.py", line 858, in ApprovedAddMember raise Errors.MMAlreadyAMember, email MMAlreadyAMember: jarrell@vt.edu ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605933&group_id=103 From marc_news@merlins.org Mon Sep 9 02:19:21 2002 From: marc_news@merlins.org (Marc MERLIN) Date: Sun, 8 Sep 2002 18:19:21 -0700 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list In-Reply-To: <20020905200814.GE2024@ferrara.linux.it> References: <20020905200814.GE2024@ferrara.linux.it> Message-ID: <20020909011921.GI3806@merlins.org> On Thu, Sep 05, 2002 at 10:08:14PM +0200, Simone Piunno wrote: > > Hi, > > I run a bunch of lists with reply_goes_to_list=1 > > (yeah, I know that reply-to munging is considered harmful but I consider > more important to keep discussions inside the lists and anyway this has I'm just amazed at how many times I've read this complete nonsense. What you all are doing is furthering people's ignorance of their mail clients functionality and preventing people from replying directly to the original sender if so wished. There is a reason why you have at least two reply functions: reply to author and reply to all/list. Yes, it does mean you have to use your brain and decide which one you want to do. Any attempt to make this choice go away with something magic that somehow figures out what the poster really meant to do are _not_ going to work. Please leave people in peace and let them decide for themselves which one they want to do. By forcing a reply to list upon them, you are removing that choice and furthering their ignorance of the two reply functions. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. 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@merlins.org Mon Sep 9 02:25:06 2002 From: marc_news@merlins.org (Marc MERLIN) Date: Sun, 8 Sep 2002 18:25:06 -0700 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list In-Reply-To: <20020909011921.GI3806@merlins.org> References: <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> Message-ID: <20020909012506.GL3806@merlins.org> On Sun, Sep 08, 2002 at 06:19:21PM -0700, Marc MERLIN wrote: > On Thu, Sep 05, 2002 at 10:08:14PM +0200, Simone Piunno wrote: > > > > Hi, > > > > I run a bunch of lists with reply_goes_to_list=1 > > > > (yeah, I know that reply-to munging is considered harmful but I consider > > more important to keep discussions inside the lists and anyway this has > > I'm just amazed at how many times I've read this complete nonsense. Sorry, this was probably unclear: "nonsense" as in "keeping discussions inside the lists" should be by clueing in posters on the two reply functions, not by diverting reply to author to reply to the list and almost forcing all replies to the list. I know that the first thing I do is strip all those evil reply-to's as soon as they enter my systems. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. 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 spacey-mailman@lenin.nu Mon Sep 9 02:26:49 2002 From: spacey-mailman@lenin.nu (Peter C. Norton) Date: Sun, 8 Sep 2002 18:26:49 -0700 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list In-Reply-To: <20020909011921.GI3806@merlins.org> References: <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> Message-ID: <20020909012649.GI32339@lenin.nu> On Sun, Sep 08, 2002 at 06:19:21PM -0700, Marc MERLIN wrote: > Please leave people in peace and let them decide for themselves which one > they want to do. By forcing a reply to list upon them, you are removing that > choice and furthering their ignorance of the two reply functions. Can you keep religious arguments off the list? The option is there, and he wants to use it. You can run your lists differently. -- The 5 year plan: In five years we'll make up another plan. Or just re-use this one. From marc_news@merlins.org Mon Sep 9 02:56:13 2002 From: marc_news@merlins.org (Marc MERLIN) Date: Sun, 8 Sep 2002 18:56:13 -0700 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list In-Reply-To: <20020909012649.GI32339@lenin.nu> References: <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020909012649.GI32339@lenin.nu> Message-ID: <20020909015613.GP3806@merlins.org> On Sun, Sep 08, 2002 at 06:26:49PM -0700, Peter C. Norton wrote: > On Sun, Sep 08, 2002 at 06:19:21PM -0700, Marc MERLIN wrote: > > Please leave people in peace and let them decide for themselves which one > > they want to do. By forcing a reply to list upon them, you are removing that > > choice and furthering their ignorance of the two reply functions. > > Can you keep religious arguments off the list? The option is there, > and he wants to use it. You can run your lists differently. If I may: 1) He made the incorrect statement that you need/want to munge reply-to to have a discussion list. This is very incorrect. Had he not said that, I'd have left the post alone: I do not want this all too common misconception to spread any further. 2) his users then come on my lists and bitch that they want the setting switched and insist and my lists are broken when in fact they've never learned to use their mail client properly. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. 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@merlins.org Mon Sep 9 02:52:17 2002 From: marc_news@merlins.org (Marc MERLIN) Date: Sun, 8 Sep 2002 18:52:17 -0700 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list In-Reply-To: <20020909013128.GJ32339@lenin.nu> References: <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020909012506.GL3806@merlins.org> <20020909013128.GJ32339@lenin.nu> Message-ID: <20020909015217.GO3806@merlins.org> [I hope you don't mind that I redirect this to the list, I think I have a suggestion to improve mailman 2.1 On Sun, Sep 08, 2002 at 06:31:28PM -0700, Peter C. Norton wrote: > BTW, the reason that I set reply-to's on one of the lists I run is > that when a thread gets going and lots of people start responding, for > some reason the Cc: list grew as long as my arm. And I got really That's indeed a minor problem, but at least with the nodupes feature in mailman 2.1, you only get one copy. Now that I think of it, it wouldn't be too hard for mailman when it sends the list copy out to (optionally) remove from Cc all the Emails from members that have the nodupes option set. That way, the Cc would be left only with Emails that aren't subscribed to the list. What do you think? > Though many people know better, my experience even on a somewhat > technical list is that most people don't exercise any discipline in > discriminating who they reply to, and they assume that the list is > going to work with their mailer and dtrt. So I work with that > assumption. Unfortunately you aren't the only one. Am I so deluted to still want people to learn and know just a tiny little bit about their mail clients and use them properly? Note that I'm not just bitching, I did spend many hours writing a patch to do reply-to munging per receipient so that people who really aren't willing to learn and/or bitch too loudly can be given the option just for them and then they leave you in peace (announced here a few months ago, and an outdated copy is here: http://mail.python.org/pipermail/mailman-users/2002-March/018145.html http://mail.python.org/pipermail-21/mailman-developers/2002-March/011068.html http://marc.merlins.org/tmp/replyto.diff.cvs ) Unfortunately it never made the cut for mailman 2.1 Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. 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 chuqui@plaidworks.com Mon Sep 9 04:12:54 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Sun, 8 Sep 2002 20:12:54 -0700 Subject: [Mailman-Developers] stupid CVS question... Message-ID: <08410D19-C3A2-11D6-A383-0003934516A8@plaidworks.com> Okay, I'm confused. or senile. Or stupid. pick one. Or two. having downloaded 2.1b3, I want to update it to current CVS. Since there aren't CVS nightly tarballs (why not?), I've tried to go in to CVS and do it. And I can't. What's the magic incantation for this? obviously, my CVS hacking is weak.... -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ Very funny, Scotty. Now beam my clothes down here, will you? From chk@pobox.com Mon Sep 9 04:27:30 2002 From: chk@pobox.com (Harald Koch) Date: Sun, 08 Sep 2002 23:27:30 -0400 Subject: [Mailman-Developers] 2.1b3 and mail -> news Message-ID: <11648.1031542050@elisabeth.cfrq.net> I'm having trouble in 2.1b3 with all of my mail->news lists. I get the following error message: Sep 08 23:23:22 2002 (25916) Uncaught runner exception: len() of unsized object Sep 08 23:23:22 2002 (25916) Traceback (most recent call last): File "/home/mm/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mm/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mm/Mailman/Queue/NewsRunner.py", line 56, in _dispose prepare_message(mlist, msg, msgdata) File "/home/mm/Mailman/Queue/NewsRunner.py", line 132, in prepare_message count = len(email.Iterators.body_line_iterator(msg)) TypeError: len() of unsized object And files appear in qfiles/shunt. (queue and list config files available upon request.) This is happening with all of the lists I have setup as news<->mail lists, which just means I've probably got a consistent configuration error :-) -- Harald Koch "It takes a child to raze a village." -Michael T. Fry From spacey-mailman@lenin.nu Mon Sep 9 05:42:08 2002 From: spacey-mailman@lenin.nu (Peter C. Norton) Date: Sun, 8 Sep 2002 21:42:08 -0700 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list In-Reply-To: <20020909015217.GO3806@merlins.org> References: <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020909012506.GL3806@merlins.org> <20020909013128.GJ32339@lenin.nu> <20020909015217.GO3806@merlins.org> Message-ID: <20020909044208.GA12379@lenin.nu> On Sun, Sep 08, 2002 at 06:52:17PM -0700, Marc MERLIN wrote: > [I hope you don't mind that I redirect this to the list, I think I have a > suggestion to improve mailman 2.1 > > On Sun, Sep 08, 2002 at 06:31:28PM -0700, Peter C. Norton wrote: > > BTW, the reason that I set reply-to's on one of the lists I run is > > that when a thread gets going and lots of people start responding, for > > some reason the Cc: list grew as long as my arm. And I got really > > That's indeed a minor problem, but at least with the nodupes feature in > mailman 2.1, you only get one copy. > > Now that I think of it, it wouldn't be too hard for mailman when it sends > the list copy out to (optionally) remove from Cc all the Emails from members > that have the nodupes option set. > That way, the Cc would be left only with Emails that aren't subscribed to > the list. > > What do you think? That would definetly limit the # of Cc:'s on a message. Its an interesting approach, though perhaps too subtle. I think it would be appropriate to also have an option that just stripped Cc's. > > Though many people know better, my experience even on a somewhat > > technical list is that most people don't exercise any discipline in > > discriminating who they reply to, and they assume that the list is > > going to work with their mailer and dtrt. So I work with that > > assumption. > > Unfortunately you aren't the only one. Am I so deluted to still want people > to learn and know just a tiny little bit about their mail clients and use > them properly? Marc, I noticed that I got 2 of these messages in my inbox. Even though you know I'm subscribed to mailman-developers, you sent me a copy. This is the thing that I use reply-to forcing to prevent. I suspect you did this on purpose, so I'd like to hear whave you had in mind when you sent this. > Note that I'm not just bitching, I did spend many hours writing a patch to > do reply-to munging per receipient so that people who really aren't willing > to learn and/or bitch too loudly can be given the option just for them and > then they leave you in peace (announced here a few months ago, and an > outdated copy is here: > http://mail.python.org/pipermail/mailman-users/2002-March/018145.html > http://mail.python.org/pipermail-21/mailman-developers/2002-March/011068.html > http://marc.merlins.org/tmp/replyto.diff.cvs ) > > Unfortunately it never made the cut for mailman 2.1 I know how you feel. I'm going to have to apply my patch to automaticly reject messages from addresses that aren't subscribed to 2.0.x. I wish I could have written it before 2.0 came out. On the positive side I know a lot more about python now, and maybe I can update my patch to use withlist to make old lists behave the right way, and to remove the stuff I put in for 2.x where x > 0. -Peter -- The 5 year plan: In five years we'll make up another plan. Or just re-use this one. From marc_news@merlins.org Mon Sep 9 07:37:07 2002 From: marc_news@merlins.org (Marc MERLIN) Date: Sun, 8 Sep 2002 23:37:07 -0700 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list In-Reply-To: <20020909044208.GA12379@lenin.nu> References: <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020909012506.GL3806@merlins.org> <20020909013128.GJ32339@lenin.nu> <20020909015217.GO3806@merlins.org> <20020909044208.GA12379@lenin.nu> Message-ID: <20020909063707.GB3806@merlins.org> On Sun, Sep 08, 2002 at 09:42:08PM -0700, Peter C. Norton wrote: > > Now that I think of it, it wouldn't be too hard for mailman when it sends > > the list copy out to (optionally) remove from Cc all the Emails from members > > that have the nodupes option set. > > That way, the Cc would be left only with Emails that aren't subscribed to > > the list. > > > > What do you think? > > That would definetly limit the # of Cc:'s on a message. Its an > interesting approach, though perhaps too subtle. I think it would be > appropriate to also have an option that just stripped Cc's. That wouldn't work too well I think, if I post to a list and Cc a non subscriber on purpose, the non subscriber will not get the replies (although admittedly, he won't get them either if people use list reply instead of group reply) > > Unfortunately you aren't the only one. Am I so deluted to still want > > people to learn and know just a tiny little bit about their mail clients > > and use them properly? > > Marc, I noticed that I got 2 of these messages in my inbox. Even though > you know I'm subscribed to mailman-developers, you sent me a copy. This I usually use group reply instead of list-reply because of the above reason. The other reason is that if you are Cced in the answer, you see I answered your post and you can sort the mail in a way that you'll read it earlier. I didn't see your answer because I wasn't Cced, and it could have sat in my random list mail folder for quite a while before I saw it. But since you requested it (people usually but it in the header or footer), I used list reply on this answer. > is the thing that I use reply-to forcing to prevent. I suspect you did Well, you are behind the times :) Ben and I got code in mailman 2.1 (which runs this list) that lets you not get the second copy. You just didn't enable the option. Go to http://mail.python.org/mailman-21/options/mailman-developers and check "Avoid duplicate copies of messages?" Besides reply-to munging in no way prevents you from getting a copy: group reply will reply to the reply-to address + To + Cc, so everyone gets a copy anyway. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. 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 Mon Sep 9 09:21:21 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 09 Sep 2002 01:21:21 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-606615 ] unsubscribing via the mail interface Message-ID: Feature Requests item #606615, was opened at 2002-09-09 08:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=606615&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ray Gardener (asrag) Assigned to: Nobody/Anonymous (nobody) Summary: unsubscribing via the mail interface Initial Comment: Unsubscribing via the mail interface currently requires the list password. What would be nice would be if this password were not supplied a confirmation message would go back to the subscriber with a unique id for confirmation of the request on mail back. Alternatively some option for requesting the password via a mail request woud also help R Gardener ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=606615&group_id=103 From javier@KJSL.COM Mon Sep 9 03:30:22 2002 From: javier@KJSL.COM (Javier Henderson) Date: Sun, 8 Sep 2002 19:30:22 -0700 Subject: [Mailman-Developers] 2.1b3+ problem with held up postings that shouldn't Message-ID: <15740.1982.234397.196534@grumman.kjsl.com> The environment: FreeBSD 4.6-STABLE, Python 2.1.2 from the ports, sendmail 8.11.6, Apache 1.3.23 from the ports, and Mailman 2.1b3+ built from the Sept 3 CVS tree. There are several lists running on the system, the behavior for some of them is set for postings from nonsubscribed addresses to be forwarded to the list owner and otherwise discarded. However, they are instead getting held up for approval. Any ideas? -jav From noreply@sourceforge.net Mon Sep 9 16:55:39 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 09 Sep 2002 08:55:39 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-606615 ] unsubscribing via the mail interface Message-ID: Feature Requests item #606615, was opened at 2002-09-09 04:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=606615&group_id=103 Category: None Group: None >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Ray Gardener (asrag) Assigned to: Nobody/Anonymous (nobody) Summary: unsubscribing via the mail interface Initial Comment: Unsubscribing via the mail interface currently requires the list password. What would be nice would be if this password were not supplied a confirmation message would go back to the subscriber with a unique id for confirmation of the request on mail back. Alternatively some option for requesting the password via a mail request woud also help R Gardener ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-09 11:55 Message: Logged In: YES user_id=12800 This is already in Mailman 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=606615&group_id=103 From lrosa@mail.hypertrek.info Mon Sep 9 17:04:48 2002 From: lrosa@mail.hypertrek.info (Luigi Rosa) Date: Mon, 9 Sep 2002 18:04:48 +0200 Subject: [Mailman-Developers] stupid CVS question... In-Reply-To: <08410D19-C3A2-11D6-A383-0003934516A8@plaidworks.com> References: <08410D19-C3A2-11D6-A383-0003934516A8@plaidworks.com> Message-ID: <27192418234.20020909180448@mail.hypertrek.info> Hello Chuq, Monday, September 9, 2002, 5:12:54 AM, you wrote: CVR> What's the magic incantation for this? obviously, my CVS hacking is CVR> weak.... Mine is not very strong, but it works. Move in the mailman source and issue ONCE this command: cvs -d:pserver:anonymous@cvs.mailman.sourceforge.net:/cvsroot/mailman co mailman To update the source issue, move to the source directory and issue this command: cvs -z3 -d:pserver:anonymous@cvs.mailman.sourceforge.net:/cvsroot/mailman update mailman Then make make install as usual. This is what I usually do. Once in a while (or when I see that the configure file has been update) I issue the ./configure command before make;make install I don't know if this is the right thing to do, if anyone has better suggestions, so much the better. -- Best regards, Luigi mailto:lrosa@mail.hypertrek.info From posel@inf.fu-berlin.de Mon Sep 9 18:07:16 2002 From: posel@inf.fu-berlin.de (Johannes Posel) Date: Mon, 9 Sep 2002 19:07:16 +0200 Subject: [Mailman-Developers] Fwd: eMail command processing? (was: [Mailman-Users] Error in *eMail* rejecting a moderation request?) In-Reply-To: <14132491720.20020902151217@inf.fu-berlin.de> References: <18515208879.20020824154809@inf.fu-berlin.de> <14132491720.20020902151217@inf.fu-berlin.de> Message-ID: <18930878230.20020909190716@inf.fu-berlin.de> Dear Mailman developers, I've posted my question already to the users list, but did not get any feedback, so perhaps this is a bug? Thanks for your help! ===8<==============Original message text=============== > I'm running Mailman 2.1b3, and it works fine after a few install > headaches ;) My MTA is Exim v3.36, and I've set it up according to > README.EXIM. > Now, a list moderator got an approval request[1] for a message held in > the mod queue, which had inside these instructions as well[2]. The > subject was "confirm ..." with some sort of code in it. He wanted to > try it, but got only an error back: >> The results of your email command are provided below. Attached is your >> original message. >> >> - Results: >> Invalid confirmation string. Note that confirmation strings expire >> approximately 3 days after the initial subscription request. If your >> confirmation has expired, please try to re-submit your original request or >> message. >> >> - Unprocessed: >> > If you reply to this message, keeping the Subject: header intact, >> > Mailman will discard the held message. Do this if the message is >> > spam. If you reply to this message and include an Approved: header >> > with the list password in it, the message will be approved for posting >> > to the list. The Approved: header can also appear in the first line >> > of the body of the reply. >> - Done. > Is this some kind of bug or error in my setup? As he rightly points > out, if Mailman provides him with an eMail based moderation, he'd > really want to use it. > Thanks for any input! > Cheers, > Johannes mailto:posel@inf.fu-berlin.de > [1] > As list administrator, your authorization is requested for the > following mailing list posting: > List: Cafe@xyz > From: somebody@someplace.tld > Subject: Hi > Reason: Posts by member are currently quarantined for moderation > At your convenience, visit: > http://stromgrade.its-toasted.org/mailman/admindb/cafe > to approve or deny the request. > [2] > If you reply to this message, keeping the Subject: header intact, > Mailman will discard the held message. Do this if the message is > spam. If you reply to this message and include an Approved: header > with the list password in it, the message will be approved for posting > to the list. The Approved: header can also appear in the first line > of the body of the reply. ===8<===========End of original message text=========== Thanks again, Johannes mailto:posel@inf.fu-berlin.de -- You have an unusual magnetic personality. Don't walk too close to metal objects which are not fastened down. From les@2pi.org Mon Sep 9 19:01:42 2002 From: les@2pi.org (Les Niles) Date: Mon, 9 Sep 2002 11:01:42 -0700 Subject: [Mailman-Developers] A question about OutgoingRunner and SMTPDirect Message-ID: <200209091801.LAA03056@mutiny.2pi.org> When SMTPDirect has a temporary delivery failure, it raises an exception with a list of the failed recipients. But OutgoingRunner leaves the message queued with the original recipient list. There's some logic in SMTPDirect to keep a list of undelivered recipients, but AFAICT only when an exception is raised by the lower-level delivery function, which doesn't happen for these temporary delivery failures. (The particular failure we see, pretty frequently, is a "450 -- enable to check MX record", for a single recipient, which results in almost the entire list getting the message over and over.) Is this an oversight, or a design decision based on the behavior of the smtp delivery mechanism? If the former I'd be happy to fix it, but if it's the latter I'd rather not waste my time nor break our Mailman. :) -les From noreply@sourceforge.net Mon Sep 9 22:22:44 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 09 Sep 2002 14:22:44 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-606978 ] explicit email Reply-To header Problem Message-ID: Bugs item #606978, was opened at 2002-09-09 17:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=606978&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Joel Webb (webbgroup) Assigned to: Nobody/Anonymous (nobody) Summary: explicit email Reply-To header Problem Initial Comment: I am running RH 7.3 with mailman 2.0.12 I have configured some list to use a specific email address to reply to. Now I am trying to delete the address and have the list server replies to back to the original poster. I have clicked on the Poster radiobox and delete the email address that is in the explicit email Reply-To header. After I click save changes, the Poster radiobox has been changed but the explicit email Reply-To header still stays inside the textbox without deletion. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=606978&group_id=103 From mradamlacey@hotmail.com Tue Sep 10 02:34:01 2002 From: mradamlacey@hotmail.com (Adam Lacey) Date: Mon, 09 Sep 2002 20:34:01 -0500 Subject: [Mailman-Developers] recompiling a python module Message-ID: Using Mailman 2.0.9, I am trying to limit access to certain administrative options (pretty much everything except for membership management) Barry Watson was helpful, but maybe anyone really good with python can help me more --- How can I recompile (specifically admin.py) into byte code (I assume admin.pyc) ?? Because it is linked to several other modules, I cant seem to get it to compile. By the way, my understanding is, to compile you enter the python environment and then use the compile command. Should I run 'make' in the source file to recompile everything with my edited admin.py? Basically I need some help in integrating my change into Mailman. Thanks _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com From noreply@sourceforge.net Tue Sep 10 20:32:16 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 10 Sep 2002 12:32:16 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-607469 ] Missing return in __nonzero__ Message-ID: Bugs item #607469, was opened at 2002-09-10 15:32 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=607469&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Jon Parise (parise) Assigned to: Nobody/Anonymous (nobody) Summary: Missing return in __nonzero__ Initial Comment: In Mailman/Cgi/options.py, the Global class's __nonzero__ method is missing a return statement. Execution results in a "TypeError: __nonzero__ must return an int" exception. Fix is attached. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=607469&group_id=103 From noreply@sourceforge.net Wed Sep 11 02:19:54 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 10 Sep 2002 18:19:54 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-607469 ] Missing return in __nonzero__ Message-ID: Bugs item #607469, was opened at 2002-09-10 15:32 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=607469&group_id=103 Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Jon Parise (parise) Assigned to: Nobody/Anonymous (nobody) Summary: Missing return in __nonzero__ Initial Comment: In Mailman/Cgi/options.py, the Global class's __nonzero__ method is missing a return statement. Execution results in a "TypeError: __nonzero__ must return an int" exception. Fix is attached. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-10 21:19 Message: Logged In: YES user_id=12800 Fixed, thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=607469&group_id=103 From pioppo@ferrara.linux.it Wed Sep 11 20:58:29 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Wed, 11 Sep 2002 21:58:29 +0200 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list In-Reply-To: <20020909011921.GI3806@merlins.org> References: <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> Message-ID: <20020911195829.GD3121@ferrara.linux.it> On Sun, Sep 08, 2002 at 06:19:21PM -0700, Marc MERLIN wrote: > > (yeah, I know that reply-to munging is considered harmful but I consider > > more important to keep discussions inside the lists and anyway this has > > I'm just amazed at how many times I've read this complete nonsense. Marc, I see you are the only one fighting my request and I have 3 people saying it's ok for them. I think that not implementing this feature we wouldn't improve people's usage of reply-to in any way... we'd just leave the situation as it is, e.g. 99% of the people doesn't {know how, want} to use their mailer the way you teach. We already have a big disclaimer stating the reasons why people should choose reply-to-poster, including a link to a detailed document. Don't you think this is enough to educate people? Don't you think that people aware of the problem can have still valid reasons to choose another option in their environment? Definitely we should stick to mechanism, not policy. > What you all are doing is furthering people's ignorance of their > mail clients functionality and preventing people from replying This is no longer true. Thanks to the multiple reply-to feature we're preventing nothing. > There is a reason why you have at least two reply functions: reply to > author and reply to all/list. Yes, it does mean you have to use your > brain and decide which one you want to do. > Any attempt to make this choice go away with Agreed, but what I want to develop is a feature where Mailman simply suggests "The Right Thing", without removing your freedom degree. > Please leave people in peace and let them decide for themselves right! please leave admins in peace and let them decide for themselves. > By forcing a reply to list upon them, you are removing that > choice again, I'm neither removing nor forcing anything. -- Adde parvum parvo magnus acervus erit. Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From marc_news@merlins.org Wed Sep 11 22:12:05 2002 From: marc_news@merlins.org (Marc MERLIN) Date: Wed, 11 Sep 2002 14:12:05 -0700 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list In-Reply-To: <20020911195829.GD3121@ferrara.linux.it> References: <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911195829.GD3121@ferrara.linux.it> Message-ID: <20020911211205.GA23883@merlins.org> On Wed, Sep 11, 2002 at 09:58:29PM +0200, Simone Piunno wrote: > On Sun, Sep 08, 2002 at 06:19:21PM -0700, Marc MERLIN wrote: > > > > (yeah, I know that reply-to munging is considered harmful but I consider > > > more important to keep discussions inside the lists and anyway this has > > > > I'm just amazed at how many times I've read this complete nonsense. > > Marc, I see you are the only one fighting my request and I have > 3 people saying it's ok for them. I'm opposing the incorrect statement, not the feature. > We already have a big disclaimer stating the reasons why people > should choose reply-to-poster, including a link to a detailed > document. Don't you think this is enough to educate people? You'd think. People wiz right through it looking for the "where do I click to override" > Don't you think that people aware of the problem can have still > valid reasons to choose another option in their environment? I don't honestly care that much, but I do care about the "since we have to use reply-to for discussion lists" kind statements. What mucking around you want to do with the Reply-To header doesn't really matter, it just further encourages its (mis)use > > What you all are doing is furthering people's ignorance of their > > mail clients functionality and preventing people from replying > > This is no longer true. > Thanks to the multiple reply-to feature we're preventing nothing. Sorry, not true. When you set a reply-to to any value, you are preventing the user to chose between reply to list/all or just replying to the original sender. Reply-To is typically not conditional (except for good MUAs like mine that can be told to ignore it altogether) You are also try to further mis-teach people to use the reply function to magically do the right thing in all cases (which of course it can't) > Agreed, but what I want to develop is a feature where Mailman simply > suggests "The Right Thing", without removing your freedom degree. Reply-To is not a suggestion, it's a redirection of the answer. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. 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 jarrell@vt.edu Wed Sep 11 22:46:58 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Wed, 11 Sep 2002 17:46:58 -0400 Subject: [Mailman-Developers] mailmanctl Message-ID: <5.1.0.14.2.20020911174608.00a1a430@mail.vt.edu> So, is there are real need for mailmanctl to dump the entire 3K usage text into the error log if you happen to prematurely hit enter before your fingers remember to type "start"? From claw@kanga.nu Thu Sep 12 05:26:58 2002 From: claw@kanga.nu (J C Lawrence) Date: Wed, 11 Sep 2002 21:26:58 -0700 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list In-Reply-To: Message from Simone Piunno of "Wed, 11 Sep 2002 21:58:29 +0200." <20020911195829.GD3121@ferrara.linux.it> References: <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911195829.GD3121@ferrara.linux.it> Message-ID: <21670.1031804818@kanga.nu> On Wed, 11 Sep 2002 21:58:29 +0200 Simone Piunno wrote: > On Sun, Sep 08, 2002 at 06:19:21PM -0700, Marc MERLIN wrote: >>> (yeah, I know that reply-to munging is considered harmful but I >>> consider more important to keep discussions inside the lists and >>> anyway this has >> I'm just amazed at how many times I've read this complete nonsense. > Marc, I see you are the only one fighting my request and I have 3 > people saying it's ok for them. No, for most of us know this religious debate of old, are tired of it, understand it far better than we're interested in, and just don't bother. >> By forcing a reply to list upon them, you are removing that choice > again, I'm neither removing nor forcing anything. Given a list which munges Reply-To in any manner, how do I: a) Move a thread on to a different list? b) Ensure that all replies default to me only and not the list (so that I may summarise later)? c) Trivially (default command) reply to author only? d) Remove myself from followups to a thread? -- 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 Thu Sep 12 07:04:41 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Wed, 11 Sep 2002 23:04:41 -0700 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list In-Reply-To: <21670.1031804818@kanga.nu> Message-ID: <870D2C4C-C615-11D6-8B0F-0003934516A8@plaidworks.com> On Wednesday, September 11, 2002, at 09:26 PM, J C Lawrence wrote: >> Marc, I see you are the only one fighting my request and I have 3 >> people saying it's ok for them. > > No, for most of us know this religious debate of old, are tired of it, > understand it far better than we're interested in, and just don't > bother. > If you insist on counting noses, I guess I'll add mine. I avoid reply-to arguments because I've found people don't want to discuss it, they want to browbeat everyone until the other side gives up in disgust and gives them what they want. That's not a discussion, that's a lecture. At best. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ The first rule of holes: If you are in one, stop digging. From nb@cisto.com Thu Sep 12 10:52:38 2002 From: nb@cisto.com (Norbert Bollow) Date: Thu, 12 Sep 2002 11:52:38 +0200 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list In-Reply-To: <21670.1031804818@kanga.nu> (message from J C Lawrence on Wed, 11 Sep 2002 21:26:58 -0700) References: <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911195829.GD3121@ferrara.linux.it> <21670.1031804818@kanga.nu> Message-ID: <200209120952.g8C9qcp25575@quill.local> Simone Piunno wrote: > >>> (yeah, I know that reply-to munging is considered harmful but I > >>> consider more important to keep discussions inside the lists and > >>> anyway this has Sounds like you've never seen a list blow up in a mail loop because of some broken "vacation" autoresponder robot which sends automated responses to the Reply-To: address. > >> I'm just amazed at how many times I've read this complete nonsense. > > > Marc, I see you are the only one fighting my request and I have 3 > > people saying it's ok for them. J C Lawrence replied: > No, for most of us know this religious debate of old, are tired of it, > understand it far better than we're interested in Yes. > Given a list which munges Reply-To in any manner, how do I: > > a) Move a thread on to a different list? > > b) Ensure that all replies default to me only and not the list (so > that I may summarise later)? > > c) Trivially (default command) reply to author only? > > d) Remove myself from followups to a thread? e) Cross-post a discussion across two mailing lists? (Sometimes that is the right thing to do.) f) Ensure that my backup email address gets copied on a thread? (E.g. Because my primary email address which is subscribed to the list is temporarily broken or something.) Greetings, Norbert. -- Founder & Steering Committee member of http://gnu.org/projects/dotgnu/ 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 noreply@sourceforge.net Thu Sep 12 18:49:25 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 12 Sep 2002 10:49:25 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-608524 ] QRUNNER is fucking the machine perform.. Message-ID: Bugs item #608524, was opened at 2002-09-12 14:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608524&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jozeph Brasil (jozeph) Assigned to: Nobody/Anonymous (nobody) Summary: QRUNNER is fucking the machine perform.. Initial Comment: Hello Everybody, I'm with a big problem... :( I'm running mailman-2.0.13-1U70_1cl under python-2.1-14cl with gcc-2.95.3-20U70_1cl in an IBM NETFINITY 300 PIII 500 XEXON with 64MiB. When qrunner starts the proccess my machine stay totally SLOWLY... Look the qrunner proccess: mailman 12365 95.7 51.2 32340 30092 tty1 R 15:27 4:37 python -S cron/qrunner How you can see... look at the CPU / MEM usage... I need to wait more less 30 minutes to qrunner stop the proccess and... In qfiles directory have only 10 or 15 messages in delivery... Anyone have idea what's up? How fix that? PS: I disable my mailman at moment... :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608524&group_id=103 From noreply@sourceforge.net Thu Sep 12 18:51:37 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 12 Sep 2002 10:51:37 -0700 Subject: [Mailman-Developers] [ mailman-Patches-413752 ] Coerce posts to plain text. Message-ID: Patches item #413752, was opened at 2001-04-04 14:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Geoffrey T. Dairiki (dairiki) Assigned to: Nobody/Anonymous (nobody) Summary: Coerce posts to plain text. Initial Comment: This patch adds the ability to have all posts to a mailing list forced into a MIME text/plain format. Many mailing lists have a charter which forbids binary and HTML posts to the list. This patch allows such a charter to be enforced is a maximally transparent manner. The feature is configurable on a per-list basis. If enabled, all posts to the list are run through a filter which: Squashes multipart messages into a single flat message (it picks the most plain-text-like alternative from multipart/alternative entities.) Converts 'text/html', 'text/enriched', and 'text/richtext' entities to 'text/plain'. Deletes cruft headers from content of type 'message/rfc822'. Deletes any uuencoded files from 'text/plain' entities. Entities of any other types are assumed to be binary attachements are are deleted. This patch is on mailman-2.0.3. ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 14:51 Message: Logged In: YES user_id=17693 Hey dairiki, please... look at https://sourceforge.net/tracker/index.php?func=detail&aid=608524&group_id=103&atid=100103 I don't know if the problem is plaintext bug! :( ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 14:16 Message: Logged In: YES user_id=45814 Note also that the recent patch sets also incorporate patch #415448 [1]: a minor patch so that Mailman recognizes bounce messages from swbell.net ("Sun Internet Mail Server"). This patch inadvertently slipped in, but it does no harm. If you don't like it just delete the patches to Mailman/Bouncers/SimpleMatch.py. Reference: [1] http://sf.net/tracker/?func=detail&aid=415448&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-30 13:07 Message: Logged In: YES user_id=45814 Enh? The current version of Mailman is 2.0.13. That said, the latest patch set (named mailman-2.0.13-plaintext-0.17.patch, and attached below) will work fine, I think, for Mailmain versions 2.0.x back to at least 2.0.8, and probably earlier. Feel free to e-mail me privately for more help. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-30 12:02 Message: Logged In: NO I'm new to Mailman. I don't understand why you don't have a patch for the current version of Mailman, 2.0.10. Can I apply an earlier patch safely? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-28 01:40 Message: Logged In: YES user_id=12800 BTW, I've finally added that link from the wiki to this patch. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-28 00:44 Message: Logged In: YES user_id=45814 It seems the patches continue to work (basically unchanged) for Mailman-2.0.13. Updated patches are attached below. The patches as well as a pre-patched Mailman-2.0.13 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-27 21:22 Message: Logged In: NO Hi Dairiki, It's me... I added your patch in my latest version and it's running OK... you can post the patch here! :) ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-08-27 16:00 Message: Logged In: YES user_id=17693 Hello dairiki... do you have this patch for Mailman-2.0.13 ? ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2002-08-13 12:43 Message: Logged In: YES user_id=45814 I don't have strong feelings, but my druthers would be to wait until 2.1 is officially designated "stable". A link from the wiki would be great! (There is/was already a link from the FAQ.) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-13 12:29 Message: Logged In: YES user_id=12800 Since this patch is against 2.0.x and since MM2.1 provides support for stuff like this, I'm inclined to close this patch. I'd be willing to add a link to this from the unofficial patches wiki. What do you think? ---------------------------------------------------------------------- Comment By: Seb Wills (sebwills) Date: 2002-02-23 13:20 Message: Logged In: YES user_id=467580 This patch seems to leave any preamble above the first part of a multipart message intact. Many mailers put blurb such as "This is a MIME-encoded message; you will need a MIME- aware mail client to see all of this message." here, which it makes no sense to reproduce after the mail has be coerced into plaintext. Looks like it's easy enough to change this behaviour by commenting out the line mimetools.copybinary(infp, outfp) # copy preamble from Mailman/FilteringMimeWriter.py ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-12-15 16:15 Message: Logged In: YES user_id=45814 Another bug fix. Lines which contain nothing but the word 'end' mysteriously dissapear. (Reported by David Gibbs.) The only changed file in Mailman/FilteringMimeWriter.py, I've attached the latest version of that file to this page. As usual, patches on mailman 2.0.8 are also attached. Diffs and a patched Mailman-2.0.8 tarball are at ftp://www.dairiki.org/pub/mailman/ ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-09-08 17:08 Message: Logged In: YES user_id=45814 More fixes. * Mailman/FilteringMimeWriter.py: Fixes for bugs in python 1.5.2's quopri library module. The plaintext patches are at version 0.14. Look for the patches on Mailman 2.0.6, as well as a complete tarball of patched Mailman 2.0.6 code at ftp://www.dairiki.org/pub/mailman/ Patches on 2.0.6 are also attached to this page. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-08-25 16:34 Message: Logged In: YES user_id=45814 More fixes: * Mailman/PlaintextMimeWriter.py: Change Message-ID: of filtered messages. * Mailman/pythonlib/multifile.py: Fix obscure but occasionally fatal bug. The first fix is very minor. The second fix fixes a bug which caused the plaintext filter to fail occasionally. Diffs from mailman-2.0.6 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.patch.gz Pre-patched mailman-2.0.6 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.6-plaintext-0.13.tgz ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-06-16 15:33 Message: Logged In: NO After applying this patch to 2.0.5, I found that I had to add this line manually to my existing config file $prefix/Mailman/mm_cfg.py... DEFAULT_FORCE_PLAIN_TEXT = 0 If this line is not added, any web requests and any messages posted will produce an error "AttributeError : DEFAULT_FORCE_PLAIN_TEXT". Not sure if I did something wrong or if this is normal, but I wanted to advise others just in case ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-19 20:49 Message: Logged In: YES user_id=45814 More fixes: * Mailman/FilteringMimeWriter.py: Handle 'content-type: multipart' (no subtype) gracefully. * Mailman/Handlers/PlainText.py: Catch exceptions (fatal errors) from plaintext filter. When exception is caught, an error is logged, but the message is passed on unfiltered. (A diagnostic message is added to the message headers.) This should make it so little piddly bugs in the filter will get noticed, but at the same time will not cause messages to get stuck in the queue. Patches from mailman-2.0.5 are available from this page and are also at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.patch.gz Pre-patched mailman-2.0.5 source code is at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.10.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-17 16:27 Message: Logged In: YES user_id=45814 Another minor bugfix: it turns out pythons mimetools doesn't treat the content-transfer-encoding is a case insensitive fashion --- so now we smash the case ourself. A new patch set on mailman-2.0.5 is available on this page. Pre-patched mailman source code can be found at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.9.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 01:38 Message: Logged In: YES user_id=45814 Disregard last. (Apparently one can't attache files bigger than 256 kb.) Mailman-2.0.5 with plaintext patches applied can be found (for a limited time) at: ftp://www.dairiki.org/pub/mailman/mailman-2.0.5-plaintext-0.8.tgz ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 01:33 Message: Logged In: YES user_id=45814 If you don't want to mess with patching the source, I've also attached (below) a tarball of the mailman-2.0.5 source with my patches already applied. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-08 01:16 Message: Logged In: YES user_id=45814 Here's a rough outline of how to proceed: 1. Start by unpacking a fresh copy of mailman-2.0.5.tgz 2. Change into the top source directory (which was created in the previous step. 3. Try applying my patches with: patch -p1 < [where.ever]/mailman-2.0.5-plaintext-0.8.patch (that's "dash pee one") That should work --- you should not get any warnings or prompts from patch. If you do, something is fishy. 4. Run ./configure and 'make install' as usual (read mailman's INSTALL for instructions on this.) Feel free to write me at . ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-05-08 00:30 Message: Logged In: NO For *some* reason when I apply the patch (the newest one) to my freshly downloaded version of Mailman 2.0.5 and compile and install mail never reaches the list. I've tried without the patch and everything works fine... perhaps I'm patching wrong? I'm just saying: patch < name_of_patch It makes me fix a few paths to some of the files, but that's it... :-/ Any help would be appriciated! ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-05-07 13:25 Message: Logged In: YES user_id=45814 Fixed bug (reported by Pug Bainter -- thanks!) New patches, on mailman-2.0.5 uploaded (below). The only real change is: --- 0.5/Mailman/FilteringMimeWriter.py Wed, 04 Apr 2001 10:04:36 -0700 dairiki (mailman/k/4_FilteringM 1.2 664) +++ 0.8(w)/Mailman/FilteringMimeWriter.py Mon, 07 May 2001 09:05:18 -0700 dairiki (mailman/k/4_FilteringM 1.3 664) @@ -185,8 +185,12 @@ pname, pval = string.split(param, '=', 1) return (string.lower(pname), rfc822.unquote(pval)) - return map(split_param, message.getplist()) - + def valid_param(param): + return '=' in param + + # Trailing ;'s in content-type yield empty strings from getplist(). + return map(split_param, + filter(valid_param, message.getplist())) def discards_data(fp): """Determine whether file object ignores data written to it. ---------------------------------------------------------------------- Comment By: Geoffrey T. Dairiki (dairiki) Date: 2001-04-05 12:37 Message: Logged In: YES user_id=45814 I've just made a minor change: HTML converted to plain-text now includes a list of links at the end of the message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=413752&group_id=103 From noreply@sourceforge.net Thu Sep 12 20:35:59 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 12 Sep 2002 12:35:59 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-608524 ] QRUNNER is fucking the machine perform.. Message-ID: Bugs item #608524, was opened at 2002-09-12 14:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608524&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None >Priority: 9 Submitted By: Jozeph Brasil (jozeph) Assigned to: Nobody/Anonymous (nobody) Summary: QRUNNER is fucking the machine perform.. Initial Comment: Hello Everybody, I'm with a big problem... :( I'm running mailman-2.0.13-1U70_1cl under python-2.1-14cl with gcc-2.95.3-20U70_1cl in an IBM NETFINITY 300 PIII 500 XEXON with 64MiB. When qrunner starts the proccess my machine stay totally SLOWLY... Look the qrunner proccess: mailman 12365 95.7 51.2 32340 30092 tty1 R 15:27 4:37 python -S cron/qrunner How you can see... look at the CPU / MEM usage... I need to wait more less 30 minutes to qrunner stop the proccess and... In qfiles directory have only 10 or 15 messages in delivery... Anyone have idea what's up? How fix that? PS: I disable my mailman at moment... :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608524&group_id=103 From noreply@sourceforge.net Thu Sep 12 20:54:42 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 12 Sep 2002 12:54:42 -0700 Subject: [Mailman-Developers] [ mailman-Patches-483696 ] Categorisation of lists in ListInfo View Message-ID: Patches item #483696, was opened at 2001-11-20 04:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=483696&group_id=103 Category: Web UI Group: None Status: Open Resolution: None Priority: 5 Submitted By: andy (andy_cat) Assigned to: Nobody/Anonymous (nobody) Summary: Categorisation of lists in ListInfo View Initial Comment: This patch allows categorisation of lists when displaying the "list of lists" in listinfo.py and admin.py It does this by adding a new property to the MailList object called "categories", a new MailList member function called GetListCategories, and a dictionary making function in Utils.py Changed files are: listinfo.py admin.py Defaults.py MailList.py Utils.py Version.py htmlformat.py Preexisting lists will show up as "Unclassified" once you apply the patch and set LISTINFO_USE_CATEGORIES = 1 in Defaults.py To set the categories, either use the Mailman list admin GUI for the list and set the "categories affilations" value (a list can be in multiple categories) in the General Options page ( Configuration Categories ) or if you have many lists to categorise it will be easier to use command line python. $python -i bin/withlist Loading list: (unlocked) >>> m.Lock() >>> m.categories='testing' >>> m.Save() >>> Unlocking (but not saving) list: Finalizing substitute your lists name for , and if you have lots you may want to script this. Python code done by Patch and these docs by ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 16:54 Message: Logged In: YES user_id=17693 Hello, I install your patch but the listinfo don't show the list names... admin is working ok... the problem is listinfo... if possible, see: http://lists.homelinux.com/mailman/listinfo,admin, etc Thanks, ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=483696&group_id=103 From raquel@thericehouse.net Thu Sep 12 22:40:05 2002 From: raquel@thericehouse.net (Raquel Rice) Date: Thu, 12 Sep 2002 14:40:05 -0700 Subject: [Mailman-Developers] Moderator's Interface Message-ID: <20020912144005.7d8d9e95.raquel@thericehouse.net> I've just upgraded to using Mailman 2.1b3, which provides for an "administrator" and a "moderator". In the password setup, I've specified seperate passwords and in the general options I've specified seperate addresses. However, at the admin login, the moderator cannot login using her password. Is there a seperate page for the moderator(s) to login? The only thing I've been able to find is "admindb" for moderation purposes, but not for adding/editing/removing subscriber info. I'm lost. Thanks! -- Raquel ============================================================ The true secret of giving advice is, after you have honestly given it, to be perfectly indifferent whether it is taken or not and never persist in trying to set people right. --Hannah Whitall Smith, Writer and Evangelist From pioppo@ferrara.linux.it Thu Sep 12 23:30:31 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Fri, 13 Sep 2002 00:30:31 +0200 Subject: [Mailman-Developers] feature request: new option forreply_goes_to_list In-Reply-To: <200209120952.g8C9qcp25575@quill.local> <870D2C4C-C615-11D6-8B0F-0003934516A8@plaidworks.com> <21670.1031804818@kanga.nu> <20020911211205.GA23883@merlins.org> <3D7FA7BE.3397AC80@nleaudio.com> References: <20020911195829.GD3121@ferrara.linux.it> <21670.1031804818@kanga.nu> <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911195829.GD3121@ferrara.linux.it> <20020911211205.GA23883@merlins.org> <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911195829.GD3121@ferrara.linux.it> <3D7FA7BE.3397AC80@nleaudio.com> Message-ID: <20020912223031.GA5081@ferrara.linux.it> On Wed, Sep 11, 2002 at 02:12:05PM -0700, Marc MERLIN wrote: > > Thanks to the multiple reply-to feature we're preventing nothing. > > Sorry, not true. > When you set a reply-to to any value, you are preventing the user to chose > between reply to list/all or just replying to the original sender. bogus argument: when you don't set a reply-to you are preventing the user to choose between reply to originasender/all or just replying to the list. you can't have everything on single button, so you are always preventing the alternative use the from button, whatever it was. > Reply-To is typically not conditional (except for good MUAs like mine that > can be told to ignore it altogether) sorry, can you rephrase? On Wed, Sep 11, 2002 at 09:26:58PM -0700, J C Lawrence wrote: > Given a list which munges Reply-To in any manner, how do I: > > a) Move a thread on to a different list? people will move if you ask and they want (they are free to choose, you are not free to force them). With multiple reply-to you can start cross-posting and the reply to the reply to your message could be on the 2nd list only. This is again a matter of policy and you could like this kind of things but another admin could even want to completely forbid'em. Anyway, I grant you that this case is messed up by reply-to-list. > b) Ensure that all replies default to me only and not the list (so > that I may summarise later)? Agreed > c) Trivially (default command) reply to author only? bogus, see the answer to Marc. > d) Remove myself from followups to a thread? just avoid using reply-to... by default they will reply to the list. On Thu, Sep 12, 2002 at 11:52:38AM +0200, Norbert Bollow wrote: > Sounds like you've never seen a list blow up in a mail loop because of > some broken "vacation" autoresponder robot which sends automated > responses to the Reply-To: address. no, I've never seen a loop caused by this, but I've seen several loops. If you are really concerned by loops you could use the max-per-day feature already in place for -owner autoresponder. > e) Cross-post a discussion across two mailing lists? (Sometimes that is > the right thing to do.) sorry, not sure I understand.... - I send the message "To: a,b" and "Reply-To: a,b" - Reply-To: is left untouched by Mailman (even if set with reply-to-list) - People will reply to "a,b" by default, not carrying on the Reply-To: (regardless of its value, so configuration doesn't matter) where is the problem? > f) Ensure that my backup email address gets copied on a thread? > (E.g. Because my primary email address which is subscribed to the > list is temporarily broken or something.) again, you can only affect the 1st reply... replies to replies to your message won't see your reply-to: thanks to multiple reply-to having another address copied in the 1st reply is not a problem. Summary: Reply-to-munging with multiple address prevents those 2 cases: > a) Move a thread on to a different list? > b) Ensure that all replies default to me only and not the list (so > that I may summarise later)? but on the usability side, the very common reply-to-list case is made more difficult for the user (he can't 1-click-reply to the list only [1]: he has to reply to all and then remove the unwanted addresses). Admins have then a tradeoff: "what has more value for my users?" This is a matter of policy and there are certainly lists where most users would answer "I prefer my freedom to do things like moving threads and summarizing and don't care for usability" and there are also many lists where they'd asnwer "I prefer usability and I'll never use those 2 exotic cases where pristine reply-to is required". Policy decisions should be left to the admin. [1] practically noone uses mutt and the nice L key feature. I'm the only one :) -- Adde parvum parvo magnus acervus erit. Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From noreply@sourceforge.net Fri Sep 13 02:40:52 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 12 Sep 2002 18:40:52 -0700 Subject: [Mailman-Developers] [ mailman-Patches-433767 ] Subscriber Profiler Message-ID: Patches item #433767, was opened at 2001-06-16 13:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=433767&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Swee Heng (sweeheng) Assigned to: Nobody/Anonymous (nobody) Summary: Subscriber Profiler Initial Comment: This is a patch to mailman-2.0.5 to implement a "subscriber profiler" feature. See my 2 postings on the mailing list for more details: o http://mail.python.org/pipermail/mailman-developers/2001-May/004270.html o http://mail.python.org/pipermail/mailman-developers/2001-June/004279.html Feel free to email me comments and queries at . (I finally figured out how to use SourceForge! :) ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 22:40 Message: Logged In: YES user_id=17693 Hello... I install mailman from a RPM file... and install the patch manually... I need to know how COMPILE profile CGI-BIN file manually... do you know how? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=433767&group_id=103 From dan.mick@sun.com Fri Sep 13 03:16:42 2002 From: dan.mick@sun.com (Dan Mick) Date: Thu, 12 Sep 2002 19:16:42 -0700 Subject: [Mailman-Developers] feature request: new option forreply_goes_to_list References: <20020911195829.GD3121@ferrara.linux.it> <21670.1031804818@kanga.nu> <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911195829.GD3121@ferrara.linux.it> <20020911211205.GA23883@merlins.org> <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911195829.GD3121@ferrara.linux.it> <3D7FA7BE.3397AC80@nleaudio.com> <20020912223031.GA5081@ferrara.linux.it> Message-ID: <3D814A8A.3050102@sun.com> Simone Piunno wrote: > On Wed, Sep 11, 2002 at 02:12:05PM -0700, Marc MERLIN wrote: > > >>>Thanks to the multiple reply-to feature we're preventing nothing. >> >> >>Sorry, not true. >>When you set a reply-to to any value, you are preventing the user to chose >>between reply to list/all or just replying to the original sender. > > > bogus argument: > when you don't set a reply-to you are preventing the user to choose > between reply to originasender/all or just replying to the list. Wrong. Every mailreader I've ever used has a two-option (at least) choice: reply to sender ("From:") or reply to all (From: and Cc:). If Reply-To: is set, "reply to sender" uses that instead; you can't reply to "From:" without editing the address. > you can't have everything on single button, so you are always preventing > the alternative use the from button, whatever it was. This doesn't make any sense. From terri@zone12.com Fri Sep 13 04:54:35 2002 From: terri@zone12.com (Terri Oda) Date: Thu, 12 Sep 2002 23:54:35 -0400 Subject: [Mailman-Developers] Keeping only the last X months of archives Message-ID: <20020913035435.GA1338@ostraya.zone12.com> Someone suggested that on our job posting list, there was no point to keeping postings more than, say, 3 months old. It sounds like everyone agrees that it's a waste of space and it's probably up to me to implement something. It shouldn't be too hard to make a little cron script to move the older archives (I'm a pack rat with data, sometimes. ;) ) and clean & rebuild the html, but before I sit down and do it... is this already an option somewhere? Has anyone got an implementation already? And if not, would such a thing be useful to anyone else? Terri From noreply@sourceforge.net Fri Sep 13 07:38:43 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 12 Sep 2002 23:38:43 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-608774 ] Stripped port info from DEFAULT_URL_HOST Message-ID: Bugs item #608774, was opened at 2002-09-13 06:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608774&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Eugene Eric Kim (eekim) Assigned to: Nobody/Anonymous (nobody) Summary: Stripped port info from DEFAULT_URL_HOST Initial Comment: I installed Mailman 2.1b3 on a Linux box with Apache 2 running on port 2000. I added the following lines to mm_cfg.py: DEFAULT_URL_HOST = "host.domain:2000" add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) (host.domain is my hostname and domain name.) I then accessed http://host.domain:2000/mailman/admin and created a new list. The list was created just fine, except in the resulting "Mailing list creation results" page, the first two options ("Visit list info" and "Visit list admin") stripped port 2000 from the URL. Also, the confirmation e-mail I received also stripped port 2000 from the URLs. However, the third option ("Create another list") did have port 2000 in the URL. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608774&group_id=103 From noreply@sourceforge.net Fri Sep 13 07:50:49 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 12 Sep 2002 23:50:49 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-608774 ] Stripped port info from DEFAULT_URL_HOST Message-ID: Bugs item #608774, was opened at 2002-09-13 06:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608774&group_id=103 Category: Web/CGI Group: 2.1 beta >Status: Deleted Resolution: None Priority: 5 Submitted By: Eugene Eric Kim (eekim) Assigned to: Nobody/Anonymous (nobody) Summary: Stripped port info from DEFAULT_URL_HOST Initial Comment: I installed Mailman 2.1b3 on a Linux box with Apache 2 running on port 2000. I added the following lines to mm_cfg.py: DEFAULT_URL_HOST = "host.domain:2000" add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) (host.domain is my hostname and domain name.) I then accessed http://host.domain:2000/mailman/admin and created a new list. The list was created just fine, except in the resulting "Mailing list creation results" page, the first two options ("Visit list info" and "Visit list admin") stripped port 2000 from the URL. Also, the confirmation e-mail I received also stripped port 2000 from the URLs. However, the third option ("Create another list") did have port 2000 in the URL. ---------------------------------------------------------------------- >Comment By: Eugene Eric Kim (eekim) Date: 2002-09-13 06:50 Message: Logged In: YES user_id=39362 Sorry. I realize now that I should have edited DEFAULT_URL_PATTERN instead of DEFAULT_URL_HOST. I did that, and the above problem went away. I also had to make sure I added a new PUBLIC_ARCHIVE_URL to my mm_cfg.py. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608774&group_id=103 From noreply@sourceforge.net Fri Sep 13 08:36:02 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 00:36:02 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-608789 ] Stripped port info from List-Archive URL Message-ID: Bugs item #608789, was opened at 2002-09-13 07:36 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608789&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Eugene Eric Kim (eekim) Assigned to: Nobody/Anonymous (nobody) Summary: Stripped port info from List-Archive URL Initial Comment: I'm running Mailman 2.1b3 on a host with Apache running on port 2000. In mm_cfg.py, I have: DEFAULT_URL_PATTERN = 'http://%s:2000/mailman/' PUBLIC_ARCHIVE_URL = 'http://%(hostname)s:2000/pipermail/%(listname)s' This works fine for HTML pages generated by the CGI scripts, as well as for the URLs sent out in the bodies of confirmation e-mails. However, the URLs contained in List-Archive headers in e-mails sent to lists do not have port 2000 in them. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608789&group_id=103 From claw@kanga.nu Fri Sep 13 09:35:24 2002 From: claw@kanga.nu (J C Lawrence) Date: Fri, 13 Sep 2002 01:35:24 -0700 Subject: [Mailman-Developers] feature request: new option forreply_goes_to_list In-Reply-To: Message from Simone Piunno of "Fri, 13 Sep 2002 00:30:31 +0200." <20020912223031.GA5081@ferrara.linux.it> References: <20020911195829.GD3121@ferrara.linux.it> <21670.1031804818@kanga.nu> <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911195829.GD3121@ferrara.linux.it> <20020911211205.GA23883@merlins.org> <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911195829.GD3121@ferrara.linux.it> <3D7FA7BE.3397AC80@nleaudio.com> <20020912223031.GA5081@ferrara.linux.it> Message-ID: <4877.1031906124@kanga.nu> On Fri, 13 Sep 2002 00:30:31 +0200 Simone Piunno wrote: > but on the usability side, the very common reply-to-list case is made > more difficult for the user (he can't 1-click-reply to the list only > [1]: he has to reply to all and then remove the unwanted addresses). You assumed that doing a group reply is (significantly) more difficult than doing a personal reply, as well as that the recipient list must be edited in either case. In general neither assumption is supportable. -- 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 Fri Sep 13 17:51:34 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 09:51:34 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-605933 ] subscribe by invite dies on dup user Message-ID: Bugs item #605933, was opened at 2002-09-07 03:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605933&group_id=103 Category: (un)subscribing Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) Summary: subscribe by invite dies on dup user Initial Comment: Playing with the "invite" feature, I invited myself, knowing I was already on the list. If you reply by email, it properly bounces back a "you're already subscribed" error. Click the web link, however, and fill out the form (which, btw mistakenly said that the moderater had to approve it on an open list; I don't remember if that's hardcoded or dynamic, but I *thought* it was dynamic) and when you submit it you get a traceback... the cgi-form really ought to catch this condition gracefully... Traceback (most recent call last): File "/home/mailman/scripts/driver", line 82, in run_main main() File "/home/mailman/Mailman/Cgi/confirm.py", line 110, in main subscription_confirm(mlist, doc, cookie, cgidata) File "/home/mailman/Mailman/Cgi/confirm.py", line 314, in subscription_confirm op, addr, pw, digest, lang = mlist.ProcessConfirmation( File "/home/mailman/Mailman/MailList.py", line 1072, in ProcessConfirmation self.ApprovedAddMember(userdesc) File "/home/mailman/Mailman/MailList.py", line 858, in ApprovedAddMember raise Errors.MMAlreadyAMember, email MMAlreadyAMember: jarrell@vt.edu ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 12:51 Message: Logged In: YES user_id=12800 There's another bug you didn't mention . The invite page should not allow you to invite a member. I'm fixing all three bugs now, thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605933&group_id=103 From noreply@sourceforge.net Fri Sep 13 19:16:13 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 11:16:13 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-608789 ] Stripped port info from List-Archive URL Message-ID: Bugs item #608789, was opened at 2002-09-13 03:36 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608789&group_id=103 Category: mail delivery Group: 2.1 beta >Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: Eugene Eric Kim (eekim) Assigned to: Nobody/Anonymous (nobody) Summary: Stripped port info from List-Archive URL Initial Comment: I'm running Mailman 2.1b3 on a host with Apache running on port 2000. In mm_cfg.py, I have: DEFAULT_URL_PATTERN = 'http://%s:2000/mailman/' PUBLIC_ARCHIVE_URL = 'http://%(hostname)s:2000/pipermail/%(listname)s' This works fine for HTML pages generated by the CGI scripts, as well as for the URLs sent out in the bodies of confirmation e-mails. However, the URLs contained in List-Archive headers in e-mails sent to lists do not have port 2000 in them. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 14:16 Message: Logged In: YES user_id=12800 Whenever you make a change to the mm_cfg.py file, you have to be sure to do a restart or your changes won't get picked up. Make the change, then do "mailmanctl restart". It worked for me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608789&group_id=103 From noreply@sourceforge.net Fri Sep 13 19:22:31 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 11:22:31 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-608789 ] Stripped port info from List-Archive URL Message-ID: Bugs item #608789, was opened at 2002-09-13 07:36 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608789&group_id=103 Category: mail delivery Group: 2.1 beta Status: Closed Resolution: Works For Me Priority: 5 Submitted By: Eugene Eric Kim (eekim) Assigned to: Nobody/Anonymous (nobody) Summary: Stripped port info from List-Archive URL Initial Comment: I'm running Mailman 2.1b3 on a host with Apache running on port 2000. In mm_cfg.py, I have: DEFAULT_URL_PATTERN = 'http://%s:2000/mailman/' PUBLIC_ARCHIVE_URL = 'http://%(hostname)s:2000/pipermail/%(listname)s' This works fine for HTML pages generated by the CGI scripts, as well as for the URLs sent out in the bodies of confirmation e-mails. However, the URLs contained in List-Archive headers in e-mails sent to lists do not have port 2000 in them. ---------------------------------------------------------------------- >Comment By: Eugene Eric Kim (eekim) Date: 2002-09-13 18:22 Message: Logged In: YES user_id=39362 Thanks! That corrected the problem. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 18:16 Message: Logged In: YES user_id=12800 Whenever you make a change to the mm_cfg.py file, you have to be sure to do a restart or your changes won't get picked up. Make the change, then do "mailmanctl restart". It worked for me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608789&group_id=103 From noreply@sourceforge.net Fri Sep 13 19:40:38 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 11:40:38 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-605263 ] Bad var in ListAdmin._UpdateRecords() Message-ID: Bugs item #605263, was opened at 2002-09-05 17:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605263&group_id=103 Category: configuring/installing Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Les Niles (lniles) Assigned to: Nobody/Anonymous (nobody) Summary: Bad var in ListAdmin._UpdateRecords() Initial Comment: ListAdmin._UpdateRecords() (in the CVS head, and as far as I can tell all the way back to its inception) refers to "mlist", which raises a NameError when updating some lists. Syntactically it would seem that this should be "self" instead, and experimentally that solves the problem. Here's the patch: *** ListAdmin.py.~1~ Wed Sep 4 23:25:26 2002 --- ListAdmin.py Thu Sep 5 00:38:24 2002 *************** *** 539,545 **** # pre-2.1a2 compatibility when, addr, passwd, digest = info fullname = '' ! lang = mlist.preferred_language elif len(info) == 5: # pre-2.1a4 compatibility when, addr, passwd, digest, lang = info --- 539,545 ---- # pre-2.1a2 compatibility when, addr, passwd, digest = info fullname = '' ! lang = self.preferred_language elif len(info) == 5: # pre-2.1a4 compatibility when, addr, passwd, digest, lang = info ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 14:40 Message: Logged In: YES user_id=12800 Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605263&group_id=103 From noreply@sourceforge.net Fri Sep 13 19:41:26 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 11:41:26 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-602077 ] make install fails with import error Message-ID: Bugs item #602077, was opened at 2002-08-29 16:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=602077&group_id=103 Category: configuring/installing Group: 2.1 beta >Status: Pending Resolution: None Priority: 5 Submitted By: Goeran Zaengerlein (timetrack) Assigned to: Nobody/Anonymous (nobody) Summary: make install fails with import error Initial Comment: I tried to install Mailman 2.1b3 and I followed the installation instruction exactly but make install fails with the following message: --- snip --- Compiling /usr/local/mailman/Mailman/versions.py ... Traceback (most recent call last): File "bin/update", line 44, in ? import paths ImportError: No module named paths make: *** [update] Error 1 --- snap --- SuSE 7.2 Python 2.2.1 gcc 2.95.3 The problem was already described here: http://mail.python.org/pipermail/mailman-users/2002- July/020991.html but no solution has been posted as far as I could see... Any idea what I did wrong? ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 14:41 Message: Logged In: YES user_id=12800 Moving to pending status, since I think this is the problem, but haven't heard an update from the submitter. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-05 02:22 Message: Logged In: YES user_id=12800 Did you install Python via RPM? If so, be sure you have the python-devel package installed. I don't know why this is, but I've seen reports of this problem when folks only have the python package installed. Installing the python-devel or installing Python from source seems to solve this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=602077&group_id=103 From noreply@sourceforge.net Fri Sep 13 19:38:05 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 11:38:05 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-605557 ] language support Message-ID: Bugs item #605557, was opened at 2002-09-06 09:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605557&group_id=103 Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Emilio Delgado (popemiko) Assigned to: Nobody/Anonymous (nobody) Summary: language support Initial Comment: Bug in Mailman version 2.1b3 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 "/var/lib/mailman/scripts/driver", line 82, in run_main main() File "/var/lib/mailman/Mailman/Cgi/create.py", line 60, in main request_creation(doc) File "/var/lib/mailman/Mailman/Cgi/create.py", line 376, in request_creation [_(Utils.GetLanguageDescr(L)) for L in langs], File "/var/lib/mailman/Mailman/Utils.py", line 599, in GetLanguageDescr return mm_cfg.LC_DESCRIPTIONS[lang][0] KeyError: admlogin_files Python information: Variable Value sys.version 2.2 (#1, Feb 24 2002, 16:21:58) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux-i386 Environment variables: Variable Value HTTP_REFERER http://192.168.1.15/mailman/admin SERVER_SOFTWARE Apache-AdvancedExtranetServer/1.3.23 (Mandrake Linux/4.1mdk) mod_ssl/2.8.7 OpenSSL/0.9.6c PHP/4.1.2 PYTHONPATH /var/lib/mailman SCRIPT_FILENAME /var/lib/mailman/cgi-bin/create SERVER_ADMIN root@localhost SCRIPT_NAME /mailman/create SCRIPT_URI http://infor.unibertsitatea.net/mailman/create SERVER_SIGNATURE Apache-AdvancedExtranetServer/1.3.23 Server at infor.unibertsitatea.net Port 80 REQUEST_METHOD GET HTTP_HOST 192.168.1.15 SCRIPT_URL /mailman/create SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/create HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 HTTP_ACCEPT_CHARSET ISO-8859-1, utf-8;q=0.66, *;q=0.66 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204 HTTP_CONNECTION keep-alive SERVER_NAME infor.unibertsitatea.net REMOTE_ADDR 192.168.1.15 REMOTE_PORT 1281 HTTP_ACCEPT_LANGUAGE en-us SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 DOCUMENT_ROOT /var/www/html HTTP_ACCEPT_ENCODING gzip, deflate, compress;q=0.9 SERVER_ADDR 192.168.1.15 HTTP_KEEP_ALIVE 300 ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 14:38 Message: Logged In: YES user_id=12800 Did you perhaps drop a file called admlogin_files in your $prefix/templates directory? That directory should only contain subdirs for the language templates. I'll check in a change that will make Mailman less vulnerable to these problems. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605557&group_id=103 From noreply@sourceforge.net Fri Sep 13 20:08:23 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 12:08:23 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-601082 ] personalized recip should be MIMEed Message-ID: Bugs item #601082, was opened at 2002-08-27 21:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=601082&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: personalized recip should be MIMEed Initial Comment: If the list delivery is personalized, user's name is placed in To: header. When the user choose to register non-ascii character in the name, To: header contain non-ascii and breaks RFC(number?Idontknow). A quick and dirty patch is included. I hope Barry can inspect and revise it. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 15:08 Message: Logged In: YES user_id=12800 Ouch, this is a tougher problem because you don't really know what character set the name is in. It may not be the charset for the user's preferred language at all. I can see three approaches. First, you should never have funny characters in the real name component (use the encoded name instead). Second, there could be a a second entry box under the name asking for the charset of the name. It would default to us-ascii (or maybe just empty). I fear however that most people will be entirely clueless as to what the proper value would be. Third, if there are non-ascii characters in the name, I think we could just encode with utf-8 and be done with it -- you can't really guess much more about the proper encoding. I'm not sure the latter will work or will even be cross platform. Ideas? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=601082&group_id=103 From noreply@sourceforge.net Fri Sep 13 20:17:12 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 12:17:12 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-598010 ] Bad Pickle? Message-ID: Bugs item #598010, was opened at 2002-08-20 19:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=598010&group_id=103 Category: None Group: 2.1 beta >Status: Pending Resolution: None Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: Bad Pickle? Initial Comment: Some days ago my server startet forgetting some imcoming mails to some special lists. SInce then I receive the followin error-notes on my Server. Could somebody explain me what`s going on very fast? Some of my important mailinglists aren`t usable any more. File "/usr/lib/mailman/bin/qrunner", line 266, in ? main() File "/usr/lib/mailman/bin/qrunner", line 226, in main qrunner.run() File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 129, in _dispose status = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 152, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Handlers/Moderate.py", line 101, in process Hold.hold_for_approval(mlist, msg, msgdata, Hold.ModeratedPost) File "/usr/lib/mailman/Mailman/Handlers/Hold.py", line 219, in hold_for_approval cookie = Pending.new(Pending.HELD_MESSAGE, id) File "/usr/lib/mailman/Mailman/Pending.py", line 64, in new db = _load() File "/usr/lib/mailman/Mailman/Pending.py", line 121, in _load return cPickle.load(fp) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 15:17 Message: Logged In: YES user_id=12800 Moving status to pending since I haven't heard any followup from the submitter. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-22 15:17 Message: Logged In: YES user_id=12800 It looks like the file containing your pending actions got corrupted. Possibly you had a disk corruption, or out of space problem, or something similar. If you have a data/pending.pck.tmp file, move that to data/pending.pck. Otherwise you'll have to simply remove the data/pending.pck file, but if you do that you'll lose all your pending subscriptions and held messages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=598010&group_id=103 From noreply@sourceforge.net Fri Sep 13 20:24:00 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 12:24:00 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-601082 ] personalized recip should be MIMEed Message-ID: Bugs item #601082, was opened at 2002-08-28 03:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=601082&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: personalized recip should be MIMEed Initial Comment: If the list delivery is personalized, user's name is placed in To: header. When the user choose to register non-ascii character in the name, To: header contain non-ascii and breaks RFC(number?Idontknow). A quick and dirty patch is included. I hope Barry can inspect and revise it. ---------------------------------------------------------------------- >Comment By: Simone Piunno (pioppo) Date: 2002-09-13 21:24 Message: Logged In: YES user_id=227443 If the address is coming from a web browser I believe you should be able to guess the encoding from the HTTP headers (at least for POST). If the address is coming from the command line you could try to check KBCHARSET or you could just add an optional parameter (the list admin shouldn't be so clueless) If the address is coming from an email you could allow non-ASCII only if properly encoded (so that you can deduce the encoding from the email) In any case you should store the encoding valuesomewhere in the list database file, for later use. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 21:08 Message: Logged In: YES user_id=12800 Ouch, this is a tougher problem because you don't really know what character set the name is in. It may not be the charset for the user's preferred language at all. I can see three approaches. First, you should never have funny characters in the real name component (use the encoded name instead). Second, there could be a a second entry box under the name asking for the charset of the name. It would default to us-ascii (or maybe just empty). I fear however that most people will be entirely clueless as to what the proper value would be. Third, if there are non-ascii characters in the name, I think we could just encode with utf-8 and be done with it -- you can't really guess much more about the proper encoding. I'm not sure the latter will work or will even be cross platform. Ideas? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=601082&group_id=103 From noreply@sourceforge.net Fri Sep 13 20:46:46 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 12:46:46 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-596361 ] rejection-notice not translated Message-ID: Bugs item #596361, was opened at 2002-08-17 02:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=596361&group_id=103 Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: rejection-notice not translated Initial Comment: on the admindb screen, detailed description of the held messages include 'rejection-notice' field to be sent to the message sender but the default value in the text form is in english and not translated into the list-preferred language. Following short patch may work: --- admindb.py.orig Fri Aug 16 11:39:53 2002 +++ admindb.py Sat Aug 17 14:57:37 2002 @@ -595,8 +595,8 @@ t.AddRow([ Bold(_('If you reject this post,
please explain (optional):')), TextArea('comment-%d' % id, rows=4, cols=80, - text = Utils.wrap(msgdata.get('rejection-notice', - _('[No explanation given]')), + text = Utils.wrap(_(msgdata.get('rejection-notice', + _('[No explanation given]'))), column=80)) ]) row, col = t.GetCurrentRowIndex(), t.GetCurrentCellIndex() ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 15:46 Message: Logged In: YES user_id=12800 Thanks. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-08-23 20:17 Message: Logged In: YES user_id=67709 Sorry for the inconvenience. I uplaod a diff file. There is some clutter in creating mailman.pot, so I revised the patch. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 17:16 Message: Logged In: YES user_id=12800 In general it's better to attach patches instead of pasting them in. SF doesn't preserve whitespace :( Updating this one so SF will send me the whitespace preserved patch in an email notification. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=596361&group_id=103 From noreply@sourceforge.net Fri Sep 13 20:47:44 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 12:47:44 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-593728 ] Traceback rebuilding archive Message-ID: Bugs item #593728, was opened at 2002-08-11 14:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103 Category: Pipermail Group: 2.1 beta >Status: Pending Resolution: None Priority: 5 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback rebuilding archive Initial Comment: Witn Mailman 2.1b3, rebuilding a pipermail archive using $ bin/arch listname runs fine for 2 lists, but on the third one gives the following traceback: [...] Updating HTML for article 52 Updating HTML for article 53 Schreibe Archivzustand in Datei /home/mailman/archives/private/humor/pipermail.pck Traceback (most recent call last): File "bin/arch", line 160, in ? main() File "bin/arch", line 148, in main archiver.processUnixMailbox(fp, Article, start, end) File "/home/mailman/Mailman/Archiver/pipermail.py", line 545, in processUnixMailbox m = mbox.next() File "/usr/local/lib/python2.2/mailbox.py", line 34, in next return self.factory(_Subfile(self.fp, start, stop)) File "/home/mailman/Mailman/Mailbox.py", line 69, in scrubber return mailbox.scrub(msg) File "/home/mailman/Mailman/Mailbox.py", line 89, in scrub return self._scrubber(self._mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 159, in process part.set_payload(_("""\ File "/home/mailman/Mailman/i18n.py", line 76, in _ return _translation.gettext(s) % dict UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 15:47 Message: Logged In: YES user_id=12800 I'm moving the bug report to pending since I haven't seen an update. I suspect this is fixed in current cvs. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-16 17:55 Message: Logged In: YES user_id=12800 Can you upload the .mbox file for the list you're regenerating? If not (perhaps because it's proprietary information), can you make it available for me to look at privately? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=593728&group_id=103 From noreply@sourceforge.net Fri Sep 13 20:50:36 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 12:50:36 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-566301 ] umbrella list: unsubscribe key public Message-ID: Bugs item #566301, was opened at 2002-06-08 17:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=566301&group_id=103 Category: security/privacy Group: 2.1 beta >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: umbrella list: unsubscribe key public Initial Comment: Mailman offers a feature to set up an "umbrella-list", which is used if a list just has other lists as members. Assume we have an umbrella-list U, which has to members, X and Y - both are also lists. Now, cleverly, the monthly password reminders are not sent to X and Y, but to "X-owner" and "Y-owner" instead, so this information should reach the owners of the subscribed lists (sending a password reminder to X would mean giving each member of the X list the power to unsubscribe X from U etc.). But: If a member of X or Y opens the member options page (http://my.server.net/mailman/options/U/X) and clicks on the "unsubscribe" button, the necessary key is mailed to X (and not to "X-owner"). This is probably not what we want. If the list archive is not private, the password is even available to everyone out there. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 15:50 Message: Logged In: YES user_id=12800 I don't plan to fix umbrella lists since I want this feature to go away. I'd accept a patch though. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-16 17:59 Message: Logged In: YES user_id=12800 Umbrella lists are a hack that will eventually go away. Still, if they're there now they should at least be safer. Any chance you'd like to generate a patch for this problem? If not, I'm lowering the priority because it involves a soon-to-be deprecated feature. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=566301&group_id=103 From noreply@sourceforge.net Fri Sep 13 20:49:46 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 12:49:46 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-571636 ] Traceback in error log - bounce handling Message-ID: Bugs item #571636, was opened at 2002-06-20 09:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=571636&group_id=103 Category: bounce detection Group: 2.1 beta Status: Open Resolution: None >Priority: 4 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback in error log - bounce handling Initial Comment: I got this traceback in my error log: Jun 20 14:58:56 2002 (1992) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/BounceRunner.py", line 71, in _dispose addrs = BouncerAPI.ScanMessages(mlist, msg) File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 60, in ScanMessages addrs = sys.modules[modname].process(msg) File "/home/mailman/Mailman/Bouncers/Microsoft.py", line 35, in process body = StringIO(subpart.get_payload()) TypeError: expected read buffer, list found The following had probably happened: 1. A spam mail was sent to one of our lists. 2. The list tried to send a "waiting for moderator approval" mail to the sender of the spam mail. 3. The "waiting for moderator approval" mail bounced (because the sender address was, of course, invalid). The bounce in (3) gave me the traceback and was moved to qfiles/shunt/. PCK file is attached to this bug report. Let me know if you need the DB file too... :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-22 23:31 Message: Logged In: YES user_id=12800 If this message has been in the queue since before you upgraded, it's still got a bogus representation, which won't be automatically fixed. You'd need to do some manual hacking on the object representation and then re-save it. If the message is important to you and you can't fix it, upload it or email it and I'll attempt to do so. If the message isn't important to you, just discard it. Messages sent after the upgrade should be fine. ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2002-08-19 10:20 Message: Logged In: YES user_id=184577 Well, at least something must have happened, because now the traceback looks different, this is the output of dumpdb on it: Traceback (most recent call last): File "/home/mailman/bin/dumpdb", line 130, in ? msg = main() File "/home/mailman/bin/dumpdb", line 124, in main pp.pprint(m) File "/usr/lib/python2.2/pprint.py", line 110, in pprint self.__stream.write(self.pformat(object) + "\n") File "/usr/lib/python2.2/pprint.py", line 114, in pformat self.__format(object, sio, 0, 0, {}, 0) File "/usr/lib/python2.2/pprint.py", line 136, in __format rep = self.__repr(object, context, level - 1) File "/usr/lib/python2.2/pprint.py", line 200, in __repr self.__depth, level) File "/usr/lib/python2.2/pprint.py", line 287, in _safe_repr rep = `object` File "/home/mailman/Mailman/Message.py", line 41, in __repr__ return self.__str__() File "/home/mailman/pythonlib/email/Message.py", line 89, in __str__ return self.as_string(unixfrom=1) File "/home/mailman/pythonlib/email/Message.py", line 99, in as_string g.flatten(self, unixfrom=unixfrom) File "/home/mailman/pythonlib/email/Generator.py", line 81, in flatten self._write(msg) File "/home/mailman/pythonlib/email/Generator.py", line 109, in _write self._dispatch(msg) File "/home/mailman/pythonlib/email/Generator.py", line 136, in _dispatch meth(msg) File "/home/mailman/pythonlib/email/Generator.py", line 219, in _handle_multipart g.flatten(part, unixfrom=0) File "/home/mailman/pythonlib/email/Generator.py", line 81, in flatten self._write(msg) File "/home/mailman/pythonlib/email/Generator.py", line 109, in _write self._dispatch(msg) File "/home/mailman/pythonlib/email/Generator.py", line 136, in _dispatch meth(msg) File "/home/mailman/pythonlib/email/Generator.py", line 278, in _handle_message g.flatten(msg.get_payload(0), unixfrom=0) File "/home/mailman/pythonlib/email/Message.py", line 167, in get_payload raise TypeError, i TypeError: 0 (Using latest CVS checked out today 19-aug-2002) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-09 15:26 Message: Logged In: YES user_id=12800 I think we resolved this one, didn't we? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=571636&group_id=103 From barry@python.org Fri Sep 13 22:24:26 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 13 Sep 2002 17:24:26 -0400 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list References: <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911195829.GD3121@ferrara.linux.it> Message-ID: <15746.22410.409287.495569@anthem.wooz.org> >>>>> "SP" == Simone Piunno writes: SP> I think that not implementing this feature we wouldn't improve SP> people's usage of reply-to in any way... we'd just leave the SP> situation as it is, e.g. 99% of the people doesn't {know how, SP> want} to use their mailer the way you teach. SP> Definitely we should stick to mechanism, not policy. In general, I agree. But when deciding on a new feature (which this is so don't even think about it for 2.1 :), try a simple experiment. See if you can explain how the feature interacts with all the existing related features, and then see if you can go from there to an explanation of how to accomplish the simple tasks that people want to accomplish. I find that the more cruft we bolt on (esp. to something like Reply-To munging), the harder it gets to explain. That's a bad sign. SP> Agreed, but what I want to develop is a feature where Mailman SP> simply suggests "The Right Thing", without removing your SP> freedom degree. Explicit is better than implicit. http://www.python.org/doc/Humor.html#zen -Barry From barry@python.org Fri Sep 13 22:27:20 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 13 Sep 2002 17:27:20 -0400 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list References: <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911195829.GD3121@ferrara.linux.it> <21670.1031804818@kanga.nu> <200209120952.g8C9qcp25575@quill.local> Message-ID: <15746.22584.694676.615006@anthem.wooz.org> >>>>> "NB" == Norbert Bollow writes: NB> Sounds like you've never seen a list blow up in a mail loop NB> because of some broken "vacation" autoresponder robot which NB> sends automated responses to the Reply-To: address. Note that if the vacation program is only slightly broken, then it will have a Precedence header that Mailman can do something with. MM2.1 will not autorespond to any message that has a Precedence: {bulk,list,junk} header. If the vacation program is /really/ broken, then there's a governor on the autoreply system as a fallback. But I wouldn't mind if someone suggested that folks using such broken vacation programs get disabled or removed automatically . -Barry From barry@python.org Fri Sep 13 22:32:29 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 13 Sep 2002 17:32:29 -0400 Subject: [Mailman-Developers] feature request: new option forreply_goes_to_list References: <20020911195829.GD3121@ferrara.linux.it> <21670.1031804818@kanga.nu> <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911211205.GA23883@merlins.org> <3D7FA7BE.3397AC80@nleaudio.com> <20020912223031.GA5081@ferrara.linux.it> <3D814A8A.3050102@sun.com> Message-ID: <15746.22893.10129.140035@anthem.wooz.org> >>>>> "DM" == Dan Mick writes: DM> Wrong. Every mailreader I've ever used has a two-option (at DM> least) choice: reply to sender ("From:") or reply to all DM> (From: and Cc:). I must admit to leading a MUA cloistered life. I wonder if the problem is that there are widely used mail readers that /don't/ make a very clear distinction between reply-to-sender and reply-to-all? I'm thinking like MSN or AOL or Outlook or Outlook Express. Certainly the minority MUAs I use (VM/XEmacs, Mozilla/Netscape, MacOSX Mail) all have two very clearly marked buttons for the two functions. I think even my mom or dad could handle it. -Barry From barry@python.org Fri Sep 13 22:19:24 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 13 Sep 2002 17:19:24 -0400 Subject: [Mailman-Developers] feature request: new option for reply_goes_to_list References: <20020905200814.GE2024@ferrara.linux.it> Message-ID: <15746.22108.218105.873977@anthem.wooz.org> >>>>> "SP" == Simone Piunno writes: SP> The problem is that sometimes a non-subscriber sends a SP> question to the list and subscribers think he is also a SP> subscriber and do not CC him. I think it would be nice to use SP> the multi-valued reply-to this way: Reply-to munging is such a lose that I'm loath to pile more crud onto it. The more we do this, the harder it gets to explain or understand how it all hangs together. I'm not sure it's worth trying to solve the problem you describe. If a non-member posts to a list and doesn't get cc'd I'm inclined to call it pilot error rather than have the listserver try to some how defend against it. >>>>> "MM" == Marc MERLIN writes: MM> Now that I think of it, it wouldn't be too hard for mailman MM> when it sends the list copy out to (optionally) remove from Cc MM> all the Emails from members that have the nodupes option set. MM> That way, the Cc would be left only with Emails that aren't MM> subscribed to the list. Hmm, that's an interesting idea. Of course, those Cc's will still be contained in the direct copy the recipient will get. Does it matter that the (noduped) cc'd member will get a message with a different recipient list than what the rest of the list membership gets? I'll put this on the todo list. -Barry From marc_news@merlins.org Fri Sep 13 22:47:57 2002 From: marc_news@merlins.org (Marc MERLIN) Date: Fri, 13 Sep 2002 14:47:57 -0700 Subject: [Mailman-Developers] feature request: new option forreply_goes_to_list In-Reply-To: <20020912223031.GA5081@ferrara.linux.it> References: <21670.1031804818@kanga.nu> <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911195829.GD3121@ferrara.linux.it> <20020911211205.GA23883@merlins.org> <20020905200814.GE2024@ferrara.linux.it> <20020909011921.GI3806@merlins.org> <20020911195829.GD3121@ferrara.linux.it> <3D7FA7BE.3397AC80@nleaudio.com> <20020912223031.GA5081@ferrara.linux.it> Message-ID: <20020913214757.GM16211@merlins.org> On Fri, Sep 13, 2002 at 12:30:31AM +0200, Simone Piunno wrote: > > Reply-To is typically not conditional (except for good MUAs like mine that > > can be told to ignore it altogether) > > sorry, can you rephrase? If you set a reply-to, you are forcing most mail clients to reply to the list when the user is trying to reply to the sender only. A small list of mail client (like mutt) can be told to ignore reply-to or to ask whether it should be honored. > practically noone uses mutt and the nice L key feature. > I'm the only one :) Note too that because of this, I don't see your answer until way later because I'm not Cced and your mail just sits in my spool, along with the other 1000+ list mail messages I have. (not that I overly care either way, but that's why I don't typically use list reply to) Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. 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@merlins.org Fri Sep 13 22:51:55 2002 From: marc_news@merlins.org (Marc MERLIN) Date: Fri, 13 Sep 2002 14:51:55 -0700 Subject: [Mailman-Developers] Re: trimming Cc with mailman on reply to all In-Reply-To: <15746.22108.218105.873977@anthem.wooz.org> References: <20020905200814.GE2024@ferrara.linux.it> <15746.22108.218105.873977@anthem.wooz.org> Message-ID: <20020913215155.GN16211@merlins.org> On Fri, Sep 13, 2002 at 05:19:24PM -0400, Barry A. Warsaw wrote: > >>>>> "MM" == Marc MERLIN writes: > > MM> Now that I think of it, it wouldn't be too hard for mailman > MM> when it sends the list copy out to (optionally) remove from Cc > MM> all the Emails from members that have the nodupes option set. > MM> That way, the Cc would be left only with Emails that aren't > MM> subscribed to the list. > > Hmm, that's an interesting idea. Of course, those Cc's will still be > contained in the direct copy the recipient will get. Does it matter Correct, so for one list member a reply to all will generate multiple messages, but receipients will only get one if they have nodupes enabled (which is a default) The idea is that for everyone else on the list side, the Cc doesn't keep growing. > that the (noduped) cc'd member will get a message with a different > recipient list than what the rest of the list membership gets? I think it's acceptable. In order not to make mailman look more complex than it already is and add yet another option, I'd be tempted to just remove from the Cc line every member that is subscribed to the list and that has nodupes enabled. I think that would take care of it, it should be up to the people in the Cc to decide whether they want their address stripped from the Cc line, not from the member who receives the Email. Would you agree? Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. 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 Sep 13 22:53:37 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 13 Sep 2002 14:53:37 -0700 Subject: [Mailman-Developers] [ mailman-Patches-433767 ] Subscriber Profiler Message-ID: Patches item #433767, was opened at 2001-06-16 12:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=433767&group_id=103 Category: None >Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Swee Heng (sweeheng) Assigned to: Nobody/Anonymous (nobody) Summary: Subscriber Profiler Initial Comment: This is a patch to mailman-2.0.5 to implement a "subscriber profiler" feature. See my 2 postings on the mailing list for more details: o http://mail.python.org/pipermail/mailman-developers/2001-May/004270.html o http://mail.python.org/pipermail/mailman-developers/2001-June/004279.html Feel free to email me comments and queries at . (I finally figured out how to use SourceForge! :) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 17:53 Message: Logged In: YES user_id=12800 Do you have any interest in porting this to MM2.1? I tried to look at the screen shots but got 404 errors, are they still available? Would you like me to add links to this patch for the MM2.0 unsupported patches page? See http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/UnofficialMailman20xPatches ---------------------------------------------------------------------- Comment By: Jozeph Brasil (jozeph) Date: 2002-09-12 21:40 Message: Logged In: YES user_id=17693 Hello... I install mailman from a RPM file... and install the patch manually... I need to know how COMPILE profile CGI-BIN file manually... do you know how? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=433767&group_id=103 From barry@python.org Sat Sep 14 00:22:57 2002 From: barry@python.org (Barry A. Warsaw) Date: Fri, 13 Sep 2002 19:22:57 -0400 Subject: [Mailman-Developers] Re: trimming Cc with mailman on reply to all References: <20020905200814.GE2024@ferrara.linux.it> <15746.22108.218105.873977@anthem.wooz.org> <20020913215155.GN16211@merlins.org> Message-ID: <15746.29521.97353.694025@anthem.wooz.org> >>>>> "MM" == Marc MERLIN writes: MM> Correct, so for one list member a reply to all will generate MM> multiple messages, but receipients will only get one if they MM> have nodupes enabled (which is a default) The idea is that for MM> everyone else on the list side, the Cc doesn't keep growing. I'm nearly convinced. :) >> that the (noduped) cc'd member will get a message with a >> different recipient list than what the rest of the list >> membership gets? MM> I think it's acceptable. In order not to make mailman look MM> more complex than it already is and add yet another option, MM> I'd be tempted to just remove from the Cc line every member MM> that is subscribed to the list and that has nodupes enabled. +1 MM> I think that would take care of it, it should be up to the MM> people in the Cc to decide whether they want their address MM> stripped from the Cc line, not from the member who receives MM> the Email. MM> Would you agree? Yes. Note that the dup avoidance logic suppresses dups for members in the To, CC, Resent-To, and Resent-Cc headers, but I think I only want to remove addresses from the Cc headers. For one thing, it makes the code simpler and for another I think the Cc headers are the biggest culprit. Attached is a patch to AvoidDuplicates.py that seems to accomplish this. Any objections if I just check this in? -Barry -------------------- snip snip -------------------- Index: AvoidDuplicates.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Handlers/AvoidDuplicates.py,v retrieving revision 2.0 diff -u -r2.0 AvoidDuplicates.py --- AvoidDuplicates.py 5 Mar 2002 05:08:45 -0000 2.0 +++ AvoidDuplicates.py 13 Sep 2002 23:22:37 -0000 @@ -24,7 +24,7 @@ from Mailman import mm_cfg -from email.Utils import getaddresses +from email.Utils import getaddresses, formataddr @@ -33,15 +33,29 @@ # Short circuit if not recips: return - # Figure out the set of explicit recipients + # Seed this set with addresses we don't care about dup avoiding explicit_recips = {} + listaddrs = [mlist.GetListEmail(), mlist.GetBouncesEmail(), + mlist.GetOwnerEmail(), mlist.GetRequestEmail()] + for addr in listaddrs: + explicit_recips[addr] = 1 + # Figure out the set of explicit recipients + ccaddrs = {} for header in ('to', 'cc', 'resent-to', 'resent-cc'): - for name, addr in getaddresses(msg.get_all(header, [])): + addrs = getaddresses(msg.get_all(header, [])) + if header == 'cc': + for name, addr in addrs: + ccaddrs[addr] = name, addr + for name, addr in addrs: if not addr: continue + # Ignore the list addresses for purposes of dup avoidance explicit_recips[addr] = 1 + # Now strip out the list addresses + for addr in listaddrs: + del explicit_recips[addr] if not explicit_recips: - # No one was explicitly addressed, so we can do any dup collapsing + # No one was explicitly addressed, so we can't do any dup collapsing return newrecips = [] for r in recips: @@ -60,6 +74,8 @@ if send_duplicate: msgdata.setdefault('add-dup-header', {})[r] = 1 newrecips.append(r) + elif ccaddrs.has_key(r): + del ccaddrs[r] else: # Otherwise, this is the first time they've been in the recips # list. Add them to the newrecips list and flag them as having @@ -67,3 +83,6 @@ newrecips.append(r) # Set the new list of recipients msgdata['recips'] = newrecips + del msg['cc'] + for item in ccaddrs.values(): + msg['cc'] = formataddr(item) From noreply@sourceforge.net Sun Sep 15 23:07:11 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 15 Sep 2002 15:07:11 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-609692 ] Non-member hold reason is wrong Message-ID: Bugs item #609692, was opened at 2002-09-15 15:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=609692&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Les Niles (lniles) Assigned to: Nobody/Anonymous (nobody) Summary: Non-member hold reason is wrong Initial Comment: Maybe I'm missing something, but it would seem that Handlers.Moderate.process() should call hold.hold_for_approval() with a fourth arg of Hold.NonMemberPost instead of Hold.ModeratedPost at line 85. The latter causes confusion for the typical case of a member (person) posting from other than her subscribed email address, since she gets back a message saying that the post was to a moderated list. And the default reject message for the moderator, something about the posting being deemed inappropriate, is not appropriate. :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=609692&group_id=103 From JasonR.Mastaler Mon Sep 16 19:11:44 2002 From: JasonR.Mastaler (JasonR.Mastaler) Date: Mon, 16 Sep 2002 12:11:44 -0600 Subject: [Mailman-Developers] mailman-bugs list? Message-ID: How about shuffling all the Sourceforge bug reports/replies to a separate list, instead of here? Not all of us are interested in reading these reports, and they also clutter this list IMO. -- (http://tmda.net/) From JasonR.Mastaler Mon Sep 16 19:13:03 2002 From: JasonR.Mastaler (JasonR.Mastaler) Date: Mon, 16 Sep 2002 12:13:03 -0600 Subject: [Mailman-Developers] Re: mailman-bugs list? References: Message-ID: Jason R. Mastaler writes: > How about shuffling all the Sourceforge bug reports/replies to a > separate list, instead of here? Er, I meant not only bugs, but all the tracker traffic (bugs, feature requests, patches, etc). -- (http://tmda.net/) From wheakory@isu.edu Tue Sep 17 00:00:11 2002 From: wheakory@isu.edu (Kory Wheatley) Date: Mon, 16 Sep 2002 17:00:11 -0600 Subject: [Mailman-Developers] Changing content before approving message Message-ID: <3D86627B.7B8D8A16@isu.edu> Is there a way when the moderator receive a message, and before he approves it to be sent to the mailing list, to change the content and the from address in the message and then send it to the list with these changes or updates in place. I thought there was a command that you could use to "Approved: listpassword" to change the content with. There are times that we need to change the body and the from address of the pending message before it can be approved. Please help this is real critical and I would appreciate any information. We are using RED HAT 7.2 with python 1.5.2 and mailman 2.0.13 -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From noreply@sourceforge.net Tue Sep 17 00:31:14 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 16 Sep 2002 16:31:14 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-610265 ] Bad date field causes archiver to crash Message-ID: Bugs item #610265, was opened at 2002-09-17 09:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610265&group_id=103 Category: command line scripts Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Tim Potter (tpot) Assigned to: Nobody/Anonymous (nobody) Summary: Bad date field causes archiver to crash Initial Comment: The following date header causes the archiver to crash with an exception. Date: Fri, 1 Jan 1904 10:52:29 +1000 Traceback (innermost last): File "/var/mailman/bin/arch", line 129, in ? main() File "/var/mailman/bin/arch", line 119, in main archiver.close() File "/var/mailman/Mailman/Archiver/pipermail.py", line 306, in close self.write_TOC() File "/var/mailman/Mailman/Archiver/HyperArch.py", line 897, in write_TOC self.sortarchives() File "/var/mailman/Mailman/Archiver/HyperArch.py", line 835, in sortarchives self.archives.sort(sf) File "/var/mailman/Mailman/Archiver/HyperArch.py", line 826, in sf al=s.volNameToDate(a) File "/var/mailman/Mailman/Archiver/HyperArch.py", line 821, in volNameToDate return time.mktime((year,month,1,0,0,0,0,1,-1)) OverflowError: mktime argument out of range [whoops - the line numbers are out by one because I added some debugging] [tpot@dp:~]$ rpm -qa | grep mailman mailman-2.0.11-1 Regards, Tim. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610265&group_id=103 From jonc@nc.rr.com Tue Sep 17 00:41:06 2002 From: jonc@nc.rr.com (Jon Carnes) Date: 16 Sep 2002 19:41:06 -0400 Subject: [Mailman-Developers] Re: [Mailman-Users] Changing content before approving message In-Reply-To: <3D86627B.7B8D8A16@isu.edu> References: <3D86627B.7B8D8A16@isu.edu> Message-ID: <1032219667.2094.7.camel@Anncons.nc.rr.com> Do you have root (or mailman command line) access on the box? If so, then you can simply edit the waiting file in the queue. It's very simple and works every time. Otherwise, there are some older patches - which probably still work - that allow you to edit the message via the web interface and then approve it. The problem with the 2.0x series of Mailman is that the message you see in the web interface is a partial copy of the message that is actually in the queue. In order to edit via the web-interface you need to load the entire message into the web-interface and then on approval, dump out the contents of the web-form into the queue (deleting or overwriting the current queued up message). Good Luck - Jon Carnes On Mon, 2002-09-16 at 19:00, Kory Wheatley wrote: > Is there a way when the moderator receive a message, and before he > approves it to be sent to the mailing list, to change the content and > the from address in the message and then send it to the list with these > changes or updates in place. > > I thought there was a command that you could use to "Approved: > listpassword" to change the content with. > > There are times that we need to change the body and the from address of > the pending message before it can be approved. > Please help this is real critical and I would appreciate any > information. > > We are using RED HAT 7.2 with python 1.5.2 and mailman 2.0.13 > > -- > ######################################### > Kory Wheatley > Academic Computing Analyst Sr. > Phone 282-3874 > ######################################### > Everything must point to him. > > > > ------------------------------------------------------ > 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 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ From mjm@michaelmeltzer.com Tue Sep 17 06:54:15 2002 From: mjm@michaelmeltzer.com (Michael Meltzer) Date: Tue, 17 Sep 2002 01:54:15 -0400 Subject: [Mailman-Developers] 2.1b3+ private.py bug report Message-ID: <057c01c25e0e$a7f1f400$0b01a8c0@mjm2> mailman from CVS as of 8pm EDT 9/16/02 it looks like private.py has a interesting problem :-), Scrubber.py is very good at saving files with various MIME types, the problem when you go to get them thought private.py they are returned with mime type of "text/html", The funny thing is for a jpeg Internet Explorer will display correctly(I am assuming the extension is being used) but Netscape 4.7 and Opera 6.0 your get the dance of binary text across the screen. BTW, on a related issue, their is a small security issue, maybe, public archives seem to stright to the paths, any one who know the system might be able to interject a php or shtml script into the archive and get, for example Apache, to think it a server side executable, the default install from the BSD ports collect for Apache/php would do this. Might Want to give people a heads up in INSTALL and have them tighten down their .htaccess file for this pathing, might even consider added a .htaccess to the default install. I would hate to have mailman end up with a CERT with is really not being it's fault. MJM From claw@kanga.nu Tue Sep 17 09:32:22 2002 From: claw@kanga.nu (J C Lawrence) Date: Tue, 17 Sep 2002 01:32:22 -0700 Subject: [Mailman-Developers] mailman-bugs list? In-Reply-To: Message from Jason R. Mastaler of "Mon, 16 Sep 2002 12:11:44 MDT." References: Message-ID: <28676.1032251542@kanga.nu> On Mon, 16 Sep 2002 12:11:44 -0600 Jason R Mastaler wrote: > How about shuffling all the Sourceforge bug reports/replies to a > separate list, instead of here? They used to be separate and were deliberately moved to the -developers list as a way of keeping them under scrutiny and review. -- 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 Sep 17 09:33:28 2002 From: claw@kanga.nu (J C Lawrence) Date: Tue, 17 Sep 2002 01:33:28 -0700 Subject: [Mailman-Developers] Changing content before approving message In-Reply-To: Message from Kory Wheatley of "Mon, 16 Sep 2002 17:00:11 MDT." <3D86627B.7B8D8A16@isu.edu> References: <3D86627B.7B8D8A16@isu.edu> Message-ID: <28703.1032251608@kanga.nu> On Mon, 16 Sep 2002 17:00:11 -0600 Kory Wheatley wrote: > Is there a way when the moderator receive a message, and before he > approves it to be sent to the mailing list, to change the content and > the from address in the message and then send it to the list with > these changes or updates in place. Please see the FAQ. -- 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 brian@pro-phile.com Tue Sep 17 00:00:19 2002 From: brian@pro-phile.com (Brian Teal) Date: Mon, 16 Sep 2002 16:00:19 -0700 Subject: [Mailman-Developers] Need installer ASAP Message-ID: <000201c25dd4$d4c9a570$0200a8c0@ddr> I have just upgraded our servers and need to have Mailman installed ASAP. I don't know enough about Unix to do it myself. Are there any installers out there? I know I'm leaving myself wide open, but anyone I work with I'll have to require some information from. Thanks in advance. From dax@gurulabs.com Tue Sep 17 08:29:56 2002 From: dax@gurulabs.com (Dax Kelson) Date: 17 Sep 2002 01:29:56 -0600 Subject: [Mailman-Developers] SOLVED: Postfix+Mailman alias-free and in separate namespace Message-ID: <1032247796.1341.15.camel@mentor> I've created the script postfix-to-mailman.py. Python seemed natural, as mailman is written in python, and invoking postfix-to-mailman.py script on delivery to mailman just warms up the disk cache with all the python code and speeds invocation of mailman. Postfix configuration samples (thanks Wietse) can be found inside the script itself. The script is heavily based on the qmail-to-postfix script by Bruce Perens. You can get the script at: http://www.gurulabs.com/downloads.html Dax Kelson Guru Labs From haroldp@sierraweb.com Mon Sep 16 22:27:23 2002 From: haroldp@sierraweb.com (Harold Paulson) Date: Mon, 16 Sep 2002 14:27:23 -0700 Subject: [Mailman-Developers] Suppress "results of your email commands" message in 2.1? Message-ID: Hello, I'm trying to integrate Mailman into a larger site, and the "The results of your email commands" messages that get sent to users are somewhat redundant in my setup. Can Mailman be configured NOT to send these messages? - H -- Harold Paulson Sierra Web Design haroldp@sierraweb.com http://www.sierraweb.com VOICE: 775.833.9500 FAX: 775-201-4458 From noreply@sourceforge.net Tue Sep 17 15:21:17 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 17 Sep 2002 07:21:17 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-610570 ] RFC 2369 URL is broken Message-ID: Bugs item #610570, was opened at 2002-09-17 07:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610570&group_id=103 Category: documentation Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Nick Arnett (narnett) Assigned to: Nobody/Anonymous (nobody) Summary: RFC 2369 URL is broken Initial Comment: Paths to RFCs have changed. The correct one for 2369 is now http://www.faqs.org/rfcs/rfc2369.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610570&group_id=103 From donn@u.washington.edu Tue Sep 17 17:18:00 2002 From: donn@u.washington.edu (Donn Cave) Date: Tue, 17 Sep 2002 09:18:00 -0700 Subject: [Mailman-Developers] mailman-bugs list? Message-ID: <200209171618.g8HGI0jC027926@mailhost1.u.washington.edu> Quoth J C Lawrence : | On Mon, 16 Sep 2002 12:11:44 -0600 | Jason R Mastaler wrote: | > How about shuffling all the Sourceforge bug reports/replies to a | > separate list, instead of here? | | They used to be separate and were deliberately moved to the -developers | list as a way of keeping them under scrutiny and review. For me, it would be more effective to that end if the original subject appeared in my mailer's presentation of the Subject header. I mean, in this morning's mail, I see "[Mailman-Developers] [ mailman-Bugs-610570 ] RFC" and that's better than usual. I know this is my fault - you all probably have fancier mailers or more screen real estate or whatever, but I thought I'd share that anyway. I probably overlook some traffic that I could be scrutinizing and reviewing, if the first 2 or 3 letters of the subject don't grab me. Donn Cave, University Computing Services, University of Washington donn@u.washington.edu From mjm@michaelmeltzer.com Tue Sep 17 17:15:13 2002 From: mjm@michaelmeltzer.com (Michael Meltzer) Date: Tue, 17 Sep 2002 12:15:13 -0400 Subject: [Mailman-Developers] remove quoted mail. Message-ID: <010e01c25e65$676a6910$34f820c0@ix1x1000> This is a multi-part message in MIME format. ---------------------- multipart/alternative attachment Does anyone have a modul that I can use after MimeDel.py to remove any = part of a message that is more that 2 quote levels deep, I getting = requests from digest users and I would not mind not wasting my = bandwidth. I know I have to leave some for people inline answering. But = figure 2 levels people should context and should be ok. ith all the = different version of quoting it looks like it would be a nightmare and I = would be willing to have some people screwed by this rarely. Extra = credit for a match to 2.1b3+ :-) Any code or barring that any ideas to = code against. MJM PS. please not a debate about user training. ---------------------- multipart/alternative attachment-- From JasonR.Mastaler Tue Sep 17 17:31:57 2002 From: JasonR.Mastaler (JasonR.Mastaler) Date: Tue, 17 Sep 2002 10:31:57 -0600 Subject: [Mailman-Developers] Re: mailman-bugs list? References: <28676.1032251542@kanga.nu> Message-ID: J C Lawrence writes: > They used to be separate and were deliberately moved to the > -developers list as a way of keeping them under scrutiny and review. Forcing everyone to look at them seems like an asinine way to accomplish this. If someone is interested in keeping them under scrutiny and review, they'll just subscribe to the -bugs list; otherwise not. No worries though, I'll just killfile noreply@sourceforge.net. -- (http://tmda.net/) From claw@kanga.nu Tue Sep 17 18:24:38 2002 From: claw@kanga.nu (J C Lawrence) Date: Tue, 17 Sep 2002 10:24:38 -0700 Subject: [Mailman-Developers] Re: mailman-bugs list? In-Reply-To: Message from Jason R. Mastaler of "Tue, 17 Sep 2002 10:31:57 MDT." References: <28676.1032251542@kanga.nu> Message-ID: <1266.1032283478@kanga.nu> On Tue, 17 Sep 2002 10:31:57 -0600 Jason R Mastaler wrote: > J C Lawrence writes: >> They used to be separate and were deliberately moved to the >> -developers list as a way of keeping them under scrutiny and review. > Forcing everyone to look at them seems like an asinine way to > accomplish this. This is a -developers list, not a support list. -- 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 thomas@xs4all.net Tue Sep 17 21:38:13 2002 From: thomas@xs4all.net (Thomas Wouters) Date: Tue, 17 Sep 2002 22:38:13 +0200 Subject: [Mailman-Developers] Re: trimming Cc with mailman on reply to all In-Reply-To: <15746.29521.97353.694025@anthem.wooz.org> References: <20020905200814.GE2024@ferrara.linux.it> <15746.22108.218105.873977@anthem.wooz.org> <20020913215155.GN16211@merlins.org> <15746.29521.97353.694025@anthem.wooz.org> Message-ID: <20020917203813.GA1017@xs4all.nl> On Fri, Sep 13, 2002 at 07:22:57PM -0400, Barry A. Warsaw wrote: > Attached is a patch to AvoidDuplicates.py that seems to accomplish > this. Any objections if I just check this in? Making it a config setting would be nice. I don't think we'd enable it for our internal lists, for instance; not because we like to have large Cc: lists, but because we like to educate our employees... preferably loudly and with blunt objects. :) -- Thomas Wouters Hi! I'm a .signature virus! copy me into your .signature file to help me spread! From noreply@sourceforge.net Tue Sep 17 22:55:38 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 17 Sep 2002 14:55:38 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-601082 ] personalized recip should be MIMEed Message-ID: Bugs item #601082, was opened at 2002-08-27 21:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=601082&group_id=103 Category: mail delivery Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: personalized recip should be MIMEed Initial Comment: If the list delivery is personalized, user's name is placed in To: header. When the user choose to register non-ascii character in the name, To: header contain non-ascii and breaks RFC(number?Idontknow). A quick and dirty patch is included. I hope Barry can inspect and revise it. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-17 17:55 Message: Logged In: YES user_id=12800 This was a fun one! The quick and dirty patch wasn't really enough. Now we essentially keep non-ascii names as unicode in the member database and then do output encoding as necessary for the context. MM 2.1b4 should have all the code for this. ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2002-09-13 15:24 Message: Logged In: YES user_id=227443 If the address is coming from a web browser I believe you should be able to guess the encoding from the HTTP headers (at least for POST). If the address is coming from the command line you could try to check KBCHARSET or you could just add an optional parameter (the list admin shouldn't be so clueless) If the address is coming from an email you could allow non-ASCII only if properly encoded (so that you can deduce the encoding from the email) In any case you should store the encoding valuesomewhere in the list database file, for later use. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 15:08 Message: Logged In: YES user_id=12800 Ouch, this is a tougher problem because you don't really know what character set the name is in. It may not be the charset for the user's preferred language at all. I can see three approaches. First, you should never have funny characters in the real name component (use the encoded name instead). Second, there could be a a second entry box under the name asking for the charset of the name. It would default to us-ascii (or maybe just empty). I fear however that most people will be entirely clueless as to what the proper value would be. Third, if there are non-ascii characters in the name, I think we could just encode with utf-8 and be done with it -- you can't really guess much more about the proper encoding. I'm not sure the latter will work or will even be cross platform. Ideas? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=601082&group_id=103 From barry@python.org Tue Sep 17 22:59:36 2002 From: barry@python.org (Barry A. Warsaw) Date: Tue, 17 Sep 2002 17:59:36 -0400 Subject: [Mailman-Developers] Re: trimming Cc with mailman on reply to all References: <20020905200814.GE2024@ferrara.linux.it> <15746.22108.218105.873977@anthem.wooz.org> <20020913215155.GN16211@merlins.org> <15746.29521.97353.694025@anthem.wooz.org> <20020917203813.GA1017@xs4all.nl> Message-ID: <15751.42440.581910.494472@anthem.wooz.org> >>>>> "TW" == Thomas Wouters writes: >> Attached is a patch to AvoidDuplicates.py that seems to >> accomplish this. Any objections if I just check this in? TW> Making it a config setting would be nice. I don't think we'd TW> enable it for our internal lists, for instance; not because we TW> like to have large Cc: lists, but because we like to educate TW> our employees... preferably loudly and with blunt objects. :) The issue actually only comes up when users have selected their own no-dupes option. I'd rather not bombard them with another option for stripping the cc headers and I think even giving the list admins a choice is overkill. But let's see what happens in practice. Thanks, -Barry From noreply@sourceforge.net Wed Sep 18 13:22:53 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 18 Sep 2002 05:22:53 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-611065 ] MailCommandHandler bug w/ python 1.5.2 Message-ID: Bugs item #611065, was opened at 2002-09-18 15:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611065&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Tomas Lindroos (skitta) Assigned to: Nobody/Anonymous (nobody) Summary: MailCommandHandler bug w/ python 1.5.2 Initial Comment: The file Mailman/MailCommandHandler.py contains two lines of code that makes (at least) the cron-job qrunner fail when using python 1.5.2. I have not checked wether this could effect other parts of the system. The problem can be found on lines 123-124, where calls to the method .lower() is made. With python 1.5.2, string objects do not have this method. The obvious fix is of course: Mailman/ $ diff MailCommandHandler.py MailCommandHandler.py~ 123,124c123,124 < precedence = string.lower(msg.get('precedence', '')) < ack = string.lower(msg.get('x-ack', '')) --- > precedence = msg.get('precedence', '').lower() > ack = msg.get('x-ack', '').lower() The strings-library is used at all other places in the file, and a grep lower\( `find . -name "*.py"` | grep -v string.lower finds no other problems of this type. (I don't guarantee that :) The traceback log from the error-log: qrunner(22189): Traceback (innermost last): qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 283, in ? qrunner(22189): kids = main(lock) qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 253, in main qrunner(22189): keepqueued = dispose_message(mlist, msg, msgdata) qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 157, in dispose_message qrunner(22189): mlist.ParseMailCommands(msg) qrunner(22189): File "/export/mailman-2.0.12/Mailman/MailCommandHandler.py", line 123, in ParseMailCommands qrunner(22189): precedence = msg.get('precedence', '').lower() qrunner(22189): AttributeError : 'string' object has no attribute 'lower' /skitta -- Tomas 'Skitta' Lindroos. UNIX Systems Analyst, Åbo Akademi University ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611065&group_id=103 From noreply@sourceforge.net Wed Sep 18 13:25:11 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 18 Sep 2002 05:25:11 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-611065 ] MailCommandHandler bug w/ python 1.5.2 Message-ID: Bugs item #611065, was opened at 2002-09-18 15:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611065&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None >Priority: 7 Submitted By: Tomas Lindroos (skitta) Assigned to: Nobody/Anonymous (nobody) Summary: MailCommandHandler bug w/ python 1.5.2 Initial Comment: The file Mailman/MailCommandHandler.py contains two lines of code that makes (at least) the cron-job qrunner fail when using python 1.5.2. I have not checked wether this could effect other parts of the system. The problem can be found on lines 123-124, where calls to the method .lower() is made. With python 1.5.2, string objects do not have this method. The obvious fix is of course: Mailman/ $ diff MailCommandHandler.py MailCommandHandler.py~ 123,124c123,124 < precedence = string.lower(msg.get('precedence', '')) < ack = string.lower(msg.get('x-ack', '')) --- > precedence = msg.get('precedence', '').lower() > ack = msg.get('x-ack', '').lower() The strings-library is used at all other places in the file, and a grep lower\( `find . -name "*.py"` | grep -v string.lower finds no other problems of this type. (I don't guarantee that :) The traceback log from the error-log: qrunner(22189): Traceback (innermost last): qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 283, in ? qrunner(22189): kids = main(lock) qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 253, in main qrunner(22189): keepqueued = dispose_message(mlist, msg, msgdata) qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 157, in dispose_message qrunner(22189): mlist.ParseMailCommands(msg) qrunner(22189): File "/export/mailman-2.0.12/Mailman/MailCommandHandler.py", line 123, in ParseMailCommands qrunner(22189): precedence = msg.get('precedence', '').lower() qrunner(22189): AttributeError : 'string' object has no attribute 'lower' /skitta -- Tomas 'Skitta' Lindroos. UNIX Systems Analyst, Åbo Akademi University ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611065&group_id=103 From noreply@sourceforge.net Wed Sep 18 13:52:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 18 Sep 2002 05:52:55 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-611065 ] MailCommandHandler bug w/ python 1.5.2 Message-ID: Bugs item #611065, was opened at 2002-09-18 08:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611065&group_id=103 Category: mail delivery Group: 2.0.x >Status: Closed >Resolution: Out of Date Priority: 7 Submitted By: Tomas Lindroos (skitta) Assigned to: Nobody/Anonymous (nobody) Summary: MailCommandHandler bug w/ python 1.5.2 Initial Comment: The file Mailman/MailCommandHandler.py contains two lines of code that makes (at least) the cron-job qrunner fail when using python 1.5.2. I have not checked wether this could effect other parts of the system. The problem can be found on lines 123-124, where calls to the method .lower() is made. With python 1.5.2, string objects do not have this method. The obvious fix is of course: Mailman/ $ diff MailCommandHandler.py MailCommandHandler.py~ 123,124c123,124 < precedence = string.lower(msg.get('precedence', '')) < ack = string.lower(msg.get('x-ack', '')) --- > precedence = msg.get('precedence', '').lower() > ack = msg.get('x-ack', '').lower() The strings-library is used at all other places in the file, and a grep lower\( `find . -name "*.py"` | grep -v string.lower finds no other problems of this type. (I don't guarantee that :) The traceback log from the error-log: qrunner(22189): Traceback (innermost last): qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 283, in ? qrunner(22189): kids = main(lock) qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 253, in main qrunner(22189): keepqueued = dispose_message(mlist, msg, msgdata) qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 157, in dispose_message qrunner(22189): mlist.ParseMailCommands(msg) qrunner(22189): File "/export/mailman-2.0.12/Mailman/MailCommandHandler.py", line 123, in ParseMailCommands qrunner(22189): precedence = msg.get('precedence', '').lower() qrunner(22189): AttributeError : 'string' object has no attribute 'lower' /skitta -- Tomas 'Skitta' Lindroos. UNIX Systems Analyst, Åbo Akademi University ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-18 08:52 Message: Logged In: YES user_id=12800 Already fixed in Mailman 2.0.13. Please upgrade. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611065&group_id=103 From noreply@sourceforge.net Wed Sep 18 14:23:57 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 18 Sep 2002 06:23:57 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-611065 ] MailCommandHandler bug w/ python 1.5.2 Message-ID: Bugs item #611065, was opened at 2002-09-18 15:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611065&group_id=103 Category: mail delivery Group: 2.0.x Status: Closed Resolution: Out of Date Priority: 7 Submitted By: Tomas Lindroos (skitta) Assigned to: Nobody/Anonymous (nobody) Summary: MailCommandHandler bug w/ python 1.5.2 Initial Comment: The file Mailman/MailCommandHandler.py contains two lines of code that makes (at least) the cron-job qrunner fail when using python 1.5.2. I have not checked wether this could effect other parts of the system. The problem can be found on lines 123-124, where calls to the method .lower() is made. With python 1.5.2, string objects do not have this method. The obvious fix is of course: Mailman/ $ diff MailCommandHandler.py MailCommandHandler.py~ 123,124c123,124 < precedence = string.lower(msg.get('precedence', '')) < ack = string.lower(msg.get('x-ack', '')) --- > precedence = msg.get('precedence', '').lower() > ack = msg.get('x-ack', '').lower() The strings-library is used at all other places in the file, and a grep lower\( `find . -name "*.py"` | grep -v string.lower finds no other problems of this type. (I don't guarantee that :) The traceback log from the error-log: qrunner(22189): Traceback (innermost last): qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 283, in ? qrunner(22189): kids = main(lock) qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 253, in main qrunner(22189): keepqueued = dispose_message(mlist, msg, msgdata) qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 157, in dispose_message qrunner(22189): mlist.ParseMailCommands(msg) qrunner(22189): File "/export/mailman-2.0.12/Mailman/MailCommandHandler.py", line 123, in ParseMailCommands qrunner(22189): precedence = msg.get('precedence', '').lower() qrunner(22189): AttributeError : 'string' object has no attribute 'lower' /skitta -- Tomas 'Skitta' Lindroos. UNIX Systems Analyst, Åbo Akademi University ---------------------------------------------------------------------- >Comment By: Tomas Lindroos (skitta) Date: 2002-09-18 16:23 Message: Logged In: YES user_id=613582 Argh! I went straight to the "download" mirror on ftp.gnu.org, and the mirror doesn't seem to be up-to-date - the newest package there is 2.0.12. My mistake. But not completely :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-18 15:52 Message: Logged In: YES user_id=12800 Already fixed in Mailman 2.0.13. Please upgrade. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611065&group_id=103 From noreply@sourceforge.net Wed Sep 18 17:46:06 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 18 Sep 2002 09:46:06 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-611159 ] Option to require ACK on moderated post Message-ID: Feature Requests item #611159, was opened at 2002-09-18 09:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=611159&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Len Lattanzi (zardoz) Assigned to: Nobody/Anonymous (nobody) Summary: Option to require ACK on moderated post Initial Comment: I'd like an option where all moderated e-mail requires an ack from the poster before the admin is notified. This would stop 99% of the spam/virii that I get. The e-mail reporting to the user that the mail is pending moderater approval could have an expedite link or even an "oops" link, I didn't mean to send that to the group. Un-ack'ed mail should be discarded automatically -- especially if the "pending approval" message can't even be delivered. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=611159&group_id=103 From noreply@sourceforge.net Wed Sep 18 17:56:14 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 18 Sep 2002 09:56:14 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-609692 ] Non-member hold reason is wrong Message-ID: Bugs item #609692, was opened at 2002-09-15 15:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=609692&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Les Niles (lniles) Assigned to: Nobody/Anonymous (nobody) Summary: Non-member hold reason is wrong Initial Comment: Maybe I'm missing something, but it would seem that Handlers.Moderate.process() should call hold.hold_for_approval() with a fourth arg of Hold.NonMemberPost instead of Hold.ModeratedPost at line 85. The latter causes confusion for the typical case of a member (person) posting from other than her subscribed email address, since she gets back a message saying that the post was to a moderated list. And the default reject message for the moderator, something about the posting being deemed inappropriate, is not appropriate. :) ---------------------------------------------------------------------- >Comment By: Les Niles (lniles) Date: 2002-09-18 09:56 Message: Logged In: YES user_id=92931 Oops -- Hold.NonMemberPost should replace Hold.ModeratedPost at line 101, not line 85. (This is in Sept 3 2002 CVS.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=609692&group_id=103 From noreply@sourceforge.net Wed Sep 18 18:23:04 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 18 Sep 2002 10:23:04 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-611185 ] rmlist doesn't delete lock files Message-ID: Bugs item #611185, was opened at 2002-09-18 13:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611185&group_id=103 Category: command line scripts Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Linda Julien (leira) Assigned to: Nobody/Anonymous (nobody) Summary: rmlist doesn't delete lock files Initial Comment: I'm using 2.0.13. The rmlist script doesn't delete lock files associated with the list (if any exist). Removing a list and creating a new one with the same name can have unexpected results. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611185&group_id=103 From noreply@sourceforge.net Wed Sep 18 18:36:25 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 18 Sep 2002 10:36:25 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-611065 ] MailCommandHandler bug w/ python 1.5.2 Message-ID: Bugs item #611065, was opened at 2002-09-18 08:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611065&group_id=103 Category: mail delivery Group: 2.0.x Status: Closed Resolution: Out of Date Priority: 7 Submitted By: Tomas Lindroos (skitta) Assigned to: Nobody/Anonymous (nobody) Summary: MailCommandHandler bug w/ python 1.5.2 Initial Comment: The file Mailman/MailCommandHandler.py contains two lines of code that makes (at least) the cron-job qrunner fail when using python 1.5.2. I have not checked wether this could effect other parts of the system. The problem can be found on lines 123-124, where calls to the method .lower() is made. With python 1.5.2, string objects do not have this method. The obvious fix is of course: Mailman/ $ diff MailCommandHandler.py MailCommandHandler.py~ 123,124c123,124 < precedence = string.lower(msg.get('precedence', '')) < ack = string.lower(msg.get('x-ack', '')) --- > precedence = msg.get('precedence', '').lower() > ack = msg.get('x-ack', '').lower() The strings-library is used at all other places in the file, and a grep lower\( `find . -name "*.py"` | grep -v string.lower finds no other problems of this type. (I don't guarantee that :) The traceback log from the error-log: qrunner(22189): Traceback (innermost last): qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 283, in ? qrunner(22189): kids = main(lock) qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 253, in main qrunner(22189): keepqueued = dispose_message(mlist, msg, msgdata) qrunner(22189): File "/export/mailman-2.0.12/cron/qrunner", line 157, in dispose_message qrunner(22189): mlist.ParseMailCommands(msg) qrunner(22189): File "/export/mailman-2.0.12/Mailman/MailCommandHandler.py", line 123, in ParseMailCommands qrunner(22189): precedence = msg.get('precedence', '').lower() qrunner(22189): AttributeError : 'string' object has no attribute 'lower' /skitta -- Tomas 'Skitta' Lindroos. UNIX Systems Analyst, Åbo Akademi University ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-18 13:36 Message: Logged In: YES user_id=12800 Ah thanks for letting me know ftp.gnu.org was out of date! I've just sent them a message so they should be grabbing the new files shortly. ---------------------------------------------------------------------- Comment By: Tomas Lindroos (skitta) Date: 2002-09-18 09:23 Message: Logged In: YES user_id=613582 Argh! I went straight to the "download" mirror on ftp.gnu.org, and the mirror doesn't seem to be up-to-date - the newest package there is 2.0.12. My mistake. But not completely :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-18 08:52 Message: Logged In: YES user_id=12800 Already fixed in Mailman 2.0.13. Please upgrade. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611065&group_id=103 From wheakory@isu.edu Wed Sep 18 20:38:21 2002 From: wheakory@isu.edu (Kory Wheatley) Date: Wed, 18 Sep 2002 13:38:21 -0600 Subject: [Mailman-Developers] Re: [Mailman-Users] Changing content before approving message References: <3D86627B.7B8D8A16@isu.edu> <1032219667.2094.7.camel@Anncons.nc.rr.com> Message-ID: <3D88D62D.48158595@isu.edu> Jon Carnes wrote: > Do you have root (or mailman command line) access on the box? If so, > then you can simply edit the waiting file in the queue. It's very > simple and works every time. > > Otherwise, there are some older patches - which probably still work - > that allow you to edit the message via the web interface and then > approve it. > > The problem with the 2.0x series of Mailman is that the message you see > in the web interface is a partial copy of the message that is actually > in the queue. In order to edit via the web-interface you need to load > the entire message into the web-interface and then on approval, dump out > the contents of the web-form into the queue (deleting or overwriting the > current queued up message). > > Good Luck - Jon Carnes > > On Mon, 2002-09-16 at 19:00, Kory Wheatley wrote: > > Is there a way when the moderator receive a message, and before he > > approves it to be sent to the mailing list, to change the content and > > the from address in the message and then send it to the list with these > > changes or updates in place. > > > > I thought there was a command that you could use to "Approved: > > listpassword" to change the content with. > > > > There are times that we need to change the body and the from address of > > the pending message before it can be approved. > > Please help this is real critical and I would appreciate any > > information. > > > > We are using RED HAT 7.2 with python 1.5.2 and mailman 2.0.13 > > > > -- > > ######################################### > > Kory Wheatley > > Academic Computing Analyst Sr. > > Phone 282-3874 > > ######################################### > > Everything must point to him. > > > > > > > > ------------------------------------------------------ > > 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 > > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ These older patches that your are referring to, do you know where there at. I don't really know what to look for in the searchable archives. -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From mradamlacey@hotmail.com Thu Sep 19 01:12:30 2002 From: mradamlacey@hotmail.com (Adam Lacey) Date: Wed, 18 Sep 2002 19:12:30 -0500 Subject: [Mailman-Developers] Re: Mailman-Developers Digest, Vol 125, Issue 1 Message-ID: Trying to hack interface to bypass Mailman's authorization so that I can integrate it with another administrative environment, so basically I am trying to spoof the cookie that mailman sends after successful login from my own environment. I have isolated the cookie and but my problem is how the program encrypts or encodes the password and timestamp data. I dont know how to recreate this cookie. Could someone enlighten me how to do this? Or what the cookie looks like, and how it is encoded? Basically my external administrative environment will have a list of who is authorized to edit which list, and once that authorization is successful, it will send a cookie (one which looks just like the one mailman is expecting) to the user. So then the user will seamlessly be able to have administrative access. Thanks _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx From mjm@michaelmeltzer.com Thu Sep 19 21:45:27 2002 From: mjm@michaelmeltzer.com (Michael Meltzer) Date: Thu, 19 Sep 2002 16:45:27 -0400 Subject: [Mailman-Developers] Minimal headers Message-ID: <038101c2601d$7c2ce3f0$34f820c0@ix1x1000> This is a multi-part message in MIME format. ---------------------- multipart/alternative attachment Does anyone have the Minimal set of header that are currently needed for = list email? i.e a whitelist, As they say everything counts in large = amounts, thinking of writing a filter and wanted to ask before the RFC = dig and trying to figure out the ones for list house keeping. ThankYou MJM ---------------------- multipart/alternative attachment-- From wheakory@isu.edu Thu Sep 19 23:31:11 2002 From: wheakory@isu.edu (Kory Wheatley) Date: Thu, 19 Sep 2002 16:31:11 -0600 Subject: [Mailman-Developers] Sendmail to Postfix Message-ID: <3D8A502F.C1168864@isu.edu> I'm converting over to POSTFIX from Sendmail (well actually I can switch back and forth between the two in RedHat 7.3) and I'm running Mailman 2.0.13 without problems (only problem is with large lists, here I believe Postfix can help me there). Postfix has more tweak options that's why I want to switch. When I make the change to "Postfix" is there anything I need to change on Mailman to make it run with Postfix, in other words will I break anything? -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From JasonR.Mastaler Fri Sep 20 00:49:13 2002 From: JasonR.Mastaler (JasonR.Mastaler) Date: Thu, 19 Sep 2002 17:49:13 -0600 Subject: [Mailman-Developers] handling multi-byte characters in templates Message-ID: When Mailman.Utils.maketext() does string substitution in a template containing multi-byte characters (such as in templates/ja/), how does it avoid errors during dictionary interpolation? TMDA is using a nearly identical function to make text from templates, but certain multi-byte characters (Japanese in particular) in the templates trigger the following exceptions: ValueError: incomplete format key TypeError: not enough arguments for format string Someone suggested that the Japanese text probably has characters in it that include an ascii % as part of the multi-byte character. I'm wondering how Mailman gets around this problem. -- (http://tmda.net/) From tkikuchi@is.kochi-u.ac.jp Fri Sep 20 01:28:34 2002 From: tkikuchi@is.kochi-u.ac.jp (Tokio Kikuchi) Date: Fri, 20 Sep 2002 09:28:34 +0900 Subject: [Mailman-Developers] handling multi-byte characters in templates References: Message-ID: <3D8A6BB2.5010409@is.kochi-u.ac.jp> Jason, Japanese is the most difficult language when you internationalize applications. ;-) 1. it is multibyte 2. there are three coding schemes (although standad is one: JIS) they are iso-2022-jp, shift-jis, and euc-jp 3. iso-2022-jp is used for mail and news messages. you will hear many complaints if you use other code even if it is followed by MIME scheme. 4. because iso-2022-jp is 7bit, it contains many special characters like \,%,&,... (they are ESCaped) 5. among the three, euc-jp is the best for using in programming because all the japanese characters are msb set 1. (like UTF-8) Therefore, japanese messages are best treated 1. use euc-jp within internal process of messages and patterns. 2. convert the message charset from iso-2022-jp to euc-jp, when it first enter the processing pipeline. 3. convert again to iso-2022-jp when the message going out. Jason R. Mastaler wrote: > When Mailman.Utils.maketext() does string substitution in a template > containing multi-byte characters (such as in templates/ja/), how does > it avoid errors during dictionary interpolation? euc-jp is used in the templates. > > TMDA is using a nearly identical function to make text from templates, > but certain multi-byte characters (Japanese in particular) in the > templates trigger the following exceptions: > > ValueError: incomplete format key > > TypeError: not enough arguments for format string > > Someone suggested that the Japanese text probably has characters in it > that include an ascii % as part of the multi-byte character. > > I'm wondering how Mailman gets around this problem. > -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From noreply@sourceforge.net Fri Sep 20 16:42:29 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 20 Sep 2002 08:42:29 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-612174 ] subscribe_policy + ALLOW_OPEN_SUBSCRIBE Message-ID: Bugs item #612174, was opened at 2002-09-20 15:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612174&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Jay Luker (lbjay) Assigned to: Nobody/Anonymous (nobody) Summary: subscribe_policy + ALLOW_OPEN_SUBSCRIBE Initial Comment: There is a flaw somewhere in the logic that alters the value of subscribe_policy based on the value of mm_cfg.ALLOW_OPEN_SUBSCRIBE. I have ALLOW_OPEN_SUBSCRIBE = 0. When I attempt to set subscribe_policy = 1 via the config_list script, subscribe_policy is always set to 2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612174&group_id=103 From noreply@sourceforge.net Fri Sep 20 17:02:52 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 20 Sep 2002 09:02:52 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-612174 ] subscribe_policy + ALLOW_OPEN_SUBSCRIBE Message-ID: Bugs item #612174, was opened at 2002-09-20 15:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612174&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Jay Luker (lbjay) Assigned to: Nobody/Anonymous (nobody) Summary: subscribe_policy + ALLOW_OPEN_SUBSCRIBE Initial Comment: There is a flaw somewhere in the logic that alters the value of subscribe_policy based on the value of mm_cfg.ALLOW_OPEN_SUBSCRIBE. I have ALLOW_OPEN_SUBSCRIBE = 0. When I attempt to set subscribe_policy = 1 via the config_list script, subscribe_policy is always set to 2. ---------------------------------------------------------------------- >Comment By: Jay Luker (lbjay) Date: 2002-09-20 16:02 Message: Logged In: YES user_id=51347 OK, I was just able to track this down further. The problem (I think) lies in Gui/Privacy.py. _setValue states: "For subscribe_policy when ALLOW_OPEN_SUBSCRIBE is true, we need to add one to the value because the page didn't present an open list as an option." ... but then the subsequent code actually adds one to the value if ALLOW_OPEN_SUBSCRIBE is untrue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612174&group_id=103 From JasonR.Mastaler Fri Sep 20 21:29:30 2002 From: JasonR.Mastaler (JasonR.Mastaler) Date: Fri, 20 Sep 2002 14:29:30 -0600 Subject: [Mailman-Developers] Re: handling multi-byte characters in templates References: <3D8A6BB2.5010409@is.kochi-u.ac.jp> Message-ID: Tokio Kikuchi writes: > Therefore, japanese messages are best treated > 1. use euc-jp within internal process of messages and patterns. > 2. convert the message charset from iso-2022-jp to euc-jp, when it > first enter the processing pipeline. > 3. convert again to iso-2022-jp when the message going out. Thank-you for the thorough explanation. I have a few more questions about this. Do you know what people use for Japanese character code conversion these days in Python? I see that Mailman seems to be converting the templates from euc-jp to iso-2022-jp when sending out mail messages, but can't figure out where this is being done in the code. Also, I found the JapaneseCodecs package for Python. The README says: "By using this package, Japanese characters can be treated as a character string instead of a byte sequence." This makes it seem like if I used JapaneseCodecs, no conversion would be necessary -- I just could store templates in iso-2022-jp and the special characters like `%' wouldn't interfere. Does this sound right? Thanks. -- (http://tmda.net/) From noreply@sourceforge.net Fri Sep 20 21:40:30 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 20 Sep 2002 13:40:30 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-456080 ] qmail-to-mailman.py & README.QMAIL diff Message-ID: Bugs item #456080, was opened at 2001-08-28 02:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=456080&group_id=103 Category: configuring/installing Group: More Information Needed Status: Closed Resolution: Out of Date Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: qmail-to-mailman.py & README.QMAIL diff Initial Comment: contrib/qmail-to-mailman.py and README.QMAIL differ. a) contrib/qmail-to-mailman.py says: # To configure a virtual domain to connect to mailman, create these files: # # ~mailman/.qmail-default # |preline /usr/bin/python /home/mailman/mail-in.py This should be EITHER: # |preline /path/to/python /path/to/qmail-to-mailman.py OR (not sure about preline!!) # |/path/to/python /path/to/qmail-to-mailman.py The real question: To preline or not to preline? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-09-20 13:40 Message: Logged In: NO preline! You need preline, if you do not have it, then your mbox archives will be broken and hypermail will not archive. preline inserts an mbox-style From line at the head of the message, and hypermail depends on it. See "Q. Still having problems? Running QMail?" in the mailman FAQ. README.QMAIL needs to be fixed. It fooled me... Anyone who is successfully running this without preline apparently has never noticed that they have no hypermail archives! ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-05 10:06 Message: Logged In: YES user_id=12800 I don't know anything about qmail, so if there are changes to be made against the MM2.1cvs tree, please attach diffs. In the meantime, I'm closing this bug. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-10-06 05:00 Message: Logged In: NO Not to preline. Running mailman and qmail-to-mailman.py for ages without preline and without problems. ---------------------------------------------------------------------- Comment By: Ralf Hildebrandt (hildeb) Date: 2001-09-20 03:42 Message: Logged In: YES user_id=77128 According to the instructions that apply if you DON'T use qmail-to-mailman.py, I'd say the opposite: You need preline. ---------------------------------------------------------------------- Comment By: Ricardo Kustner (rixhq) Date: 2001-09-09 22:13 Message: Logged In: YES user_id=16263 http://www.qmail.org/man/man1/preline.html I think the info on the manpage should be enough to decide wether or not you need preline... (ie does mailman need the extra headers generated by preline?) As far was I can see we don't need preline... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=456080&group_id=103 From tkikuchi@is.kochi-u.ac.jp Sat Sep 21 02:05:28 2002 From: tkikuchi@is.kochi-u.ac.jp (Tokio Kikuchi) Date: Sat, 21 Sep 2002 10:05:28 +0900 Subject: [Mailman-Developers] Re: handling multi-byte characters in templates References: <3D8A6BB2.5010409@is.kochi-u.ac.jp> Message-ID: <3D8BC5D8.9050709@is.kochi-u.ac.jp> Jason R. Mastaler wrote: > Tokio Kikuchi writes: > > >>Therefore, japanese messages are best treated >>1. use euc-jp within internal process of messages and patterns. >>2. convert the message charset from iso-2022-jp to euc-jp, when it >> first enter the processing pipeline. >>3. convert again to iso-2022-jp when the message going out. > > > Thank-you for the thorough explanation. I have a few more questions > about this. > > Do you know what people use for Japanese character code conversion > these days in Python? I see that Mailman seems to be converting the > templates from euc-jp to iso-2022-jp when sending out mail messages, > but can't figure out where this is being done in the code. Conversion is done when the internal crafted massage is genarated by using Mailman.Message class which utilizes email package. In email/Charset.py, defined are: # Defaults CHARSETS = { # input header enc body enc output conv 'iso-8859-1': (QP, QP, None), 'iso-8859-2': (QP, QP, None), 'us-ascii': (None, None, None), 'big5': (BASE64, BASE64, None), 'gb2312': (BASE64, BASE64, None), 'euc-jp': (BASE64, None, 'iso-2022-jp'), 'shift_jis': (BASE64, None, 'iso-2022-jp'), 'iso-2022-jp': (BASE64, None, None), 'koi8-r': (BASE64, BASE64, None), 'utf-8': (BASE64, BASE64, 'utf-8'), } Read the source for more. These implementation are mostly done by Ben Gertzfield and he is on this list I believe. Unfortunately, these automatic conversion is for internaly generated message only (I suppose) so I'm writing conversion modules for 2 and 3. They are in http://mm.tkikuchi.net/mailman-2.1.ja/Mailman/Handlers/ which are pre-email style and need rewriting though. > > Also, I found the JapaneseCodecs package for Python. The README says: > > "By using this package, Japanese characters can be treated as a > character string instead of a byte sequence." Looks like it mean "a 'unicode' character string." > > This makes it seem like if I used JapaneseCodecs, no conversion would > be necessary -- I just could store templates in iso-2022-jp and the > special characters like `%' wouldn't interfere. Does this sound > right? No. You must escape with '%%' or convert into 'euc-jp' or 'unicode' before template substitutions, and un-escape or convert to 'iso-2022-jp' after, of course. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From chuqui@plaidworks.com Sun Sep 22 04:35:43 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Sat, 21 Sep 2002 20:35:43 -0700 Subject: [Mailman-Developers] stupid CVS question... In-Reply-To: <27192418234.20020909180448@mail.hypertrek.info> Message-ID: <5F591198-CDDC-11D6-A8B9-0003934516A8@plaidworks.com> thanks! it worked! On Monday, September 9, 2002, at 09:04 AM, Luigi Rosa wrote: > Monday, September 9, 2002, 5:12:54 AM, you wrote: > > CVR> What's the magic incantation for this? obviously, my CVS hacking > is > CVR> weak.... > > Mine is not very strong, but it works. > -- 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 Sun Sep 22 05:00:52 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Sat, 21 Sep 2002 21:00:52 -0700 Subject: [Mailman-Developers] funny error messages in make install for CVS on Mac OS X Message-ID: Hey, barry -- starting to play with the CVS on OS X, and I happened to notice some weird errors on install: for p in email-2.3 JapaneseCodecs-1.4.8 KoreanCodecs-2.0.5; \ do \ gunzip -c $p.tar.gz | tar xf -; \ (cd $p ; PYTHONPATH=/usr/local/mailman/pythonlib /usr/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done ld: for architecture i386 ld: warning /usr/lib/bundle1.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: warning build/temp.darwin-6.1-Power Macintosh-2.2/_japanese_codecs.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: warning /usr/lib/gcc/darwin/3.1/libgcc.a archive's cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (can't load from it) ld: warning /usr/lib/libSystem.dylib cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: for architecture i386 ld: warning /usr/lib/bundle1.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: warning build/temp.darwin-6.1-Power Macintosh-2.2/_koco.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: warning /usr/lib/gcc/darwin/3.1/libgcc.a archive's cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (can't load from it) ld: warning /usr/lib/libSystem.dylib cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: for architecture i386 ld: warning /usr/lib/bundle1.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: warning build/temp.darwin-6.1-Power Macintosh-2.2/hangul.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: warning /usr/lib/gcc/darwin/3.1/libgcc.a archive's cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (can't load from it) ld: warning /usr/lib/libSystem.dylib cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) It looks like some of the international character stuff is assuming Wintel architecture in some way that's not obvious from 10 minutes of looking at the source... ideas? -- 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 Sun Sep 22 11:20:07 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 22 Sep 2002 03:20:07 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-612784 ] feature-request : Use of Spamassassintag Message-ID: Bugs item #612784, was opened at 2002-09-22 12:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612784&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Alexandre Dulaunoy (adulau) Assigned to: Nobody/Anonymous (nobody) Summary: feature-request : Use of Spamassassintag Initial Comment: Mail::SpamAssassin is adding a tag when He suspects to be a spam. Do you plan to add a test on it and not forward mail into the mailing if the tag is present ? It's also useful when the list is moderated. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612784&group_id=103 From chuqui@plaidworks.com Sun Sep 22 20:06:33 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Sun, 22 Sep 2002 12:06:33 -0700 Subject: [Mailman-Developers] mailman on OS X 10.2 Message-ID: <68EA9EB1-CE5E-11D6-A8B9-0003934516A8@plaidworks.com> I finally had time to install 2.1b3+ on OS X 10.2 Install was fairly straightforward. Here is the script of what I had to do to install. It assumes a generic 10.2 system with a working sendmail. My current mm_cfg.py is here: I'm leaving the beast fairly generic until I figure out how 2.1 works and what I want to tweak.... So far, looks pretty solid. Kewl. (one thing I DO know. I STILL don't like the look of Pipermail. Ohwell... But unlike 2.0.x, it worked out fo the box for me....) -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ From JasonR.Mastaler Mon Sep 23 03:14:00 2002 From: JasonR.Mastaler (JasonR.Mastaler) Date: Sun, 22 Sep 2002 20:14:00 -0600 Subject: [Mailman-Developers] Re: handling multi-byte characters in templates References: <3D8A6BB2.5010409@is.kochi-u.ac.jp> <3D8BC5D8.9050709@is.kochi-u.ac.jp> Message-ID: Tokio Kikuchi writes: > Conversion is done when the internal crafted massage is genarated by > using Mailman.Message class which utilizes email package. In > email/Charset.py, defined are: Ok, I see. Thanks again for your help, I'm much more clear on how to proceed with this problem now. -- (http://tmda.net/) From joshuae@bitmine.net Mon Sep 23 17:43:09 2002 From: joshuae@bitmine.net (Joshua Eichen) Date: Mon, 23 Sep 2002 09:43:09 -0700 Subject: [Mailman-Developers] Checking if a varible is set inside the MailList class Message-ID: <20020923164309.GB9503@bitmine.net> I'm trying to figure out if a varibe is already set inside the mailman clas= s=20 and if not, set it. The cleanest thing I've come up with is=20 self.var_name =3D getattr(self, var_name, default). Is there a more elegent solution? Joshua --=20 Bury my heart at Betrand Russellstraat. keyserver: seattle.keyserver.net fingerprint: 363E D1F4 8EC0 DDE3 5DC1 056F E8ED 5163 EE1B 2333 From wheakory@isu.edu Mon Sep 23 19:01:56 2002 From: wheakory@isu.edu (Kory Wheatley) Date: Mon, 23 Sep 2002 12:01:56 -0600 Subject: [Mailman-Developers] Postfix alias files Message-ID: <3D8F5713.6333FC06@isu.edu> Question, what are the alias files configured like for POSTFIX when using Mailman, are they the same syntax as Sendmail? Could someone give me an example? -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From claw@kanga.nu Mon Sep 23 19:05:30 2002 From: claw@kanga.nu (J C Lawrence) Date: Mon, 23 Sep 2002 11:05:30 -0700 Subject: [Mailman-Developers] Postfix alias files In-Reply-To: Message from Kory Wheatley of "Mon, 23 Sep 2002 12:01:56 MDT." <3D8F5713.6333FC06@isu.edu> References: <3D8F5713.6333FC06@isu.edu> Message-ID: <24167.1032804330@kanga.nu> On Mon, 23 Sep 2002 12:01:56 -0600 Kory Wheatley wrote: > Question, what are the alias files configured like for POSTFIX when > using Mailman, are they the same syntax as Sendmail? With the rare exceptions of QMail, all Unix alias files have the same format. Caveat: Sendmail smrsh, which doesn't change the alias file format, but does change its external requirements. -- 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 wheakory@isu.edu Mon Sep 23 23:52:09 2002 From: wheakory@isu.edu (Kory Wheatley) Date: Mon, 23 Sep 2002 16:52:09 -0600 Subject: [Mailman-Developers] Postfix with Mailman Message-ID: <3D8F9B19.A319DB49@isu.edu> I recently switched from Sendmail to Postfix running on Mailman 2.1b3 Red Hat 7.3 and I followed all the instructions in the README.POSTFIX file. I've got the aliases located in "/home/mailman/data" and mailman as the "mail-gid", not using virtual domains. Turned off Sendmail and turned on Postfix and when I send a message nothing happens, nothing goes in the queue directory, nothing goes in the mailman log files, it's as if nothing was sent, because nothing is reported in /var/spool/postfix. In the Postfix configuration file (main.cf) I changed the myhostname to "myhostname= kwlinux.isu.edu" , which is my Mailmans machines hostname. I changed mydomain to "mydomain = isu.edu" and mydestination is setup as "mydestination= $myhostname, localhost, $mydomain" and the inet_interfaces is setup as "inet_interface = localhost". Changed alias_map to point to the alias file in mailman, is there something I'm missing?. -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From jarrell@vt.edu Tue Sep 24 15:29:57 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Tue, 24 Sep 2002 10:29:57 -0400 Subject: [Mailman-Developers] Fwd: Re: [Mailman-Users] Re: un-subscription problems Message-ID: <5.1.0.14.2.20020924102847.00a37120@lennier.cc.vt.edu> Hey, Barry, have you noticed these? email is doing the header breaking thing again... Found two in mailman-users today. >Date: Tue, 24 Sep 2002 09:28:11 -0400 (EDT) >Date-warning: Date header was inserted by gkar.cc.vt.edu >From: Jon Carnes >Subject: Re: [Mailman-Users] Re: un-subscription problems >To: Anthony Carmody >Cc: mailman-users@python.org > > >cons.nc.rr.com><017e01c2612b$7eea5690$6700a8c0@interfa.office><1032614940.16 > 33.39.camel@Ann cons.nc.rr.com> > ><000701c261d1$19b70880$0d4efea9@Main><1032664586.1642.14.camel@Anncons.nc.rr > .com> <00d701c262b2$8de7e1c0$6700a8c0@interfa.office> > <1032790602.1673.122.camel@Anncons.nc.rr.com> > <036d01c26375$9b0c4030$6700a8c0@interfa.office> >Content-Type: text/plain >Content-Transfer-Encoding: 7bit >X-Mailer: Evolution/1.0.2-5mdk >Message-Id: <1032874162.5317.18.camel@Anncons.nc.rr.com> >Mime-Version: 1.0 >X-Spam-Status: No, hits=-3.4 required=5.0 tests=IN_REP_TO >Sender: mailman-users-admin@python.org >Errors-To: mailman-users-admin@python.org >X-BeenThere: mailman-users@python.org >X-Mailman-Version: 2.0.13 (101270) >Precedence: bulk >List-Help: >List-Post: >List-Subscribe: , > >List-Id: Mailman mailing list management users >List-Unsubscribe: , > >List-Archive: >Date: 24 Sep 2002 09:29:21 -0400 > >I From wheakory@isu.edu Tue Sep 24 19:52:09 2002 From: wheakory@isu.edu (Kory Wheatley) Date: Tue, 24 Sep 2002 12:52:09 -0600 Subject: [Mailman-Developers] Help with mailman and postfix Message-ID: <3D90B459.7D6C06CA@isu.edu> I recently switched from Sendmail to Postfix running on Mailman 2.1b3 Red Hat 7.3 and I followed all the instructions in the README.POSTFIX file. I've got the aliases located in "/home/mailman/data" and mailman as the "mail-gid", not using virtual domains. Turned off Sendmail and turned on Postfix and when I send a message nothing happens, nothing goes in the queue directory, nothing goes in the mailman log files, it's as if nothing was sent, because nothing is reported in /var/spool/postfix. In the Postfix configuration file (main.cf) I changed the myhostname to "myhostname= kwlinux.isu.edu" , which is my Mailmans machines hostname. I changed mydomain to "mydomain = isu.edu" and mydestination is setup as "mydestination= $myhostname, localhost, $mydomain" and the inet_interfaces is setup as "inet_interface = localhost". Changed alias_map to point to the alias file in mailman, is there something I'm missing, is there something else I need to activate on my system, or tell my Red Hat Linux 7.3 that Postfix is now the MTA. -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From JasonR.Mastaler Wed Sep 25 02:00:16 2002 From: JasonR.Mastaler (JasonR.Mastaler) Date: Tue, 24 Sep 2002 19:00:16 -0600 Subject: [Mailman-Developers] Multipart/Report MIME content-type (RFC 1892) Message-ID: Shouldn't Mailman's reports be sent using the Multipart/Report MIME content-type defined by RFC 1892 rather than Multipart/Mixed? It seems more appropriate. Quoting from section 1 of RFC 1892: 1. The Multipart/Report MIME content-type The Multipart/Report MIME content-type is a general "family" or "container" type for electronic mail reports of any kind. Although this memo defines only the use of the Multipart/Report content-type with respect to delivery status reports, mail processing programs will benefit if a single content-type is used to for all kinds of reports. -- (http://tmda.net/) From noreply@sourceforge.net Wed Sep 25 19:52:52 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 25 Sep 2002 11:52:52 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-614569 ] Email appoval confirm dies Message-ID: Bugs item #614569, was opened at 2002-09-25 14:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=614569&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Email appoval confirm dies Initial Comment: Confirming a held post (as moderator) via email, with the "Approved: pass" line in thebody of the message, causes an error with this traceback: File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 198, in _dispose res.process() File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 93, in process stop = self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 119, in do_command return handler.process(self, args) File "/usr/local/mailman/Mailman/Commands/cmd_confirm.py", line 44, in process results = mlist.ProcessConfirmation(cookie, res.msg) File "/usr/local/mailman/Mailman/MailList.py", line 1096, in ProcessConfirmation subpart = email.Iterators.typed_subpart_iterator( TypeError: unsubscriptable object I don't know that this is specific to having the Approved: line in the mesage, but I can't add that as a header with my email client. - Stoney ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=614569&group_id=103 From noreply@sourceforge.net Thu Sep 26 17:06:27 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 26 Sep 2002 09:06:27 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-614569 ] Email appoval confirm dies Message-ID: Bugs item #614569, was opened at 2002-09-25 14:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=614569&group_id=103 Category: mail delivery Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Email appoval confirm dies Initial Comment: Confirming a held post (as moderator) via email, with the "Approved: pass" line in thebody of the message, causes an error with this traceback: File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 198, in _dispose res.process() File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 93, in process stop = self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 119, in do_command return handler.process(self, args) File "/usr/local/mailman/Mailman/Commands/cmd_confirm.py", line 44, in process results = mlist.ProcessConfirmation(cookie, res.msg) File "/usr/local/mailman/Mailman/MailList.py", line 1096, in ProcessConfirmation subpart = email.Iterators.typed_subpart_iterator( TypeError: unsubscriptable object I don't know that this is specific to having the Approved: line in the mesage, but I can't add that as a header with my email client. - Stoney ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=614569&group_id=103 From noreply@sourceforge.net Thu Sep 26 17:22:05 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 26 Sep 2002 09:22:05 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-615040 ] problem creating newlist Message-ID: Bugs item #615040, was opened at 2002-09-26 16:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=615040&group_id=103 Category: command line scripts Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tim White (reverend_timmyd) Assigned to: Nobody/Anonymous (nobody) Summary: problem creating newlist Initial Comment: I get the following when I try to run "newlist": Traceback (innermost last): File "/home/admin/src/mailman-2.0.13/bin/newlist", line 52, in ? import paths ImportError: No module named paths any ideas? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=615040&group_id=103 From noreply@sourceforge.net Thu Sep 26 17:43:54 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 26 Sep 2002 09:43:54 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-615040 ] problem creating newlist Message-ID: Bugs item #615040, was opened at 2002-09-26 19:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=615040&group_id=103 Category: command line scripts Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tim White (reverend_timmyd) Assigned to: Nobody/Anonymous (nobody) Summary: problem creating newlist Initial Comment: I get the following when I try to run "newlist": Traceback (innermost last): File "/home/admin/src/mailman-2.0.13/bin/newlist", line 52, in ? import paths ImportError: No module named paths any ideas? ---------------------------------------------------------------------- Comment By: Tomas Lindroos (skitta) Date: 2002-09-26 19:43 Message: Logged In: YES user_id=613582 Don't run "newlist" from the source directory, run it from the installation directory. This is true for some other scripts as well. Check the installation directory, and you will find a file "paths.py", which is correctly imported from "newlist" (and other) scripts. The same library can be found in other directories as well (i.e. $install_dir/cron/). /skitta ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=615040&group_id=103 From noreply@sourceforge.net Fri Sep 27 07:42:10 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 26 Sep 2002 23:42:10 -0700 Subject: [Mailman-Developers] [ mailman-Patches-615387 ] Umbrella list member exploder. Message-ID: Patches item #615387, was opened at 2002-09-27 16:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=615387&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Simon Coggins (scoggins) Assigned to: Nobody/Anonymous (nobody) Summary: Umbrella list member exploder. Initial Comment: If you subscribe a list to another list with the format +somelist@mailman.domain then that line is removed and all of the members of 'somelist' are put in it's place. This allows you to have heiracial lists that apear to come from the master list, but are totaly generated on the fly by the members of other lists. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=615387&group_id=103 From noreply@sourceforge.net Fri Sep 27 07:44:41 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 26 Sep 2002 23:44:41 -0700 Subject: [Mailman-Developers] [ mailman-Patches-615388 ] Patch to enhance Sendmail.py Message-ID: Patches item #615388, was opened at 2002-09-27 16:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=615388&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Simon Coggins (scoggins) Assigned to: Nobody/Anonymous (nobody) Summary: Patch to enhance Sendmail.py Initial Comment: This patches changes Sendmail.py so it actually works and stops some of the problems with the old Sendmail.py like duplicate messages and other unknown conditions of sendmail. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=615388&group_id=103 From noreply@sourceforge.net Fri Sep 27 20:57:25 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 27 Sep 2002 12:57:25 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-615040 ] problem creating newlist Message-ID: Bugs item #615040, was opened at 2002-09-26 16:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=615040&group_id=103 Category: command line scripts Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tim White (reverend_timmyd) Assigned to: Nobody/Anonymous (nobody) Summary: problem creating newlist Initial Comment: I get the following when I try to run "newlist": Traceback (innermost last): File "/home/admin/src/mailman-2.0.13/bin/newlist", line 52, in ? import paths ImportError: No module named paths any ideas? ---------------------------------------------------------------------- >Comment By: Tim White (reverend_timmyd) Date: 2002-09-27 19:57 Message: Logged In: YES user_id=618626 thanks for the help. However, the guy that installed it for me had to hack it up so much to make it work with plesk (my virtual host management software, that we've had to write some custom scripts to use instead of the ones that came w/ mailman... ---------------------------------------------------------------------- Comment By: Tomas Lindroos (skitta) Date: 2002-09-26 16:43 Message: Logged In: YES user_id=613582 Don't run "newlist" from the source directory, run it from the installation directory. This is true for some other scripts as well. Check the installation directory, and you will find a file "paths.py", which is correctly imported from "newlist" (and other) scripts. The same library can be found in other directories as well (i.e. $install_dir/cron/). /skitta ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=615040&group_id=103 From chk@pobox.com Mon Sep 30 02:57:33 2002 From: chk@pobox.com (Harald Koch) Date: Sun, 29 Sep 2002 21:57:33 -0400 Subject: [Mailman-Developers] 'message ignored by' messages? Message-ID: <26205.1033351053@elisabeth.cfrq.net> I'm running 2.1b3. I found the following in logs/vette: Sep 29 14:35:29 2002 (1853) Precedence: bulk message ignored by: csc494-request@third-bit.com Sep 29 14:48:29 2002 (1853) Precedence: bulk message ignored by: csc494-request@third-bit.com Sep 29 17:11:59 2002 (1853) Precedence: bulk message ignored by: csc494-request@third-bit.com Sep 29 21:34:59 2002 (1853) Precedence: bulk message ignored by: csc494-request@third-bit.com There's a bunch more, dating back to time immemorial. They tend to, but don't always, follow some other message in the logs by exactly 30 seconds (the queue processing interval?): Sep 29 14:34:59 2002 (1853) csc494 post from chk@pobox.com held: Post to moderated list Sep 29 14:47:59 2002 (1853) csc494 post from g@mbl.ca held: Post to moderated list Sep 29 17:11:59 2002 (1853) Precedence: bulk message ignored by: csc494-request@third-bit.com Sep 29 21:34:59 2002 (1853) Precedence: bulk message ignored by: csc494-request@third-bit.com There are no messages in the sendmail logs addressed to "csc494-request", so this looks to me like something internal to mailman's queue processing. Should I just ignore these? Is there anyway to capture the message that is being ignored? Thanks, -- Harald Koch "It takes a child to raze a village." -Michael T. Fry From noreply@sourceforge.net Mon Sep 30 18:43:38 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 30 Sep 2002 10:43:38 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-616674 ] bin/arch not processing mbox import corr Message-ID: Bugs item #616674, was opened at 2002-09-30 13:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=616674&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: fuzzy (fuzzynco) Assigned to: Nobody/Anonymous (nobody) Summary: bin/arch not processing mbox import corr Initial Comment: I needed to import an archive from yahoo!groups. a list formerly on Y!G is now on my server with MM2.1b3. After creating the mbox file with a perl script na dtesting it with pine (to make sure all the email is acuallu there), I tried to import it using arch. there are a few thousand emails in the file, but arch only finds 2? I posted to the mm users mailing list and got a reply from Larry Weeks, said to send him a copy of the file, and he tested it with bin/arch from 2.0.6 and it works as expected. since the mbox file is readable by pine, shouldn't arch handle it correctly? email me if i can provide any thing that would help diagnose the problem. thanks... fuzzy@pooh.asarian.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=616674&group_id=103 From marklists@mceahern.com Wed Sep 18 19:32:20 2002 From: marklists@mceahern.com (Mark McEahern) Date: Wed, 18 Sep 2002 18:32:20 -0000 Subject: [Mailman-Developers] message url in footer Message-ID: It would be great if I could modify the footer of a mailing list to insert the archive URL of the current message. Is that easy/possible? I apologize if this is a FAQ. I read the FAQ and the wish list and couldn't find a reference to it. I also did at least a cursory google search and couldn't find anything obvious related to this: http://www.google.com/search?q=mailman+footer http://www.google.com/search?q=mailman+footer+archive Thanks, // mark p.s. Suggestion: Put a "last updated" date on the wish list. - From silviu@genesys.ro Thu Sep 26 17:24:36 2002 From: silviu@genesys.ro (Silviu Marin-Caea) Date: Thu, 26 Sep 2002 19:24:36 +0300 Subject: [Mailman-Developers] large attachments replaced by links Message-ID: <3D9334C4.60106@genesys.ro> Sorry if this is not a new ideea. We have some internal lists. Users have the (bad) habbit of sending large attached files on these lists. What I'd like mailman to be able to do is to automatically take those attachments out of the posts, storing them to a directory I specify, and replace them with links to the stored files. Like this: "The file attached to this message can be found here http://bla-blaserver.net/attach/grossely_large_and_stupid_presentation.ppt" Configuring a http (or ftp) server to publish those attachments would be the job of the admin. Thank you. Please CC to me the eventual replies. -- Silviu Marin-Caea Systems Engineer Linux/Unix http://www.genesys.ro Phone +40723-267961