Mailman 3 November 2005 - 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-1365282 ] Add New Langauge Punjabi (pa) to mailman
by SourceForge.net Nov. 28, 2005

Nov. 28, 2005

Patches item #1365282, was opened at 2005-11-24 05:19 Message generated for change (Comment added) made by aalam You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1365282&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: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Amanpreet Singh Alam (aalam) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Add New Langauge Punjabi (pa) to mailman Initial Comment: Hello I translate mailman to Punajbi and Want to include in mailman. As per direction from Barry, I m attaching file here! following is info about Language "Punjabi" ISO Code = "pa" Coding = Unicode (UTF-8) Can u please include those files for Punjabi to Mailman? thanks AP Singh Alam http://punlinux.sf.net ---------------------------------------------------------------------- >Comment By: Amanpreet Singh Alam (aalam) Date: 2005-11-28 05:45 Message: Logged In: YES user_id=1200839 I buid on Fedora and it was ready can u please help me to send the errors? thanks AP Singh ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-11-26 06:32 Message: Logged In: YES user_id=67709 Hi, I tested your translation and get error. Will you please test your translation by yourself before submitting to the patch tracker? You should add your language in templates/Makefile.in, messages/Makefile.in and Mailman/Defaults.py.in then do the configure/make install. bin/transcheck should help debugging. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1365282&group_…

1 0

[ mailman-Bugs-1367783 ] Content filtering encoded HTML to plain text garbles result
by SourceForge.net Nov. 28, 2005

Nov. 28, 2005

Bugs item #1367783, was opened at 2005-11-27 14:26 Message generated for change (Settings changed) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1367783&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: Closed Resolution: Fixed Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Mark Sapiro (msapiro) Summary: Content filtering encoded HTML to plain text garbles result Initial Comment: If content filtering is on and convert_html_to_plaintext is yes and the HTML parts to be converted are base64 or quoted-printable encoded, the part is not decoded prior to passing to mm_cfg.HTML_TO_PLAIN_TEXT_COMMAND. This can result in the HTML not being converted at all if base64 encoded data 'passes through' mm_cfg.HTML_TO_PLAIN_TEXT_COMMAND, or the result being garbled if there are quoted-printable characters inside HTML tags. Fixed in CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1367783&group_…

1 0

[ mailman-Bugs-1367783 ] Content filtering encoded HTML to plain text garbles result
by SourceForge.net Nov. 28, 2005

Nov. 28, 2005

Bugs item #1367783, was opened at 2005-11-27 14:26 Message generated for change (Settings changed) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1367783&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: Fixed Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Mark Sapiro (msapiro) Summary: Content filtering encoded HTML to plain text garbles result Initial Comment: If content filtering is on and convert_html_to_plaintext is yes and the HTML parts to be converted are base64 or quoted-printable encoded, the part is not decoded prior to passing to mm_cfg.HTML_TO_PLAIN_TEXT_COMMAND. This can result in the HTML not being converted at all if base64 encoded data 'passes through' mm_cfg.HTML_TO_PLAIN_TEXT_COMMAND, or the result being garbled if there are quoted-printable characters inside HTML tags. Fixed in CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1367783&group_…

1 0

[ mailman-Bugs-1367783 ] Content filtering encoded HTML to plain text garbles result
by SourceForge.net Nov. 28, 2005

Nov. 28, 2005

Bugs item #1367783, was opened at 2005-11-27 14:26 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=1367783&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: Mark Sapiro (msapiro) Assigned to: Mark Sapiro (msapiro) Summary: Content filtering encoded HTML to plain text garbles result Initial Comment: If content filtering is on and convert_html_to_plaintext is yes and the HTML parts to be converted are base64 or quoted-printable encoded, the part is not decoded prior to passing to mm_cfg.HTML_TO_PLAIN_TEXT_COMMAND. This can result in the HTML not being converted at all if base64 encoded data 'passes through' mm_cfg.HTML_TO_PLAIN_TEXT_COMMAND, or the result being garbled if there are quoted-printable characters inside HTML tags. Fixed in CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1367783&group_…

1 0

[ mailman-Patches-1287921 ] post log entries show envelope sender, not From:
by SourceForge.net Nov. 28, 2005

Nov. 28, 2005

Patches item #1287921, was opened at 2005-09-11 11:00 Message generated for change (Settings changed) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287921&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: Mailman 2.1 Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Mark Sapiro (msapiro) Summary: post log entries show envelope sender, not From: Initial Comment: The interpolation dictionary used with the SMTPDirect.py log messages includes 'sender' which is obtained with the Message.get_sender() method. If mm_cfg.USE_ENVELOPE_SENDER is Yes, this method returns the envelope sender which, since this is an outgoing message, is always the listname-bounces address. Since 'listname' is already in the dictionary, this is redundant. It would be more useful, at least for lists which aren't anonymous, to override this behavior and get the sender with get_sender(use_envelope=0) which would return the From: address. The patch makes this change. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-11-12 16:01 Message: Logged In: YES user_id=1123998 This has been fixed differently from the patch that was here. The patch would always use the From:, but the fix correctly calls msg.get_sender() without forcing use_envelope=0; it just does it earlier. The fix is in CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1287921&group_…

1 0

[ mailman-Patches-1318883 ] Line following Approved: line in body of post is stripped
by SourceForge.net Nov. 28, 2005

Nov. 28, 2005

Patches item #1318883, was opened at 2005-10-08 14:12 Message generated for change (Settings changed) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1318883&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: list administration Group: Mailman 2.1 Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Mark Sapiro (msapiro) Summary: Line following Approved: line in body of post is stripped Initial Comment: If a post contains an [Aa]pproved?: line as the first non-blank line of the first text/plain part (and doesn't contain an Approved?: header), the line itself is deleted, but so is the first of the remaining lines. If this first remaining line is a blank line which preceeded the Approved: line, no harm is done, but if there are no blank lines preceeding the Approved: line, the line following the Approved: line which may be non-blank is stripped. This occurs because after the Approved: line is removed, the remaining lines are re-joined beginning with line 1 and not line 0. The patch to Mailman/Handlers/Approve.py corrects this. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-11-12 18:46 Message: Logged In: YES user_id=1123998 Patch has been commited in CVS ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1318883&group_…

1 0

[ mailman-Bugs-1263213 ] checkbox "Send list created" not saved if failure
by SourceForge.net Nov. 28, 2005

Nov. 28, 2005

Bugs item #1263213, was opened at 2005-08-18 09:50 Message generated for change (Settings changed) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263213&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/CGI Group: None Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Daniel (doolyo) Assigned to: Mark Sapiro (msapiro) Summary: checkbox "Send list created" not saved if failure Initial Comment: On the list creation page (/mailman/create), if we check the "Send list created e-mail to list owner" button to 'yes' and that we put a wrong password by submitting the form, the checkbox will come back to 'no'. This is not the case with the other checkboxes or the text, everything else comes back to the previously chosen values. ---------------------------------------------------------------------- Comment By: Daniel (doolyo) Date: 2005-11-09 01:53 Message: Logged In: YES user_id=1320890 Thanks for that, msapiro. Regards, Daniel ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-11-08 18:49 Message: Logged In: YES user_id=1123998 The attached patch fixes the bug including correctly initializing the button from DEFAULT_DEFAULT_MEMBER_MODERATION and remembering the prior choice across errors. There is still an issue in that language selections are not remembered across errors. ---------------------------------------------------------------------- Comment By: Daniel (doolyo) Date: 2005-08-18 11:49 Message: Logged In: YES user_id=1320890 Oops, sorry. It is not the correct checkbox. It is the other, called 'Should new members be quarantined before they are allowed to post unmoderated to this list?'. The rest is true for the fact that it looses it's 'yes' value. Thanks, Daniel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263213&group_…

1 0

[ mailman-Bugs-815297 ] Breaking signatures in message/rfc822 attachement!
by SourceForge.net Nov. 26, 2005

Nov. 26, 2005

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_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: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 8 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: 2005-11-26 15:58 Message: Logged In: YES user_id=113859 This is still a serious bug. I guess that the real fix will be to rewrite the email and mime handling classes to at least additionally save an original version of the different email parts without stripping and further formatting. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-05-10 20:15 Message: Logged In: YES user_id=113859 There is another possibility when mailman breaks the signature and that is when the signed part contains an empty header with _two_ spaces after the colon, like forward and sign an email with X-Empty-Header-with-two-spaces:<space><space> patch 933757 does not remedy this, though. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-04-12 19:17 Message: Logged In: YES user_id=113859 I have created a patch to address the problem. [ 933757 ] fix for [815297] signatures break https://sourceforge.net/tracker/index.php?func=detail&aid=933757&group_id=1… ---------------------------------------------------------------------- Comment By: Marc Mutz (mmutz) Date: 2003-10-03 17:54 Message: Logged In: YES user_id=82377 This is not limited to message/rfc822 at all: As a specific example, create a message with an attachment and add the header Content-Disposition: attachment; filename="more-than-70-chars. txt" (all in a single line), then send it through a mailman-managed ml. Result: mailman "fixes" the message to look like Content-Disposition: attachment; \tfilename="more-than-70-chars.txt" It even does that inside a multipart/signed part, and this is where it breaks the signature verification. ---------------------------------------------------------------------- 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_i…

1 0

[ mailman-Patches-1365282 ] Add New Langauge Punjabi (pa) to mailman
by SourceForge.net Nov. 26, 2005

Nov. 26, 2005

Patches item #1365282, was opened at 2005-11-24 05:19 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1365282&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: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Amanpreet Singh Alam (aalam) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Add New Langauge Punjabi (pa) to mailman Initial Comment: Hello I translate mailman to Punajbi and Want to include in mailman. As per direction from Barry, I m attaching file here! following is info about Language "Punjabi" ISO Code = "pa" Coding = Unicode (UTF-8) Can u please include those files for Punjabi to Mailman? thanks AP Singh Alam http://punlinux.sf.net ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-11-26 06:32 Message: Logged In: YES user_id=67709 Hi, I tested your translation and get error. Will you please test your translation by yourself before submitting to the patch tracker? You should add your language in templates/Makefile.in, messages/Makefile.in and Mailman/Defaults.py.in then do the configure/make install. bin/transcheck should help debugging. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1365282&group_…

1 0