Mailman-coders October 2005

mailman-coders@python.org

1 participants
19 discussions

[ mailman-Bugs-1344305 ] trojan problem
by SourceForge.net 31 Oct '05

31 Oct '05

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

1 0

[ mailman-Bugs-1344305 ] trojan problem
by SourceForge.net 31 Oct '05

31 Oct '05

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

1 0

[ mailman-Patches-1343100 ] config_list vs. PEP 263
by SourceForge.net 30 Oct '05

30 Oct '05

Patches item #1343100, was opened at 2005-10-31 12:58 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1343100&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: config_list vs. PEP 263 Initial Comment: As of Python 2.3, DeprecatedWarning is issued for non-US-ASCII source. Let output of bin/config_list be compliant to PEP 263. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1343100&group_…

1 0

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

26 Oct '05

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

1 0

[ mailman-Bugs-736559 ] Subject wrap with tab character
by SourceForge.net 26 Oct '05

26 Oct '05

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

1 0

[ mailman-Bugs-1337731 ] Content-Transfer-Encoding header missing
by SourceForge.net 25 Oct '05

25 Oct '05

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

1 0

[ mailman-Bugs-736559 ] Subject wrap with tab character
by SourceForge.net 24 Oct '05

24 Oct '05

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

1 0

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

19 Oct '05

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

1 0

[ mailman-Patches-1298355 ] Select language(s) when install
by SourceForge.net 18 Oct '05

18 Oct '05

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

1 0

[ mailman-Patches-839386 ] MySQL MemberAdaptor for Mailman 2.1
by SourceForge.net 18 Oct '05

18 Oct '05

Patches item #839386, was opened at 2003-11-10 10:04 Message generated for change (Comment added) made by gustavo_peters You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Kev Green (kyrian) Assigned to: Nobody/Anonymous (nobody) Summary: MySQL MemberAdaptor for Mailman 2.1 Initial Comment: A MemberAdaptor "plugin" which should allow Mailman list members to be loaded from a MySQL database, rather than just a Mailman "pickle" file. Provided as-is, and without warranty, this "plugin" may destroy your server, soul, scalp, house, and life. Please use it with caution. Kev Green, oRe Net. http://www.orenet.co.uk/ ---------------------------------------------------------------------- Comment By: Gustavo Peters (gustavo_peters) Date: 2005-10-18 18:08 Message: Logged In: YES user_id=1272569 asa<cdzxcx ---------------------------------------------------------------------- Comment By: adrianwi (adrianwi) Date: 2005-09-14 12:32 Message: Logged In: YES user_id=1175103 Thank you for developing this adaptor! So far it's working well with the limited testing I've done. There seems to be a minor bug in the addNewMember method of this adaptor (version 1.61). At lines 579-584, there are SQL statements which add a new row in the MySQL database for a new member. In those statements, the column 'delivery_status' is given the value of MemberAdaptor.UNKNOWN. MemberAdaptor.py defines: # Delivery statuses ENABLED = 0 # enabled UNKNOWN = 1 # legacy disabled BYUSER = 2 # disabled by user choice BYADMIN = 3 # disabled by admin choice BYBOUNCE = 4 # disabled by bounces So, it appears that the SQL statements should be changed to use the value of MemberAdaptor.ENABLED instead of MemberAdaptor.UNKNOWN (which is "legacy disabled"). Making this change prevents "nomail [reason]" ? from being set in the user's options for new members (as seen in the web interface). This was tested with Mailman 2.1.6. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2005-07-27 05:38 Message: Logged In: YES user_id=99923 Folks, For my own sanity I have decided to create a dedicated area of my business website for various opensource projects, and put this project among others under there, so please refer to this location for updates to this patch in future: http://www.orenet.co.uk/opensource/ I will still be reading bug reports via sourceforge, but if nothing else, their user interface is much more fiddly and time consuming to publish files than a quick tar -czvf and an scp, so I'll be using my own environment to host the files at least for the time being. The latest version at this time is 1.61, I belive it still requires substantial testing which I'll get around to one of these days. K. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2005-05-31 11:57 Message: Logged In: YES user_id=99923 Folks, Well, I've finally gotten around to releasing an update to this thing, after a phone conversation with the client who are using it, and I've incorporated a couple of cosmetic fixes, fairly substantial changes to make the bounce processing work properly (the ability to set people to NOMAIL now exists, and real world testing is commencing soon), and incorporated the flat vs. wide table archivecture types with various bugfixes. Main notes: * It would be a good idea to change all your delivery_status fields from VARCHAR(255) to INT(10) or similar, so that they will work properly, and not bomb out on this new version (they should be okay I think, but I'd advise the change). * The missing-'AND' typo has been rectified. Any suggestions and bugs should be sent to my sourceforge account address, which ends up in the right place. K. ---------------------------------------------------------------------- Comment By: Gergely EGERVARY (egervary) Date: 2005-04-09 03:14 Message: Logged In: YES user_id=1255996 Thank you for your good work. FYI: there's a missing "AND" in MysqlMemberships.py in line 494. ---------------------------------------------------------------------- Comment By: simboforge (simboforge) Date: 2005-03-11 15:22 Message: Logged In: YES user_id=1226150 excellent. can you please give me a list of the files modified from the original distro? grep sees six that grep have msyql in them. thx ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2005-03-11 14:56 Message: Logged In: YES user_id=99923 The flat file databases are unused when you put the MySQL adaptor in place, and they are untouched (and indeed not deleted) by it, the MySQL adaptor only queries the MySQL tables for membership information, without trying to force you into using it fulltime by deleting anything, etc. Once you unconfigure the MySQL adaptor, Mailman should revert back to your existing flat file databases. Of course, I could have missed something, etc. so do back up your flat file databases before installing the MySQL adaptor, and then you can just migrate back to them by restoring the backups. Either way, you have come up with a good question for an FAQ on the SQL adaptor :-) K. ---------------------------------------------------------------------- Comment By: simboforge (simboforge) Date: 2005-03-11 14:42 Message: Logged In: YES user_id=1226150 neat. just what i was looking for. i have a couple of live lists running on version version 2.1.5. i am a bit leary about unzipping this distrobution over the top of my working mailman as i am not sure how to backup the existing flat file databases. i would prefer to experiment with dropping the adapter into my existing installation. any pointers as to where to start? thx ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-12-13 10:34 Message: Logged In: YES user_id=99923 Oh, btw. v1.57 hasn't been tested yet, so it might kill your server, eat your dog, and stick your wife in the oven. Be careful using it! ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-12-13 10:33 Message: Logged In: YES user_id=99923 Version 1.57: 2004/12/13 * Merge in Daniel Shriver patch/code for a flat table architecture. [ Suggested by Kevin McCann <kmccann(at)bellanet.org>, but I hadn't found time to do it myself... ] * Add bugfix information from Jinhyok Heo <novembre(a)NOSPAM.ournature.org> * Add in mksqlmailman script from TheSin <thesin(a)SPAMNOTHANKS.southofheaven.org> * Follow Barry Warsaw's suggestion on delivery status timestamp. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-01-08 03:38 Message: Logged In: YES user_id=99923 Latest version incorporates automated generation of the necessary tables, cleaner error reporting, and updated documentation. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2003-11-11 03:14 Message: Logged In: YES user_id=99923 Bit of an oops in version 1.49, 1.50 now uploaded, which should fix it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&group_i…

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders October 2005