From noreply at sourceforge.net Mon Sep 1 22:15:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 2 00:16:02 2003 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 9 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-09-02 00:15 Message: Logged In: YES user_id=12800 Bumping priority. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-15 14:55 Message: Logged In: YES user_id=11375 OK, done! This patch is now ready to go in: some people have looked at the RSS and haven't spotted any problems. Barry, can I please get CVS write access to check this in? ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 21:00 Message: Logged In: YES user_id=11375 Attaching correct version of the patch. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 20:52 Message: Logged In: YES user_id=11375 Here at last is an updated version of the patch that's crawling closer to being complete. There's now a RSS_NUM_ARTICLES setting in Defaults.py, the generated URLs are correct, and I modified the English template to link to the RSS file. Remaining things: check the generated RSS for correctness; edit all of the other language templates to include the RSS file (I may ask for CVS write access to do that). It would be really nice if the Mailman upgrade script could update existing general list information pages to include the LINK element; any suggestion about how to go about that? ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:00 Message: Logged In: YES user_id=7830 OK, I've regenerated the patch with some code which works for me. http://rdfweb.org/2003/06/mailman-rss/rsspatch Health warning: * I suspect it may fail in conditions when get_archives() returns a list not a string (does this ever happen?). * See also problems mentioned below, regenerating partial archives seems tricky. Hope this is useful anyways... Dan ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 07:48 Message: Logged In: YES user_id=7830 I thought I'd have a look at this myself, though have modest knowledge of both Python and MailMan. In the course of trying to patch the patch, I tried running the archiver over just the last couple of messages, to speed things along: "../../bin/arch -s 4390 rdfweb-dev". Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 310, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1082, in write_TOC rss.write(self.RSS()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 769, in RSS date, msgid = self.database.dateIndex.first() AttributeError: HyperDatabase instance has no attribute 'dateIndex' Not sure what's going on there, but this seemed as good a place of any to keep note of it. Investigating... ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 07:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 From noreply at sourceforge.net Tue Sep 2 04:24:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 2 06:24:37 2003 Subject: [ mailman-Bugs-767596 ] mailman list archive links not working with virtual hosts Message-ID: Bugs item #767596, was opened at 2003-07-08 09:55 Message generated for change (Comment added) made by thomas_ah You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=767596&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nick Hemsley (blackisha) Assigned to: Nobody/Anonymous (nobody) Summary: mailman list archive links not working with virtual hosts Initial Comment: any mailman page with a link to the archives page for a mailing-list on a virtual-host, points to the primary hostname, instead of pointing to the virtual-domain. try this page for an example of the problem http://itomic.com/mailman/listinfo/asaconsultants_itomic.com the Asaconsultants archives link points to http://earth.itomic.com/pipermail/asaconsultants_itomic.com/ which is the primary hostname of the server on which itomic.com resides. it should point to http://itomic.com/pipermail/asaconsultants_itomic.com p.s. this list was recently upgraded to 2.1.2 by make install-ing into a previously existing mailman (2.0.13) directory (it said things in make install about upgrading, so I assumed it was handling ok) ---------------------------------------------------------------------- Comment By: Thomas Arendsen Hein (thomas_ah) Date: 2003-09-02 12:24 Message: Logged In: YES user_id=839582 leftlink: Remove PUBLIC_ARCHIVE_URL from mm_cfg.py since this will be calculated by Defaults.py blackisha (and maybe leftlink, too): You need to use add_virtualhost statements in your mm_cfg.py: DEFAULT_EMAIL_HOST = 'itomic.com' DEFAULT_URL_HOST = DEFAULT_EMAIL_HOST add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) We just stumbled into the same problems here :) ---------------------------------------------------------------------- Comment By: rich cowan (leftlink) Date: 2003-08-26 01:45 Message: Logged In: YES user_id=538509 This bug should renamed: "LIST Archive Links Broken After 2.1 Upgrade." That's because it is one of several problems with updating: it appears that on one machine where the list info is at: domain.org/cgi-bin/mailman/listinfo/nosi-steering the archives link for this list points to: domain.org/pipermail/ i.e. the list name vanishes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=767596&group_id=103 From noreply at sourceforge.net Tue Sep 2 04:27:00 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 2 06:27:04 2003 Subject: [ mailman-Bugs-782024 ] Private archives link error Message-ID: Bugs item #782024, was opened at 2003-08-02 19:24 Message generated for change (Comment added) made by thomas_ah You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=782024&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nicola Soranzo (soranzo) Assigned to: Nobody/Anonymous (nobody) Summary: Private archives link error Initial Comment: If I visit http://domain/mailman/private/listname/ all the links to the Thread, Subject, ... monthly archives are correct, but if the URL is http://domain/mailman/private/listname (without the trailing slash), the links are incorrect, eg.: http://domain/mailman/private/2003-July/thread.html (without the listname between private and the month). ---------------------------------------------------------------------- Comment By: Thomas Arendsen Hein (thomas_ah) Date: 2003-09-02 12:27 Message: Logged In: YES user_id=839582 A quick fix is to add a redirect in your web server. But since the List-Archive mail header points to the link without a trailing slash, this should be done in the cgi script, too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=782024&group_id=103 From noreply at sourceforge.net Tue Sep 2 08:49:39 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 2 10:49:43 2003 Subject: [ mailman-Patches-799166 ] install-sh doesn't support multiple sources Message-ID: Patches item #799166, was opened at 2003-09-02 16:49 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=799166&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Joerg Friedrich (jeff42) Assigned to: Nobody/Anonymous (nobody) Summary: install-sh doesn't support multiple sources Initial Comment: Hi, When not having installed a 'install'-programm configure falls back to the provided install-sh. But this Program does'nt support multiple source files. I encountered not installed files in messages (the mo-files) and the icons. Since I had no time to take a look at install-sh I send two patches to the Makefiles. Yours, Joerg ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=799166&group_id=103 From noreply at sourceforge.net Tue Sep 2 11:00:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 2 13:00:21 2003 Subject: [ mailman-Feature Requests-799248 ] enhanced list of subscriptions Message-ID: Feature Requests item #799248, was opened at 2003-09-02 13:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=799248&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Fred L. Drake, Jr. (fdrake) Assigned to: Nobody/Anonymous (nobody) Summary: enhanced list of subscriptions Initial Comment: After dealing with mailbox quota problems in the aftermath of the Sobig.F worm, I found it would be really nice if the "List my subscriptions" display contained more information. Most importantly, whether email would actually be sent for each subscription. The most valuable information to include could probably be determined by looking for fields that differ for some lists. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=799248&group_id=103 From noreply at sourceforge.net Tue Sep 2 11:05:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 2 13:05:30 2003 Subject: [ mailman-Patches-605234 ] Stylesheet support for archives Message-ID: Patches item #605234, was opened at 2002-09-05 15:57 Message generated for change (Comment added) made by fdrake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=605234&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 4 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: 2003-09-02 13:05 Message: Logged In: YES user_id=3066 Bumped priority a little now that MM2.1 is out. ;) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 19:04 Message: Logged In: YES user_id=12800 Postponing this to post-MM2.1 :( ---------------------------------------------------------------------- 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 noreply at sourceforge.net Tue Sep 2 12:33:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 2 14:33:53 2003 Subject: [ mailman-Feature Requests-797436 ] subscription confirmation log access Message-ID: Feature Requests item #797436, was opened at 2003-08-29 10:58 Message generated for change (Comment added) made by jcdill You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=797436&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: subscription confirmation log access Initial Comment: Please create a system for mailing list owners to access the logs that prove that subscriptions were confirmed (opt-in confirmation). Ideally, this would be available both via the web administration page and via email, like all other list management tasks. ---------------------------------------------------------------------- >Comment By: JC Dill (jcdill) Date: 2003-09-02 11:33 Message: Logged In: YES user_id=836732 This was just posted to nanog: From: Vivek Khera Organization: Khera Communications, Inc., Rockville, MD Subject: Re: Media: Fearing 'Spam' Label, Advertisers Wary of E-Mail To: SPAM-L@PEACH.EASE.LSOFT.COM Precedence: list X-UIDL: 96919 >>>>> "JD" == JC Dill writes: JD> At 12:27 PM 8/29/2003, Laura Atkins wrote: >> > This is what a list manager server *should* do, if it isn't doing it >> > already then we need to just ask the developers to add this feature in. >> >> A lot of hassle for an extremely limited (if any) benefit. JD> I believe that being able to prove that a subscription was confirmed JD> is going to become increasingly important as legitimate mailing lists JD> are increasingly being asked to prove their legitimacy. Proof means JD> keeping and being able to produce the relevant logs, doesn't it? We have found that by keeping a copy of the confirmation request and upon confirmation the full headers of the incoming message, we cover pretty much any request we've gotten. Nobody has ever asked for more (not to say that they won't in the future). Since we started allowing confirm by click, instead of the return message headers, we keep the details of time, IP address, browser version, and full HTTP request. That seems to have been sufficient, too. We keep this information in the per-subscriber record in our database, so that we can pull it up any time, for as long as the record is in our database (up to 6 months after they unsubscribe). After that time, we'd have to dig thru some CDs to find it, but it is there forever. This is all for our proprietary broadcast-only announcement system, so it was easy to modify to do this... What I'd really like is for Mailman to support this type of record keeping, so the discussion lists we operate for some non-profits can also have this kind of protection. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=797436&group_id=103 From noreply at sourceforge.net Tue Sep 2 12:34:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 2 14:34:50 2003 Subject: [ mailman-Feature Requests-797436 ] subscription confirmation log access Message-ID: Feature Requests item #797436, was opened at 2003-08-29 10:58 Message generated for change (Comment added) made by jcdill You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=797436&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: subscription confirmation log access Initial Comment: Please create a system for mailing list owners to access the logs that prove that subscriptions were confirmed (opt-in confirmation). Ideally, this would be available both via the web administration page and via email, like all other list management tasks. ---------------------------------------------------------------------- >Comment By: JC Dill (jcdill) Date: 2003-09-02 11:34 Message: Logged In: YES user_id=836732 oops, it was spam-l, not nanog. Sorry! ---------------------------------------------------------------------- Comment By: JC Dill (jcdill) Date: 2003-09-02 11:33 Message: Logged In: YES user_id=836732 This was just posted to nanog: From: Vivek Khera Organization: Khera Communications, Inc., Rockville, MD Subject: Re: Media: Fearing 'Spam' Label, Advertisers Wary of E-Mail To: SPAM-L@PEACH.EASE.LSOFT.COM Precedence: list X-UIDL: 96919 >>>>> "JD" == JC Dill writes: JD> At 12:27 PM 8/29/2003, Laura Atkins wrote: >> > This is what a list manager server *should* do, if it isn't doing it >> > already then we need to just ask the developers to add this feature in. >> >> A lot of hassle for an extremely limited (if any) benefit. JD> I believe that being able to prove that a subscription was confirmed JD> is going to become increasingly important as legitimate mailing lists JD> are increasingly being asked to prove their legitimacy. Proof means JD> keeping and being able to produce the relevant logs, doesn't it? We have found that by keeping a copy of the confirmation request and upon confirmation the full headers of the incoming message, we cover pretty much any request we've gotten. Nobody has ever asked for more (not to say that they won't in the future). Since we started allowing confirm by click, instead of the return message headers, we keep the details of time, IP address, browser version, and full HTTP request. That seems to have been sufficient, too. We keep this information in the per-subscriber record in our database, so that we can pull it up any time, for as long as the record is in our database (up to 6 months after they unsubscribe). After that time, we'd have to dig thru some CDs to find it, but it is there forever. This is all for our proprietary broadcast-only announcement system, so it was easy to modify to do this... What I'd really like is for Mailman to support this type of record keeping, so the discussion lists we operate for some non-profits can also have this kind of protection. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=797436&group_id=103 From noreply at sourceforge.net Tue Sep 9 04:41:22 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 9 06:41:26 2003 Subject: [ mailman-Bugs-803045 ] mailman breaks PGP/MIME messages Message-ID: Bugs item #803045, was opened at 2003-09-09 12:41 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803045&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Enno Rehling (eressea) Assigned to: Nobody/Anonymous (nobody) Summary: mailman breaks PGP/MIME messages Initial Comment: When sending PGP/MIME messages to mailman, mailman tries to wrap the message by packaging it into its own message. To quote the enimgamil developers: "The message from mailman, however, has a Content- Type: multipart/mixed, where the signed message is packed into the first part of that message (there is an additional part with some footer message). This is not compliant to the PGP/MIME standard, no tool will be able to read such a message." I originally filed this bug with the enigmail developers, but agree with them that the bug is on mailman's side. Original bug report (including attachments of example mail) can be read at http://mozdev.org/bugs/show_bug.cgi?id=4601 This is with the mailman 2.1.2-6 deian package ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803045&group_id=103 From noreply at sourceforge.net Wed Sep 10 07:31:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Sep 10 09:31:23 2003 Subject: [ mailman-Bugs-803729 ] LookupError: unknown encoding: X-UNKNOWN Message-ID: Bugs item #803729, was opened at 2003-09-10 15:31 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ervin N?meth (nemethe) Assigned to: Nobody/Anonymous (nobody) Summary: LookupError: unknown encoding: X-UNKNOWN Initial Comment: Our site encounters the following problem. mailman-2.1.2 installed from OpenBSD ports. Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) LookupError: unknown encoding: X-UNKNOWN ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_id=103 From noreply at sourceforge.net Wed Sep 10 10:29:22 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Sep 10 12:29:56 2003 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 19:17 Message generated for change (Comment added) made by wookiew You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 9 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- Comment By: Michael Weber (wookiew) Date: 2003-09-10 16:29 Message: Logged In: YES user_id=863445 So far the patch is included (by the way: i hope that Defaults.py.in in the patch *means* Defaults.py ) and mailman get a restart. Hopefully i add the two lines in listinfo.html ( /de/ because we have german speaking lists) and take a look for the xml file). After search the whole device (only to be sure) i can say: There is no file like this. Is another patch need before? Another setup to make? I cant find any hint here... so i have to ask. But the idea is great... if it work on my lists its genious... regards, Michael running version 2.1.1 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-09-02 04:15 Message: Logged In: YES user_id=12800 Bumping priority. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-15 18:55 Message: Logged In: YES user_id=11375 OK, done! This patch is now ready to go in: some people have looked at the RSS and haven't spotted any problems. Barry, can I please get CVS write access to check this in? ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-11 01:00 Message: Logged In: YES user_id=11375 Attaching correct version of the patch. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-11 00:52 Message: Logged In: YES user_id=11375 Here at last is an updated version of the patch that's crawling closer to being complete. There's now a RSS_NUM_ARTICLES setting in Defaults.py, the generated URLs are correct, and I modified the English template to link to the RSS file. Remaining things: check the generated RSS for correctness; edit all of the other language templates to include the RSS file (I may ask for CVS write access to do that). It would be really nice if the Mailman upgrade script could update existing general list information pages to include the LINK element; any suggestion about how to go about that? ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 15:00 Message: Logged In: YES user_id=7830 OK, I've regenerated the patch with some code which works for me. http://rdfweb.org/2003/06/mailman-rss/rsspatch Health warning: * I suspect it may fail in conditions when get_archives() returns a list not a string (does this ever happen?). * See also problems mentioned below, regenerating partial archives seems tricky. Hope this is useful anyways... Dan ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:48 Message: Logged In: YES user_id=7830 I thought I'd have a look at this myself, though have modest knowledge of both Python and MailMan. In the course of trying to patch the patch, I tried running the archiver over just the last couple of messages, to speed things along: "../../bin/arch -s 4390 rdfweb-dev". Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 310, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1082, in write_TOC rss.write(self.RSS()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 769, in RSS date, msgid = self.database.dateIndex.first() AttributeError: HyperDatabase instance has no attribute 'dateIndex' Not sure what's going on there, but this seemed as good a place of any to keep note of it. Investigating... ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 22:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 21:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-18 01:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 20:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 19:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 19:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 19:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 From noreply at sourceforge.net Wed Sep 10 11:17:59 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Sep 10 13:18:02 2003 Subject: [ mailman-Bugs-803871 ] 2.1.2/Solaris 8 Problems with OutgoingRunner Message-ID: Bugs item #803871, was opened at 2003-09-10 13:17 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803871&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Charles Gagnon (charlesg) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.2/Solaris 8 Problems with OutgoingRunner Initial Comment: Mailman 2.1.2, Solaris 8 and Python 2.2.2 seem to be a bad combo. The "qrunner --runner=OutgoingRunner:0:1 -s" process starts okay and stays okay to send one message (either confirmation or post) and than is just hangs. After downgrading the Python version to 2.1.3 on the same Solaris 8 server, everything seems okay. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803871&group_id=103 From noreply at sourceforge.net Wed Sep 10 21:53:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Sep 10 23:53:36 2003 Subject: [ mailman-Patches-804162 ] Bug: unsubscription confirmation from Web bypasses approval Message-ID: Patches item #804162, was opened at 2003-09-11 12:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=804162&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: Bug: unsubscription confirmation from Web bypasses approval Initial Comment: When a member submit unsubscription request from Web UI (options) without logging in then submit confirmation from Web UI (confirm), s/he can be unsubscribed without moderator approval. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=804162&group_id=103 From noreply at sourceforge.net Sat Sep 13 11:03:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Sep 13 11:03:13 2003 Subject: [ mailman-Bugs-805630 ] mail to foo-bar@ list languishes in maildir Message-ID: Bugs item #805630, was opened at 2003-09-13 11:03 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=805630&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: John A. Martin (jamux) Assigned to: Nobody/Anonymous (nobody) Summary: mail to foo-bar@ list languishes in maildir Initial Comment: Mail to a list with a hyphen in its name languishes forever in qfiles/maildir. The culprin might be in MaildirRunner.py # We only care about the listname and the subq as in listname@ or # listname-request@ lre = re.compile(r""" ^ # start of string (?P[^-@]+) # listname@ or listname-subq@ (?: # non-grouping - # dash separator (?P[^-+@]+) # everything up to + or - or @ )? # if it exists """, re.VERBOSE | re.IGNORECASE) How about list-name@? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=805630&group_id=103 From noreply at sourceforge.net Tue Sep 16 05:14:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 16 05:15:03 2003 Subject: [ mailman-Patches-807016 ] dutch translation breaks e-mail confirmation instructions Message-ID: Patches item #807016, was opened at 2003-09-16 09:14 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=807016&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Ward Vandewege (ward) Assigned to: Nobody/Anonymous (nobody) Summary: dutch translation breaks e-mail confirmation instructions Initial Comment: The Dutch translation in templates/nl/invite.txt translates the 'confirm' command for e-mail replies to an invitation by list owners into Dutch. Mailman does not respond to Dutch commands, so this breaks Mailman. The attached patch fixes this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=807016&group_id=103 From noreply at sourceforge.net Thu Sep 18 11:13:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Sep 18 11:13:46 2003 Subject: [ mailman-Feature Requests-808626 ] ability to allow postings from all users from *@domain.com Message-ID: Feature Requests item #808626, was opened at 2003-09-18 10:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=808626&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Felicia Berryman (felicia) Assigned to: Nobody/Anonymous (nobody) Summary: ability to allow postings from all users from *@domain.com Initial Comment: Ability to allow *@domain.com. I administer a list that is automatically posted to in order to give developers cvs updates. I only want the automatic posters to have access from the list. It would be nice if I could allow any postings from a particular machine/IP. For example, all users from with @domain.com. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=808626&group_id=103 From noreply at sourceforge.net Thu Sep 18 11:23:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Sep 18 11:23:46 2003 Subject: [ mailman-Feature Requests-808642 ] ability to specify digested "waiting for approval" messages. Message-ID: Feature Requests item #808642, was opened at 2003-09-18 10:23 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=808642&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Felicia Berryman (felicia) Assigned to: Nobody/Anonymous (nobody) Summary: ability to specify digested "waiting for approval" messages. Initial Comment: I'd like the ability to specify digested "waiting for approval" messages. If I get 30 messages waiting my approval per day, then I get 30 notifications plus reminders that messages are waiting. I'd like the ability to get these messages in daily and weekly digests. Furthermore, it might be nice to only have particular messages digested, such as the messages with the explaination "Non-members are not allowed to post messages to this list.". All other posts would then come to me right away. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=808642&group_id=103 From noreply at sourceforge.net Sun Sep 21 21:07:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Sep 21 21:08:06 2003 Subject: [ mailman-Feature Requests-808626 ] ability to allow postings from all users from *@domain.com Message-ID: Feature Requests item #808626, was opened at 2003-09-18 11:13 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=808626&group_id=103 Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Felicia Berryman (felicia) Assigned to: Nobody/Anonymous (nobody) Summary: ability to allow postings from all users from *@domain.com Initial Comment: Ability to allow *@domain.com. I administer a list that is automatically posted to in order to give developers cvs updates. I only want the automatic posters to have access from the list. It would be nice if I could allow any postings from a particular machine/IP. For example, all users from with @domain.com. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-09-21 21:07 Message: Logged In: YES user_id=12800 Mailman 2.1 already has this feature. Privacy options -> sender filters -> accept_these_nonmembers (and other variables) accept Python regular expressions. See the details for details. :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=808626&group_id=103 From noreply at sourceforge.net Mon Sep 22 09:26:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Sep 22 09:26:52 2003 Subject: [ mailman-Bugs-759841 ] Multipart/mixed issues in archives Message-ID: Bugs item #759841, was opened at 2003-06-24 14:22 Message generated for change (Comment added) made by mrjc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Multipart/mixed issues in archives Initial Comment: We are having problems with mailing lists that are not being properly stripped down to text content in the archives. When there is multipart/mixed, it doesn't pull the multipart/alternative sections into their appropriate text portions. For example, from content such as the following: ============================================================================== >From ... [...] Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=------------InterScan_NT_MIME_Boundary [...] This is a multi-part message in MIME format. --------------InterScan_NT_MIME_Boundary Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C336A1.2C7564BC" Content-Transfer-Encoding: 7bit ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Kevin has a pending checkin that addresses the minss/maxss issue. =20 [...] ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message= [...] ============================================================================== I only get the following: ============================================================================== [64bit-compiler-analysis] RE: vpr analysis Syyyy Kyyyyy syyyk at yyy.com Thu Jun 19 14:27:16 CDT 2003 Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- Skipped content of type multipart/alternative -------------------------------------------------------------------------------- Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- More information about the 64bit-compiler-analysis mailing list ============================================================================== As you can see, the actual content of the multipart/alternative portion [text/plain and text/html] were completely stripped out instead of being shown a plain text. ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-22 13:26 Message: Logged In: YES user_id=50125 This is causing me real problems! Is there any known workarounds? If I can't fix this I might have to use a different package as presently all my archives are useless! ---------------------------------------------------------------------- Comment By: Pug Bainter (phelim_gervase) Date: 2003-06-24 17:01 Message: Logged In: YES user_id=484284 This appears to be within: def process(mlist, msg, msgdata=None): at around line 276, but I saw no way of making it recurse for multipart/[mixed|alternative] sub-MIME parts. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 From noreply at sourceforge.net Mon Sep 22 09:34:41 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Sep 22 09:34:51 2003 Subject: [ mailman-Bugs-759841 ] Multipart/mixed issues in archives Message-ID: Bugs item #759841, was opened at 2003-06-24 14:22 Message generated for change (Comment added) made by mrjc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Multipart/mixed issues in archives Initial Comment: We are having problems with mailing lists that are not being properly stripped down to text content in the archives. When there is multipart/mixed, it doesn't pull the multipart/alternative sections into their appropriate text portions. For example, from content such as the following: ============================================================================== >From ... [...] Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=------------InterScan_NT_MIME_Boundary [...] This is a multi-part message in MIME format. --------------InterScan_NT_MIME_Boundary Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C336A1.2C7564BC" Content-Transfer-Encoding: 7bit ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Kevin has a pending checkin that addresses the minss/maxss issue. =20 [...] ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message= [...] ============================================================================== I only get the following: ============================================================================== [64bit-compiler-analysis] RE: vpr analysis Syyyy Kyyyyy syyyk at yyy.com Thu Jun 19 14:27:16 CDT 2003 Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- Skipped content of type multipart/alternative -------------------------------------------------------------------------------- Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- More information about the 64bit-compiler-analysis mailing list ============================================================================== As you can see, the actual content of the multipart/alternative portion [text/plain and text/html] were completely stripped out instead of being shown a plain text. ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-22 13:34 Message: Logged In: YES user_id=50125 Additionally I think it is appropriate to up the priority on this bug as it causes key functionality to fail. ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-22 13:26 Message: Logged In: YES user_id=50125 This is causing me real problems! Is there any known workarounds? If I can't fix this I might have to use a different package as presently all my archives are useless! ---------------------------------------------------------------------- Comment By: Pug Bainter (phelim_gervase) Date: 2003-06-24 17:01 Message: Logged In: YES user_id=484284 This appears to be within: def process(mlist, msg, msgdata=None): at around line 276, but I saw no way of making it recurse for multipart/[mixed|alternative] sub-MIME parts. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 From noreply at sourceforge.net Mon Sep 22 11:45:12 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Sep 22 11:45:16 2003 Subject: [ mailman-Patches-810675 ] Add 'Discard all messages marked "Defer"' option to admindb Message-ID: Patches item #810675, was opened at 2003-09-22 08:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=810675&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Eddie Kohler (xexd) Assigned to: Nobody/Anonymous (nobody) Summary: Add 'Discard all messages marked "Defer"' option to admindb Initial Comment: Hi, This slight change to the admindb page is useful for filtering spam from a mailing list. Instead of individually clicking "Discard" on every spam message (timeconsuming), you go through the messages, mark only the Accepts and Rejects, then check the 'Discard all messages marked "Defer"' box. This speeds up my mailing list processing significantly. Eddie ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=810675&group_id=103 From noreply at sourceforge.net Tue Sep 23 15:23:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 23 15:23:56 2003 Subject: [ mailman-Bugs-811343 ] url parse (probably) cannot handle port number Message-ID: Bugs item #811343, was opened at 2003-09-23 19:23 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=811343&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael W. Cocke (mcocke) Assigned to: Nobody/Anonymous (nobody) Summary: url parse (probably) cannot handle port number Initial Comment: If you use a port number on the url (example www2.catherders.com:3800, such as dyndns webhob requires) the web interface breaks/fails to function in many places. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=811343&group_id=103 From noreply at sourceforge.net Fri Sep 26 21:26:54 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Sep 26 21:27:18 2003 Subject: [ mailman-Bugs-759841 ] Multipart/mixed issues in archives Message-ID: Bugs item #759841, was opened at 2003-06-24 07:22 Message generated for change (Comment added) made by q7joey You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Multipart/mixed issues in archives Initial Comment: We are having problems with mailing lists that are not being properly stripped down to text content in the archives. When there is multipart/mixed, it doesn't pull the multipart/alternative sections into their appropriate text portions. For example, from content such as the following: ============================================================================== >From ... [...] Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=------------InterScan_NT_MIME_Boundary [...] This is a multi-part message in MIME format. --------------InterScan_NT_MIME_Boundary Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C336A1.2C7564BC" Content-Transfer-Encoding: 7bit ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Kevin has a pending checkin that addresses the minss/maxss issue. =20 [...] ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message= [...] ============================================================================== I only get the following: ============================================================================== [64bit-compiler-analysis] RE: vpr analysis Syyyy Kyyyyy syyyk at yyy.com Thu Jun 19 14:27:16 CDT 2003 Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- Skipped content of type multipart/alternative -------------------------------------------------------------------------------- Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- More information about the 64bit-compiler-analysis mailing list ============================================================================== As you can see, the actual content of the multipart/alternative portion [text/plain and text/html] were completely stripped out instead of being shown a plain text. ---------------------------------------------------------------------- Comment By: Joe Pruett (q7joey) Date: 2003-09-26 18:26 Message: Logged In: YES user_id=559223 i agree that this should be a high priority issue. a simple message with just multipart/alternative will show up in the archive ok, but if there is any other kind of attachment, then the entire multipart section is skipped and you just get a link for the extra attachment for download/view ability. i haven't started to look at the code (and i'm not a python/mailman person), but i'll report anything i can find. ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-22 06:34 Message: Logged In: YES user_id=50125 Additionally I think it is appropriate to up the priority on this bug as it causes key functionality to fail. ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-22 06:26 Message: Logged In: YES user_id=50125 This is causing me real problems! Is there any known workarounds? If I can't fix this I might have to use a different package as presently all my archives are useless! ---------------------------------------------------------------------- Comment By: Pug Bainter (phelim_gervase) Date: 2003-06-24 10:01 Message: Logged In: YES user_id=484284 This appears to be within: def process(mlist, msg, msgdata=None): at around line 276, but I saw no way of making it recurse for multipart/[mixed|alternative] sub-MIME parts. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 From noreply at sourceforge.net Sat Sep 27 03:23:29 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Sep 27 03:23:41 2003 Subject: [ mailman-Bugs-759841 ] Multipart/mixed issues in archives Message-ID: Bugs item #759841, was opened at 2003-06-24 14:22 Message generated for change (Comment added) made by mrjc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Multipart/mixed issues in archives Initial Comment: We are having problems with mailing lists that are not being properly stripped down to text content in the archives. When there is multipart/mixed, it doesn't pull the multipart/alternative sections into their appropriate text portions. For example, from content such as the following: ============================================================================== >From ... [...] Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=------------InterScan_NT_MIME_Boundary [...] This is a multi-part message in MIME format. --------------InterScan_NT_MIME_Boundary Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C336A1.2C7564BC" Content-Transfer-Encoding: 7bit ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Kevin has a pending checkin that addresses the minss/maxss issue. =20 [...] ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message= [...] ============================================================================== I only get the following: ============================================================================== [64bit-compiler-analysis] RE: vpr analysis Syyyy Kyyyyy syyyk at yyy.com Thu Jun 19 14:27:16 CDT 2003 Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- Skipped content of type multipart/alternative -------------------------------------------------------------------------------- Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- More information about the 64bit-compiler-analysis mailing list ============================================================================== As you can see, the actual content of the multipart/alternative portion [text/plain and text/html] were completely stripped out instead of being shown a plain text. ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-27 07:23 Message: Logged In: YES user_id=50125 This fails for many of my users as they habitually attach a photo of themselves in their signatures. They are incredulous at the idea that mailman can't handle it. Thanks ---------------------------------------------------------------------- Comment By: Joe Pruett (q7joey) Date: 2003-09-27 01:26 Message: Logged In: YES user_id=559223 i agree that this should be a high priority issue. a simple message with just multipart/alternative will show up in the archive ok, but if there is any other kind of attachment, then the entire multipart section is skipped and you just get a link for the extra attachment for download/view ability. i haven't started to look at the code (and i'm not a python/mailman person), but i'll report anything i can find. ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-22 13:34 Message: Logged In: YES user_id=50125 Additionally I think it is appropriate to up the priority on this bug as it causes key functionality to fail. ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-22 13:26 Message: Logged In: YES user_id=50125 This is causing me real problems! Is there any known workarounds? If I can't fix this I might have to use a different package as presently all my archives are useless! ---------------------------------------------------------------------- Comment By: Pug Bainter (phelim_gervase) Date: 2003-06-24 17:01 Message: Logged In: YES user_id=484284 This appears to be within: def process(mlist, msg, msgdata=None): at around line 276, but I saw no way of making it recurse for multipart/[mixed|alternative] sub-MIME parts. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 From noreply at sourceforge.net Sat Sep 27 08:52:11 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Sep 27 08:52:24 2003 Subject: [ mailman-Feature Requests-813527 ] Export list members Message-ID: Feature Requests item #813527, was opened at 2003-09-27 08:52 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=813527&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Gilles Beauregard (balour) Assigned to: Nobody/Anonymous (nobody) Summary: Export list members Initial Comment: Membership list (list members) must be avalaible to list owner for backup purpose. At the moment, they to have an eassy access to their members list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=813527&group_id=103 From noreply at sourceforge.net Sat Sep 27 12:48:10 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Sep 27 12:48:30 2003 Subject: [ mailman-Bugs-759841 ] Multipart/mixed issues in archives Message-ID: Bugs item #759841, was opened at 2003-06-24 07:22 Message generated for change (Comment added) made by q7joey You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Multipart/mixed issues in archives Initial Comment: We are having problems with mailing lists that are not being properly stripped down to text content in the archives. When there is multipart/mixed, it doesn't pull the multipart/alternative sections into their appropriate text portions. For example, from content such as the following: ============================================================================== >From ... [...] Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=------------InterScan_NT_MIME_Boundary [...] This is a multi-part message in MIME format. --------------InterScan_NT_MIME_Boundary Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C336A1.2C7564BC" Content-Transfer-Encoding: 7bit ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Kevin has a pending checkin that addresses the minss/maxss issue. =20 [...] ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message= [...] ============================================================================== I only get the following: ============================================================================== [64bit-compiler-analysis] RE: vpr analysis Syyyy Kyyyyy syyyk at yyy.com Thu Jun 19 14:27:16 CDT 2003 Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- Skipped content of type multipart/alternative -------------------------------------------------------------------------------- Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- More information about the 64bit-compiler-analysis mailing list ============================================================================== As you can see, the actual content of the multipart/alternative portion [text/plain and text/html] were completely stripped out instead of being shown a plain text. ---------------------------------------------------------------------- Comment By: Joe Pruett (q7joey) Date: 2003-09-27 09:48 Message: Logged In: YES user_id=559223 i have a few line patch that seems to make it do what is expected. i can't see how to attach via sourceforge yet, so i'll paste it here: --- /usr/local/src/mailman-2.1.2/Mailman/Handlers/Scrubber.py Fri Feb 7 23:13:50 2003 +++ ./Scrubber.py Sat Sep 27 08:58:46 2003 @@ -286,11 +286,13 @@ # BAW: Martin's original patch suggested we might want to try # generalizing to utf-8, and that's probably a good idea (eventually). text = [] - for part in msg.get_payload(): + for part in msg.walk(): + if part.get_main_type() == 'multipart': + continue # All parts should be scrubbed to text/plain by now. partctype = part.get_content_type() if partctype <> 'text/plain': - text.append(_('Skipped content of type %(partctype)s')) + text.append(_('Skipped content of type %(partctype)s\n')) continue try: t = part.get_payload(decode=1) ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-27 00:23 Message: Logged In: YES user_id=50125 This fails for many of my users as they habitually attach a photo of themselves in their signatures. They are incredulous at the idea that mailman can't handle it. Thanks ---------------------------------------------------------------------- Comment By: Joe Pruett (q7joey) Date: 2003-09-26 18:26 Message: Logged In: YES user_id=559223 i agree that this should be a high priority issue. a simple message with just multipart/alternative will show up in the archive ok, but if there is any other kind of attachment, then the entire multipart section is skipped and you just get a link for the extra attachment for download/view ability. i haven't started to look at the code (and i'm not a python/mailman person), but i'll report anything i can find. ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-22 06:34 Message: Logged In: YES user_id=50125 Additionally I think it is appropriate to up the priority on this bug as it causes key functionality to fail. ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-22 06:26 Message: Logged In: YES user_id=50125 This is causing me real problems! Is there any known workarounds? If I can't fix this I might have to use a different package as presently all my archives are useless! ---------------------------------------------------------------------- Comment By: Pug Bainter (phelim_gervase) Date: 2003-06-24 10:01 Message: Logged In: YES user_id=484284 This appears to be within: def process(mlist, msg, msgdata=None): at around line 276, but I saw no way of making it recurse for multipart/[mixed|alternative] sub-MIME parts. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 From noreply at sourceforge.net Sat Sep 27 17:53:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Sep 27 17:54:06 2003 Subject: [ mailman-Bugs-813760 ] digest default has no effect on mass subscribe Message-ID: Bugs item #813760, was opened at 2003-09-27 17:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=813760&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matt DeLuco (duke) Assigned to: Nobody/Anonymous (nobody) Summary: digest default has no effect on mass subscribe Initial Comment: When mass subscribing some ~245 members to a list, I wanted them all to receive digests by default. So under Digest Options, I set digest to be the default delivery mode for new users. Upon subscribing all the users (this happens entering email addresses by file or form), not one user was set to receive a digest. I had to go through all of them and manually set it (heh, there's probably an easier way, isn't there.) This is Mailman version 2.1.1, installed by hand (ie: no package system.) Linux 2.4.22, GCC 3.2.3, Python 2.2.3. Gentoo Linux distribution. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=813760&group_id=103 From noreply at sourceforge.net Sun Sep 28 21:21:35 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Sep 28 21:21:52 2003 Subject: [ mailman-Patches-601117 ] add sequencial number in subject prefix Message-ID: Patches item #601117, was opened at 2002-08-28 05:07 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add sequencial number in subject prefix Initial Comment: This patch for 'CookHeaders.py' add an ability to add a sequencial number in the subject prefix. You can define a subject prefix like: [listname %d] Then, the subject line of delivered mail becomes: Subject: [listname 123] Hoge hoge When someone replied this mail, mailman receives a messages with: Subject: Re: [listname 123] Hoge hoge Then, this patch removes [listname \d+] part and deliver it with: Subject: [listname 124] Re: Hoge hoge And next, another person replies with Subject: Re: [listname 124] Re: Hoge hoge Then, (magically!) you get: Subject: [listname 125] Re: Hoge hoge Not with Re: Re: Hoge hoge. Looks like complicated but this patch has been working well with Japanese-enhanced Mailman for more than a year. Without %d, this patch works like current version, I believe. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-09-29 01:21 Message: Logged In: YES user_id=67709 Now the patch includes instruction in General admin page. (in detail part). In source dir you should type: patch -p0 < /path/to/seqnum.patch ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-05-18 02:01 Message: Logged In: YES user_id=67709 Here is update of my patch for 2.1.2 ---------------------------------------------------------------------- Comment By: Mitchell Marks (jojoba2) Date: 2003-05-17 17:42 Message: Logged In: YES user_id=718482 Is there a version vor MM 2.1.2? I'm trying the older one but doesn't seem to work. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-27 05:33 Message: Logged In: YES user_id=67709 sorry for daily update but there was an error in i18n handling of '(no subject)' ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-26 01:25 Message: Logged In: YES user_id=67709 update of patch for 2.1.1 if the subject is all ascii, then cat the prefix and subject before it is instantiated. Hope to solve prefix only subject 1st line. Note: with this patch without $d, Re: [prefix] is now mungled to [prefix] Re:. This is useful if someone post new issue as follow up to old subject like; New subject bah bah was Re: [prefix] foo ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-14 11:33 Message: Logged In: YES user_id=67709 Hi, I am pleased you like this patch. Here is my current version attached. ---------------------------------------------------------------------- Comment By: Fabio Rossetti (fabiorossetti) Date: 2003-02-14 10:02 Message: Logged In: YES user_id=693899 If you need a quick fix to make the patch work with 2.1.1 here's my take (it's the diff file adapted to work with 2.1.1 CookHeaders.py) 17a18 > (sequence version) 221c222,223 < prefix = mlist.subject_prefix --- > prefix = mlist.subject_prefix.strip(); > if not prefix: return 237,243c239,250 < if prefix and subject: < pattern = re.escape(prefix.strip()) < for decodedsubj, charset in headerbits: < if re.search(pattern, decodedsubj, re.IGNORECASE): < # The subject's already got the prefix, so don't change it < return < del msg['subject'] --- > headerstring = '' > fws = '' > cset = None > for (s, c) in headerbits: > headerstring += fws + s > if c == None or c == 'us-ascii': > fws = ' ' > cset = Utils.GetCharSet(mlist.preferred_language) > else: > fws = '' > cset = c > # Note: searching prefix in subject is REMOVED. (seq version) 245a253,275 > else: > subject = headerstring > # If the subject_prefix contains '%d', it is replaced with the > # mailing list sequential number. Also, if the prefix is closed with > # [],(), or {}, the prefix in the responding post subject will be cared. > # sequential number format allows '%05d' like pattern. > p = re.compile('%\d*d') > if p.search(prefix,1): > # prefix have number, so we should search prefix w/number > # in subject. > prefix_pattern = p.sub(r'\s*\d+\s*', prefix) > else: > prefix_pattern = prefix > prefix_pattern = re.sub('([\[\(\{])', '\\\g<1>', prefix_pattern) > subject = re.sub(prefix_pattern, '', subject) > subject = re.compile('(RE:\s*)+', re.I).sub('Re: ', subject, 1) > # and substitute %d in prefix with post_id > try: > prefix = prefix % mlist.post_id > except: > pass > # Note that trailing space was stripped in seq version (TK) > prefix += ' ' 248,262c278,288 < for s, c in headerbits: < # Once again, convert the string to unicode. < if c is None: < c = Charset('iso-8859-1') < if not isinstance(c, Charset): < c = Charset(c) < if not _isunicode(s): < codec = c.input_codec or 'ascii' < try: < s = unicode(s, codec, 'replace') < except LookupError: < # Unknown codec, is this default reasonable? < s = unicode(s, Utils.GetCharSet (mlist.preferred_language), < 'replace') < h.append(s, c) --- > # in seq version, subject header is already concatnated > if not _isunicode(subject): > try: > subject = unicode(subject, cset, 'replace') > except LookupError: > # unknown codec > cset = Utils.GetCharSet(mlist.preferred_language) > subject = unicode(subject, cset, 'replace') > subject = subject.encode(cset) > h.append(subject, cset) > del msg['subject'] ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-12-20 04:31 Message: Logged In: YES user_id=67709 update for 2.1b6+ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:59 Message: Logged In: YES user_id=67709 I have uploaded the patch with the same name as the old one. Please download the upper one because it's newer. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:53 Message: Logged In: YES user_id=67709 Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 From noreply at sourceforge.net Tue Sep 30 01:57:48 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 30 01:57:52 2003 Subject: [ mailman-Feature Requests-814917 ] Log reason for bounce Message-ID: Feature Requests item #814917, was opened at 2003-09-29 22:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=814917&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mark Dadgar (mdadgar) Assigned to: Nobody/Anonymous (nobody) Summary: Log reason for bounce Initial Comment: When doing automated bounce management, it would be great if Mailman would log the reason for a bounce (even if it means logging the whole set of headers). Now that everyone and their brother is maintaining blacklists, it's tough to do debug delivery problems if you can't see the bounce messages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=814917&group_id=103 From noreply at sourceforge.net Tue Sep 30 13:42:25 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 30 13:42:29 2003 Subject: [ mailman-Bugs-815297 ] Breaking signatures in message/rfc822 attachement! Message-ID: Bugs item #815297, was opened at 2003-09-30 19:42 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: Breaking signatures in message/rfc822 attachement! Initial Comment: Mailman _must_ not touch MIME-parts which are nested more deeply in the mail. As tested with Mailman 2.1.2, header lines will be sometimes reformatted in message/rfc822 attachments which will break the OpenPGP signature (also conforming to the PGP/MIME standard) on that part. I'm attaching a simple email with on long header. Forward this as MIME part and sign it sending it through Mailman, the signature will be broken. This is an email security affecting bug, because if people start believing that a *BAD* signature does not mean much, because they get many broken by mailman, they will not react to a seriously manipulated email anymore! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_id=103 From noreply at sourceforge.net Tue Sep 30 13:46:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 30 13:47:04 2003 Subject: [ mailman-Bugs-815297 ] Breaking signatures in message/rfc822 attachement! Message-ID: Bugs item #815297, was opened at 2003-09-30 19:42 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: Breaking signatures in message/rfc822 attachement! Initial Comment: Mailman _must_ not touch MIME-parts which are nested more deeply in the mail. As tested with Mailman 2.1.2, header lines will be sometimes reformatted in message/rfc822 attachments which will break the OpenPGP signature (also conforming to the PGP/MIME standard) on that part. I'm attaching a simple email with on long header. Forward this as MIME part and sign it sending it through Mailman, the signature will be broken. This is an email security affecting bug, because if people start believing that a *BAD* signature does not mean much, because they get many broken by mailman, they will not react to a seriously manipulated email anymore! ---------------------------------------------------------------------- >Comment By: Bernhard Reiter (ber) Date: 2003-09-30 19:46 Message: Logged In: YES user_id=113859 Here is the email signed by myself and broken after delivery through mailman. Check the "To:" header line. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_id=103 From noreply at sourceforge.net Tue Sep 30 16:10:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 30 16:10:23 2003 Subject: [ mailman-Patches-444879 ] Archive indexer control to improve index Message-ID: Patches item #444879, was opened at 2001-07-26 18:01 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Archive indexer control to improve index Initial Comment: This patch is applicable to Mailman 2.0.6 release and supercedes ealier patches 401669 and 402422. This patch should improve the quality of search results returned by search engines such as htdig (http://www.htdig.org) where the seach engine's index builder responds to strings embedded in the html pages that are the subject of the indexing. The changes in this patch: 1. allow strings for enabling and disabling indexing to be defined in mm_cfg.py. 2. embeds those strings in the pages generated as the html version of a list's archive. By default nothing in the html changes. To get the desired effect, you must define ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in mm_cfg.py You probably want to run this patch as follows: cd patch -p1 < See also the associated patch for integrating the htdig search software with mailman's internal archiver ouput. ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:10 Message: Logged In: YES user_id=75166 indexing-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:37 Message: Logged In: YES user_id=75166 indexing-2.1.2-0.1.patch.gz no longer needs patch #661138 to be applied as that patch was incorporated in the MM 2.1.2 release ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:34 Message: Logged In: YES user_id=75166 indexing-2.1.2-0.1.patch.gz is revised for MM 2.1.2 compatibility. Before applying thisversion of the patch you must also apply Bug fix patch #728836 to the source distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 15:49 Message: Logged In: YES user_id=75166 indexing-2.1.1-0.1.patch.gz introduces no functional change but applies without offset warnings to MM 2.1.1 Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:05 Message: Logged In: YES user_id=75166 indexing-2.1-0.1.patch is a revised version of the patch that is compatible with MM 2.1. Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:55 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:53 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:52 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 10:22 Message: Logged In: YES user_id=75166 indexing-2.1b5-0.1.patch is a revised version of the patch that is compatible with MM 2.1b5 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:40 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:39 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:46 Message: Logged In: YES user_id=75166 indexing-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:32 Message: Logged In: YES user_id=75166 An additional file, README.NOINDEXtags is added to indexing-2.0.13-0.3.patch version that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:19 Message: Logged In: YES user_id=75166 An error when building the indexing-2.1b2-0.1.patch meant that copies of the originals of two of the files modified by this version of the patch were added when the patch was run. indexing-2.1b2-0.1.patch removes this error. However, the original error is benign and can be corrected by deleting the extra files HyperArch.py.orig and Defaults.py.in.orig. An additional file, README.NOINDEXtags is added that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:19 Message: Logged In: YES user_id=12800 Another question: is there no standard (de-facto or otherwise) for generic markup that tells indexers not to index a particular section? IOW, for ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is there some generic value that would instruct most (all?) indexers to ignore that section? Or does it necessarily have to be indexer specific? I'm thinking of the situation where you might have ht://Dig installed locally, but your archives are still being spidered by external indexers. It would be good if something more generic could be added to Defaults.py.in ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:14 Message: Logged In: YES user_id=12800 Looking at the 2.1b2 patch, why does it try to create HyperArch.py.orig and Defaults.py.in.orig? Are those included in the patch by mistake? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:08 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:33 Message: Logged In: YES user_id=75166 indexing-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:23 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:11 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch should apply without problems to MM 2.0.12 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:50 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:53 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch should apply without problems to MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:43 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:14 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002. Corrects problem noted or 5 Mar 2002 by nobody ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-05 21:41 Message: Logged In: NO When applying this patch I get an error with Hunk 1 and Defaults.py is not updated. This happens with the a clean download of the latest cvs installation (5 Mar 2002). Any ideas what the problem is? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:53 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:48 Message: Logged In: YES user_id=75166 indexing-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:07 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:03 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.7 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 From noreply at sourceforge.net Tue Sep 30 16:14:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 30 16:14:46 2003 Subject: [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 Category: Unofficial 2.0 patch Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Integration of Mailman & htdig for archi Initial Comment: This patch is applicable to Mailman 2.0.6 release that has had search enhancement patch 444879 patch installed - if your Defaults.py has the ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in it then you've got that patch. It replaces earlier patches 401670 and 402423 and is mainly to correct some problems arising from fixes introduced into Mailman by bug fix releases since the 402423 patch. This patch integrates htdig with Mailman and provides: 1. per list search facility with a search form on the list's TOC page. 2. maintenance of privacy of private archives which requires the user to establish their credentials via the normal private archive access before any access via htdig is allowed. 3. a common base URL for both public and private archive access via htsearch results so that htdig indices are unaffected by changingan archive from private to public and vice versa. All access to archives via htdig is controlled by a new wrapped cgi- bin script called htdig.py. 4. a new cron activated script and extra crontab entry which runs htdig regularly to maintain the per list search indices. 5. automatic creation, deletion and maintenance of htdig configuration files and such. Beyond installing htdig and telling Mailman where it is via mm_cfg you do not have to do any other setup. Well not quite you do have to set up a single per installation symlink to allow htdig to find the automatically generated per list htdig configuration files. You probably want to run this patch as follows: cd patch -p1 < ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:14 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-06 17:47 Message: Logged In: YES user_id=75166 last comment should have read: htdig-2.1.2-0.4.patch.gz corrects an error in 2 scripts, mmsearch.py and remote_mmsearch, which caused an exception if list archives were being accessed via HTTPS and a search was performed. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-06 17:45 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.3.patch.gz corrects an error in 2 scripts, mmsearch.py and remote_mmsearch, which caused an exception if list archives were being accessed via HTTPS and a search was performed. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-01 19:00 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.3.patch.gz adds some minor performance improvement in template handling in MM 2.1.2 You should consider also applying this bug-fis patch: [ 730769 ] template access hierarchy is broken http://sourceforge.net/tracker/index.php? func=detail&aid=730769&group_id=103&atid=100103 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 15:44 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.2.patch.gz corrects error in file uploaded as htdig-2.1.2-0.1.patch.gz. Sorry for any inconvenience. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:46 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.1.patch.gz is a revised version for MM 2.1.2 compatibility. It also incoporates a previosuly unpublished change to overcome a potential problem with htdig excluced urls - see the INSTALL.htdig-mm file for more information ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-21 18:29 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.4.patch.gz fixes a problem with mmsearch handling multi-page search results from htsearch. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-21 17:54 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.3.patch.gz fixes a fault when mmsearch.py is rasing an excpetion because it has had a problem running htsearch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-20 14:10 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.2.patch.gz close a security exploit which allows leakage of information held in htdig's per-list search indexes to users not authorized to view private list archives. Read file INSTALL.htdig-mm installed by this patch for details and instructions for upgrading MM installations using earlier versions of this patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 15:50 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.1.patch.gz introduces no functional change but applies without offset warnings to MM 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-05 18:12 Message: Logged In: YES user_id=75166 It seems it is possible, if this patch is installed, for a list's htdig conf file and the list specific htdig index db files to be read directly through the web interface for list archives. Even if this patch isn't installed it seems a list's pipermail.pck file can also be read directly through the web interface for list archives. This seems to be true for accesses via /pipermail for public lists and via /mailman/private for private lists. The problem does not occur for htdig search results accessed via /mailman/htdig as the htdig.py script is more protective than private.py Broadly speaking the data affected is availble to a user in normal operation which is why I do not consider the issue to be a security breach as such. Adding the following RewriteRule to Apache's httpd.conf prevents the situation, assuming you got the RewriteEngine On: RewriteRule ^(/pipermail/.*)/(pipermail.pck|htdig/[^/]*)$ $1/index.html [F] RewriteRule ^(/mailman/private/.*)/(pipermail.pck|htdig/[^/]*)$ $1/index.htm l [F] You could, of course, substitute an R flag for the F flag on the RewriteRules and be more hacker friendly. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-22 14:20 Message: Logged In: YES user_id=75166 htdig-2.1-0.3.patch corrects yet another bug in htdig.py. Hope that all of them! Stops use of obsolete config variable DEFAULT_HOST in several files. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:18 Message: Logged In: YES user_id=75166 htdig-2.1-0.2.patch corrects a bug in htdig.py and deals with an adverse interaction between htdig.py and a bug in $prefix/scripts/driver (see #668685 for a patch to fix this). It also improves the content type and security handling by htdig.py for MM 2.1 version of patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:14 Message: Logged In: YES user_id=75166 Uploaded wrong file mailer-2.0.13-0.4.patch on last attempt. Should have been htdig-2.0.13-0.4.patch which improves the content type and security handling by htdig.py for MM 2.0.13 version of patch. Please ignore mailer-2.0.13-0.4.patch file ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:09 Message: Logged In: YES user_id=75166 mailer-2.0.13-0.4.patch improves the content type and security handling by htdig.py for MM 2.0.13 version of patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:07 Message: Logged In: YES user_id=75166 htdig-2.1-0.1.patch is a revised version of the patch that is compatible with MM 2.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:48 Message: Logged In: YES user_id=75166 htdig-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-04 10:53 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.3.patch corrects a minor typo in text appearing in the list TOC after the patch is applied. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 10:24 Message: Logged In: YES user_id=75166 htdig-2.1b5-0.1.patch is a revised version of the patch that is compatible with MM 2.1b5 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:43 Message: Logged In: YES user_id=75166 htdig-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-14 11:50 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.3.patch removes use of the file() function, used instead of the open() function, in three cron scripts added by the patch. Use of the file() function created an unnecessary dependency on Python 2.2 ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-12 16:51 Message: Logged In: YES user_id=624179 Got a workaround! The line referred to in the traceback: file(rundig_run_file, 'w').close() is used to create a 'rundig_last_run' file of lenght 0 bytes Creating this manually (or copying it) means the line isn't called and everything seems to work. Either file() is not a valid function call or my python is broken - I'm not literate enough in python to know the answer though! ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-06 14:18 Message: Logged In: YES user_id=624179 Just rebuilt MM as 2.1b3 with htdig. Upgraded lists which had htdig before work fine New lists give the obvious error: Unable to read word database file Did you run htmerge? Running the cronjob doesn't fix as it used to, message is: Output from command /usr/bin/python - S /usr/local/mailman/cron/nightly_htdig .. Traceback (most recent call last): File "/usr/local/mailman/cron/nightly_htdig", line 153, in ? main() File "/usr/local/mailman/cron/nightly_htdig", line 118, in main file(rundig_run_file, 'w').close() NameError: global name 'file' is not defined The archive/htdig folder only contains the xx.conf file, but no db.xx files If I copy in db.xx files from another list then the problem goes away (except I've now got an invalid set of references!) Is this my elementary error or is it more sinister?! ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-15 11:02 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.2.patch corrects a dumb syntax error in htdig- 2.1b3-0.1.patch which will typically show up as logged errors in the operation of the ArchRunner qrunner at line 721 of HyperArch.py ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:51 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 16:33 Message: Logged In: YES user_id=12800 I've sent Richard some comments off-line about this patch. Meta comments: the 2.0.x patches can't be officially supported, but I'm going to create an unofficial patches page off the wiki for where the 2.0 patches can be migrated. I think this patch set is too big for MM2.1, but if it's cleaned up as per my private message, let's re-evaluate it for MM2.2 (or 3.0). ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:11 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:35 Message: Logged In: YES user_id=75166 htdig-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:25 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 15:07 Message: Logged In: YES user_id=75166 Do not use htdig-2.0.12-0.1.patch there is an error in it. Use htdig-2.0.12-0.2.patch instead ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:10 Message: Logged In: YES user_id=75166 htdig-2.0.12-0.1.patch is a revised version of the patch that applies without complaint to MM 2.0.12. It also add a facility for adding site wide htdig configuration attributes to all list specific htdig configuration files. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:59 Message: Logged In: YES user_id=75166 htdig-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 This version removes an incompatibility with Python 2.2 which caused warning messages to be generated when any of the family cron/nightly_htdig scripts were run. Some guidance on file access permissions for some htdig database files needed by rundig have been added to installation notes. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:59 Message: Logged In: YES user_id=75166 htdig-2.0.10-0.1.patch is a revised version of the patch that is compatible with MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:46 Message: Logged In: YES user_id=75166 htdig-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:22 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002 Known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:56 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:58 Message: Logged In: YES user_id=75166 htdig-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 17:33 Message: Logged In: YES user_id=75166 The htdig-2.0.8-0.1.patch version of the patch resolves a problem that can arise with htdig indexing if the web_page_url for a list uses other than the http addressing (some folks want to use https). While specified as for MM 2.0.8 the revised patch should work OK with 2.0.7, 2.0.6 and probably back as far as 2.0.3. If you do not have the requirement for using other than http addressing in you lists web_page_urls it probably isn't worth the trouble of upgrading to this patch level. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:08 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:00 Message: Logged In: YES user_id=75166 This patch should also apply without problems to Mm 2.0.7 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-09 11:54 Message: Logged In: YES user_id=75166 The htdig-2.0.6-03.patch version of the patch makes some previously hard-coded things configurable and enhances the capability to run the htdig searches and indexing on a different machine to the one delivering Mailman and Mailman's web UI. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 From noreply at sourceforge.net Tue Sep 30 16:33:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 30 16:33:09 2003 Subject: [ mailman-Patches-644810 ] Sendmail mailer in Python Message-ID: Patches item #644810, was opened at 2002-11-27 16:27 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Sendmail mailer in Python Initial Comment: This patch provide a Python implementation (with C wrapper) of a Sendmail mailer, if Sendmail is your MTA of choice, which removes the necessity of maintining an aliases database on your Mailman server. All subject to a bunch of conditions most prominent of which is that the server has to be pretty much dedicated to MM. This patch draws on an original contribution by David Champion which is included in the contrib directory of the Mailman 2.1b distribution as mm-handler. See the README.SENDMAIL.mailer installed by this patch for differences between this and David's Perl original and more information of what you are getting into if you use this patch. Versions of the patch for MM 2.0.13 and MM 2.1b5 are available. This patch requires patch 644797 to be installed before it. In the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:33 Message: Logged In: YES user_id=75166 mailer-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:31 Message: Logged In: YES user_id=75166 mailer-2.1.2-0.1.patch.gz removes support for MM 2.0.13 mail aliases from the mailer and is MM 2.1.2 compatible ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:50 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch is also applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-16 15:30 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch and mailer-2.0.13-0.4.patch have VERP handling added and a new feature to rejct delivery of mail to existing lists by adding the lists names to a SUSPENDED_LISTS dictionary variable defined in mm_cfg.py. This is equivalent to deleting list aliases from the aliases file, while leaving the list itself in place, in a conventional sendmail configuration. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-03 18:19 Message: Logged In: YES user_id=75166 the mm_mailer script in mailer-2.1-0.2.patch now handles VERP'ed return addresses in bounced mail which I missed in the original implementation ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:34 Message: Logged In: YES user_id=75166 mailer-2.1-0.1.patch is a revision of the patch for MM 2.1 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 12:16 Message: Logged In: YES user_id=75166 mailer-2.1b6-0.1.patch is MM 2.1b6 compatible. It also folds the case of listname and servername for compaiblity with MMs naive belief that listnames are case all lower case. case "(Email addresses are not case sensitive, but they are sensitive to almost everything else :-)" ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-03 17:37 Message: Logged In: YES user_id=75166 Fix for permissions related exceptions being generated by the subprocess spawned by mm_mailer script ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-03 17:36 Message: Logged In: YES user_id=75166 Fix for permissions related exceptions being generated by the subprocess spawned by mm_mailer script. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 16:29 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 From noreply at sourceforge.net Tue Sep 30 16:39:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 30 16:39:47 2003 Subject: [ mailman-Patches-644797 ] Revised mailer exit status Message-ID: Patches item #644797, was opened at 2002-11-27 15:56 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Revised mailer exit status Initial Comment: This patch modifies the Python scripts in $prefix/scripts/ that are used by the MTA to deliver incoming mail to Mailman. The exit statuses now returned are drawn from the mail related values defined in /usr/include/sysexits.h This allows the MTA to return more meaningful responses to the sender when rejecting mail. It also allows a more sympathetic treatment of mail in the event that the Python script suffers an unexpected exception when handling incoming email. Such exceptions are now logged to MM's $prefix/logs/erro in all but the most extreme error cases and the internal information about the Python exception is not passed into the response to the sender. There are two patch versions; one for MM 2.0.13 and the other for MM 2.1b5 in the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:39 Message: Logged In: YES user_id=75166 exitstatus-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:40 Message: Logged In: YES user_id=75166 exitstatus-2.1.2-0.1.patch is a revision of the patch for MM 2.1.2 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:42 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is alos applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:30 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is a revision of the patch for MM 2.1 compatibility ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-24 03:29 Message: Logged In: YES user_id=12800 Sorry Richard, I have to defer this one. It's too much for me to think about for MM2.1. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:58 Message: Logged In: YES user_id=75166 exitstatus-2.1b6-0.1.patch is a revision of the patch for MM 2.1b6 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 15:58 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 From noreply at sourceforge.net Tue Sep 30 16:43:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 30 16:43:28 2003 Subject: [ mailman-Patches-760567 ] moderation request message content Message-ID: Patches item #760567, was opened at 2003-06-25 15:25 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=760567&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: moderation request message content Initial Comment: This patch makes per-list configurable the inclusion of the body of messages that require moderation in the request messages sent to list moderators. This patch has similar objectives to those of patch #593674 but is a simpler implementation. This adds one list attribute, which can be set or unset via the web admin GUI, and which controls whether the moderated message body is included in the moderator request. Apply the attached patch file with the MM build directory as the current working directory using the command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:43 Message: Logged In: YES user_id=75166 modinc-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-25 17:21 Message: Logged In: YES user_id=75166 Missed one changed file from initial patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=760567&group_id=103 From noreply at sourceforge.net Tue Sep 30 16:45:39 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Sep 30 16:45:45 2003 Subject: [ mailman-Bugs-777444 ] mailmanctl doesn't setgroups when run as root Message-ID: Bugs item #777444, was opened at 2003-07-25 10:02 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=777444&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: mailmanctl doesn't setgroups when run as root Initial Comment: When mailmanctl is executed as root the checkprivs function performs setgid and setuid to reduce the process privileges. But mailmanctl fails to set the supplemental groups of the process to those of the setuid'ed user, effectively leaving the processes with the same group privileges as root and, potentially, without the group privileges of the setuid'ed user. This patch uses os.setgroups() to fix that. Problem definition and solution by Jonas Meurer. I'm just filing the bug fix for him. Apply the patch from within the Mailman build directory with: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:45 Message: Logged In: YES user_id=75166 grpsec-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=777444&group_id=103