Mailman 3 December 2002 - Mailman-Developers

[ mailman-Patches-657951 ] Generate RSS summary in archives
by noreply＠sourceforge.net Dec. 23, 2002

Dec. 23, 2002

Patches item #657951, was opened at 2002-12-23 14:17 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: 5 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: 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…

1 0

[ mailman-Feature Requests-534234 ] Automatic RSS feed generation
by noreply＠sourceforge.net Dec. 23, 2002

Dec. 23, 2002

Feature Requests item #534234, was opened at 2002-03-24 00:12 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=534234&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rob Lanphier (robla) Assigned to: Nobody/Anonymous (nobody) Summary: Automatic RSS feed generation Initial Comment: It would be really great to have an automatic RSS feed as a result of using Mailman archiving. More info on RSS: http://purl.org/rss/1.0/ http://directory.google.com/Top/Reference/Libraries/Library_and_Information… RSS Validator: http://aggregator.userland.com/validator ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:22 Message: Logged In: YES user_id=11375 Patch #657951 adds an RSS summary to mailing lists. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-08-07 13:02 Message: Logged In: YES user_id=147905 If it's useful a friend and I have recently hacked on a <a href="http://taint.org/mmrss/">Perl script</a> which generates RSS feeds by scraping the Mailman archives. We made some (I think) significant improvements over the original which are documented in <a href="http://www.spack.org/index.cgi/MailmanHelp">our version</a> of the script. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-03 01:21 Message: Logged In: YES user_id=12800 Care to submit a patch? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=534234&group_i…

1 0

[ mailman-Patches-657951 ] Generate RSS summary in archives
by noreply＠sourceforge.net Dec. 23, 2002

Dec. 23, 2002

Patches item #657951, was opened at 2002-12-23 14:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i… Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 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: 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…

1 0

[ mailman-Patches-657951 ] Generate RSS summary in archives
by noreply＠sourceforge.net Dec. 23, 2002

Dec. 23, 2002

Patches item #657951, was opened at 2002-12-23 14:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i… Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i…

1 0

White space disappearing in subject header?
by Nick Arnett Dec. 23, 2002

Dec. 23, 2002

Does this sound familiar to anyone -- I couldn't find it in the known bugs. I haven't figured out how to reproduce this exactly, but some of my users noticed that sometimes Mailman is dropping the spaces between words toward the end of long subject lines. They report that they've put the spaces back in, but the message comes ot of the list server with them gone again. If it's not a known bug, I'll look into it some more and submit a bug report. Nick -- Nick Arnett Phone/fax: (408) 904-7198 narnett(a)mccmedia.com

3 2

[ mailman-Bugs-657443 ] Header and footer in multipart
by noreply＠sourceforge.net Dec. 22, 2002

Dec. 22, 2002

Bugs item #657443, was opened at 2002-12-22 11:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=657443&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Demeilliez Bruno (dive_bruno) Assigned to: Nobody/Anonymous (nobody) Summary: Header and footer in multipart Initial Comment: Hi, I have install mailman 2.1b6 on redhat 7.1. My mailling list is in french and when I received mail from the list with theBat, the header and the footer is in multipart (like at the end). I would like the bady and the footer was in the same message. Can you tell me if it's a bug or a configuration problem ? And how I can resolve it ? Thank's for your help. Bruno Example : .... From: Bruno Demeilliez <webmaster(a)aquanaute.com> X-Mailer: The Bat! (v1.62 Christmas Edition) Organization: Aquanaute.com X-Priority: 3 (Normal) Message-ID: <11916819925.20021222110418(a)aquanaute.com> To: test2(a)aquanaute.com MIME-Version: 1.0 Subject: Test X-BeenThere: test2(a)aquanaute.com X-Mailman-Version: 2.1b6 Precedence: list Reply-To: Bruno Demeilliez <webmaster(a)aquanaute.com>, test2(a)aquanaute.com List-Id: <test2.aquanaute.com> List-Help: <mailto:test2-request@aquanaute.com?subject=help> List-Post: <mailto:test2@aquanaute.com> List-Subscribe: <http://www.aquanaute.com/mailman/listinfo/test2>, <mailto:test2-request@aquanaute.com?subject=subscribe> List-Archive: <http://www.aquanaute.com/pipermail/test2> List-Unsubscribe: <http://www.aquanaute.com/mailman/listinfo/test2>, <mailto:test2-request@aquanaute.com?subject=unsubscribe> Content-Type: multipart/mixed; boundary="===============2617006012765839==" Sender: test2-bounces(a)aquanaute.com Errors-To: test2-bounces(a)aquanaute.com --===============2617006012765839== Content-Transfer-Encoding: 8bit content-type: text/plain Bonjour test2, Amicalement, Bruno --- Pour l'équipe d'Aquanaute.com http://www.aquanaute.com SARL de presse Aquanaute.com 8 rue Duployé 38100 Grenoble France Tél et Fax : 04 76 99 93 77 --===============2617006012765839== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit _______________________________________________ Liste de discussion Test2 Liste hébergée et administrée gratuitement par Aquanaute.com Présentation de la liste, Abonnement / Désabonnement : http://www.aquanaute.com/mailman/listinfo/test2 Archives de la liste : http://aquanaute.com/listes/Test2/ --===============2617006012765839==-- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=657443&group_i…

1 0

[ mailman-Patches-601117 ] add sequencial number in subject prefix
by noreply＠sourceforge.net Dec. 20, 2002

Dec. 20, 2002

Patches item #601117, was opened at 2002-08-28 05:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_i… Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 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: 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_i…

1 0

[ mailman-Patches-655214 ] Fix archiving
by noreply＠sourceforge.net Dec. 20, 2002

Dec. 20, 2002

Patches item #655214, was opened at 2002-12-17 14:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=655214&group_i… Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Fix archiving Initial Comment: This patch restores MIME charset capabilities for article archiving in CVS mailman. It: - removes the .charset attribute from articles; all articles are encoded in the list's charset, - decodes subject and author to Unicode; if this fails, no decoding (not even MIME) is done to subject and author, - MIME-decodes the body in the constructor using get_payload, removes the hand-crafted qp decoding from _get_body, - Unicode-decodes the body in the constructor if the body's charset differs from the list's charset, - fixes processbody_URLquote to always return byte strings (by escaping the URL also); comparing the old and the new string is no longer possible since the old string is Unicode and the new string is a list-encoded byte string. - changes text archiving to have the archives in the list's encoding, with unsupported characters 'replace'd - Fixes a bug in the scrubber, where a content-transfer-encoding might have survived flattening of the message. With these changes, I can process the playground archives correctly, to get mojibake-free pages. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-12-20 00:45 Message: Logged In: YES user_id=67709 Thanks. It looks like working for me (Japanese), except there was a typo: if isinstance(body, unicode): should be if isinstance(body, types.UnicodeType): ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-12-19 06:55 Message: Logged In: YES user_id=21627 Oops, attached. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-12-19 03:13 Message: Logged In: YES user_id=67709 Hi, Martin, Haven't you forget to attach file? I am interested in reviewing your patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=655214&group_i…

1 0

Archive templates in mm 2.1?
by mch＠cix.compulink.co.uk Dec. 19, 2002

Dec. 19, 2002

'Scuse me if I've missed something obvious... but is the code for HTML templates for the mailman/Pipermail archives checked in for 2.1? I did look at the release notes for 2.1bN but didn't see it... I'm asking because I'm planning upgrades for what will be a suite of mailing lists (for journalists :-) Though I don't speak Python (yet) I can just about pick out the sense in it... so if there's specific help needed... Mike Holderness in this instance, www.londonfreelance.org

1 0

[ mailman-Patches-656346 ] correct logging of pending requests
by noreply＠sourceforge.net Dec. 19, 2002

Dec. 19, 2002

Patches item #656346, was opened at 2002-12-19 15:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=656346&group_i… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jost Krieger (jkrieger) Assigned to: Nobody/Anonymous (nobody) Summary: correct logging of pending requests Initial Comment: I have no idea what the previous code was supposed to do. The new version logs what I think it should log (for me). --- Mailman/MailList.py.ORIG Wed Nov 27 12:01:18 2002 +++ Mailman/MailList.py Wed Nov 27 12:01:44 2002 @@ -826,7 +826,7 @@ if recipient <> email: who = "%s (%s)" % (email, recipient.split('@')[0]) else: - who = name + who = "%s (%s)" % (email, name) syslog('subscribe', '%s: pending %s %s', self.internal_name(), who, by) raise Errors.MMSubscribeNeedsConfirmation ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=656346&group_i…

1 0