Mailman 3 January 2006 - Mailman-coders

[ mailman-Bugs-1305881 ] Problem creating list via web
by SourceForge.net Jan. 27, 2006

Jan. 27, 2006

Bugs item #1305881, was opened at 2005-09-27 15:49 Message generated for change (Comment added) made by jontek You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&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: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jon (jontek) Assigned to: Nobody/Anonymous (nobody) Summary: Problem creating list via web Initial Comment: I tried to create a list via: https://www.mydomain.dom/mailman/create. When filled all data, it replies with this message: ------------------------------------- Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 187, in process_request mlist.Create(listname, owner, pw, langs, emailhost) File "/usr/local/mailman/Mailman/MailList.py", line 457, in Create self.InitVars(name, admin, crypted_password) File "/usr/local/mailman/Mailman/MailList.py", line 372, in InitVars baseclass.InitVars(self) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/listname.mbox' Python information: Variable Value sys.version 2.3.4 (#2, Aug 6 2004, 21:29:10) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_REFERER https://www.mydomain.dom/mailman/create SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_perl/1.29 PHP/4.3.8 mod_ssl/2.8.19 OpenSSL/0.9.7d SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache/1.3.31 Server at www.mydomain.dom Port 443 REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 145 HTTP_ACCEPT_CHARSET ISO-8859-15,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Debian package 1.0.7-1) HTTP_CONNECTION keep-alive HTTP_COOKIE POSTNUKESID=4b502f13b908db42087f9b9753295c78; PHPSESSID=f7592dbf314acec6d743601e8cc3487f SERVER_NAME www.mydomain.dom REMOTE_ADDR 83.33.129.253 SERVER_PORT 443 SERVER_ADDR 207.228.236.31 DOCUMENT_ROOT /usr/local/www/data/www.mydomain.dom PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/create SERVER_ADMIN webmaster(a)mydomain.dom HTTP_HOST www.mydomain.dom HTTPS on REQUEST_URI /mailman/create HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 3249 HTTP_ACCEPT_LANGUAGE eu,es-es;q=0.7,es;q=0.3 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate UNIQUE_ID QzlLGc-k7B8AAR2b2MM --------------------------- Thanks JOn ---------------------------------------------------------------------- >Comment By: Jon (jontek) Date: 2006-01-27 11:12 Message: Logged In: YES user_id=1352490 Well, all the perms in both directories are mailman:mailman I have been create (check_perms says "all OK" but it isn't) the three directories: 1. #/usr/local/mailman/lists>mkdir listname 2. #/usr/local/mailman/archives/private>mkdir listname 3. #/usr/local/mailman/archives/private>mkdir listname.mbox 4. chown www (to the three) Will I change the directory owner to www? May that destroy or corrupt other lists? Thank you again. JOn ---------------------------------------------------------------------- Comment By: echoism (echoism) Date: 2006-01-05 16:34 Message: Logged In: YES user_id=1420107 I had this same problem. It is a permission issue, because the webserver doesn't have access to create a file in /usr/local/mailman/archives/private. This directory has permissions of 750, owned by the mailman user. The webserver, however, runs cgi scripts as nobody, not mailman. You can confirm this, by checking your /usr/local/mailman/lists directory, the list you tried to create should have a directory there, owned by nobody (or, whatever account your webserver uses), as the permissions for the lists directory permit write access. ---------------------------------------------------------------------- Comment By: Jon (jontek) Date: 2005-09-27 16:44 Message: Logged In: YES user_id=1352490 #/usr/local/mailman>/usr/local/mailman/bin/check_perms No problems found #/usr/local/mailman> ---------------------------------------------------------------------- Comment By: Jon (jontek) Date: 2005-09-27 16:32 Message: Logged In: YES user_id=1352490 Thanks but it doesn't still work. I have done: /usr/local/mailman/bin/check_perms -f and fixed all the problems, but it still doesn't work. :o( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-09-27 16:21 Message: Logged In: YES user_id=12800 Run bin/check_perms ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1305881&group_…

1 0

[ mailman-Patches-1415961 ] List bandwidth monitor
by SourceForge.net Jan. 27, 2006

Jan. 27, 2006

Patches item #1415961, was opened at 2006-01-26 22:41 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=1415961&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: command line scripts Group: None Status: Open Resolution: None Priority: 5 Submitted By: Bryan Carbonnell (carbonnb) Assigned to: Nobody/Anonymous (nobody) Summary: List bandwidth monitor Initial Comment: I needed a way to monitor the bandwidth usage for a specific list that I administer. Since there is no way in mailman to do this, I wrote a Python script to parse the POST log and take the size of the posts to a specific list and then multiply that by the number of active subscribers at the time this script was run. This gets the "stats" from the day before the script is run. These stats are only approximates, since digest users are counted as receiving the mail on the day that it was sent, even though it may not have. There are some constants at the top of the file that you will need to modify to uit your installation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1415961&group_…

1 0

[ mailman-Patches-1415956 ] Sitewide headers/footers & XHTML Compliant Web UI
by SourceForge.net Jan. 27, 2006

Jan. 27, 2006

Patches item #1415956, was opened at 2006-01-26 22:23 Message generated for change (Comment added) made by carbonnb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1415956&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Bryan Carbonnell (carbonnb) Assigned to: Nobody/Anonymous (nobody) Summary: Sitewide headers/footers & XHTML Compliant Web UI Initial Comment: This patch was borne out of a request I received to make the Mailman UI fit the look of the web site. This patch allows you to set a site wide header and footer. This allows you to pretty much make the MM UI look like any other site. While I was at it I also made the web UI XHTML compliant. Once you patch your source and install it, all you need to do is edit the html files in the templates/en directory. Most of the pages will get the header and footers from the site-header.html and site-footer.html files, but some of the HTML files already contain theor own header/footer so you will need ot edit some of these files as well. Since this also adds XHTML compliance, this superceeds patch #116035 ---------------------------------------------------------------------- >Comment By: Bryan Carbonnell (carbonnb) Date: 2006-01-26 22:31 Message: Logged In: YES user_id=449953 I am also uploading a second version of this patch. This second version will add the sitewide headers/footer to source that has been patched with the ht://dig integration patches. At the time I posted this, the official ht://dig integration patches were not released, but the MM2.1.6 patches appear to work with MM 2.1.7, so they are what were used. to apply this patch use this command from your mailman source directory: patch -p1 <full/path/to/headfoot-htdig-2.1.7-0.1.patch ---------------------------------------------------------------------- Comment By: Bryan Carbonnell (carbonnb) Date: 2006-01-26 22:27 Message: Logged In: YES user_id=449953 I have only tested this with the english pages. I'm not sure how to deal with i18n yet, but I'm reading and I will update this patch as soon as I figure out how to deal with it. To apply this patch for MM2.1.7, you will need to apply patch #1405790 (Mailman 2.1.7 multiple patch) first. to apply this patch use this command from your mailman source directory: patch -p1 <full/path/to/headfoot-2.1.7-0.1.patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1415956&group_…

1 0

[ mailman-Patches-1415956 ] Sitewide headers/footers & XHTML Compliant Web UI
by SourceForge.net Jan. 27, 2006

Jan. 27, 2006

Patches item #1415956, was opened at 2006-01-26 22:23 Message generated for change (Comment added) made by carbonnb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1415956&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Bryan Carbonnell (carbonnb) Assigned to: Nobody/Anonymous (nobody) Summary: Sitewide headers/footers & XHTML Compliant Web UI Initial Comment: This patch was borne out of a request I received to make the Mailman UI fit the look of the web site. This patch allows you to set a site wide header and footer. This allows you to pretty much make the MM UI look like any other site. While I was at it I also made the web UI XHTML compliant. Once you patch your source and install it, all you need to do is edit the html files in the templates/en directory. Most of the pages will get the header and footers from the site-header.html and site-footer.html files, but some of the HTML files already contain theor own header/footer so you will need ot edit some of these files as well. Since this also adds XHTML compliance, this superceeds patch #116035 ---------------------------------------------------------------------- >Comment By: Bryan Carbonnell (carbonnb) Date: 2006-01-26 22:27 Message: Logged In: YES user_id=449953 I have only tested this with the english pages. I'm not sure how to deal with i18n yet, but I'm reading and I will update this patch as soon as I figure out how to deal with it. To apply this patch for MM2.1.7, you will need to apply patch #1405790 (Mailman 2.1.7 multiple patch) first. to apply this patch use this command from your mailman source directory: patch -p1 <full/path/to/headfoot-2.1.7-0.1.patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1415956&group_…

1 0

[ mailman-Patches-1415956 ] Sitewide headers/footers & XHTML Compliant Web UI
by SourceForge.net Jan. 27, 2006

Jan. 27, 2006

Patches item #1415956, was opened at 2006-01-26 22:23 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=1415956&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Bryan Carbonnell (carbonnb) Assigned to: Nobody/Anonymous (nobody) Summary: Sitewide headers/footers & XHTML Compliant Web UI Initial Comment: This patch was borne out of a request I received to make the Mailman UI fit the look of the web site. This patch allows you to set a site wide header and footer. This allows you to pretty much make the MM UI look like any other site. While I was at it I also made the web UI XHTML compliant. Once you patch your source and install it, all you need to do is edit the html files in the templates/en directory. Most of the pages will get the header and footers from the site-header.html and site-footer.html files, but some of the HTML files already contain theor own header/footer so you will need ot edit some of these files as well. Since this also adds XHTML compliance, this superceeds patch #116035 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1415956&group_…

1 0

[ mailman-Feature Requests-1182014 ] forum like interface to mailman
by SourceForge.net Jan. 26, 2006

Jan. 26, 2006

Feature Requests item #1182014, was opened at 2005-04-12 22:40 Message generated for change (Comment added) made by mapopa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1182014&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 Submitted By: mariuz (mapopa) Assigned to: Nobody/Anonymous (nobody) Summary: forum like interface to mailman Initial Comment: one long term item would be creating an forum like interface for archives / mail The idea came to me after some users on mono list requested a forum for mono http://lists.ximian.com/mailman/listinfo/mono-list the basic forum interface (there are many others) http://www.gotmono.com/cgi-bin/yabb/YaBB.pl?board=ASPX ---------------------------------------------------------------------- >Comment By: mariuz (mapopa) Date: 2006-01-26 02:37 Message: Logged In: YES user_id=85089 Arioch /BDV/ wrote to me an email "I do not have my SF's password here, so i cannot comment ont bug-tracker yet. Can i ask You to add the following links tou You feature request ? F.Req: http://sourceforge.net/tracker/index.php?func=detail&aid=1182014&group_id=1… 1) www.FudForum.org - PHP-based WWW-forum, who claims of a feature to be a front-end for nntp and maillist's 2) http://comments.gmane.org/gmane.discuss/7911 This is my long-standing dream, it was even registered on SourceForge's bug-tracker. Alas, later removed. Perhaps this can be achived using "external membership sources", but other from root page of mailman.sf.net i could not find any reference|description what it is. If it ws implemented, i guess Mailman, Sourceforge and Gmane were in benefit all :) " ---------------------------------------------------------------------- Comment By: mariuz (mapopa) Date: 2005-08-30 00:24 Message: Logged In: YES user_id=85089 On ubuntuforums.org they have two way between mailman and vbulletin Here is the example http://ubuntuforums.org/showthread.php?t=60843 ---------------------------------------------------------------------- Comment By: Fred H Olson (fholson) Date: 2005-08-24 00:57 Message: Logged In: YES user_id=1334022 There is an open source development project similar to this: GroupServer is a GPL open source collaboration server. It supports many-to-many interaction in groups and communities via email and an integrated web forum interface. See http://groupserver.org/ How much do mailman and groupserver developers communicate? Has collaboration of some sort been considered? Fred Olson http://justcomm.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1182014&group_…

1 0

[ mailman-Patches-1123383 ] Daily Status Report script...
by SourceForge.net Jan. 26, 2006

Jan. 26, 2006

Patches item #1123383, was opened at 2005-02-15 20:14 Message generated for change (Comment added) made by shub 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: Brad Knowles (shub) Date: 2006-01-26 01:55 Message: Logged In: YES user_id=18417 Folks, Okay, I just uploaded version 0.0.15, which addresses the most recent comments here from Mark and Tom, and makes a few additional tweaks as well. See the version comments at the top of the script. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-11-06 18:25 Message: Logged In: YES user_id=1123998 The vette log summary lists posts held for moderation individually under "Other Errors:". The following patch (watch out for wrapped lines) summarizes them by list instead. --- mmdsr 2005-09-29 21:31:33.000000000 -0700 +++ mmdsrx 2005-11-06 08:20:58.835895418 -0800 @@ -415,10 +415,15 @@ echo "------------------------------" >> $TMP $GREP -i 'Posting to a moderated newsgroup' $TMPLOG | $AWK '{ print $6 }' | $SORT | $UNIQ -c | $SORT -nr >> $TMP + echo "" >> $TMP + echo "Post to moderated list (by list):" >> $TMP + echo "------------------------------" >> $TMP + $GREP -i 'Post to moderated list' $TMPLOG | $AWK '{ print $6 }' | $SORT | $UNIQ -c | $SORT -nr >> $TMP + echo "" >> $TMP echo "Other Errors:" >> $TMP echo "------------------------------" >> $TMP - $EGREP -vi '(Post by non-member|suspicious header|message approved|Discarded posting|bulk message discarded|junk message discarded|Message has implicit destination|Posting to a moderated newsgroup|Message discarded, msgid)' $TMPLOG | $SED 's/^.* ([0-9]*) //' | $SORT | $UNIQ -c | $SORT -nr >> $TMP + $EGREP -vi '(Post by non-member|suspicious header|message approved|Discarded posting|bulk message discarded|junk message discarded|Message has implicit destination|Posting to a moderated newsgroup|Post to moderated list|Message discarded, msgid)' $TMPLOG | $SED 's/^.* ([0-9]*) //' | $SORT | $UNIQ -c | $SORT -nr >> $TMP else ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-10-19 08: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-22 23: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 02: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 02: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 14: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 20: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 15: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 08: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-Bugs-1411656 ] 2.1.7 not available from gnu or list.org
by SourceForge.net Jan. 21, 2006

Jan. 21, 2006

Bugs item #1411656, was opened at 2006-01-21 19:23 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=1411656&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 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.7 not available from gnu or list.org Initial Comment: list.org/download.html has links to retrieve the latest release from "GNU" and "list.org", but neither of these are up to date. ftp.gnu.org has only 2.1.5, and the list.org mailman.tar.gz unpacked into 2.1.6. Best, Karl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1411656&group_…

1 0

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

Jan. 19, 2006

Patches item #657951, was opened at 2002-12-23 13:17 Message generated for change (Comment added) made by ssrjazz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 9 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: Jeff Schoby (ssrjazz) Date: 2006-01-19 13:32 Message: Logged In: YES user_id=198250 Does anyone have any idea why when I run ~mailman/bin/arch <listname> it will generate the rss.xml file, but when new emails come in to said list it doesn't do ANYTHING with the xml file? I'd like for the rss feed to update itself every time a new post comes into a list. Right now it isn't doing that. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-12-06 12:01 Message: Logged In: YES user_id=75166 The following is based on the July 2003 version of the patch file posted on sourceforge. The RSS patch adds the RSS() function as member function of the HyperArchive class defined in HyperArch.py. It has been reported that the following statement in RSS(): date, msgid = self.database.dateIndex.first() may generate an AttributeError exception: AttributeError: HyperDatabase instance has no attribute 'dateIndex' The RSS patch appears to make the assumption that whenever the RSS() function is called from the write_TOC() member function of the HyperArchive class the __openIndices() function has already been called on the latest period archive associated with the list, whose TOC page is being generated by write_TOC(), and that no intervening call to __closeIndices() has been made. If the assumption were correct then whenever the RSS() function was called on a HyperArchive instance, the xxxxxIndices attributes of the HyperDatabase instance "owned" by the HyperArchive instance would be pointing to valid instance of DumbBTree. Unfortunately, this assumption is not correct. In order to do its work, write_TOC() does not itself need to perform any call to the __openIndices() function for the list/archive/database whose TOC page is to be recreated. It just happens that in some circumstances, some of the code which might call write_TOC may have called the __openIndices() function at some prior point and left the HyperDatabase instance with a valid set of xxxxxIndices attributes in place when write_TOC() is called. For the RSS patch to be work reliably the code in the RSS() function has to be changed so that it ensures that the conditions it wants prevail when it executes the statement giving the problem. The following is an untested code change but if part of the RSS() function's code definition in HyperArch.py is modified from: <quote> # Get the most recent messages. The only index operation # we can count on is traversal by increasing date, so # we end up traversing all of the entries and remembering the last # N of them. Sigh. items = [] try: date, msgid = self.database.dateIndex.first() items.append(msgid) except KeyError: pass while 1: try: </quote> to read: <quote> # Get the most recent messages. The only index operation # we can count on is traversal by increasing date, so # we end up traversing all of the entries and remembering the last # N of them. Sigh. items = [] got_first = 0 try: msgid = self.database.first(self.archives[0], 'date') if msgid: items.append(msgid) got_first = 1 except KeyError: pass while got_first and 1: try: </quote> this should fix the exception problem. ---------------------------------------------------------------------- Comment By: Roy M. Silvernail (codewhacker) Date: 2003-12-23 13:35 Message: Logged In: YES user_id=670974 I'm trying to enrich the RSS output by adding a proper [description] and a [content:encoded] module, but I am having the devil's own time locating the raw message text. Be happy to contribute a patch if you can point me to the raw content (without the italics markup for quoting). Thanks! ---------------------------------------------------------------------- Comment By: Michael Weber (wookiew) Date: 2003-09-10 11:29 Message: Logged In: YES user_id=863445 So far the patch is included (by the way: i hope that Defaults.py.in in the patch *means* Defaults.py ) and mailman get a restart. Hopefully i add the two lines in listinfo.html ( /de/ because we have german speaking lists) and take a look for the xml file). After search the whole device (only to be sure) i can say: There is no file like this. Is another patch need before? Another setup to make? I cant find any hint here... so i have to ask. But the idea is great... if it work on my lists its genious... regards, Michael running version 2.1.1 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-09-01 23:15 Message: Logged In: YES user_id=12800 Bumping priority. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-15 13:55 Message: Logged In: YES user_id=11375 OK, done! This patch is now ready to go in: some people have looked at the RSS and haven't spotted any problems. Barry, can I please get CVS write access to check this in? ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 20:00 Message: Logged In: YES user_id=11375 Attaching correct version of the patch. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 19:52 Message: Logged In: YES user_id=11375 Here at last is an updated version of the patch that's crawling closer to being complete. There's now a RSS_NUM_ARTICLES setting in Defaults.py, the generated URLs are correct, and I modified the English template to link to the RSS file. Remaining things: check the generated RSS for correctness; edit all of the other language templates to include the RSS file (I may ask for CVS write access to do that). It would be really nice if the Mailman upgrade script could update existing general list information pages to include the LINK element; any suggestion about how to go about that? ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 10:00 Message: Logged In: YES user_id=7830 OK, I've regenerated the patch with some code which works for me. http://rdfweb.org/2003/06/mailman-rss/rsspatch Health warning: * I suspect it may fail in conditions when get_archives() returns a list not a string (does this ever happen?). * See also problems mentioned below, regenerating partial archives seems tricky. Hope this is useful anyways... Dan <danbri(a)w3.org> ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 06:48 Message: Logged In: YES user_id=7830 I thought I'd have a look at this myself, though have modest knowledge of both Python and MailMan. In the course of trying to patch the patch, I tried running the archiver over just the last couple of messages, to speed things along: "../../bin/arch -s 4390 rdfweb-dev". Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 310, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1082, in write_TOC rss.write(self.RSS()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 769, in RSS date, msgid = self.database.dateIndex.first() AttributeError: HyperDatabase instance has no attribute 'dateIndex' Not sure what's going on there, but this seemed as good a place of any to keep note of it. Investigating... ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 06:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 17: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 15: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 19: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 14: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 13: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 13:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 13: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-Bugs-1408801 ] mail with special characters not archived on pipermail
by SourceForge.net Jan. 18, 2006

Jan. 18, 2006

Bugs item #1408801, was opened at 2006-01-17 23:22 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1408801&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: Pipermail Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Jericho (jericho001) Assigned to: Nobody/Anonymous (nobody) Summary: mail with special characters not archived on pipermail Initial Comment: Mail with the following text: MÃ¥ns ÃhrstrÃ¶m Will not be archived on the list archive (via Pipermail). No warning or errors are generated, nothing in the logs to show the failure (that I could see). Converting the special chars to the approximate letters "Mans Ohrstrom" allowed the mail to reach the archive. Delivered by Mailman version 2.1.7rc1 ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-01-18 07:10 Message: Logged In: YES user_id=1123998 There is a bug in this area in the 2.1.7 release, but it will log an error and shunt the message (1395683) <https://sourceforge.net/tracker/index.php?func=detail&aid=1395683&group_id=…> I suggest you get the 2.1.7 final release and apply the cumulative patch (1405790) <https://sourceforge.net/tracker/index.php?func=detail&aid=1405790&group_id=…> or update to the latest CVS and see if the problem still exists. Also note that if it is bug 1395683, an htmlized message would have been created at archives/private/LIST_NAME/yyyy-Month/nnnnnn.html, but it would not be linked from any of the html index files. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1408801&group_…

1 0