Mailman 3 June 2007 - 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-1696053 ] Hebrew Translation Attached!
by SourceForge.net June 22, 2007

June 22, 2007

Patches item #1696053, was opened at 2007-04-07 07:24 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1696053&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: Dubi (dovzamir) Assigned to: Nobody/Anonymous (nobody) Summary: Hebrew Translation Attached! Initial Comment: Attached are the Hebrew files for Mailman 2.1.9 I added a parameter to the LC_DESCRIPTION function, and these are the files that are affected by the addition of 'direction' to the 'LC_DESCRIPTION' function. They have been changed, and diffs are attached... ./Mailman/Cgi/create.py ./Mailman/Defaults.py.in ./Mailman/Defaults.py ./Mailman/Utils.py ./messages/es/README.es ./messages/ja/README.ja ./messages/ja/doc/Defaults.py.in ./messages/eu/README.eu Likewise, all translation files are attached. There is still a problem displaying command line output in the correct direction. Still looking for a solution... ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-06-22 14:34 Message: Logged In: YES user_id=1123998 Originator: NO Replacement didn't help. Uploaded file was 207,802 bytes. When downloaded, the file is identical except now there are 8 extraneous bytes appended. Some versions of gunzip including 1.3.5 will report "decompression OK, trailing garbage ignored", and the resultant file will be fine. Reportedly there are other gunzip versions and/or .gz expanders that will not process the file. If you can't expand the downloaded file, you can try running this python script to truncate it to the proper length. >>> f = open('Mailman_2.1.9_he.tar.gz', 'r+b') >>> f.seek(207802) >>> f.truncate() >>> f.close() ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-06-22 14:06 Message: Logged In: YES user_id=1123998 Originator: NO Attempt to replace Mailman_2.1.9_he.tar.gz with one that doesn't have 6 extraneous trailing bytes. Also moved from 'bugs' to 'patches'. File Added: Mailman_2.1.9_he.tar.gz ---------------------------------------------------------------------- Comment By: Dubi (dovzamir) Date: 2007-04-26 11:33 Message: Logged In: YES user_id=1207589 Originator: YES File Added: Mailman_2.1.9_he.tar.gz ---------------------------------------------------------------------- Comment By: Dubi (dovzamir) Date: 2007-04-26 11:30 Message: Logged In: YES user_id=1207589 Originator: YES File Added: Mailman_2.1.9_he.tar.gz ---------------------------------------------------------------------- Comment By: Dubi (dovzamir) Date: 2007-04-26 11:27 Message: Logged In: YES user_id=1207589 Originator: YES File Added: Mailman_2.1.9_he.tar.gz ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1696053&group_…

1 0

[ mailman-Patches-1696053 ] Hebrew Translation Attached!
by SourceForge.net June 22, 2007

June 22, 2007

Patches item #1696053, was opened at 2007-04-07 07:24 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1696053&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: Dubi (dovzamir) Assigned to: Nobody/Anonymous (nobody) Summary: Hebrew Translation Attached! Initial Comment: Attached are the Hebrew files for Mailman 2.1.9 I added a parameter to the LC_DESCRIPTION function, and these are the files that are affected by the addition of 'direction' to the 'LC_DESCRIPTION' function. They have been changed, and diffs are attached... ./Mailman/Cgi/create.py ./Mailman/Defaults.py.in ./Mailman/Defaults.py ./Mailman/Utils.py ./messages/es/README.es ./messages/ja/README.ja ./messages/ja/doc/Defaults.py.in ./messages/eu/README.eu Likewise, all translation files are attached. There is still a problem displaying command line output in the correct direction. Still looking for a solution... ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-06-22 14:06 Message: Logged In: YES user_id=1123998 Originator: NO Attempt to replace Mailman_2.1.9_he.tar.gz with one that doesn't have 6 extraneous trailing bytes. Also moved from 'bugs' to 'patches'. File Added: Mailman_2.1.9_he.tar.gz ---------------------------------------------------------------------- Comment By: Dubi (dovzamir) Date: 2007-04-26 11:33 Message: Logged In: YES user_id=1207589 Originator: YES File Added: Mailman_2.1.9_he.tar.gz ---------------------------------------------------------------------- Comment By: Dubi (dovzamir) Date: 2007-04-26 11:30 Message: Logged In: YES user_id=1207589 Originator: YES File Added: Mailman_2.1.9_he.tar.gz ---------------------------------------------------------------------- Comment By: Dubi (dovzamir) Date: 2007-04-26 11:27 Message: Logged In: YES user_id=1207589 Originator: YES File Added: Mailman_2.1.9_he.tar.gz ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1696053&group_…

1 0

[ mailman-Patches-1740331 ] New translation: Slovak
by SourceForge.net June 20, 2007

June 20, 2007

Patches item #1740331, was opened at 2007-06-20 15:06 Message generated for change (Comment added) made by rebum You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1740331&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 Private: No Submitted By: Martin Matuska (rebum) Assigned to: Nobody/Anonymous (nobody) Summary: New translation: Slovak Initial Comment: The attached patch adds the slovak translation to Mailman 2.1.9. The included .po file is from SVN trunk. I would like to become the language champion for the Slovak language. Thank you, Martin Matuska <martin at matuska dot org> <mm at FreeBSD dot org> ---------------------------------------------------------------------- >Comment By: Martin Matuska (rebum) Date: 2007-06-20 18:07 Message: Logged In: YES user_id=41220 Originator: YES Updated translation and single mailman.po + templates can be found under: http://www.matuska.org/martin/mailman ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1740331&group_…

1 0

[ mailman-Patches-1740331 ] New translation: Slovak
by SourceForge.net June 20, 2007

June 20, 2007

Patches item #1740331, was opened at 2007-06-20 15:06 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=1740331&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 Private: No Submitted By: Martin Matuska (rebum) Assigned to: Nobody/Anonymous (nobody) Summary: New translation: Slovak Initial Comment: The attached patch adds the slovak translation to Mailman 2.1.9. The included .po file is from SVN trunk. I would like to become the language champion for the Slovak language. Thank you, Martin Matuska <martin at matuska dot org> <mm at FreeBSD dot org> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1740331&group_…

1 0

[ mailman-Bugs-1738710 ] Out-of-order install instructions (permissions)
by SourceForge.net June 17, 2007

June 17, 2007

Bugs item #1738710, was opened at 2007-06-17 10:00 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1738710&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: documentation Group: 2.1 (stable) >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: David Chase (dr2chase) Assigned to: Nobody/Anonymous (nobody) Summary: Out-of-order install instructions (permissions) Initial Comment: Quoting: Warning: You want to be very sure that the user id under which your CGI scripts run is not in the mailman group you created above, otherwise private archives will be accessible to anyone. Problem #1: this is the first point in the install instructions where this is so clearly stated, far after the configure and make steps. Yeah, sure, once upon a time we were supposed to read all the instructions first before doing anything, but more people will install and use the software if you just put the steps in the right order in the documentation. Lots of other products manage to get this right. Problem #2: HOW IS THIS ACCOMPLISHED? This is important, right? Why not spend a few words on making sure people get it right? Problem #3: This looks like exactly the sort of boring mechanical thing that a computer is good at. Why is the human installer being asked to check this? ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-06-17 10:57 Message: Logged In: YES user_id=1123998 Originator: NO Problem #1 - It seems to me this is in the right place. It is under 'setting up your web server' which is where you configure the user under which Mailman CGIs will run. Problem #2 - Consult your web server documentation. Normally, your web server is not running Mailman GGIs as the mailman user anyway unless you go out of your way to make it do so. Problem #3 - We have no idea what web server you are running or how to find and parse its configuration file(s), so how can we check this mechanically? We do check at run time in the CGI wrapper to be sure that the wrapper is invoked with the group configured with --with-cgi-gid. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1738710&group_…

1 0

[ mailman-Bugs-1738710 ] Out-of-order install instructions (permissions)
by SourceForge.net June 17, 2007

June 17, 2007

Bugs item #1738710, was opened at 2007-06-17 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=100103&aid=1738710&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: documentation Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: David Chase (dr2chase) Assigned to: Nobody/Anonymous (nobody) Summary: Out-of-order install instructions (permissions) Initial Comment: Quoting: Warning: You want to be very sure that the user id under which your CGI scripts run is not in the mailman group you created above, otherwise private archives will be accessible to anyone. Problem #1: this is the first point in the install instructions where this is so clearly stated, far after the configure and make steps. Yeah, sure, once upon a time we were supposed to read all the instructions first before doing anything, but more people will install and use the software if you just put the steps in the right order in the documentation. Lots of other products manage to get this right. Problem #2: HOW IS THIS ACCOMPLISHED? This is important, right? Why not spend a few words on making sure people get it right? Problem #3: This looks like exactly the sort of boring mechanical thing that a computer is good at. Why is the human installer being asked to check this? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1738710&group_…

1 0

[ mailman-Bugs-1738667 ] misc/KoreanCodecs-2.0.5/src/hangul.c does not compile
by SourceForge.net June 17, 2007

June 17, 2007

Bugs item #1738667, was opened at 2007-06-17 07:54 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1738667&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: configuring/installing Group: 2.1 (stable) >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: David Chase (dr2chase) Assigned to: Nobody/Anonymous (nobody) Summary: misc/KoreanCodecs-2.0.5/src/hangul.c does not compile Initial Comment: SunOS ... 5.10 Generic_118855-36 i86pc i386 i86pc Python 2.3.5 (#1, Nov 30 2005, 10:43:01) [C] on sunos5 gcc -v yields: Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared Thread model: posix gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath) -------------- Compilation first fails when it attempts to invoke "cc" despite being configured to use the default (which is gcc). Hacking around this with a symbolic link from cc to gcc yields: src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant The cause of this is that two of the enums defined in hangul.c enum { /* Jaeum Codes on U+3100 */ G = 0x3131, GG, GS, N, NJ, NH, D, DD, L, LG, LM, LB, LS, LT, LP, LH, M, B, BB, BS, S, SS, NG, J, JJ, C, K, T, P, H }; preprocess to integers (after gcc -E): enum { G = 0x3131, GG, 0, N, NJ, NH, D, DD, L, LG, LM, LB, LS, LT, LP, LH, M, B, BB, BS, S, 18, NG, J, JJ, C, K, T, P, H }; Presumably this is specific to the python include file version. Proposed hackaround, inserted before the enums: #ifdef GS #undef GS #endif #ifdef SS #undef SS #endif It did at least finish the make install after this. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-06-17 08:37 Message: Logged In: YES user_id=1123998 Originator: NO I believe this is a Solaris bug, not a Mailman bug. See <http://www.google.com/search?hl=en&q=site%3Amail.python.org++inurl%3Amailma…> including <http://mail.python.org/pipermail/mailman-users/2007-January/055235.html> from which I quote This is due to a bug in Solaris 10 headers. <signal.h> includes <sys/regset.h> which pollutes the macro "namespace" (if you will) with definitions for x86 registers, like GS and SS. This is only on Solaris/x86; Solaris/sparc doesn't have this error. Regarding the cc/gcc issue see <http://www.google.com/search?hl=en&safe=off&q=site%3Amail.python.org++inurl…> including <http://mail.python.org/pipermail/mailman-users/2007-January/055506.html> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1738667&group_…

1 0

[ mailman-Bugs-1738667 ] misc/KoreanCodecs-2.0.5/src/hangul.c does not compile
by SourceForge.net June 17, 2007

June 17, 2007

Bugs item #1738667, was opened at 2007-06-17 10:54 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=1738667&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: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: David Chase (dr2chase) Assigned to: Nobody/Anonymous (nobody) Summary: misc/KoreanCodecs-2.0.5/src/hangul.c does not compile Initial Comment: SunOS ... 5.10 Generic_118855-36 i86pc i386 i86pc Python 2.3.5 (#1, Nov 30 2005, 10:43:01) [C] on sunos5 gcc -v yields: Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared Thread model: posix gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath) -------------- Compilation first fails when it attempts to invoke "cc" despite being configured to use the default (which is gcc). Hacking around this with a symbolic link from cc to gcc yields: src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant The cause of this is that two of the enums defined in hangul.c enum { /* Jaeum Codes on U+3100 */ G = 0x3131, GG, GS, N, NJ, NH, D, DD, L, LG, LM, LB, LS, LT, LP, LH, M, B, BB, BS, S, SS, NG, J, JJ, C, K, T, P, H }; preprocess to integers (after gcc -E): enum { G = 0x3131, GG, 0, N, NJ, NH, D, DD, L, LG, LM, LB, LS, LT, LP, LH, M, B, BB, BS, S, 18, NG, J, JJ, C, K, T, P, H }; Presumably this is specific to the python include file version. Proposed hackaround, inserted before the enums: #ifdef GS #undef GS #endif #ifdef SS #undef SS #endif It did at least finish the make install after this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1738667&group_…

1 0

[ mailman-Patches-1527537 ] prevent and log subscription spamflood (2.1.8)
by SourceForge.net June 13, 2007

June 13, 2007

Patches item #1527537, was opened at 2006-07-24 11:06 Message generated for change (Comment added) made by pabs3 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1527537&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: Open Resolution: None Priority: 5 Private: No Submitted By: Paul Wise (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: prevent and log subscription spamflood (2.1.8) Initial Comment: The attached patch for mailman 2.1.8 causes mailman to ignore subscriptions that already exist in pending.pck and request.pck. This prevents people from mass-spamming either the list admin or random email addresses (depending on the configuration of the list). ---------------------------------------------------------------------- >Comment By: Paul Wise (pabs3) Date: 2007-06-14 00:47 Message: Logged In: YES user_id=35028 Originator: YES New version that doesn't traceback when there are pending unsubscription attempts. File Added: imc-37-stop-subscription-spam.patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1527537&group_…

1 0