Mailman 3 October 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-Bugs-1344305 ] trojan problem
by SourceForge.net Nov. 1, 2005

Nov. 1, 2005

Bugs item #1344305, was opened at 2005-10-31 13:30 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1344305&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: More Information Needed Status: Open Resolution: None Priority: 5 Submitted By: dave the dragon (david-powell) Assigned to: Nobody/Anonymous (nobody) Summary: trojan problem Initial Comment: more a observed comment but may have other implications recently i was running bit defender antivirus on my pc and found it reported /usr/lib/mailman/tests/msgs/nimda.txt=>(IFRAME) infected: Trojan.Exploit.Html.Iframe.Filedownload.AW <- cevakrnl.xmd from what i can gather the file is one used for testing (not shure if the actual exploit code needs to be there for that though) but it raises an issue in that because of the file being included in the distributed code it may cause some distributions from including the whole package in there distributions and may also possibaly in some cercumstances lead to legal action as it may be construded that this trojan code is being distributed just feel that this should be pointed out to you Dave ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-10-31 14:17 Message: Logged In: YES user_id=1123998 The file never contained any trojan code. It is safe to look at it and if you do, you'll see that it is mostly MIME headers and a few bits of innocuous content. As of Mailman 2.1.6, the file is no longer in the distribution. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1344305&group_…

1 0

[ mailman-Bugs-1344305 ] trojan problem
by SourceForge.net Nov. 1, 2005

Nov. 1, 2005

Bugs item #1344305, was opened at 2005-10-31 21:30 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=1344305&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: More Information Needed Status: Open Resolution: None Priority: 5 Submitted By: dave the dragon (david-powell) Assigned to: Nobody/Anonymous (nobody) Summary: trojan problem Initial Comment: more a observed comment but may have other implications recently i was running bit defender antivirus on my pc and found it reported /usr/lib/mailman/tests/msgs/nimda.txt=>(IFRAME) infected: Trojan.Exploit.Html.Iframe.Filedownload.AW <- cevakrnl.xmd from what i can gather the file is one used for testing (not shure if the actual exploit code needs to be there for that though) but it raises an issue in that because of the file being included in the distributed code it may cause some distributions from including the whole package in there distributions and may also possibaly in some cercumstances lead to legal action as it may be construded that this trojan code is being distributed just feel that this should be pointed out to you Dave ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1344305&group_…

1 0

[ mailman-Patches-1343100 ] config_list vs. PEP 263
by SourceForge.net Oct. 31, 2005

Oct. 31, 2005

Patches item #1343100, was opened at 2005-10-31 12:58 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=1343100&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: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: config_list vs. PEP 263 Initial Comment: As of Python 2.3, DeprecatedWarning is issued for non-US-ASCII source. Let output of bin/config_list be compliant to PEP 263. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1343100&group_…

1 0

[ mailman-Bugs-1337731 ] Content-Transfer-Encoding header missing
by SourceForge.net Oct. 27, 2005

Oct. 27, 2005

Bugs item #1337731, was opened at 2005-10-25 18:37 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1337731&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.0.x >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: DrV (i_am_drv) Assigned to: Nobody/Anonymous (nobody) Summary: Content-Transfer-Encoding header missing Initial Comment: When sending a digest, Mailman 2.0.9 doesn't include a Content-Transfer-Encoding header, yet it seems to encode the messages with quoted-printable. As per IRC 2045: "Content-Transfer-Encoding: 7BIT" is assumed if the Content-Transfer-Encoding header field is not present. In particular, =## sequences are included, which are not decoded correctly by mail readers (tested with Mozilla Thunderbird), because the Content-Transfer-Encoding does not specify quoted-printable. The digests include correct MIME version and Content-type headers, but Content-Transfer-Encoding has been missing in all cases I have seen. Example: ------------ >From - Tue Oct 25 12:01:55 2005 X-Account-Key: account2 X-UIDL: 406934627 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Received: from lists-outbound.sourceforge.net [66.35.250.225] by wwimail002.winsdns.com with ESMTP (SMTPD32-8.15) id A05B2BFF00F0; Tue, 25 Oct 2005 01:19:23 -0400 Received: from projects.sourceforge.net (sc8-sf-list2-b.sourceforge.net [10.3.1.8]) by sc8-sf-spam1.sourceforge.net (Postfix) with ESMTP id E7BDE88948; Mon, 24 Oct 2005 22:20:05 -0700 (PDT) Date: Mon, 24 Oct 2005 22:09:26 -0700 From: freedos-devel-request(a)lists.sourceforge.net Subject: Freedos-devel digest, Vol 1 #668 - 4 msgs X-Mailer: Mailman v2.0.9-sf.net MIME-version: 1.0 Content-type: text/plain To: freedos-devel(a)lists.sourceforge.net Sender: freedos-devel-admin(a)lists.sourceforge.net Errors-To: freedos-devel-admin(a)lists.sourceforge.net X-BeenThere: freedos-devel(a)lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk Reply-To: freedos-devel(a)lists.sourceforge.net X-Reply-To: freedos-devel(a)lists.sourceforge.net List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/freedos-devel>, <mailto:freedos-devel-request@lists.sourceforge.net?subject=unsubscribe> List-Id: <freedos-devel.lists.sourceforge.net> List-Post: <mailto:freedos-devel@lists.sourceforge.net> List-Help: <mailto:freedos-devel-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/freedos-devel>, <mailto:freedos-devel-request@lists.sourceforge.net?subject=subscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=freedos-devel> Message-Id: <20051025052005.E7BDE88948(a)sc8-sf-spam1.sourceforge.net> ------------- I have only verified this for digests sent by "X-Mailer: Mailman v2.0.9-sf.net" (for mailing lists of sf.net projects). ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-10-27 01:00 Message: Logged In: YES user_id=67709 mailman 2.1.x includes the fix. Please update. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1337731&group_…

1 0

[ mailman-Bugs-736559 ] Subject wrap with tab character
by SourceForge.net Oct. 27, 2005

Oct. 27, 2005

Bugs item #736559, was opened at 2003-05-12 17:05 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=736559&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: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Swen Haubold (swen_haubold) Assigned to: Nobody/Anonymous (nobody) Summary: Subject wrap with tab character Initial Comment: Mailman: 2.1.2 The subject line is wrapped by a tab character, if the line contains more than 78 characters. In this case a space is replaced by an tab character. This behaviour gives trouble with some e-mail client and is also not handled by MHonArc correctly. In an e-mail client a long space is shown or a special character. MHonArc simply removes the tab character therefore two words are combined, e.g. the tab is inserted between the two word "and" and "delivery"; in the archive the subject contains the new word "anddelivery" ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-10-27 00:55 Message: Logged In: YES user_id=67709 RFC 2822 example states: Subject: This is a test can be represented as: Subject: This is a test Therefore, if MHonArc or a MUA simply removes tab char and not insertes a space in place of the FWS (folding white space), it is his fault. Mailman now select FWS from tab or space as appeared in the original message. ---------------------------------------------------------------------- Comment By: Jeff Wilson (jwilson75503) Date: 2005-10-25 03:47 Message: Logged In: YES user_id=1083352 This behavior seems to still occur in 2.1.6 http://www.mail-archive.com/mailman-developers% 40python.org/msg09027.html ---------------------------------------------------------------------- Comment By: Dave Disser (disser) Date: 2003-06-04 22:28 Message: Logged In: YES user_id=794167 I notice this also with Mailman 2.1.1. I don't see code in mailman doing it, so it appears to be in email.Header or unicode. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=736559&group_i…

1 0

[ mailman-Bugs-1337731 ] Content-Transfer-Encoding header missing
by SourceForge.net Oct. 26, 2005

Oct. 26, 2005

Bugs item #1337731, was opened at 2005-10-25 18:37 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=1337731&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.0.x Status: Open Resolution: None Priority: 5 Submitted By: DrV (i_am_drv) Assigned to: Nobody/Anonymous (nobody) Summary: Content-Transfer-Encoding header missing Initial Comment: When sending a digest, Mailman 2.0.9 doesn't include a Content-Transfer-Encoding header, yet it seems to encode the messages with quoted-printable. As per IRC 2045: "Content-Transfer-Encoding: 7BIT" is assumed if the Content-Transfer-Encoding header field is not present. In particular, =## sequences are included, which are not decoded correctly by mail readers (tested with Mozilla Thunderbird), because the Content-Transfer-Encoding does not specify quoted-printable. The digests include correct MIME version and Content-type headers, but Content-Transfer-Encoding has been missing in all cases I have seen. Example: ------------ >From - Tue Oct 25 12:01:55 2005 X-Account-Key: account2 X-UIDL: 406934627 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Received: from lists-outbound.sourceforge.net [66.35.250.225] by wwimail002.winsdns.com with ESMTP (SMTPD32-8.15) id A05B2BFF00F0; Tue, 25 Oct 2005 01:19:23 -0400 Received: from projects.sourceforge.net (sc8-sf-list2-b.sourceforge.net [10.3.1.8]) by sc8-sf-spam1.sourceforge.net (Postfix) with ESMTP id E7BDE88948; Mon, 24 Oct 2005 22:20:05 -0700 (PDT) Date: Mon, 24 Oct 2005 22:09:26 -0700 From: freedos-devel-request(a)lists.sourceforge.net Subject: Freedos-devel digest, Vol 1 #668 - 4 msgs X-Mailer: Mailman v2.0.9-sf.net MIME-version: 1.0 Content-type: text/plain To: freedos-devel(a)lists.sourceforge.net Sender: freedos-devel-admin(a)lists.sourceforge.net Errors-To: freedos-devel-admin(a)lists.sourceforge.net X-BeenThere: freedos-devel(a)lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk Reply-To: freedos-devel(a)lists.sourceforge.net X-Reply-To: freedos-devel(a)lists.sourceforge.net List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/freedos-devel>, <mailto:freedos-devel-request@lists.sourceforge.net?subject=unsubscribe> List-Id: <freedos-devel.lists.sourceforge.net> List-Post: <mailto:freedos-devel@lists.sourceforge.net> List-Help: <mailto:freedos-devel-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/freedos-devel>, <mailto:freedos-devel-request@lists.sourceforge.net?subject=subscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=freedos-devel> Message-Id: <20051025052005.E7BDE88948(a)sc8-sf-spam1.sourceforge.net> ------------- I have only verified this for digests sent by "X-Mailer: Mailman v2.0.9-sf.net" (for mailing lists of sf.net projects). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1337731&group_…

1 0

[ mailman-Bugs-736559 ] Subject wrap with tab character
by SourceForge.net Oct. 25, 2005

Oct. 25, 2005

Bugs item #736559, was opened at 2003-05-12 12:05 Message generated for change (Comment added) made by jwilson75503 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=736559&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: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Swen Haubold (swen_haubold) Assigned to: Nobody/Anonymous (nobody) Summary: Subject wrap with tab character Initial Comment: Mailman: 2.1.2 The subject line is wrapped by a tab character, if the line contains more than 78 characters. In this case a space is replaced by an tab character. This behaviour gives trouble with some e-mail client and is also not handled by MHonArc correctly. In an e-mail client a long space is shown or a special character. MHonArc simply removes the tab character therefore two words are combined, e.g. the tab is inserted between the two word "and" and "delivery"; in the archive the subject contains the new word "anddelivery" ---------------------------------------------------------------------- Comment By: Jeff Wilson (jwilson75503) Date: 2005-10-24 22:47 Message: Logged In: YES user_id=1083352 This behavior seems to still occur in 2.1.6 http://www.mail-archive.com/mailman-developers% 40python.org/msg09027.html ---------------------------------------------------------------------- Comment By: Dave Disser (disser) Date: 2003-06-04 17:28 Message: Logged In: YES user_id=794167 I notice this also with Mailman 2.1.1. I don't see code in mailman doing it, so it appears to be in email.Header or unicode. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=736559&group_i…

1 0

[ mailman-Patches-1123383 ] Daily Status Report script...
by SourceForge.net Oct. 19, 2005

Oct. 19, 2005

Patches item #1123383, was opened at 2005-02-15 21:14 Message generated for change (Comment added) made by tgc99 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&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: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Daily Status Report script... Initial Comment: Folks, I quickly whacked together a Daily Status Report script for Mailman (using Bourne shell, not Python ;), and thought that other folks might be interested in seeing it. The basic concept is a program that gets fired off at 23:59 every night, and goes through a variety of log files looking for entries specific to that date, and indicating problems or certain types of activity that might be of interest to someone trying to administer the server. It also does an "ls -la" of /usr/local/mailman/qfiles/*, so that you can see what is in the queue at the time of the running of the script. My concept was that this daily report would get e-mailed to the admin, or posted to a "reports" mailing list, where they could be archived and kept for future reference. The script does not (yet) do any statistics calculations, although it should be relatively easy to hack together some basic stats using awk, sort, etc.... Anyway, I thought I'd share it and let folks take a look at it, and if anyone has any recommended improvements, we can incorporate those and share them back out with everyone. The code is written under a BSD-style license, so if you don't want to contribute any changes back to me, that's okay. Of course, I would prefer that you did, but I leave the choice up to you. ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-10-19 10:23 Message: Logged In: YES user_id=1159458 ps output on solaris is full of whitespace but a further echo get's rid of it. The lines in the smtp log are sometimes broken up by a newline (right before the msgid) which throws of the summary. Piping it through sed first will rejoin the broken lines. Use $AWK instead of awk. Patch inserted below: --- mmdsr.orig 2005-10-19 09:42:30.000000000 +0200 +++ mmdsr 2005-10-19 09:44:23.000000000 +0200 @@ -203,7 +203,8 @@ # there is an easier cross-platform way to do it, please let me know. ############################################################################### -MYUID=`$PS -o user -p $$ | $TAIL -1` +GRABUID=`$PS -o user -p $$ | $TAIL -1` +MYUID=`echo $GRABUID` RUNAS="mailman" ############################################################################### @@ -254,7 +255,7 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG + $SED -e :a -e '$!N;s/\n //;ta' -e 'P;D' $LOGDIR/$LOG | $GREP -si "^$DAY [0-9][0-9:]* $YEAR" >> $TMPLOG if [ -f "$LOGDIR/${LOG}" ] ; then @@ -264,7 +265,7 @@ echo "Hourly Summary of Posts" >> $TMP echo "-----------------------" >> $TMP - $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e 's/:.*$//' $TMPLOG | $UNIQ -c | $SORT -n +1 | awk '{ printf( "%8d %02d:00-%02d :59\n", $1, $2, $2 ) }' >> $TMP + $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e 's/:.*$//' $TMPLOG | $UNIQ -c | $SORT -n +1 | $AWK '{ printf( "%8d %02d:00-%02 d:59\n", $1, $2, $2 ) }' >> $TMP echo "" >> $TMP echo "Post Count by List" >> $TMP @@ -295,7 +296,7 @@ echo "" >> $TMP echo "Hourly Summary of Messages Sent" >> $TMP echo "-------------------------------" >> $TMP - $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e 's/:.* for / /' -e 's/ recips,.*$//' $TMPLOG | awk '{ val=int($1); sum[val]+=$2 } END { for (i=0; i<24; i++) { printf "%8d %02d:00-%02d:59\n", sum[i], i, i } }' >> $TMP + $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e 's/:.* for / /' -e 's/ recips,.*$//' $TMPLOG | $AWK '{ val=int($1); sum[val]+=$ 2 } END { for (i=0; i<24; i++) { printf "%8d %02d:00-%02d:59\n", sum[i], i, i } }' >> $TMP else ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-09-23 01:17 Message: Logged In: YES user_id=18417 Okay, I took Mark's comments and incorporated them. Adrian Wells also pointed out a log file difference between Mailman 2.1.5 and 2.1.6 that caused the summary of the "smtp" log to be munged. I've now fixed these bugs, deleted the old file, and uploaded the new one (version 0.0.12). Thanks! ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-11 04:22 Message: Logged In: YES user_id=1123998 Oooops! I mistakenly thought I could add the mmdsr.patch as a downloadable file, but I can't so here it is. Watch out for wrapped lines ... --- mmdsr.orig 2005-09-06 20:37:53.000000000 -0700 +++ mmdsr 2005-09-10 18:33:14.532393572 -0700 @@ -132,6 +132,7 @@ MMDIR="/usr/local/mailman" TMPDIR="/tmp" +LOGDIR="/var/log/mailman" ############################################################################### # Maximum number of subdirectory entries to display in report @@ -234,9 +235,9 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG + $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG - if [ -f "logs/${LOG}" ] ; then + if [ -f "$LOGDIR/${LOG}" ] ; then if [ "${LOG}" = "post" ] ; then @@ -304,9 +305,9 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG + $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG - if [ -f "logs/${LOG}" ] ; then + if [ -f "$LOGDIR/${LOG}" ] ; then if [ "${LOG}" = "error" ] ; then @@ -453,4 +454,4 @@ $CAT $TMP fi -$RM $TMP +$RM -f $TMP $TMPLOG ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-11 04:16 Message: Logged In: YES user_id=1123998 I tried the script and other than the expected site specific changes, I found two issues which are both addressed by the patch in the mmdsr.patch file. 1) Mailman's log files are not necessarily in $var_prefix/logs/ - they can be in any directory. The patch adds a LOGDIR directory independant of MMDIR. 2) The $TMPLOG file is not removed at completion. The patch removes it. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-09-06 16:06 Message: Logged In: YES user_id=18417 Okay, I've deleted the old version of the mmdsr script that was attached, and uploaded the latest version. This is what we're currently using to monitor the lists on python.org, and we have found it very useful. Any comments you may have will be appreciated. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-02-22 21:10 Message: Logged In: YES user_id=18417 The UID variable in the current code was already replaced by MYUID, because I got complaints on other platforms. But UID wasn't available to me as a useful constant, so I had to use something else to obtain the value. The recommended patch from tgc99 does work, and I will be uploading a new version of the code soon. ---------------------------------------------------------------------- Comment By: adrianwi (adrianwi) Date: 2005-02-22 16:22 Message: Logged In: YES user_id=1175103 Use of variable named UID does work well with OS X (version 10.2.8). Apparently the variable UID is a constant already in use. When trying to the run the script without modification, I was receiving the following error message: UID: readonly variable This issue was resolved by changing the name of variable, UID, to something else, such as MMUID. Works fine with this change. As an aside (& for what it is worth), the UID grab command suggested by tgc99 on 2005-02-16 03:15 works on this system (OS X - version 10.2.8) ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-02-16 09:15 Message: Logged In: YES user_id=1159458 The current UID grab command doesn't work on Solaris (2.6 & 8 tested). I'd recommend this instead: ps -o user -p $$|tail -1 This is tested and works on RH 6.2, RH 7.3, RHEL 2.1, RHEL3, FC3, FreeBSD 4.9, Solaris 2.6, 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_…

1 0

[ mailman-Patches-1298355 ] Select language(s) when install
by SourceForge.net Oct. 19, 2005

Oct. 19, 2005

Patches item #1298355, was opened at 2005-09-21 22:29 Message generated for change (Comment added) made by gustavo_peters You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1298355&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: configure/install Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Select language(s) when install Initial Comment: While the number of translated languages is growing, most users are using only a few languages. With this patch, the site admin can select his/her required languages by an option to the configure script by `--with-languages' and can considerably reduce the install size. This patch is for 2.2.0a0 (most recent CVS as of writing) but also applicable to 2.1.6 except that you may have to regenerate configure script by invoing autoconf command. Patch usage: % cd mailman (src directory) % patch -p0 < /path/to/install_selected_language.patch.txt Configure usage: % ./configure --with-languages="ja fr" ... en+ja+fr % ./configure --with-languages="" ... all available languages % ./configure .... all available languages % ./configure --with-languages="none" ... English only Japanese and Korean codecs are no longer installed by `make install' but availability is checked during the configure run and urge to install if they are absent when CJK languages are included in the language list. I hope skilled developers can review this patch before I check in to the CVS. ---------------------------------------------------------------------- Comment By: Gustavo Peters (gustavo_peters) Date: 2005-10-18 18:08 Message: Logged In: YES user_id=1272569 dsfsdfdsf ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-09-21 22:35 Message: Logged In: YES user_id=67709 Oops, I forgot to check `Upload and Attach a File'. ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1298355&group_…

1 0