Mailman 3 October 2006 - Mailman-coders

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net Aug. 19, 2022

Aug. 19, 2022

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_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 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-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_i…

2 1

[ mailman-Patches-1587651 ] Roster should list private members to admins
by SourceForge.net Oct. 31, 2006

Oct. 31, 2006

Patches item #1587651, was opened at 2006-10-30 21:59 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=1587651&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web UI Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Eric Price (eprice) Assigned to: Nobody/Anonymous (nobody) Summary: Roster should list private members to admins Initial Comment: The roster page omits members of a list who choose to remain concealed, even when the viewer has admin authorization. This means admins cannot get a single list of all list members from the web interface. The roster should instead list hidden members to people who logged in with the admin password. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1587651&group_…

1 0

[ mailman-Feature Requests-1586072 ] Spam Filter ACCEPT rule not valid
by SourceForge.net Oct. 28, 2006

Oct. 28, 2006

Feature Requests item #1586072, was opened at 2006-10-27 17:57 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1586072&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: None >Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mez (ubuntumez) Assigned to: Nobody/Anonymous (nobody) Summary: Spam Filter ACCEPT rule not valid Initial Comment: In my setup, I wish to have a moderated member list, however, I also wish this list to be able to recieve email regarding bugs from Launchpad (http://launchpad.net) The way that Launchpad sends the bugs out is to use the users email address reporting the bug in the "From:" header, but uses special headers to identify the email as coming from Launchpad Obviously, I could just accept each email as it comes in, and add each sender to the approved list, however, I would rather that Mailman accept emails if their headers match the Spam Filters (and the spam filter is set to accept) At the moment, it matches the spam header, but doesnt do anything to the message - the default action for accept is "do nothing here" - which then passes the message down the chain, to be intercepted by another part of the code that holds the message. Changing the pipeline won't make any difference here, as the way that mailman works with this is that it doesnt set anything to say "approve this" it just says "we're not going to do anything with this here" - changging the pipeline would just catch the "Non member posting" at a different point. I'd like the Spam filters when set to Accept to actually ACCEPT the email, rather than just pass it on to other Handlers. I'm trying to hack on this myself, and if I can will post a patch, but my trials have been fruitless so far ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-10-27 18:20 Message: Logged In: YES user_id=1123998 Spam filters are working as designed. Therefore, I am moving this to feature requests because that's what it is. For your implemention efforts, if you modify the end of the process() function in SPAMDetect.py to read if action == mm_cfg.ACCEPT: msgdata['approved'] = 1 return That will make an ACCEPT rule match bypass all other holds except emergency moderation. If you want to bypass emergency moderation too, add also msgdata['adminapproved'] = 1 See Mailman/Handlers/Approve.py Note however that it is probably better to use a custom handler for this as you then won't have to maintain a patch across updates. See http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.067.htp ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1586072&group_…

1 0

[ mailman-Bugs-1586072 ] Spam Filter ACCEPT rule not valid
by SourceForge.net Oct. 28, 2006

Oct. 28, 2006

Bugs item #1586072, was opened at 2006-10-28 00:57 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=1586072&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mez (ubuntumez) Assigned to: Nobody/Anonymous (nobody) Summary: Spam Filter ACCEPT rule not valid Initial Comment: In my setup, I wish to have a moderated member list, however, I also wish this list to be able to recieve email regarding bugs from Launchpad (http://launchpad.net) The way that Launchpad sends the bugs out is to use the users email address reporting the bug in the "From:" header, but uses special headers to identify the email as coming from Launchpad Obviously, I could just accept each email as it comes in, and add each sender to the approved list, however, I would rather that Mailman accept emails if their headers match the Spam Filters (and the spam filter is set to accept) At the moment, it matches the spam header, but doesnt do anything to the message - the default action for accept is "do nothing here" - which then passes the message down the chain, to be intercepted by another part of the code that holds the message. Changing the pipeline won't make any difference here, as the way that mailman works with this is that it doesnt set anything to say "approve this" it just says "we're not going to do anything with this here" - changging the pipeline would just catch the "Non member posting" at a different point. I'd like the Spam filters when set to Accept to actually ACCEPT the email, rather than just pass it on to other Handlers. I'm trying to hack on this myself, and if I can will post a patch, but my trials have been fruitless so far ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1586072&group_…

1 0

[ mailman-Patches-1578756 ] Handle unexpected HTTP method gracefully
by SourceForge.net Oct. 22, 2006

Oct. 22, 2006

Patches item #1578756, was opened at 2006-10-17 08:45 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578756&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Thijs Kinkhorst (kink) Assigned to: Nobody/Anonymous (nobody) Summary: Handle unexpected HTTP method gracefully Initial Comment: Hi! When Mailman is confronted with an unexpected HTTP method type (e.g. PROPFIND instead of GET/HEAD/POST), it crashes. The attached patch fixes that more gracefully by throwing the appropriate HTTP error. Thanks for considering. Thijs ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2006-10-22 17:22 Message: Logged In: YES user_id=75166 There are two issues: 1. Having Mailman's CGI scripts defend themselves against inappropriate application of WebDAV methods is good and would probably be required for RFC compliance if CGI had an RFC. The fact the fix only requires change to a single driver script to defend multiple functional scripts is a tribute to the original design. 2. Inappropriate configuration of Apache servers with respect to WebDAV is wrong. a. Many if not most legacy CGI scripts will not have been programmed to defend themselves against WebDAV methods. Fixing them on an existing system is time consuming and error prone. Fixing Apache config is easier and more reliable. b. Mailman's pipermail archives and much other served resource should also not be subject to WebDAV methods Only getting the Apache config right can deal with this. Fixing CGI scripts is good. Getting the Apache configuration correct is more important. ---------------------------------------------------------------------- Comment By: Thijs Kinkhorst (kink) Date: 2006-10-22 14:34 Message: Logged In: YES user_id=285765 Yes, that's true. However, in any case mailman should output a sensible error, I think? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2006-10-22 07:35 Message: Logged In: YES user_id=75166 There is an alternative to fixing cgi scripts to cope with inappropriate WebDAV methods being applied to them, which works regardless of whether they are Mailman cgi scripts or not. Configure Apache not to apply WebDAV methods to inappropriate resources by the use of Apache directives such as DAV Off and LimitExcept GET POST. See: http://httpd.apache.org/docs/2.0/mod/mod_dav.html and http://httpd.apache.org/docs/2.0/mod/core.html#limitexcept ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578756&group_…

1 0

[ mailman-Patches-1578756 ] Handle unexpected HTTP method gracefully
by SourceForge.net Oct. 22, 2006

Oct. 22, 2006

Patches item #1578756, was opened at 2006-10-17 10:45 Message generated for change (Comment added) made by kink You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578756&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Thijs Kinkhorst (kink) Assigned to: Nobody/Anonymous (nobody) Summary: Handle unexpected HTTP method gracefully Initial Comment: Hi! When Mailman is confronted with an unexpected HTTP method type (e.g. PROPFIND instead of GET/HEAD/POST), it crashes. The attached patch fixes that more gracefully by throwing the appropriate HTTP error. Thanks for considering. Thijs ---------------------------------------------------------------------- >Comment By: Thijs Kinkhorst (kink) Date: 2006-10-22 16:34 Message: Logged In: YES user_id=285765 Yes, that's true. However, in any case mailman should output a sensible error, I think? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2006-10-22 09:35 Message: Logged In: YES user_id=75166 There is an alternative to fixing cgi scripts to cope with inappropriate WebDAV methods being applied to them, which works regardless of whether they are Mailman cgi scripts or not. Configure Apache not to apply WebDAV methods to inappropriate resources by the use of Apache directives such as DAV Off and LimitExcept GET POST. See: http://httpd.apache.org/docs/2.0/mod/mod_dav.html and http://httpd.apache.org/docs/2.0/mod/core.html#limitexcept ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578756&group_…

1 0

[ mailman-Bugs-1578539 ] Problems with Microsoft Entourage
by SourceForge.net Oct. 22, 2006

Oct. 22, 2006

Bugs item #1578539, was opened at 2006-10-16 22:03 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) Status: Open >Resolution: Invalid Priority: 5 Submitted By: Duelago (stekardavid) Assigned to: Nobody/Anonymous (nobody) Summary: Problems with Microsoft Entourage Initial Comment: When posting to a Mailman list with Microsoft Entourage (all versions) the subject line gets crippled if you use characters like åäö. Smögåsbord ends up liks Sm ö rg å rdsbord. I don't have this problem if I post to other list servers like Majordomo or ezmlm. I guess we can blame Microsoft, but why don't I have a problem with other list solutions? ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-10-22 12:59 Message: Logged In: YES user_id=67709 As I stated on 2006-10-17, Microsoft Entourage's way of encoding violates the RFC-2047 in that encoding should be in 'encoded-WORD' and not in 'encoded-character'. i.e., =?iso-8859-1?q?sm=F6g=E5sbord?= ... OK =?iso-8859-1?b?c232Z+VzYm9yZA==?= ... OK sm=?iso-8859-1?q?=F6?=g=?iso-8859-1?q?=E5?=sbord ... NG sm=?ISO-8859-1?B?9g==?=g=?ISO-8859-1?B?5Q==?=sbord ... NG ---------------------------------------------------------------------- Comment By: Duelago (stekardavid) Date: 2006-10-22 10:03 Message: Logged In: YES user_id=1622511 I start with the Mailman headers --- User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Sun, 22 Oct 2006 11:45:57 +0200 From: xxxxx <xxxxx(a)gof.se> To: FK Cirrus Goteborgs skvallerlista <xxxxx(a)hoppafallskarm.nu>, swoop xxxxx <bofh-list-xxxxx(a)diegeekdie.com> Message-ID: <C1610A75.D7E4%xxxxx(a)gof.se> Thread-Topic: Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord Thread-Index: Acb1vt+QHlom82GyEduUbQAWy48iow== Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Subject: [CG] =?iso-8859-1?q?Sm_=F6_rg_=E5_sbord?= X-BeenThere: xxxxx(a)hoppafallskarm.nu X-Mailman-Version: 2.1.8rc1 Precedence: list Reply-To: FK Cirrus Goteborgs skvallerlista <xxxxx(a)hoppafallskarm.nu> List-Id: FK Cirrus Goteborgs skvallerlista <xxxxx.hoppafallskarm.nu> List-Unsubscribe: <http://list.hoppafallskarm.nu/mailman/listinfo/xxxxx>, <mailto:xxxxx-request@hoppafallskarm.nu?subject=unsubscribe> List-Post: <mailto:xxxxx@hoppafallskarm.nu> List-Help: <mailto:xxxxx-request@hoppafallskarm.nu?subject=help> List-Subscribe: <http://list.hoppafallskarm.nu/mailman/listinfo/xxxxx>, <mailto:xxxxx-request@hoppafallskarm.nu?subject=subscribe> Sender: xxxxx-bounces(a)hoppafallskarm.nu Errors-To: xxxxx-bounces(a)hoppafallskarm.nu Detta =E4r ett test. Ignorera --- And this are the headers when I send a mail directly from Entourage to a Gmail-adress (Works fine) X-Gmail-Received: 22aebdd20f2ca6fecf30a29de7d439cfb62ebeb3 Delivered-To: stekarxxxxx(a)gmail.com Received: by 10.78.174.12 with SMTP id w12cs532759hue; Sun, 22 Oct 2006 02:46:12 -0700 (PDT) Received: by 10.48.14.4 with SMTP id 4mr11975145nfn; Sun, 22 Oct 2006 02:46:12 -0700 (PDT) Return-Path: <xxxxx(a)gof.se> Received: from www.gof.se ([193.201.96.157]) by mx.google.com with ESMTP id p20si769907nfc.2006.10.22.02.46.11; Sun, 22 Oct 2006 02:46:12 -0700 (PDT) Received-SPF: neutral (google.com: 193.201.96.157 is neither permitted nor denied by best guess record for domain of xxxxx(a)gof.se) Received: from [83.215.47.240] (83-215-47-240.bruck.dyn.salzburg-online.at [83.215.47.240]) by www.gof.se (Postfix) with ESMTP id DB574BEF10; Sun, 22 Oct 2006 11:46:00 +0200 (CEST) User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Sun, 22 Oct 2006 11:45:57 +0200 Subject: Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord From: xxxxx <xxxxx(a)gof.se> To: FK Cirrus Goteborgs skvallerlista <xxxxx(a)hoppafallskarm.nu>, swoop xxxxx <bofh-list-xxxxx(a)diegeekdie.com> Message-ID: <C1610A75.D7E4%xxxxx(a)gof.se> Thread-Topic: Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord Thread-Index: Acb1vt+QHlom82GyEduUbQAWy48iow== Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Detta =E4r ett test. Ignorera --– Headers from ezmlm. Also works fine! Return-Path: <bofh-list-xxxxx-return-21-xxxxx=gof.se(a)diegeekdie.com> X-Spam-Checker-Version: SpamAssassin 3.1.6-gr0 (2006-10-03) on olga X-Spam-Level: X-Spam-Status: No, score=-2.2 required=4.0 tests=AWL,BAYES_00,SPF_PASS, SUBJECT_ENCODED_TWICE autolearn=no version=3.1.6-gr0 X-Original-To: xxxxx(a)gof.se Delivered-To: xxxxx(a)gof.se Received: from smtp.hogia.net (phillip.hogia.net [195.78.148.4]) by www.gof.se (Postfix) with SMTP id 41E8CBEF10 for <xxxxx(a)gof.se>; Sun, 22 Oct 2006 11:46:30 +0200 (CEST) Received: (qmail 14409 invoked by uid 509); 22 Oct 2006 11:46:12 +0200 Mailing-List: contact bofh-list-xxxxx-help(a)diegeekdie.com; run by ezmlm Precedence: bulk X-No-Archive: yes List-Post: <mailto:bofh-list-xxxxx@diegeekdie.com> List-Help: <mailto:bofh-list-xxxxx-help@diegeekdie.com> List-Unsubscribe: <mailto:bofh-list-xxxxx-unsubscribe@diegeekdie.com> List-Subscribe: <mailto:bofh-list-xxxxx-subscribe@diegeekdie.com> Delivered-To: mailing list bofh-list-xxxxx(a)diegeekdie.com Received: (qmail 14397 invoked by uid 64017); 22 Oct 2006 11:46:12 +0200 User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Sun, 22 Oct 2006 11:45:57 +0200 From: xxxxx <xxxxx(a)gof.se> To: FK Cirrus Goteborgs skvallerlista <listan(a)hoppafallskarm.nu>, swoop xxxxx <bofh-list-xxxxx(a)diegeekdie.com> Message-ID: <C1610A75.D7E4%xxxxx(a)gof.se> Thread-Topic: Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord Thread-Index: Acb1vt+QHlom82GyEduUbQAWy48iow== Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Subject: [xxxxx] Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord Detta =E4r ett test. Ignorera ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-10-17 00:45 Message: Logged In: YES user_id=67709 I tested with my Entourage which I didn't use so far. It gave: Sm=?ISO-8859-1?B?9g==?=g=?ISO-8859-1?B?5Q==?=sbord and ends up by processed by mailman email.Header module: Sm =?iso-8859-1?q?=F6?= g =?iso-8859-1?q?=E5?= sbord It looks like they break a statement of RFC-2047: Ordinary ASCII text and 'encoded-word's may appear together in the same header field. However, an 'encoded-word' that appears in a header field defined as '*text' MUST be separated from any adjacent 'encoded-word' or 'text' by 'linear-white-space'. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-10-16 23:38 Message: Logged In: YES user_id=1123998 I should say, I am unable to duplicate with Mailman 2.1.5 and Thunderbird. I don't have Entourage to test with. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-10-16 23:30 Message: Logged In: YES user_id=1123998 I am unable to duplicate the problem on Mailman 2.1.5. Can you post the raw Subject: header from both the message as sent to the list and as received from the list. I'm looking for things that look like Subject: =?UTF-8?B?U23DtmfDpXNib3Jk?= or Subject: =?ISO-8859-1?Q?Sm=F6g=E5sbord?= ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_…

1 0

[ mailman-Bugs-1578539 ] Problems with Microsoft Entourage
by SourceForge.net Oct. 22, 2006

Oct. 22, 2006

Bugs item #1578539, was opened at 2006-10-17 00:03 Message generated for change (Comment added) made by stekardavid You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Duelago (stekardavid) Assigned to: Nobody/Anonymous (nobody) Summary: Problems with Microsoft Entourage Initial Comment: When posting to a Mailman list with Microsoft Entourage (all versions) the subject line gets crippled if you use characters like åäö. Smögåsbord ends up liks Sm ö rg å rdsbord. I don't have this problem if I post to other list servers like Majordomo or ezmlm. I guess we can blame Microsoft, but why don't I have a problem with other list solutions? ---------------------------------------------------------------------- >Comment By: Duelago (stekardavid) Date: 2006-10-22 12:03 Message: Logged In: YES user_id=1622511 I start with the Mailman headers --- User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Sun, 22 Oct 2006 11:45:57 +0200 From: xxxxx <xxxxx(a)gof.se> To: FK Cirrus Goteborgs skvallerlista <xxxxx(a)hoppafallskarm.nu>, swoop xxxxx <bofh-list-xxxxx(a)diegeekdie.com> Message-ID: <C1610A75.D7E4%xxxxx(a)gof.se> Thread-Topic: Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord Thread-Index: Acb1vt+QHlom82GyEduUbQAWy48iow== Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Subject: [CG] =?iso-8859-1?q?Sm_=F6_rg_=E5_sbord?= X-BeenThere: xxxxx(a)hoppafallskarm.nu X-Mailman-Version: 2.1.8rc1 Precedence: list Reply-To: FK Cirrus Goteborgs skvallerlista <xxxxx(a)hoppafallskarm.nu> List-Id: FK Cirrus Goteborgs skvallerlista <xxxxx.hoppafallskarm.nu> List-Unsubscribe: <http://list.hoppafallskarm.nu/mailman/listinfo/xxxxx>, <mailto:xxxxx-request@hoppafallskarm.nu?subject=unsubscribe> List-Post: <mailto:xxxxx@hoppafallskarm.nu> List-Help: <mailto:xxxxx-request@hoppafallskarm.nu?subject=help> List-Subscribe: <http://list.hoppafallskarm.nu/mailman/listinfo/xxxxx>, <mailto:xxxxx-request@hoppafallskarm.nu?subject=subscribe> Sender: xxxxx-bounces(a)hoppafallskarm.nu Errors-To: xxxxx-bounces(a)hoppafallskarm.nu Detta =E4r ett test. Ignorera --- And this are the headers when I send a mail directly from Entourage to a Gmail-adress (Works fine) X-Gmail-Received: 22aebdd20f2ca6fecf30a29de7d439cfb62ebeb3 Delivered-To: stekarxxxxx(a)gmail.com Received: by 10.78.174.12 with SMTP id w12cs532759hue; Sun, 22 Oct 2006 02:46:12 -0700 (PDT) Received: by 10.48.14.4 with SMTP id 4mr11975145nfn; Sun, 22 Oct 2006 02:46:12 -0700 (PDT) Return-Path: <xxxxx(a)gof.se> Received: from www.gof.se ([193.201.96.157]) by mx.google.com with ESMTP id p20si769907nfc.2006.10.22.02.46.11; Sun, 22 Oct 2006 02:46:12 -0700 (PDT) Received-SPF: neutral (google.com: 193.201.96.157 is neither permitted nor denied by best guess record for domain of xxxxx(a)gof.se) Received: from [83.215.47.240] (83-215-47-240.bruck.dyn.salzburg-online.at [83.215.47.240]) by www.gof.se (Postfix) with ESMTP id DB574BEF10; Sun, 22 Oct 2006 11:46:00 +0200 (CEST) User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Sun, 22 Oct 2006 11:45:57 +0200 Subject: Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord From: xxxxx <xxxxx(a)gof.se> To: FK Cirrus Goteborgs skvallerlista <xxxxx(a)hoppafallskarm.nu>, swoop xxxxx <bofh-list-xxxxx(a)diegeekdie.com> Message-ID: <C1610A75.D7E4%xxxxx(a)gof.se> Thread-Topic: Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord Thread-Index: Acb1vt+QHlom82GyEduUbQAWy48iow== Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Detta =E4r ett test. Ignorera --– Headers from ezmlm. Also works fine! Return-Path: <bofh-list-xxxxx-return-21-xxxxx=gof.se(a)diegeekdie.com> X-Spam-Checker-Version: SpamAssassin 3.1.6-gr0 (2006-10-03) on olga X-Spam-Level: X-Spam-Status: No, score=-2.2 required=4.0 tests=AWL,BAYES_00,SPF_PASS, SUBJECT_ENCODED_TWICE autolearn=no version=3.1.6-gr0 X-Original-To: xxxxx(a)gof.se Delivered-To: xxxxx(a)gof.se Received: from smtp.hogia.net (phillip.hogia.net [195.78.148.4]) by www.gof.se (Postfix) with SMTP id 41E8CBEF10 for <xxxxx(a)gof.se>; Sun, 22 Oct 2006 11:46:30 +0200 (CEST) Received: (qmail 14409 invoked by uid 509); 22 Oct 2006 11:46:12 +0200 Mailing-List: contact bofh-list-xxxxx-help(a)diegeekdie.com; run by ezmlm Precedence: bulk X-No-Archive: yes List-Post: <mailto:bofh-list-xxxxx@diegeekdie.com> List-Help: <mailto:bofh-list-xxxxx-help@diegeekdie.com> List-Unsubscribe: <mailto:bofh-list-xxxxx-unsubscribe@diegeekdie.com> List-Subscribe: <mailto:bofh-list-xxxxx-subscribe@diegeekdie.com> Delivered-To: mailing list bofh-list-xxxxx(a)diegeekdie.com Received: (qmail 14397 invoked by uid 64017); 22 Oct 2006 11:46:12 +0200 User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Sun, 22 Oct 2006 11:45:57 +0200 From: xxxxx <xxxxx(a)gof.se> To: FK Cirrus Goteborgs skvallerlista <listan(a)hoppafallskarm.nu>, swoop xxxxx <bofh-list-xxxxx(a)diegeekdie.com> Message-ID: <C1610A75.D7E4%xxxxx(a)gof.se> Thread-Topic: Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord Thread-Index: Acb1vt+QHlom82GyEduUbQAWy48iow== Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Subject: [xxxxx] Sm=?ISO-8859-1?B?9g==?=rg=?ISO-8859-1?B?5Q==?=sbord Detta =E4r ett test. Ignorera ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2006-10-17 02:45 Message: Logged In: YES user_id=67709 I tested with my Entourage which I didn't use so far. It gave: Sm=?ISO-8859-1?B?9g==?=g=?ISO-8859-1?B?5Q==?=sbord and ends up by processed by mailman email.Header module: Sm =?iso-8859-1?q?=F6?= g =?iso-8859-1?q?=E5?= sbord It looks like they break a statement of RFC-2047: Ordinary ASCII text and 'encoded-word's may appear together in the same header field. However, an 'encoded-word' that appears in a header field defined as '*text' MUST be separated from any adjacent 'encoded-word' or 'text' by 'linear-white-space'. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-10-17 01:38 Message: Logged In: YES user_id=1123998 I should say, I am unable to duplicate with Mailman 2.1.5 and Thunderbird. I don't have Entourage to test with. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-10-17 01:30 Message: Logged In: YES user_id=1123998 I am unable to duplicate the problem on Mailman 2.1.5. Can you post the raw Subject: header from both the message as sent to the list and as received from the list. I'm looking for things that look like Subject: =?UTF-8?B?U23DtmfDpXNib3Jk?= or Subject: =?ISO-8859-1?Q?Sm=F6g=E5sbord?= ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1578539&group_…

1 0

[ mailman-Patches-1578756 ] Handle unexpected HTTP method gracefully
by SourceForge.net Oct. 22, 2006

Oct. 22, 2006

Patches item #1578756, was opened at 2006-10-17 08:45 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578756&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Thijs Kinkhorst (kink) Assigned to: Nobody/Anonymous (nobody) Summary: Handle unexpected HTTP method gracefully Initial Comment: Hi! When Mailman is confronted with an unexpected HTTP method type (e.g. PROPFIND instead of GET/HEAD/POST), it crashes. The attached patch fixes that more gracefully by throwing the appropriate HTTP error. Thanks for considering. Thijs ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2006-10-22 07:35 Message: Logged In: YES user_id=75166 There is an alternative to fixing cgi scripts to cope with inappropriate WebDAV methods being applied to them, which works regardless of whether they are Mailman cgi scripts or not. Configure Apache not to apply WebDAV methods to inappropriate resources by the use of Apache directives such as DAV Off and LimitExcept GET POST. See: http://httpd.apache.org/docs/2.0/mod/mod_dav.html and http://httpd.apache.org/docs/2.0/mod/core.html#limitexcept ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1578756&group_…

1 0

[ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration patch
by SourceForge.net Oct. 21, 2006

Oct. 21, 2006

Patches item #820723, was opened at 2003-10-09 18:19 Message generated for change (Comment added) made by mmokrejs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman/pipermail/MHonArc integration patch Initial Comment: This patch tightly integrates the MHonArc mail-to-HTML convertor with Mailman and its internal pipermail archiving code. The purpose of the patch is to produce a fusion of (hopefully) the best features of pipermail and MHonArc for handling Mailman mailing list archives. For more detail see patch content or http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2006-10-21 11:43 Message: Logged In: YES user_id=696559 Yes, that helped. Thanks. After years I documented a bit which patches I use for mailman: #!/bin/sh gzip -dc mailman-2.1.9.tgz | tar xvf - cd mailman-2.1.9 patch -p1 < ../mailman-2.1.9-patches/modinc-2.1.9-0.1.patch gzip -dc ../mailman-2.1.9-patches/antispam-2.1.9-0.1.patch.gz | patch -p1 gzip -dc ../mailman-2.1.9-patches/mhonarc-2.1.9-0.1.patch.gz | patch -p1 cat ../mailman-2.1.9-patches/11_handle_propfind.patch | patch -p0 cat ../mailman-2.1.9-patches/72_fblast_add_shebang.patch | patch -p0 cat ../mailman-2.1.9-patches/75_emaillist_only_show_bad_emails.dpatch | patch -p1 cat ../mailman-2.1.9-patches/passwd-rfc3834.patch | patch -p0 cat ../mailman-2.1.9-patches/mailman-2.1.6rc3-relpath.patch | patch -p1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2006-10-20 10:03 Message: Logged In: YES user_id=75166 Apologies, but the URL cited above had to be changed when I changed hosting service provider as they have co-opted the /mailman/ URI root. See instead: http://www.openinfo.co.uk/mm/patches/mhonarc/index.html ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2006-10-20 09:50 Message: Logged In: YES user_id=75166 The file INSTALL.mhonarc-mm installed by this patch contains the following words. The same information is also on the openinfo web page whose URL is above. Necessary Precursors -------------------- The following patch must be applied to Mailman before applying this patch: 1. Mailman Patch #760567: both this patch and #760567 update the version number ... ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2006-10-20 00:18 Message: Logged In: YES user_id=696559 ribosome mailman-2.1.9 # gzip -dc ../mailman-2.1.9-patches/antispam-2.1.9-0.1.patch.gz | patch -p1 patching file Mailman/Cgi/private.py patching file Mailman/Defaults.py.in ribosome mailman-2.1.9 # gzip -dc ../mailman-2.1.9-patches/mhonarc-2.1.9-0.1.patch.gz | patch -p1 patching file INSTALL.mhonarc-mm patching file Mailman/Archiver/Archiver.py patching file Mailman/Archiver/HyperArch.py patching file Mailman/Archiver/pipermail.py patching file Mailman/Cgi/create.py patching file Mailman/Defaults.py.in Hunk #2 succeeded at 1390 (offset 73 lines). patching file Mailman/Errors.py patching file Mailman/Gui/Archive.py patching file Mailman/Mailbox.py patching file Mailman/Version.py Hunk #1 FAILED at 39. 1 out of 1 hunk FAILED -- saving rejects to file Mailman/Version.py.rej patching file bin/arch patching file bin/newlist patching file templates/Makefile.in patching file templates/en/author.mrc patching file templates/en/mhonarc.mrc patching file templates/en/subject.mrc ribosome mailman-2.1.9 # less Mailman/Version.py.rej *************** *** 39,45 **** # config.pck schema version number # DATA_FILE_VERSION = 96 # 96.1 to take account of extra moderate_inc_body list attribute - DATA_FILE_VERSION = 96.1 # qfile/*.db schema version number QFILE_SCHEMA_VERSION = 3 --- 39,50 ---- # config.pck schema version number # DATA_FILE_VERSION = 96 # 96.1 to take account of extra moderate_inc_body list attribute + # DATA_FILE_VERSION = 96.1 + # 96.2 to take account of extra which_archiver and + # archiver_when_wiped list attributes + # must be applied AFTER the modinc-2.1.7-0.1.patch + DATA_FILE_VERSION = 96.2 + # qfile/*.db schema version number QFILE_SCHEMA_VERSION = 3 ribosome mailman-2.1.9 # So, which patch do I have to apply before applying the 2.1.9 -0.1 version of this? It is a pitty this is not yet in the official releases. I am using mailman-20041012.tar.bz2 with these for some years and see only 2 or three types of error in the logs. But damn mailman ignores some subscription confirmation messages and breaks on some non-us-ascii encoded messages so I should upgrade to see if it helps. :(( ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2006-10-03 13:08 Message: Logged In: YES user_id=75166 mhonarc-2.1.9-0.1.patch.gz is a MM 2.1.9 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2006-04-20 01:01 Message: Logged In: YES user_id=75166 Use mhonarc-2.1.7-0.1.patch.gz for both MM 2.1.7 and MM 2.1.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2006-03-02 22:17 Message: Logged In: YES user_id=75166 mhonarc-2.1.6-0.3.patch.gz corrects a long standing omission in the code of Mailman/Cgi/create.py which fails to get the initial setup of lists created through the web quite right. This leads to spurious errors being logged on message archiving until bin/arch --wipe is run for such a list affected. Lists created with bin/newlist did not have this problem. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2005-09-23 23:45 Message: Logged In: YES user_id=75166 mhonarc-2.1.6-0.2.patch.gz corrects an error in the modified code of $prefix/bin/arch introduced by the mhonarc-2.1.6-0.1.patch.gz - the problem was not present in patches for previous MM versions. In some circumstances, after running $prefix/bin/arch --wipe, subsequent post to a list my be generated using the wrong archiver. Examining index pages in the archives of a list will show if this problem has affected that list. Reinstallation with this revised patch and rerunning $prefix/bin/arch --wipe should resolve the problem. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2005-08-23 19:43 Message: Logged In: YES user_id=75166 mhonarc-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch ---------------------------------------------------------------------- Comment By: dfragos (dfragos) Date: 2005-07-21 17:24 Message: Logged In: YES user_id=1310569 what about MM 2.1.6? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-08-03 12:04 Message: Logged In: YES user_id=75166 mhonarc-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 01:53 Message: Logged In: YES user_id=696559 I've applied this patch(mhonarc-2.1.4-0.1.patch.gz) and it works great for me. Would someone apply to offcial cvs tree? Thanks. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-02 16:32 Message: Logged In: YES user_id=75166 mhonarc-2.1.4-0.1.patch is a MM 2.1.4 compatible version of this patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-22 16:32 Message: Logged In: YES user_id=75166 mhonarc-2.1.3-0.6.patch better supports the use of MHonArc -saveresources option. Also fixes minor HTML syntax error in mhonarc.mrc and author.mrc that affected generated date and author index pages. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-14 07:49 Message: Logged In: YES user_id=75166 With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself defined in Defaults.py is the empty string and, until this is changed, the option to select MHonArc instead of pipermail for per-list archiving is not offered on the web admin GUI. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-10 19:51 Message: Logged In: YES user_id=75166 Under some circumstances, when a single message is passed to MHonArc for archiving via a pipe, MHonArc may finish its processing and exit, closing its STDIN before the Mailman process that invoked it has finished output of the message to the pipe. Mistakenly, the patched pipermail code treated this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_i…

1 0