From noreply at sourceforge.net Tue Jan 1 06:01:51 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 31 Dec 2007 21:01:51 -0800 Subject: [ mailman-Bugs-1861600 ] zh_TW options even lacks SUBMIT button Message-ID: Bugs item #1861600, was opened at 2008-01-01 13:01 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=1861600&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: zh_TW options even lacks SUBMIT button Initial Comment: Gentlemen, observe the deformed child among $ grep -ihc button mailman-2.1.10b1/templates/*/options.html|xargs 26 26 26 26 26 28 26 25 26 22 26 26 26 26 28 26 26 25 26 27 26 26 26 26 26 27 26 26 26 26 26 26 26 26 14 Yes at the very end, 14. Might as well just $ iconv -t gb2312 templates/zh_CN/options.html|iconv -f gb2312 -t big5| iconv -f big5 > templates/zh_TW/options.html It's better than a form without a submit button. Who knows how many other parts of mailman lack an eye here, a leg there... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1861600&group_id=103 From noreply at sourceforge.net Thu Jan 3 17:11:31 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 03 Jan 2008 08:11:31 -0800 Subject: [ mailman-Feature Requests-1863246 ] command-line tool consistency Message-ID: Feature Requests item #1863246, was opened at 2008-01-03 11:11 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1863246&group_id=103 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: Steve Burling (srburling) Assigned to: Nobody/Anonymous (nobody) Summary: command-line tool consistency Initial Comment: Could the command-line tools be made consistent in their lower-casing of list names? Right now, for example, if you use the name output by list_lists (which seems to be the "pretty" name) as input to list_members, list_members lower-cases the input and properly lists the members. list_owners and list_admins, on the other hand, don't, although their failure modes are different. There may be other commands that have this problem, these are just the two that I stumbled across today. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1863246&group_id=103 From noreply at sourceforge.net Thu Jan 3 18:33:29 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 03 Jan 2008 09:33:29 -0800 Subject: [ mailman-Patches-1123383 ] Daily Status Report script... Message-ID: Patches item #1123383, was opened at 2005-02-15 12:14 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 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 Private: No 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: Mark Sapiro (msapiro) Date: 2008-01-03 09:33 Message: Logged In: YES user_id=1123998 Originator: NO File Added: mmdsr ---------------------------------------------------------------------- Comment By: Dave Yost (daveyost) Date: 2007-01-12 23:32 Message: Logged In: YES user_id=330919 Originator: NO I suggest incorporating the readme into the shell script, so there is only the one file. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2006-01-25 17: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 10: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 01: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 16: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-10 19: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-10 19: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 07: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 12: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 07: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 00: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_id=103 From noreply at sourceforge.net Thu Jan 3 18:59:12 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 03 Jan 2008 09:59:12 -0800 Subject: [ mailman-Bugs-1863311 ] admlogin.html puts "MailmanLogo" *after* the Message-ID: Bugs item #1863311, was opened at 2008-01-03 17:59 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=1863311&group_id=103 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: Trent Mick (tmick) Assigned to: Nobody/Anonymous (nobody) Summary: admlogin.html puts "MailmanLogo" *after* the Initial Comment: Mailman version: 2.1.9 The admlogin.html page puts the MailmanLogo() generated footer content *after* the close of the "body" and "html" tags. E.g.: http://mail.python.org/mailman/admin/mailman-users ---------------------------- ...
Mailman-Users list run by barry at list.org, brad at python.org
Mailman-Users administrative interface (requires authorization)
Overview of all python.org mailing lists

Delivered by Mailman
version 2.1.9		 Python Powered GNU's Not Unix

---------------------------- Although browsers tend to handle this broken HTML, it foils attempts to use Apache mod_layout to add a footer (because it looks for and insert footer content there. See this bug for more details: http://bugs.activestate.com/show_bug.cgi?id=73613 (It is a bug documenting the broken result attempting to use Apache mod_layout with this on a mailman installation for openkomodo.com.) >From that bug: -------------------------- ... The right answer would be to use the "" template marker in the "admlogin.html" template **however**, that won't work because "admlogin.html" is using a different template mechanism than some of the other ".html" files in there. "" will get replaced in, e.g., "listinfo.html", but not in "admlogin.html" ... -------------------------- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1863311&group_id=103 From noreply at sourceforge.net Thu Jan 3 20:33:41 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 03 Jan 2008 11:33:41 -0800 Subject: [ mailman-Feature Requests-1863246 ] command-line tool consistency Message-ID: Feature Requests item #1863246, was opened at 2008-01-03 08:11 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1863246&group_id=103 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: Fixed Priority: 5 Private: No Submitted By: Steve Burling (srburling) Assigned to: Nobody/Anonymous (nobody) Summary: command-line tool consistency Initial Comment: Could the command-line tools be made consistent in their lower-casing of list names? Right now, for example, if you use the name output by list_lists (which seems to be the "pretty" name) as input to list_members, list_members lower-cases the input and properly lists the members. list_owners and list_admins, on the other hand, don't, although their failure modes are different. There may be other commands that have this problem, these are just the two that I stumbled across today. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-01-03 11:33 Message: Logged In: YES user_id=1123998 Originator: NO This report duplicates that in Patch 1842412. Fixed in Mailman 2.1.10. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1863246&group_id=103 From noreply at sourceforge.net Thu Jan 3 20:34:20 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 03 Jan 2008 11:34:20 -0800 Subject: [ mailman-Patches-1123383 ] Daily Status Report script... Message-ID: Patches item #1123383, was opened at 2005-02-15 12:14 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 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 Private: No 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: Mark Sapiro (msapiro) Date: 2008-01-03 11:34 Message: Logged In: YES user_id=1123998 Originator: NO I have added two files. Version 0.0.16 corrects a couple of typo/minor issues. It is the version that has been in the contrib directory of the distribution since Mailman 2.1.8. Version 0.0.17 processes two generations of rotated logs (assuming they are named xxx and xxx.1 and xxx.1 exists) so that data is not lost on the day the logs rotate. It also changes a deprecated sort key option to one that should work with all sort commands. This version will be in the contrib directory of the Mailman 2.1.10 distribution. File Added: mmdsr ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2008-01-03 09:33 Message: Logged In: YES user_id=1123998 Originator: NO File Added: mmdsr ---------------------------------------------------------------------- Comment By: Dave Yost (daveyost) Date: 2007-01-12 23:32 Message: Logged In: YES user_id=330919 Originator: NO I suggest incorporating the readme into the shell script, so there is only the one file. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2006-01-25 17: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 10: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 01: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 16: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-10 19: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-10 19: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 07: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 12: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 07: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 00: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_id=103 From noreply at sourceforge.net Fri Jan 4 03:38:31 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 03 Jan 2008 18:38:31 -0800 Subject: [ mailman-Patches-1123383 ] Daily Status Report script... Message-ID: Patches item #1123383, was opened at 2005-02-15 12:14 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 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 Private: No 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: Mark Sapiro (msapiro) Date: 2008-01-03 18:38 Message: Logged In: YES user_id=1123998 Originator: NO Re-did the 0.0.17 change to use the prior sort key field separator by default but to make it a user settable parameter. File Added: mmdsr ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2008-01-03 11:34 Message: Logged In: YES user_id=1123998 Originator: NO I have added two files. Version 0.0.16 corrects a couple of typo/minor issues. It is the version that has been in the contrib directory of the distribution since Mailman 2.1.8. Version 0.0.17 processes two generations of rotated logs (assuming they are named xxx and xxx.1 and xxx.1 exists) so that data is not lost on the day the logs rotate. It also changes a deprecated sort key option to one that should work with all sort commands. This version will be in the contrib directory of the Mailman 2.1.10 distribution. File Added: mmdsr ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2008-01-03 09:33 Message: Logged In: YES user_id=1123998 Originator: NO File Added: mmdsr ---------------------------------------------------------------------- Comment By: Dave Yost (daveyost) Date: 2007-01-12 23:32 Message: Logged In: YES user_id=330919 Originator: NO I suggest incorporating the readme into the shell script, so there is only the one file. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2006-01-25 17: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 10: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 01: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 16: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-10 19: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-10 19: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 07: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 12: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 07: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 00: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_id=103 From noreply at sourceforge.net Tue Jan 8 03:16:20 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 07 Jan 2008 18:16:20 -0800 Subject: [ mailman-Bugs-1866473 ] make logos clickable Message-ID: Bugs item #1866473, was opened at 2008-01-08 10:16 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=1866473&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: make logos clickable Initial Comment: The three logos at the bottom of most mailman screens: users are used to being able to click on things for more information, so make them clickable. Or maybe you fear sending beginners on to tangents. How often does one see a non-clickable logo these days?! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866473&group_id=103 From noreply at sourceforge.net Tue Jan 8 03:19:30 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 07 Jan 2008 18:19:30 -0800 Subject: [ mailman-Bugs-1866475 ] Do in Makefile: create install dir, check_perms Message-ID: Bugs item #1866475, was opened at 2008-01-08 10:19 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=1866475&group_id=103 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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Do in Makefile: create install dir, check_perms Initial Comment: Why can't the step in mailman-install/create-install-dir.html be instead done via make install? Just use --prefix's value. check_perms -f should also be done by the Makefile. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866475&group_id=103 From noreply at sourceforge.net Tue Jan 8 03:22:22 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 07 Jan 2008 18:22:22 -0800 Subject: [ mailman-Bugs-1866476 ] check_perms -f counts problems it just fixed Message-ID: Bugs item #1866476, was opened at 2008-01-08 10:22 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=1866476&group_id=103 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: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: check_perms -f counts problems it just fixed Initial Comment: Even upon -f, check_perms says "Problems found: 69 Re-run as norbelwitz (or root) with -f flag to fix" even though it just fixed them, as a third run without -f proves. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866476&group_id=103 From noreply at sourceforge.net Tue Jan 8 03:25:57 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 07 Jan 2008 18:25:57 -0800 Subject: [ mailman-Bugs-1866479 ] INSTALL points to non-existent documentation Message-ID: Bugs item #1866479, was opened at 2008-01-08 10:25 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=1866479&group_id=103 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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: INSTALL points to non-existent documentation Initial Comment: INSTALL says All manuals within this source distribution are provided in the admin/www directory: HTML : admin/www/mailman-install/index.html PostScript : admin/www/mailman-install.ps PDF : admin/www/mailman-install.pdf plain text : admin/www/mailman-install.txt when all along there are no such paths "admin/www". Sure, one eventually find a LaTeX file, with no instructions on how to convert it to say HTML to read. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866479&group_id=103 From noreply at sourceforge.net Tue Jan 8 03:28:04 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 07 Jan 2008 18:28:04 -0800 Subject: [ mailman-Bugs-1866480 ] FAQ mentions non-existent READMEs Message-ID: Bugs item #1866480, was opened at 2008-01-08 10:28 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=1866480&group_id=103 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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: FAQ mentions non-existent READMEs Initial Comment: Only one of these exist: $ fgrep README. FAQ README.EXIM for details. Other MTAs have (of course) also README.USERAGENT for more information. See README.QMAIL A. See the README.LINUX file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866480&group_id=103 From noreply at sourceforge.net Tue Jan 8 03:31:24 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 07 Jan 2008 18:31:24 -0800 Subject: [ mailman-Bugs-1866481 ] Preserve dates in source Message-ID: Bugs item #1866481, was opened at 2008-01-08 10:31 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=1866481&group_id=103 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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Preserve dates in source Initial Comment: When one downloads and untars, one finds all the file timestamps are the same. Please preserve the original dates of last edit. Figure out a way, don't throw away information. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866481&group_id=103 From noreply at sourceforge.net Tue Jan 8 03:35:38 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 07 Jan 2008 18:35:38 -0800 Subject: [ mailman-Bugs-1866484 ] Must provide logout buttons on every page Message-ID: Bugs item #1866484, was opened at 2008-01-08 10:35 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=1866484&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Must provide logout buttons on every page Initial Comment: All pages (that one needs a cookie to get to) must provide logout buttons! E.g., no logout provided on admindb.cgi. Would a real company have a members only area with no logout button on the panel? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866484&group_id=103 From noreply at sourceforge.net Tue Jan 8 03:40:47 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 07 Jan 2008 18:40:47 -0800 Subject: [ mailman-Bugs-1866486 ] validate HTML and email produced Message-ID: Bugs item #1866486, was opened at 2008-01-08 10:40 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=1866486&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: validate HTML and email produced Initial Comment: In your test suite add for all languages for all HTML pages run them thru a HTML validator for all administrative email sent run them thru e.g., SpamAssassin, to detect SUBJECT_NEEDS_ENCODING etc. embarrassment. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866486&group_id=103 From noreply at sourceforge.net Tue Jan 8 04:02:14 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 07 Jan 2008 19:02:14 -0800 Subject: [ mailman-Bugs-1866479 ] INSTALL points to non-existent documentation Message-ID: Bugs item #1866479, was opened at 2008-01-07 18:25 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866479&group_id=103 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: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: INSTALL points to non-existent documentation Initial Comment: INSTALL says All manuals within this source distribution are provided in the admin/www directory: HTML : admin/www/mailman-install/index.html PostScript : admin/www/mailman-install.ps PDF : admin/www/mailman-install.pdf plain text : admin/www/mailman-install.txt when all along there are no such paths "admin/www". Sure, one eventually find a LaTeX file, with no instructions on how to convert it to say HTML to read. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-01-07 19:02 Message: Logged In: YES user_id=1123998 Originator: NO This was an oversight in preparing the 2.1.10b1 release. It will be corrected in subsequent releases. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866479&group_id=103 From noreply at sourceforge.net Tue Jan 8 19:07:16 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Jan 2008 10:07:16 -0800 Subject: [ mailman-Bugs-1867104 ] missing MIME decodes for Subject headers Message-ID: Bugs item #1867104, was opened at 2008-01-09 03:07 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=1867104&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: nagae (nagaehidetake) Assigned to: Nobody/Anonymous (nobody) Summary: missing MIME decodes for Subject headers Initial Comment: There are some missing MIME decodes for Subject headers. I found this problem in the following programs (as the result of searching "%(subject)s" in LC_MESSAGES). * reject notification mail for held messages Mailman/ListAdmin.py * cancel confirmation and cancel result screen for held messages Mailman/Cgi/confirm.py * archived HTML for forwarded mails in the style of message/rfc822 attachment Mailman/Handlers/Scrubber.py A patch for Mailman 2.1.9 is attached. Original discussion in the ML mmjp-users (Japanese Mailman users) is: http://mm.tkikuchi.net/pipermail/mmjp-users/2008-January/002256.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867104&group_id=103 From noreply at sourceforge.net Wed Jan 9 00:13:05 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Jan 2008 15:13:05 -0800 Subject: [ mailman-Bugs-1867275 ] more exact than List-Archive Message-ID: Bugs item #1867275, was opened at 2008-01-09 07:13 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=1867275&group_id=103 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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: more exact than List-Archive Initial Comment: Gentlemen, $ w3m -dump http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/33295/raw |grep Archive List-Archive: Archived-At: This means: mailman could, if it tried harder, put a header into the message with the exact URL of where it archived the message at, instead of just its current "go look thru the heap, Holmes" Archived-At header. Instead users will quote a 3rd party (gmane.org here), which might go belly up at any time, when referring to the article. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867275&group_id=103 From noreply at sourceforge.net Wed Jan 9 00:16:55 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Jan 2008 15:16:55 -0800 Subject: [ mailman-Bugs-1867277 ] where the moderator is to login Message-ID: Bugs item #1867277, was opened at 2008-01-09 07:16 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=1867277&group_id=103 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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: where the moderator is to login Initial Comment: Allow me to point out that once we have grasped the fact that there is both a moderator and an administrator, it then becomes very hard to find out where the moderator is supposed to login. See patch. You might want to mention it too on the screens that talk about the moderator. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867277&group_id=103 From noreply at sourceforge.net Wed Jan 9 00:20:52 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Jan 2008 15:20:52 -0800 Subject: [ mailman-Bugs-1867279 ] Approved header password worries Message-ID: Bugs item #1867279, was opened at 2008-01-09 07:20 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=1867279&group_id=103 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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Approved header password worries Initial Comment: [Entering my bug into the tiny window might have folded the lines. Good thing I now have ADSL, as you don't accept bugs by email.] At many places one sees Messages containing an Approved: header with the list owner password are still allowed through or Then, when the message shows up in your mailbox, make your edits and resend the message to the list, including an Approved: header with the list password as its value. or Which promptly gets sent to the list, one then thinks. List password or moderator password or both etc. or more in templates/* etc. The user thinks "oh great, the software intends so ever nonchalantly to send the master password in all four directions." Therefore remember to assure the user each time you broach the issue, that the password will be replaced by and he can be rest assured, etc. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867279&group_id=103 From noreply at sourceforge.net Wed Jan 9 00:23:43 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Jan 2008 15:23:43 -0800 Subject: [ mailman-Bugs-1867281 ] Patch for --configure discussion Message-ID: Bugs item #1867281, was opened at 2008-01-09 07: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=1867281&group_id=103 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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Patch for --configure discussion Initial Comment: See patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867281&group_id=103 From noreply at sourceforge.net Wed Jan 9 00:33:22 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Jan 2008 15:33:22 -0800 Subject: [ mailman-Bugs-1867285 ] FAQ: really need root? Message-ID: Bugs item #1867285, was opened at 2008-01-09 07:33 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=1867285&group_id=103 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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: FAQ: really need root? Initial Comment: Add to FAQ: Q: Surely I could install mailman on my web shared hosting plan without root. I'll just use --with-username=$USER --with-groupname=`id -g` ... --with-cgi-ext=.cgi etc. and then use my .procmailrc to redirect what comes to the extra mailboxes my hosting plan allows me to make... A: Ah but Holmes, you have neglected a fundamental... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867285&group_id=103 From noreply at sourceforge.net Wed Jan 9 00:36:20 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Jan 2008 15:36:20 -0800 Subject: [ mailman-Bugs-1867286 ] man newlist touchup Message-ID: Bugs item #1867286, was opened at 2008-01-09 07:36 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=1867286&group_id=103 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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: man newlist touchup Initial Comment: $ man newlist SYNOPSIS newlist [options] listname listadmin-addr admin-password NOTES You can specify as many of the arguments as you want on the command line: you will be prompted for the missing ones. ***OK, then say newlist [options] [listname] [listadmin-addr] [admin-password] OPTIONS -l language, --language=language Make the list's preferred language `language', which must be a two letter language code. ***But there are TWO kinds of Chinese! zh_CN zh_TW, etc. That's more than TWO letters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867286&group_id=103 From noreply at sourceforge.net Wed Jan 9 00:42:58 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 08 Jan 2008 15:42:58 -0800 Subject: [ mailman-Bugs-1867289 ] administration language married to list language Message-ID: Bugs item #1867289, was opened at 2008-01-09 07:42 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=1867289&group_id=103 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: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: administration language married to list language Initial Comment: Various administrators of the same list would like to interact with the web interface in various languages, independent of the list settings... Take like Wikipedia, one can browse and administer ZH.wikipedia.org in English, by using EN in one's preferences. But with mailman, no no no, you'll be administering in zh_TW, because your list is a zh_TW list. "What could be simpler?" :-( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867289&group_id=103 From noreply at sourceforge.net Thu Jan 10 22:41:01 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 10 Jan 2008 13:41:01 -0800 Subject: [ mailman-Bugs-1868873 ] deceptive listinfo "to post a message..." Message-ID: Bugs item #1868873, was opened at 2008-01-11 05:41 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=1868873&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: security/privacy Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: deceptive listinfo "to post a message..." Initial Comment: Allow me to introduce the primary bug of all, the one that is certainly the first one encounters upon first contact with mailman as a mere user. He sees on the listinfo web page: "To post a message to all the list members, send email to ..." Which means TO HIM, the innocent victim, that "posting is wide open. What ever you send will get full executive treatment and be sent to all members and the archive forthwith". When in fact it really means "Yes, we say 'to post', but to post is not to receive, necessarily. I.E., depending on policies, your message might 1. go to /dev/null, 2. go to /dev/null with a notice back to you, 3. go into a queue for moderator approval, 4. as 3 but with a notice back to you, 5.... and it all depends on the configuration, which the moderator/administrator has elected not to make public, i.e., one of 1,2,3,4... will happen, and we could tell you here, but we won't. So what happens, is due to the *deceptive* message "To post a message to all the list members, send email to ..." the user posts and waits several days not knowing what is happening, while his burning question lies unseen who knows where. If subscription is required to post, than say "subscription is required to post". If you are not willing to mention that subscription is or is not required, in an effort to thwart spammers, then say "subscription may be required to post". Anyway, the software is very aware of just what requirements there are to post, so it should say them there on listinfo, unless the administrator has checked "[x]Obfuscate posting requirements on listinfo page". Whereupon say "subscription may be required to post, but the administrator has chosen not to reveal what they may be." Anyway, in no case continue saying "To post a message to all the list members, send email to ..." as it looks like the current message. If the list is really wide open, say "Membership not required to post"... Don't just reply to this bug saying to ask the administrator to edit the HTML files for his site, as the forwarding in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=199195 probably thought. Tell them to edit the HTML if checking the above [x] box is not enough. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1868873&group_id=103 From noreply at sourceforge.net Thu Jan 10 22:47:00 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 10 Jan 2008 13:47:00 -0800 Subject: [ mailman-Bugs-1867285 ] FAQ: really need root? Message-ID: Bugs item #1867285, was opened at 2008-01-09 07:33 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867285&group_id=103 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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: FAQ: really need root? Initial Comment: Add to FAQ: Q: Surely I could install mailman on my web shared hosting plan without root. I'll just use --with-username=$USER --with-groupname=`id -g` ... --with-cgi-ext=.cgi etc. and then use my .procmailrc to redirect what comes to the extra mailboxes my hosting plan allows me to make... A: Ah but Holmes, you have neglected a fundamental... ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-11 05:47 Message: Logged In: YES user_id=1971011 Originator: YES Add to Q: And for sending mail I can use /usr/sbin/sendmail -i -f ... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867285&group_id=103 From noreply at sourceforge.net Sun Jan 13 10:40:50 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 13 Jan 2008 01:40:50 -0800 Subject: [ mailman-Bugs-1870246 ] sync_members just failes if even 1 email address is invalid Message-ID: Bugs item #1870246, was opened at 2008-01-13 18:40 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=1870246&group_id=103 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: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tony Mobily (mercmobily) Assigned to: Nobody/Anonymous (nobody) Summary: sync_members just failes if even 1 email address is invalid Initial Comment: Hi, Right now, sync_members just fails if there are invalid email addresses. I wrote a Drupal module that uses mailman to send emails. The problem I have is that I am using sync_members automatically, and it would be 100 times easier for me if the invalid email addresses were ignored, rather than the whole script failing. The code is: # first filter out any invalid addresses filemembers = email.Utils.getaddresses(filemembers) invalid = 0 for name, addr in filemembers: try: Utils.ValidateEmail(addr) except Errors.EmailAddressError: print _('Invalid : %(addr)30s') invalid = 1 if invalid: print _('You must fix the preceding invalid addresses first.') sys.exit(1) I think having a command line option for this would be fantastic - something like "-i" ("ignore invalid email addresses"), which if selected makes sure that the script simply ignores invalid email addresses, and basically "always works" (unless of course the mailing list name is wrong, etc.). I don't know python at all (shame on me), or I swear I'd be submitting a patch (I am a Drupal developer, and submit patches whenever I can). Thank you!!! Merc. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1870246&group_id=103 From noreply at sourceforge.net Thu Jan 17 02:17:11 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 16 Jan 2008 17:17:11 -0800 Subject: [ mailman-Bugs-1861600 ] whole HTML templates approach wrong Message-ID: Bugs item #1861600, was opened at 2008-01-01 13:01 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1861600&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) >Summary: whole HTML templates approach wrong Initial Comment: Gentlemen, observe the deformed child among $ grep -ihc button mailman-2.1.10b1/templates/*/options.html|xargs 26 26 26 26 26 28 26 25 26 22 26 26 26 26 28 26 26 25 26 27 26 26 26 26 26 27 26 26 26 26 26 26 26 26 14 Yes at the very end, 14. Might as well just $ iconv -t gb2312 templates/zh_CN/options.html|iconv -f gb2312 -t big5| iconv -f big5 > templates/zh_TW/options.html It's better than a form without a submit button. Who knows how many other parts of mailman lack an eye here, a leg there... ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-17 09:17 Message: Logged In: YES user_id=1971011 Originator: YES Gentlemen, I have figured out how to use the poorly documented transcheck command, and the winner is.... $ for i in $(cd messages;ls); do echo -n $i:\ ; bin/transcheck -q $i;done ar: 15 warnings in 2 files ca: 51 warnings in 4 files cs: 2 warnings in 1 files da: 17 warnings in 2 files de: 38 warnings in 10 files es: 40 warnings in 6 files ja: 0 warnings in 0 files ... sv: 50 warnings in 2 files tr: 21 warnings in 2 files uk: 17 warnings in 2 files vi: 9 warnings in 3 files zh_CN: 31 warnings in 4 files zh_TW: 93 warnings in 10 files That's right, zh_TW, another gold medal. Actually it appears your whole approach is wrong. With entire .html and .txt files to be translated, there will always be missing buttons, etc. If instead using just strings in .po files, if a message isn't translated, at least the English will be shown to the user. Anyway how terrible to have unlucky languages with missing buttons. Let's see how MediaWiki does this. There is just one template, and the stings are translated only. Doesn't that make more sense? You program's functionality shouldn't vary by language, but just the strings that describe the functionality. If one wants to customize, then one should customize the template, affecting all languages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1861600&group_id=103 From noreply at sourceforge.net Thu Jan 17 02:42:40 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 16 Jan 2008 17:42:40 -0800 Subject: [ mailman-Bugs-1873369 ] trailing slash on listinfo.cgi Message-ID: Bugs item #1873369, was opened at 2008-01-17 09:42 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=1873369&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: trailing slash on listinfo.cgi Initial Comment: On listinfo.cgi there are links to http://lists.example.org/admin.cgi/members-example.org <--lacks slash, less efficient http://lists.example.org/listinfo.cgi/members-example.org http://lists.example.org/private.cgi/members-example.org/ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1873369&group_id=103 From noreply at sourceforge.net Thu Jan 17 02:43:07 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 16 Jan 2008 17:43:07 -0800 Subject: [ mailman-Bugs-1873369 ] trailing slash on listinfo.cgi Message-ID: Bugs item #1873369, was opened at 2008-01-17 09:42 Message generated for change (Settings changed) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1873369&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None >Priority: 1 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: trailing slash on listinfo.cgi Initial Comment: On listinfo.cgi there are links to http://lists.example.org/admin.cgi/members-example.org <--lacks slash, less efficient http://lists.example.org/listinfo.cgi/members-example.org http://lists.example.org/private.cgi/members-example.org/ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1873369&group_id=103 From noreply at sourceforge.net Thu Jan 17 02:57:43 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 16 Jan 2008 17:57:43 -0800 Subject: [ mailman-Bugs-1861600 ] whole HTML templates approach wrong Message-ID: Bugs item #1861600, was opened at 2008-01-01 13:01 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1861600&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: whole HTML templates approach wrong Initial Comment: Gentlemen, observe the deformed child among $ grep -ihc button mailman-2.1.10b1/templates/*/options.html|xargs 26 26 26 26 26 28 26 25 26 22 26 26 26 26 28 26 26 25 26 27 26 26 26 26 26 27 26 26 26 26 26 26 26 26 14 Yes at the very end, 14. Might as well just $ iconv -t gb2312 templates/zh_CN/options.html|iconv -f gb2312 -t big5| iconv -f big5 > templates/zh_TW/options.html It's better than a form without a submit button. Who knows how many other parts of mailman lack an eye here, a leg there... ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-17 09:57 Message: Logged In: YES user_id=1971011 Originator: YES So I thought maybe for my zh_TW site, I shall change the site language to English, to avoid running all the 93 files with all kinds of missing code in them, here on Dreamhost's installation where even me, site administrator, has only the web interface. (I downloaded the source and am looking at it on my home machine, not Dreamhost's.) I thought just maybe I could at least put some Chinese in some of the four pages that we are allowed to edit via the web interface. But then I see the HTTP header already has the ascii character set defined, an as you know that overrides anything I can put in the body. Yes, I could have the zh_TW versions shown to users by default, and even edit them first to my hearts content, but that means I must change the site language to zh_TW, consigning myself to running the 93 defective parts. ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-17 09:17 Message: Logged In: YES user_id=1971011 Originator: YES Gentlemen, I have figured out how to use the poorly documented transcheck command, and the winner is.... $ for i in $(cd messages;ls); do echo -n $i:\ ; bin/transcheck -q $i;done ar: 15 warnings in 2 files ca: 51 warnings in 4 files cs: 2 warnings in 1 files da: 17 warnings in 2 files de: 38 warnings in 10 files es: 40 warnings in 6 files ja: 0 warnings in 0 files ... sv: 50 warnings in 2 files tr: 21 warnings in 2 files uk: 17 warnings in 2 files vi: 9 warnings in 3 files zh_CN: 31 warnings in 4 files zh_TW: 93 warnings in 10 files That's right, zh_TW, another gold medal. Actually it appears your whole approach is wrong. With entire .html and .txt files to be translated, there will always be missing buttons, etc. If instead using just strings in .po files, if a message isn't translated, at least the English will be shown to the user. Anyway how terrible to have unlucky languages with missing buttons. Let's see how MediaWiki does this. There is just one template, and the stings are translated only. Doesn't that make more sense? You program's functionality shouldn't vary by language, but just the strings that describe the functionality. If one wants to customize, then one should customize the template, affecting all languages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1861600&group_id=103 From noreply at sourceforge.net Thu Jan 17 03:32:50 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 16 Jan 2008 18:32:50 -0800 Subject: [ mailman-Bugs-1873392 ] Can't change users' reminders from web Message-ID: Bugs item #1873392, was opened at 2008-01-17 10:32 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=1873392&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Can't change users' reminders from web Initial Comment: On the (English) page entitled "Members mailing list administration Membership Management... Section" There is no button to adjust users' monthly password reminders. I bet one must loging as each users one by one to turn them off. All I have is the web interface on Dreamhost. I bet there's more items too that one can't change from the admin web pages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1873392&group_id=103 From noreply at sourceforge.net Thu Jan 17 04:13:26 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 16 Jan 2008 19:13:26 -0800 Subject: [ mailman-Bugs-1861600 ] whole HTML templates approach wrong Message-ID: Bugs item #1861600, was opened at 2008-01-01 13:01 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1861600&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: whole HTML templates approach wrong Initial Comment: Gentlemen, observe the deformed child among $ grep -ihc button mailman-2.1.10b1/templates/*/options.html|xargs 26 26 26 26 26 28 26 25 26 22 26 26 26 26 28 26 26 25 26 27 26 26 26 26 26 27 26 26 26 26 26 26 26 26 14 Yes at the very end, 14. Might as well just $ iconv -t gb2312 templates/zh_CN/options.html|iconv -f gb2312 -t big5| iconv -f big5 > templates/zh_TW/options.html It's better than a form without a submit button. Who knows how many other parts of mailman lack an eye here, a leg there... ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-17 11:13 Message: Logged In: YES user_id=1971011 Originator: YES I find putting & # 12345 ; style entities into the boxes on admin.cgi/.../general may be a workaround for getting past the charset stuff. Haven't tested ZH_tw blobs in EN email, or seen what will become of zh_TW archives when switching the _monolithic_ site language to EN. ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-17 09:57 Message: Logged In: YES user_id=1971011 Originator: YES So I thought maybe for my zh_TW site, I shall change the site language to English, to avoid running all the 93 files with all kinds of missing code in them, here on Dreamhost's installation where even me, site administrator, has only the web interface. (I downloaded the source and am looking at it on my home machine, not Dreamhost's.) I thought just maybe I could at least put some Chinese in some of the four pages that we are allowed to edit via the web interface. But then I see the HTTP header already has the ascii character set defined, an as you know that overrides anything I can put in the body. Yes, I could have the zh_TW versions shown to users by default, and even edit them first to my hearts content, but that means I must change the site language to zh_TW, consigning myself to running the 93 defective parts. ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-17 09:17 Message: Logged In: YES user_id=1971011 Originator: YES Gentlemen, I have figured out how to use the poorly documented transcheck command, and the winner is.... $ for i in $(cd messages;ls); do echo -n $i:\ ; bin/transcheck -q $i;done ar: 15 warnings in 2 files ca: 51 warnings in 4 files cs: 2 warnings in 1 files da: 17 warnings in 2 files de: 38 warnings in 10 files es: 40 warnings in 6 files ja: 0 warnings in 0 files ... sv: 50 warnings in 2 files tr: 21 warnings in 2 files uk: 17 warnings in 2 files vi: 9 warnings in 3 files zh_CN: 31 warnings in 4 files zh_TW: 93 warnings in 10 files That's right, zh_TW, another gold medal. Actually it appears your whole approach is wrong. With entire .html and .txt files to be translated, there will always be missing buttons, etc. If instead using just strings in .po files, if a message isn't translated, at least the English will be shown to the user. Anyway how terrible to have unlucky languages with missing buttons. Let's see how MediaWiki does this. There is just one template, and the stings are translated only. Doesn't that make more sense? You program's functionality shouldn't vary by language, but just the strings that describe the functionality. If one wants to customize, then one should customize the template, affecting all languages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1861600&group_id=103 From noreply at sourceforge.net Thu Jan 17 21:43:28 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 17 Jan 2008 12:43:28 -0800 Subject: [ mailman-Bugs-1868873 ] deceptive listinfo "to post a message..." Message-ID: Bugs item #1868873, was opened at 2008-01-11 05:41 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1868873&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: security/privacy Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: deceptive listinfo "to post a message..." Initial Comment: Allow me to introduce the primary bug of all, the one that is certainly the first one encounters upon first contact with mailman as a mere user. He sees on the listinfo web page: "To post a message to all the list members, send email to ..." Which means TO HIM, the innocent victim, that "posting is wide open. What ever you send will get full executive treatment and be sent to all members and the archive forthwith". When in fact it really means "Yes, we say 'to post', but to post is not to receive, necessarily. I.E., depending on policies, your message might 1. go to /dev/null, 2. go to /dev/null with a notice back to you, 3. go into a queue for moderator approval, 4. as 3 but with a notice back to you, 5.... and it all depends on the configuration, which the moderator/administrator has elected not to make public, i.e., one of 1,2,3,4... will happen, and we could tell you here, but we won't. So what happens, is due to the *deceptive* message "To post a message to all the list members, send email to ..." the user posts and waits several days not knowing what is happening, while his burning question lies unseen who knows where. If subscription is required to post, than say "subscription is required to post". If you are not willing to mention that subscription is or is not required, in an effort to thwart spammers, then say "subscription may be required to post". Anyway, the software is very aware of just what requirements there are to post, so it should say them there on listinfo, unless the administrator has checked "[x]Obfuscate posting requirements on listinfo page". Whereupon say "subscription may be required to post, but the administrator has chosen not to reveal what they may be." Anyway, in no case continue saying "To post a message to all the list members, send email to ..." as it looks like the current message. If the list is really wide open, say "Membership not required to post"... Don't just reply to this bug saying to ask the administrator to edit the HTML files for his site, as the forwarding in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=199195 probably thought. Tell them to edit the HTML if checking the above [x] box is not enough. ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-18 04:43 Message: Logged In: YES user_id=1971011 Originator: YES The following statement also is one where the computer knows very well what the configuration is, but is too lazy to check, even if the administrator wanted it to. So add a configuration item for this item: gloss over the facts to fool spammers [] or give the real deal [x]. "Your subscription request has been received, and will soon be acted upon. Depending on the configuration of this mailing list, your subscription request may have to be first confirmed by you via email, or approved by the list moderator. If confirmation is required, you will soon get a confirmation email which contains further instructions." ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1868873&group_id=103 From noreply at sourceforge.net Fri Jan 18 02:11:30 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 17 Jan 2008 17:11:30 -0800 Subject: [ mailman-Bugs-1874265 ] gzip step doesn't respect UTF-8 Message-ID: Bugs item #1874265, was opened at 2008-01-18 09:11 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=1874265&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 alpha Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: gzip step doesn't respect UTF-8 Initial Comment: With the site languge set to *English*, UTF-8 Chinese in message *bodies* like ?? looks great in the archives, except when they are made into .gz's whereupon they become "??" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1874265&group_id=103 From noreply at sourceforge.net Fri Jan 18 02:33:21 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 17 Jan 2008 17:33:21 -0800 Subject: [ mailman-Bugs-1874279 ] Mass Subscriptions names Message-ID: Bugs item #1874279, was opened at 2008-01-18 09:33 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=1874279&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 alpha Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Mass Subscriptions names Initial Comment: Today we look at members/add, Mass Subscriptions. Please change "Enter one address per line below..." to "Enter Bob Clodsworth or just blob at example.com, one per line:" Else no one can guess how to get names in. P.S., with site language = English, don't dream of entering and UTF-8 or &# 31309 ; stuff. You'll get an error. ASCII is assumed, dangnabit! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1874279&group_id=103 From noreply at sourceforge.net Fri Jan 18 03:52:44 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 17 Jan 2008 18:52:44 -0800 Subject: [ mailman-Bugs-1867275 ] more exact than List-Archive Message-ID: Bugs item #1867275, was opened at 2008-01-09 07:13 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867275&group_id=103 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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: more exact than List-Archive Initial Comment: Gentlemen, $ w3m -dump http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/33295/raw |grep Archive List-Archive: Archived-At: This means: mailman could, if it tried harder, put a header into the message with the exact URL of where it archived the message at, instead of just its current "go look thru the heap, Holmes" Archived-At header. Instead users will quote a 3rd party (gmane.org here), which might go belly up at any time, when referring to the article. ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-18 10:52 Message: Logged In: YES user_id=1971011 Originator: YES I see http://wiki.list.org/display/DEV/Stable+URLs you are aware of the issue. Good. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867275&group_id=103 From noreply at sourceforge.net Fri Jan 18 04:09:57 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 17 Jan 2008 19:09:57 -0800 Subject: [ mailman-Bugs-1874265 ] gzip step doesn't respect UTF-8 Message-ID: Bugs item #1874265, was opened at 2008-01-18 09:11 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1874265&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 alpha Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: gzip step doesn't respect UTF-8 Initial Comment: With the site languge set to *English*, UTF-8 Chinese in message *bodies* like ?? looks great in the archives, except when they are made into .gz's whereupon they become "??" ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-18 11:09 Message: Logged In: YES user_id=1971011 Originator: YES Don't believe me, have a look at http://tossug.org/pipermail/hojia/ Also look at the disaster of http://tossug.org/mailman/listinfo/hojia that you force charset of ASCII in the HTTP headers, and the user has not used &# codes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1874265&group_id=103 From noreply at sourceforge.net Sat Jan 19 07:54:24 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 18 Jan 2008 22:54:24 -0800 Subject: [ mailman-Bugs-1875187 ] Cannot deselect Engish Message-ID: Bugs item #1875187, was opened at 2008-01-19 14: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=1875187&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot deselect Engish Initial Comment: Discovery: cannot turn off English in admin.cgi/.../language, no matter even if another language is the preferred language. Well, then at least don't make English click-offable. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1875187&group_id=103 From noreply at sourceforge.net Sat Jan 19 07:56:43 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 18 Jan 2008 22:56:43 -0800 Subject: [ mailman-Bugs-1874279 ] Mass Subscriptions names Message-ID: Bugs item #1874279, was opened at 2008-01-18 09:33 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1874279&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 alpha Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Mass Subscriptions names Initial Comment: Today we look at members/add, Mass Subscriptions. Please change "Enter one address per line below..." to "Enter Bob Clodsworth or just blob at example.com, one per line:" Else no one can guess how to get names in. P.S., with site language = English, don't dream of entering and UTF-8 or &# 31309 ; stuff. You'll get an error. ASCII is assumed, dangnabit! ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-19 14:56 Message: Logged In: YES user_id=1971011 Originator: YES And even with site language zh_TW, on the mass subscription results page one sees UTF-8 becomes: * 積丹尼 though apparently internally it is still UTF-8 at evidenced on other pages. P.S., the zh_TW 'send me my passwd' email sends raw % mess: ??????????? ! ? email ? %(adminaddr)s. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1874279&group_id=103 From noreply at sourceforge.net Sat Jan 19 21:38:35 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 19 Jan 2008 12:38:35 -0800 Subject: [ mailman-Bugs-1875187 ] Cannot deselect Engish Message-ID: Bugs item #1875187, was opened at 2008-01-18 22:54 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1875187&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot deselect Engish Initial Comment: Discovery: cannot turn off English in admin.cgi/.../language, no matter even if another language is the preferred language. Well, then at least don't make English click-offable. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-01-19 12:38 Message: Logged In: YES user_id=1123998 Originator: NO It isn't English you can't turn off. It is the language defined as DEFAULT_SERVER_LANGUAGE. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1875187&group_id=103 From noreply at sourceforge.net Sun Jan 20 02:05:34 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 19 Jan 2008 17:05:34 -0800 Subject: [ mailman-Bugs-1868873 ] deceptive listinfo "to post a message..." Message-ID: Bugs item #1868873, was opened at 2008-01-10 16:41 Message generated for change (Comment added) made by jimpop You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1868873&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: security/privacy Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: deceptive listinfo "to post a message..." Initial Comment: Allow me to introduce the primary bug of all, the one that is certainly the first one encounters upon first contact with mailman as a mere user. He sees on the listinfo web page: "To post a message to all the list members, send email to ..." Which means TO HIM, the innocent victim, that "posting is wide open. What ever you send will get full executive treatment and be sent to all members and the archive forthwith". When in fact it really means "Yes, we say 'to post', but to post is not to receive, necessarily. I.E., depending on policies, your message might 1. go to /dev/null, 2. go to /dev/null with a notice back to you, 3. go into a queue for moderator approval, 4. as 3 but with a notice back to you, 5.... and it all depends on the configuration, which the moderator/administrator has elected not to make public, i.e., one of 1,2,3,4... will happen, and we could tell you here, but we won't. So what happens, is due to the *deceptive* message "To post a message to all the list members, send email to ..." the user posts and waits several days not knowing what is happening, while his burning question lies unseen who knows where. If subscription is required to post, than say "subscription is required to post". If you are not willing to mention that subscription is or is not required, in an effort to thwart spammers, then say "subscription may be required to post". Anyway, the software is very aware of just what requirements there are to post, so it should say them there on listinfo, unless the administrator has checked "[x]Obfuscate posting requirements on listinfo page". Whereupon say "subscription may be required to post, but the administrator has chosen not to reveal what they may be." Anyway, in no case continue saying "To post a message to all the list members, send email to ..." as it looks like the current message. If the list is really wide open, say "Membership not required to post"... Don't just reply to this bug saying to ask the administrator to edit the HTML files for his site, as the forwarding in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=199195 probably thought. Tell them to edit the HTML if checking the above [x] box is not enough. ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2008-01-19 20:05 Message: Logged In: YES user_id=3142 Originator: NO Why not just ask the administrator to edit the HTML *templates* for his site? ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-17 15:43 Message: Logged In: YES user_id=1971011 Originator: YES The following statement also is one where the computer knows very well what the configuration is, but is too lazy to check, even if the administrator wanted it to. So add a configuration item for this item: gloss over the facts to fool spammers [] or give the real deal [x]. "Your subscription request has been received, and will soon be acted upon. Depending on the configuration of this mailing list, your subscription request may have to be first confirmed by you via email, or approved by the list moderator. If confirmation is required, you will soon get a confirmation email which contains further instructions." ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1868873&group_id=103 From noreply at sourceforge.net Sun Jan 20 05:10:30 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 19 Jan 2008 20:10:30 -0800 Subject: [ mailman-Bugs-1875187 ] Cannot deselect Engish Message-ID: Bugs item #1875187, was opened at 2008-01-19 14:54 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1875187&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot deselect Engish Initial Comment: Discovery: cannot turn off English in admin.cgi/.../language, no matter even if another language is the preferred language. Well, then at least don't make English click-offable. ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-20 12:10 Message: Logged In: YES user_id=1971011 Originator: YES That's nice but for installations like Dreamhost's, where a list administrator has no access to the configuration beyond Mailman's web panel, he has no way to keep users out of the English pages, which he must then customize also along with the ones of the language he already customized. So be sure to stop restricting this restriction. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2008-01-20 04:38 Message: Logged In: YES user_id=1123998 Originator: NO It isn't English you can't turn off. It is the language defined as DEFAULT_SERVER_LANGUAGE. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1875187&group_id=103 From noreply at sourceforge.net Sun Jan 20 05:22:20 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 19 Jan 2008 20:22:20 -0800 Subject: [ mailman-Bugs-1868873 ] deceptive listinfo "to post a message..." Message-ID: Bugs item #1868873, was opened at 2008-01-11 05:41 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1868873&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: security/privacy Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: deceptive listinfo "to post a message..." Initial Comment: Allow me to introduce the primary bug of all, the one that is certainly the first one encounters upon first contact with mailman as a mere user. He sees on the listinfo web page: "To post a message to all the list members, send email to ..." Which means TO HIM, the innocent victim, that "posting is wide open. What ever you send will get full executive treatment and be sent to all members and the archive forthwith". When in fact it really means "Yes, we say 'to post', but to post is not to receive, necessarily. I.E., depending on policies, your message might 1. go to /dev/null, 2. go to /dev/null with a notice back to you, 3. go into a queue for moderator approval, 4. as 3 but with a notice back to you, 5.... and it all depends on the configuration, which the moderator/administrator has elected not to make public, i.e., one of 1,2,3,4... will happen, and we could tell you here, but we won't. So what happens, is due to the *deceptive* message "To post a message to all the list members, send email to ..." the user posts and waits several days not knowing what is happening, while his burning question lies unseen who knows where. If subscription is required to post, than say "subscription is required to post". If you are not willing to mention that subscription is or is not required, in an effort to thwart spammers, then say "subscription may be required to post". Anyway, the software is very aware of just what requirements there are to post, so it should say them there on listinfo, unless the administrator has checked "[x]Obfuscate posting requirements on listinfo page". Whereupon say "subscription may be required to post, but the administrator has chosen not to reveal what they may be." Anyway, in no case continue saying "To post a message to all the list members, send email to ..." as it looks like the current message. If the list is really wide open, say "Membership not required to post"... Don't just reply to this bug saying to ask the administrator to edit the HTML files for his site, as the forwarding in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=199195 probably thought. Tell them to edit the HTML if checking the above [x] box is not enough. ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-20 12:22 Message: Logged In: YES user_id=1971011 Originator: YES > Why not just ask the administrator to edit the HTML *templates* for his site? No. There should just be a choice on the administrator panel, Be honest about things []Yes [X]No. (Actually a group of choices, one for each thing.) [X]No by default, for security. That would cover 99% of the cases, keep people from mucking with the HTML, and make them conscious of the deception. ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2008-01-20 09:05 Message: Logged In: YES user_id=3142 Originator: NO Why not just ask the administrator to edit the HTML *templates* for his site? ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-18 04:43 Message: Logged In: YES user_id=1971011 Originator: YES The following statement also is one where the computer knows very well what the configuration is, but is too lazy to check, even if the administrator wanted it to. So add a configuration item for this item: gloss over the facts to fool spammers [] or give the real deal [x]. "Your subscription request has been received, and will soon be acted upon. Depending on the configuration of this mailing list, your subscription request may have to be first confirmed by you via email, or approved by the list moderator. If confirmation is required, you will soon get a confirmation email which contains further instructions." ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1868873&group_id=103 From noreply at sourceforge.net Sun Jan 20 06:43:10 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 19 Jan 2008 21:43:10 -0800 Subject: [ mailman-Bugs-1868873 ] deceptive listinfo "to post a message..." Message-ID: Bugs item #1868873, was opened at 2008-01-10 16:41 Message generated for change (Comment added) made by jimpop You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1868873&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: security/privacy Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: deceptive listinfo "to post a message..." Initial Comment: Allow me to introduce the primary bug of all, the one that is certainly the first one encounters upon first contact with mailman as a mere user. He sees on the listinfo web page: "To post a message to all the list members, send email to ..." Which means TO HIM, the innocent victim, that "posting is wide open. What ever you send will get full executive treatment and be sent to all members and the archive forthwith". When in fact it really means "Yes, we say 'to post', but to post is not to receive, necessarily. I.E., depending on policies, your message might 1. go to /dev/null, 2. go to /dev/null with a notice back to you, 3. go into a queue for moderator approval, 4. as 3 but with a notice back to you, 5.... and it all depends on the configuration, which the moderator/administrator has elected not to make public, i.e., one of 1,2,3,4... will happen, and we could tell you here, but we won't. So what happens, is due to the *deceptive* message "To post a message to all the list members, send email to ..." the user posts and waits several days not knowing what is happening, while his burning question lies unseen who knows where. If subscription is required to post, than say "subscription is required to post". If you are not willing to mention that subscription is or is not required, in an effort to thwart spammers, then say "subscription may be required to post". Anyway, the software is very aware of just what requirements there are to post, so it should say them there on listinfo, unless the administrator has checked "[x]Obfuscate posting requirements on listinfo page". Whereupon say "subscription may be required to post, but the administrator has chosen not to reveal what they may be." Anyway, in no case continue saying "To post a message to all the list members, send email to ..." as it looks like the current message. If the list is really wide open, say "Membership not required to post"... Don't just reply to this bug saying to ask the administrator to edit the HTML files for his site, as the forwarding in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=199195 probably thought. Tell them to edit the HTML if checking the above [x] box is not enough. ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2008-01-20 00:43 Message: Logged In: YES user_id=3142 Originator: NO > No. There should just be a choice on the administrator panel, In a perfect world, yes. However, it's a pretty minor issue, that *does* have a work around. BTW, your use of "deceptive" in the Subject is just a poor choice of wording, and probably seen as an insult by Mailman developers. I understand your emotion, but I don't understand your expectations. Best wishes, -Jim P. ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-19 23:22 Message: Logged In: YES user_id=1971011 Originator: YES > Why not just ask the administrator to edit the HTML *templates* for his site? No. There should just be a choice on the administrator panel, Be honest about things []Yes [X]No. (Actually a group of choices, one for each thing.) [X]No by default, for security. That would cover 99% of the cases, keep people from mucking with the HTML, and make them conscious of the deception. ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2008-01-19 20:05 Message: Logged In: YES user_id=3142 Originator: NO Why not just ask the administrator to edit the HTML *templates* for his site? ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-17 15:43 Message: Logged In: YES user_id=1971011 Originator: YES The following statement also is one where the computer knows very well what the configuration is, but is too lazy to check, even if the administrator wanted it to. So add a configuration item for this item: gloss over the facts to fool spammers [] or give the real deal [x]. "Your subscription request has been received, and will soon be acted upon. Depending on the configuration of this mailing list, your subscription request may have to be first confirmed by you via email, or approved by the list moderator. If confirmation is required, you will soon get a confirmation email which contains further instructions." ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1868873&group_id=103 From noreply at sourceforge.net Tue Jan 22 20:55:34 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 22 Jan 2008 11:55:34 -0800 Subject: [ mailman-Bugs-1866486 ] validate HTML and email produced Message-ID: Bugs item #1866486, was opened at 2008-01-08 10:40 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866486&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: validate HTML and email produced Initial Comment: In your test suite add for all languages for all HTML pages run them thru a HTML validator for all administrative email sent run them thru e.g., SpamAssassin, to detect SUBJECT_NEEDS_ENCODING etc. embarrassment. ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-23 03:55 Message: Logged In: YES user_id=1971011 Originator: YES And as you will find your HTML is jam packed with _very hard to maintain presentational blibber_, causing a billion validator errors, meaning it is just by shear luck that people hopefully see what your thought maybe they might see in their browsers at all, therefore I recommend you forget your FrontPage Express style tag soup mess, and try HTML Strict (http://www.w3.org/TR/html4/strict.dtd). Never mind all those colors and tables. Get in the habit of thinking from the point of all users: _accessibility_. Here's an example of how I repaired your disastrous listinfo.html. I couldn't use strict.dtd as the stuff I include of yours isn't strict. Also you insist on sticking a TABLE inside an ADDRESS, in mm-mailman-footer, so short of just hardcoding the whole thing, it will never be valid HTML. Anyway I'm just telling you, not volunteering to help, but just telling you, that aren't these

and

's easier to maintain than that TABLE tag barf that you contracted Plotzworth Whoopie Pages Web Designers for? P.S., Before making one more release, make sure what you release is valid HTML. Does Wikipedia pass the validator? Yes. It is quite bananas to just emit TAG JUMBLE GAMBLE HTML with FINGER CROSSED to people's browsers. Anyway, just some

's and

's: <mm-list-name> ????

--

????

??????????? ??????

??

?????????? ?

????

?????????

???

---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866486&group_id=103 From noreply at sourceforge.net Tue Jan 22 21:29:24 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 22 Jan 2008 12:29:24 -0800 Subject: [ mailman-Bugs-1874279 ] Mass Subscriptions names Message-ID: Bugs item #1874279, was opened at 2008-01-18 09:33 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1874279&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 alpha Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Mass Subscriptions names Initial Comment: Today we look at members/add, Mass Subscriptions. Please change "Enter one address per line below..." to "Enter Bob Clodsworth or just blob at example.com, one per line:" Else no one can guess how to get names in. P.S., with site language = English, don't dream of entering and UTF-8 or &# 31309 ; stuff. You'll get an error. ASCII is assumed, dangnabit! ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-23 04:29 Message: Logged In: YES user_id=1971011 Originator: YES By the way, on the mass subscription page, if one puts addresses both in the entry box, and in the contents of the file to be read in, one ends up with at least one garbled address... do warn or catch or say on the page that it's OK to use both, then process correctly. I did not test the mass deletions page. ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-19 14:56 Message: Logged In: YES user_id=1971011 Originator: YES And even with site language zh_TW, on the mass subscription results page one sees UTF-8 becomes: * 積丹尼 though apparently internally it is still UTF-8 at evidenced on other pages. P.S., the zh_TW 'send me my passwd' email sends raw % mess: ??????????? ! ? email ? %(adminaddr)s. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1874279&group_id=103 From noreply at sourceforge.net Tue Jan 22 21:36:33 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 22 Jan 2008 12:36:33 -0800 Subject: [ mailman-Bugs-1874279 ] Mass Subscriptions names Message-ID: Bugs item #1874279, was opened at 2008-01-18 09:33 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1874279&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 alpha Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Mass Subscriptions names Initial Comment: Today we look at members/add, Mass Subscriptions. Please change "Enter one address per line below..." to "Enter Bob Clodsworth or just blob at example.com, one per line:" Else no one can guess how to get names in. P.S., with site language = English, don't dream of entering and UTF-8 or &# 31309 ; stuff. You'll get an error. ASCII is assumed, dangnabit! ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-23 04:36 Message: Logged In: YES user_id=1971011 Originator: YES Holy moly, on the Mass Subscriptions page, if you leave the notify administrator box checked, it _really does_ send one notification for EACH subscriber! Subscribe 50 people, and the administrator gets 50 EMAILs about it, not just one email with the results about all 50 names. Who knows what pleasure is in store on the mass delete page. You have my permission to split this off into a separate bug. ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-23 04:29 Message: Logged In: YES user_id=1971011 Originator: YES By the way, on the mass subscription page, if one puts addresses both in the entry box, and in the contents of the file to be read in, one ends up with at least one garbled address... do warn or catch or say on the page that it's OK to use both, then process correctly. I did not test the mass deletions page. ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-19 14:56 Message: Logged In: YES user_id=1971011 Originator: YES And even with site language zh_TW, on the mass subscription results page one sees UTF-8 becomes: * 積丹尼 though apparently internally it is still UTF-8 at evidenced on other pages. P.S., the zh_TW 'send me my passwd' email sends raw % mess: ??????????? ! ? email ? %(adminaddr)s. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1874279&group_id=103 From noreply at sourceforge.net Wed Jan 23 14:08:51 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 05:08:51 -0800 Subject: [ mailman-Bugs-1878088 ] UNsubscribe NON-subscribers?! Message-ID: Bugs item #1878088, was opened at 2008-01-23 21:08 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=1878088&group_id=103 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: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: UNsubscribe NON-subscribers?! Initial Comment: >From the "Members list: member options login page", one can enter the name of some NON-subscriber, and click UNsubscribe, and see "The confirmation email has been sent." Now as to mail actually being sent, maybe it isn't, thank goodness, I'm not sure. but at least don't say "The confirmation email has been sent." ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1878088&group_id=103 From noreply at sourceforge.net Wed Jan 23 14:13:17 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 05:13:17 -0800 Subject: [ mailman-Bugs-1878090 ] admin wants to be informed of changes of addressif Message-ID: Bugs item #1878090, was opened at 2008-01-23 21:13 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=1878090&group_id=103 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: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: admin wants to be informed of changes of addressif Initial Comment: Users are allowed to change their addresses all behind the back of the administrator, as apparently the closest button governing this is admin_notify_mchanges which doesn't track changes of address. So in case the administrator is interested in such mundane news, he can only check Membership Management often. (Only have web interface here. No shell.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1878090&group_id=103 From noreply at sourceforge.net Wed Jan 23 14:13:52 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 05:13:52 -0800 Subject: [ mailman-Bugs-1878090 ] if admin wants to be informed of changes of address Message-ID: Bugs item #1878090, was opened at 2008-01-23 21:13 Message generated for change (Settings changed) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1878090&group_id=103 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: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) >Summary: if admin wants to be informed of changes of address Initial Comment: Users are allowed to change their addresses all behind the back of the administrator, as apparently the closest button governing this is admin_notify_mchanges which doesn't track changes of address. So in case the administrator is interested in such mundane news, he can only check Membership Management often. (Only have web interface here. No shell.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1878090&group_id=103 From noreply at sourceforge.net Wed Jan 23 14:32:38 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 05:32:38 -0800 Subject: [ mailman-Bugs-1878090 ] if admin wants to be informed of changes of address Message-ID: Bugs item #1878090, was opened at 2008-01-23 21:13 Message generated for change (Settings changed) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1878090&group_id=103 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: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None >Priority: 1 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: if admin wants to be informed of changes of address Initial Comment: Users are allowed to change their addresses all behind the back of the administrator, as apparently the closest button governing this is admin_notify_mchanges which doesn't track changes of address. So in case the administrator is interested in such mundane news, he can only check Membership Management often. (Only have web interface here. No shell.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1878090&group_id=103 From noreply at sourceforge.net Wed Jan 23 14:33:01 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 05:33:01 -0800 Subject: [ mailman-Bugs-1878088 ] UNsubscribe NON-subscribers?! Message-ID: Bugs item #1878088, was opened at 2008-01-23 21:08 Message generated for change (Settings changed) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1878088&group_id=103 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: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None >Priority: 1 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: UNsubscribe NON-subscribers?! Initial Comment: >From the "Members list: member options login page", one can enter the name of some NON-subscriber, and click UNsubscribe, and see "The confirmation email has been sent." Now as to mail actually being sent, maybe it isn't, thank goodness, I'm not sure. but at least don't say "The confirmation email has been sent." ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1878088&group_id=103 From noreply at sourceforge.net Wed Jan 23 14:34:08 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 05:34:08 -0800 Subject: [ mailman-Bugs-1867286 ] man newlist touchup Message-ID: Bugs item #1867286, was opened at 2008-01-09 07:36 Message generated for change (Settings changed) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867286&group_id=103 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: None Status: Open Resolution: None >Priority: 2 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: man newlist touchup Initial Comment: $ man newlist SYNOPSIS newlist [options] listname listadmin-addr admin-password NOTES You can specify as many of the arguments as you want on the command line: you will be prompted for the missing ones. ***OK, then say newlist [options] [listname] [listadmin-addr] [admin-password] OPTIONS -l language, --language=language Make the list's preferred language `language', which must be a two letter language code. ***But there are TWO kinds of Chinese! zh_CN zh_TW, etc. That's more than TWO letters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867286&group_id=103 From noreply at sourceforge.net Wed Jan 23 14:36:37 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 05:36:37 -0800 Subject: [ mailman-Bugs-1867285 ] FAQ: really need root? Message-ID: Bugs item #1867285, was opened at 2008-01-09 07:33 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867285&group_id=103 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 beta Status: Open Resolution: None >Priority: 1 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: FAQ: really need root? Initial Comment: Add to FAQ: Q: Surely I could install mailman on my web shared hosting plan without root. I'll just use --with-username=$USER --with-groupname=`id -g` ... --with-cgi-ext=.cgi etc. and then use my .procmailrc to redirect what comes to the extra mailboxes my hosting plan allows me to make... A: Ah but Holmes, you have neglected a fundamental... ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-23 21:36 Message: Logged In: YES user_id=1971011 Originator: YES http://mail.python.org/pipermail/mailman-users/2008-January/059940.html doesn't really nail it down. ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-11 05:47 Message: Logged In: YES user_id=1971011 Originator: YES Add to Q: And for sending mail I can use /usr/sbin/sendmail -i -f ... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867285&group_id=103 From noreply at sourceforge.net Wed Jan 23 22:56:44 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 13:56:44 -0800 Subject: [ mailman-Bugs-1878088 ] UNsubscribe NON-subscribers?! Message-ID: Bugs item #1878088, was opened at 2008-01-23 05:08 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1878088&group_id=103 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: (un)subscribing Group: 2.1 (stable) Status: Open >Resolution: Invalid Priority: 1 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: UNsubscribe NON-subscribers?! Initial Comment: >From the "Members list: member options login page", one can enter the name of some NON-subscriber, and click UNsubscribe, and see "The confirmation email has been sent." Now as to mail actually being sent, maybe it isn't, thank goodness, I'm not sure. but at least don't say "The confirmation email has been sent." ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-01-23 13:56 Message: Logged In: YES user_id=1123998 Originator: NO This is an intentional feature to prevent probing for membership on a list with private rosters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1878088&group_id=103 From noreply at sourceforge.net Thu Jan 24 01:28:38 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 16:28:38 -0800 Subject: [ mailman-Bugs-1878088 ] UNsubscribe NON-subscribers?! Message-ID: Bugs item #1878088, was opened at 2008-01-23 21:08 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1878088&group_id=103 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: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: Invalid Priority: 1 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: UNsubscribe NON-subscribers?! Initial Comment: >From the "Members list: member options login page", one can enter the name of some NON-subscriber, and click UNsubscribe, and see "The confirmation email has been sent." Now as to mail actually being sent, maybe it isn't, thank goodness, I'm not sure. but at least don't say "The confirmation email has been sent." ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-24 08:28 Message: Logged In: YES user_id=1971011 Originator: YES OK, but I would then always say "The confirmation email has been sent, if the address was a member." or something that is not ....lying.... because you will just get never ending bug reports. It is very easy to choose wording that does not lie and still states the facts that you are intentionally not revealing all the actions. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2008-01-24 05:56 Message: Logged In: YES user_id=1123998 Originator: NO This is an intentional feature to prevent probing for membership on a list with private rosters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1878088&group_id=103 From noreply at sourceforge.net Thu Jan 24 01:32:16 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 16:32:16 -0800 Subject: [ mailman-Bugs-1866473 ] make logos clickable Message-ID: Bugs item #1866473, was opened at 2008-01-08 10:16 Message generated for change (Settings changed) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866473&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI >Group: 2.1 (stable) Status: Open Resolution: None >Priority: 1 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: make logos clickable Initial Comment: The three logos at the bottom of most mailman screens: users are used to being able to click on things for more information, so make them clickable. Or maybe you fear sending beginners on to tangents. How often does one see a non-clickable logo these days?! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866473&group_id=103 From noreply at sourceforge.net Thu Jan 24 01:32:51 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 16:32:51 -0800 Subject: [ mailman-Bugs-1866475 ] Do in Makefile: create install dir, check_perms Message-ID: Bugs item #1866475, was opened at 2008-01-08 10:19 Message generated for change (Settings changed) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866475&group_id=103 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 beta Status: Open Resolution: None >Priority: 1 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Do in Makefile: create install dir, check_perms Initial Comment: Why can't the step in mailman-install/create-install-dir.html be instead done via make install? Just use --prefix's value. check_perms -f should also be done by the Makefile. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866475&group_id=103 From noreply at sourceforge.net Thu Jan 24 01:33:42 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 16:33:42 -0800 Subject: [ mailman-Bugs-1866484 ] Must provide logout buttons on every page Message-ID: Bugs item #1866484, was opened at 2008-01-08 10:35 Message generated for change (Settings changed) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866484&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI >Group: 2.1 beta Status: Open Resolution: None >Priority: 6 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Must provide logout buttons on every page Initial Comment: All pages (that one needs a cookie to get to) must provide logout buttons! E.g., no logout provided on admindb.cgi. Would a real company have a members only area with no logout button on the panel? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866484&group_id=103 From noreply at sourceforge.net Thu Jan 24 01:37:45 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 16:37:45 -0800 Subject: [ mailman-Bugs-1867277 ] where the moderator is to login Message-ID: Bugs item #1867277, was opened at 2008-01-09 07:16 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867277&group_id=103 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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: where the moderator is to login Initial Comment: Allow me to point out that once we have grasped the fact that there is both a moderator and an administrator, it then becomes very hard to find out where the moderator is supposed to login. See patch. You might want to mention it too on the screens that talk about the moderator. ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-24 08:37 Message: Logged In: YES user_id=1971011 Originator: YES Also noted in FAQ 3.45, i.e., too often asked. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1867277&group_id=103 From noreply at sourceforge.net Thu Jan 24 01:42:18 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 16:42:18 -0800 Subject: [ mailman-Bugs-1866473 ] make logos clickable Message-ID: Bugs item #1866473, was opened at 2008-01-07 21:16 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866473&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Wont Fix Priority: 1 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: make logos clickable Initial Comment: The three logos at the bottom of most mailman screens: users are used to being able to click on things for more information, so make them clickable. Or maybe you fear sending beginners on to tangents. How often does one see a non-clickable logo these days?! ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2008-01-23 19:42 Message: Logged In: YES user_id=12800 Originator: NO In fact, these used to be clickable and it caused lots of problems both for users being sent of into tangents, and for people whose email addresses were locatable by the sites behind these links. The links were removed at the requested of the FSF in fact. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866473&group_id=103 From noreply at sourceforge.net Thu Jan 24 01:49:58 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 16:49:58 -0800 Subject: [ mailman-Bugs-1878601 ] FAQ Wizard must add links to req=show on every page Message-ID: Bugs item #1878601, was opened at 2008-01-24 08:49 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=1878601&group_id=103 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: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: FAQ Wizard must add links to req=show on every page Initial Comment: Welcome to move this bug to where it belongs. Q: On http://www.python.org/cgi-bin/faqw-mm.py?req=all how does one link to one of the individual FAQs? One doesn't. One must go to http://www.python.org/cgi-bin/faqw-mm.py?req=index to find the links, because for some reason, no HREF tags are implanted into the titles on http://www.python.org/cgi-bin/faqw-mm.py?req=all or an "edit" page. I.e., I have just edited a FAQ and am starting at the results. But there is no link for me to copy to send to my friend to tell him to have a look. This is unlike Wikipedia, where there is always a link to just view, an article. Also at least in a Wikipedia TOC, one can find links to the anchors too... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1878601&group_id=103 From noreply at sourceforge.net Thu Jan 24 03:31:15 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 23 Jan 2008 18:31:15 -0800 Subject: [ mailman-Bugs-1866486 ] validate HTML and email produced Message-ID: Bugs item #1866486, was opened at 2008-01-08 10:40 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866486&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: validate HTML and email produced Initial Comment: In your test suite add for all languages for all HTML pages run them thru a HTML validator for all administrative email sent run them thru e.g., SpamAssassin, to detect SUBJECT_NEEDS_ENCODING etc. embarrassment. ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-01-24 10:31 Message: Logged In: YES user_id=1971011 Originator: YES Can't find the button to merge this with 1861600. Perhaps I don't have javascript turned on. Anyway: I did see http://wiki.list.org/display/DEV/Summer+of+Code but he's got it all wrong. Instead of going the javascript direction, he should just go to the strict.dtd direction. Using not even one TABLE, only H1 H2, etc. Indeed just like the HTML in my http://jidanni.org/ . I mean if anything, the number of buttons and choices on the Mailman web interface should shrink, not grow. Therefore the slightly looser H1 H2 etc. instead of TABLEs will not be too big anyway. I don't even see the need for any CSS. Just H2 or

lists of questions and answers (item names and their choices.) Mailman is not some multimedia application. You should go the Strict.dtd route. No color too: then you will be forced to make your H2's titles meaningful ones, improving accessibility for everybody. (P.S., the Chinese sample I gave also has its language selector ripped out, else I would have to also maintain an English page, as that is Dreamhost's site language, and cannot be turned off (bug 1875187)) ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-23 03:55 Message: Logged In: YES user_id=1971011 Originator: YES And as you will find your HTML is jam packed with _very hard to maintain presentational blibber_, causing a billion validator errors, meaning it is just by shear luck that people hopefully see what your thought maybe they might see in their browsers at all, therefore I recommend you forget your FrontPage Express style tag soup mess, and try HTML Strict (http://www.w3.org/TR/html4/strict.dtd). Never mind all those colors and tables. Get in the habit of thinking from the point of all users: _accessibility_. Here's an example of how I repaired your disastrous listinfo.html. I couldn't use strict.dtd as the stuff I include of yours isn't strict. Also you insist on sticking a TABLE inside an ADDRESS, in mm-mailman-footer, so short of just hardcoding the whole thing, it will never be valid HTML. Anyway I'm just telling you, not volunteering to help, but just telling you, that aren't these

and

's easier to maintain than that TABLE tag barf that you contracted Plotzworth Whoopie Pages Web Designers for? P.S., Before making one more release, make sure what you release is valid HTML. Does Wikipedia pass the validator? Yes. It is quite bananas to just emit TAG JUMBLE GAMBLE HTML with FINGER CROSSED to people's browsers. Anyway, just some

's and

's: <mm-list-name> ????

--

????

??????????? ??????

??

?????????? ?

????

?????????

???

---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1866486&group_id=103 From noreply at sourceforge.net Fri Jan 25 01:00:12 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 24 Jan 2008 16:00:12 -0800 Subject: [ mailman-Bugs-1879338 ] catch invalid URLs Message-ID: Bugs item #1879338, was opened at 2008-01-25 08: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=1879338&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: catch invalid URLs Initial Comment: One finds one can use URLs like http://lists.example.org/admin.cgi/zzz-example.org/zzz/add/vvv/dddd and still visit the administration pages as if one typed in a correct URL. Somewhere in Mailman, something is not checking the URL beyond a certain length or segment. You might say "so what?", but if you allow these to work, soon all kinds of people's typos will end up in documents as being the URL to use to do various tasks, just because they happened to work that day. (Yes, the above example does not bypass password checks.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1879338&group_id=103 From noreply at sourceforge.net Fri Jan 25 15:40:40 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 25 Jan 2008 06:40:40 -0800 Subject: [ mailman-Patches-1879680 ] Danish translation update for 2.1.10b Message-ID: Patches item #1879680, was opened at 2008-01-25 15:40 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=1879680&group_id=103 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: Tom G. Christensen (tgc99) Assigned to: Nobody/Anonymous (nobody) Summary: Danish translation update for 2.1.10b Initial Comment: Here's an update for the danish translation. The work was done against the 2.1 maintenance branch and the diff created with bzr diff -p1 -r1034. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1879680&group_id=103 From noreply at sourceforge.net Fri Jan 25 16:17:55 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 25 Jan 2008 07:17:55 -0800 Subject: [ mailman-Patches-1879680 ] Danish translation update for 2.1.10b Message-ID: Patches item #1879680, was opened at 2008-01-25 09:40 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1879680&group_id=103 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: Tom G. Christensen (tgc99) Assigned to: Nobody/Anonymous (nobody) Summary: Danish translation update for 2.1.10b Initial Comment: Here's an update for the danish translation. The work was done against the 2.1 maintenance branch and the diff created with bzr diff -p1 -r1034. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2008-01-25 10:17 Message: Logged In: YES user_id=12800 Originator: NO Is the branch publicly available? I'd like to see if I can bzr merge it! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1879680&group_id=103 From noreply at sourceforge.net Sat Jan 26 17:49:15 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 26 Jan 2008 08:49:15 -0800 Subject: [ mailman-Patches-1879680 ] Danish translation update for 2.1.10b Message-ID: Patches item #1879680, was opened at 2008-01-25 15:40 Message generated for change (Comment added) made by tgc99 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1879680&group_id=103 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: Tom G. Christensen (tgc99) Assigned to: Nobody/Anonymous (nobody) Summary: Danish translation update for 2.1.10b Initial Comment: Here's an update for the danish translation. The work was done against the 2.1 maintenance branch and the diff created with bzr diff -p1 -r1034. ---------------------------------------------------------------------- >Comment By: Tom G. Christensen (tgc99) Date: 2008-01-26 17:49 Message: Logged In: YES user_id=1159458 Originator: YES No it is not. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2008-01-25 16:17 Message: Logged In: YES user_id=12800 Originator: NO Is the branch publicly available? I'd like to see if I can bzr merge it! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1879680&group_id=103 From noreply at sourceforge.net Tue Jan 29 15:59:38 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 29 Jan 2008 06:59:38 -0800 Subject: [ mailman-Feature Requests-1881853 ] Increasing the Maximum lenght of message body. Message-ID: Feature Requests item #1881853, was opened at 2008-01-29 09:59 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1881853&group_id=103 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: Joe Travaglione (joetravaglione) Assigned to: Nobody/Anonymous (nobody) Summary: Increasing the Maximum lenght of message body. Initial Comment: I am unable to send out email attachments or change the length of the message body. When I attempt to change the Maximum length in KB of Message body, it does not appear as an option I can change. Is there a way to access it? I am looking for the option under general, but it does not seem to be there. Any help would be greatly appreciated. Thanks ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1881853&group_id=103 From noreply at sourceforge.net Tue Jan 29 16:42:48 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 29 Jan 2008 07:42:48 -0800 Subject: [ mailman-Feature Requests-1881853 ] Increasing the Maximum lenght of message body. Message-ID: Feature Requests item #1881853, was opened at 2008-01-29 06:59 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1881853&group_id=103 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: Works For Me Priority: 5 Private: No Submitted By: Joe Travaglione (joetravaglione) Assigned to: Nobody/Anonymous (nobody) Summary: Increasing the Maximum lenght of message body. Initial Comment: I am unable to send out email attachments or change the length of the message body. When I attempt to change the Maximum length in KB of Message body, it does not appear as an option I can change. Is there a way to access it? I am looking for the option under general, but it does not seem to be there. Any help would be greatly appreciated. Thanks ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-01-29 07:42 Message: Logged In: YES user_id=1123998 Originator: NO It is max_message_size on the General Options page under Aditional Settings towards the bottom. Maximum length in kilobytes (KB) of a message body. Use 0 for no limit. (Edit max_message_size) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1881853&group_id=103 From noreply at sourceforge.net Tue Jan 29 17:49:46 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 29 Jan 2008 08:49:46 -0800 Subject: [ mailman-Feature Requests-1881853 ] Increasing the Maximum lenght of message body. Message-ID: Feature Requests item #1881853, was opened at 2008-01-29 09:59 Message generated for change (Comment added) made by joetravaglione You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1881853&group_id=103 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: Works For Me Priority: 5 Private: No Submitted By: Joe Travaglione (joetravaglione) Assigned to: Nobody/Anonymous (nobody) Summary: Increasing the Maximum lenght of message body. Initial Comment: I am unable to send out email attachments or change the length of the message body. When I attempt to change the Maximum length in KB of Message body, it does not appear as an option I can change. Is there a way to access it? I am looking for the option under general, but it does not seem to be there. Any help would be greatly appreciated. Thanks ---------------------------------------------------------------------- >Comment By: Joe Travaglione (joetravaglione) Date: 2008-01-29 11:49 Message: Logged In: YES user_id=1994980 Originator: YES I only see 6 settings in the additional settings at the bottom. The following options can be changed: 1. Emergency moderation of all list traffic 2. Default options for new members joining this list 3. (Administrivia filter) Check postings and intercept ones that seem to be administrative requests? 4. Host name this list prefers for email. 5. Should messages from this mailing list include the RFC 2369 (i.e. List-*) headers? Yes is highly recommended. 6. Should postings include the List-Post: header? There are no other options for changing the size? Do I have an old version of listserve? Do I have to sign up for a newer version? My current version is 2.1.5. Thank you for the comment any additional ideas? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2008-01-29 10:42 Message: Logged In: YES user_id=1123998 Originator: NO It is max_message_size on the General Options page under Aditional Settings towards the bottom. Maximum length in kilobytes (KB) of a message body. Use 0 for no limit. (Edit max_message_size) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1881853&group_id=103 From noreply at sourceforge.net Tue Jan 29 18:06:10 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 29 Jan 2008 09:06:10 -0800 Subject: [ mailman-Feature Requests-1881853 ] Increasing the Maximum lenght of message body. Message-ID: Feature Requests item #1881853, was opened at 2008-01-29 06:59 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1881853&group_id=103 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: Works For Me Priority: 5 Private: No Submitted By: Joe Travaglione (joetravaglione) Assigned to: Nobody/Anonymous (nobody) Summary: Increasing the Maximum lenght of message body. Initial Comment: I am unable to send out email attachments or change the length of the message body. When I attempt to change the Maximum length in KB of Message body, it does not appear as an option I can change. Is there a way to access it? I am looking for the option under general, but it does not seem to be there. Any help would be greatly appreciated. Thanks ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-01-29 09:06 Message: Logged In: YES user_id=1123998 Originator: NO If your Mailman is provided by your hosting provider, I suspect that they removed the ability for list owners to set max_message_size for their own reasons. This is in issue you need to take up with your provider. If this is your own Mailman installation, whatever Mailman you have installed has been modified to remove this setting. I recommend upgrading to the latest version from SourceForge. ---------------------------------------------------------------------- Comment By: Joe Travaglione (joetravaglione) Date: 2008-01-29 08:49 Message: Logged In: YES user_id=1994980 Originator: YES I only see 6 settings in the additional settings at the bottom. The following options can be changed: 1. Emergency moderation of all list traffic 2. Default options for new members joining this list 3. (Administrivia filter) Check postings and intercept ones that seem to be administrative requests? 4. Host name this list prefers for email. 5. Should messages from this mailing list include the RFC 2369 (i.e. List-*) headers? Yes is highly recommended. 6. Should postings include the List-Post: header? There are no other options for changing the size? Do I have an old version of listserve? Do I have to sign up for a newer version? My current version is 2.1.5. Thank you for the comment any additional ideas? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2008-01-29 07:42 Message: Logged In: YES user_id=1123998 Originator: NO It is max_message_size on the General Options page under Aditional Settings towards the bottom. Maximum length in kilobytes (KB) of a message body. Use 0 for no limit. (Edit max_message_size) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1881853&group_id=103