From noreply at sourceforge.net Tue Nov 2 03:45:48 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Nov 2 03:45:59 2004 Subject: [ mailman-Patches-1057579 ] add urlhost/emailhost options to newlist Message-ID: Patches item #1057579, was opened at 2004-10-31 05:39 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1057579&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add urlhost/emailhost options to newlist Initial Comment: Discussions in Mailman-Developers lead to add new options to bin/newlist in such a way that current urlhost/emailhost confusion may be cleared. $ newlist --urlhost=www.dom.ain --emailhost=mail.dom.ain listname We also keep @ notation for backward compatibility: $ newlist listname@www.dom.ain This is a draft patch for program part. Documentation is yet to be fixed. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-02 02:45 Message: Logged In: YES user_id=67709 update this patch for adding documents. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1057579&group_id=103 From noreply at sourceforge.net Tue Nov 2 05:25:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Nov 2 05:25:09 2004 Subject: [ mailman-Patches-984682 ] header is not converted to unicode when sending reminder Message-ID: Patches item #984682, was opened at 2004-07-03 18:07 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=984682&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Arkadiusz Miskiewicz (arekm) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: header is not converted to unicode when sending reminder Initial Comment: [root@anduril cron]# su - mailman -s /bin/sh -c "python -S /var/lib/mailman/cron/mailpasswds -l pld-rc-scripts" Traceback (most recent call last): File "/var/lib/mailman/cron/mailpasswds", line 239, in ? main() File "/var/lib/mailman/cron/mailpasswds", line 214, in main text += (header + '\n' + NL.join(table)) UnicodeDecodeError: 'ascii' codec can't decode byte 0xb3 in position 44: ordinal not in range(128) the problem is that header is created: header = '%-40s %-10s\n%-40s %-10s' % ( _('List'), _('Password // URL'), '----', '--------') but for example Password in Polish contains non-ascii characters so this patch is needed: # Coerce everything to Unicode +header = tounicode(header, enc) text = tounicode(text, enc) table = [tounicode(_t, enc) for _t in table] This fixes problem for me. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-02 04:25 Message: Logged In: YES user_id=67709 I'll take this because it's an i18n issue. We may need more patch because passing unicode body to email is broken in japanese environment. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=984682&group_id=103 From noreply at sourceforge.net Wed Nov 3 16:33:49 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 3 16:33:51 2004 Subject: [ mailman-Feature Requests-1059566 ] Message number assignment during archiving with pipermail... Message-ID: Feature Requests item #1059566, was opened at 2004-11-03 15:33 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=1059566&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Message number assignment during archiving with pipermail... Initial Comment: Folks, Currently, pipermail will generate a number for each message as it is processing the archive, including importing mbox-format archives from other sources. Unfortunately, the numbers are specific to each installation, so importing an archive from somewhere else causes the message numbers after import to be different. Among other things, this makes it difficult to move a list from one server to another and to set up a simple redirect from the old location to the new one, since the message numbers could well be different between the two sites. It would be really, really nice if pipermail would use something like an md5 hash of the message headers to generate a unique archive id that could be used instead, so that the id could be consistent across systems. Since the "Message-id:" header should be unique for every message, and the date/time stamps and queue-ids used by the various servers (and logged within the "Received:" headers) will almost certainly be slightly different for every message, using an md5 hash should give you a good guarantee that the output pipermail archive id would likewise be completely unique. You could use the lower 16 hex characters of the 128-bit/32- character md5 hash that is typically generated, and your probability of collisions between any two messages will be vanishingly small in the resulting 64-bit space. If you're concerned about filename length, represent the data in base64 format (6 bits per ASCII character instead of four), and get the whole 128-bit hash compressed down to 22 output characters. You could then take a smaller slice and still get more bits of hash output. If you don't like md5 for personal reasons, then maybe sha-1? But please, whatever is used, please, please, please let it be something that could be derived from the headers of the messages themselves and guaranteed to be consistent across systems. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1059566&group_id=103 From noreply at sourceforge.net Wed Nov 3 17:29:37 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 3 17:29:40 2004 Subject: [ mailman-Bugs-1059598 ] Uncatched bounces by "PostMaster Enterprise" MTA Message-ID: Bugs item #1059598, was opened at 2004-11-03 17:29 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=1059598&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Alster (alster) Assigned to: Nobody/Anonymous (nobody) Summary: Uncatched bounces by "PostMaster Enterprise" MTA Initial Comment: Hi! We're currently using Mailman version 2.1.4 at lists.indymedia.org. Lately we have received a couple of non delivery notifications which have not been recognized by mailman. I'm forwarding one of them to you hoping that you will be able to include a recognition mechanism for it in one of the upcoming Mailman releases. In case you need to get into touch with the developers of thatis software, here's the product page: http://www.mailserve.net/products/enterprise_overview.htm Neither Indymedia nor me are endorsed or affiliated with them. Thanks for your continued development on a great free software! Greetings, Alster >From - Mon Nov 1 17:07:06 2004 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: Delivered-To: alster@zeromail.org Received: (qmail 13007 invoked from network); 1 Nov 2004 16:01:57 -0000 Received: from unknown (HELO smtpin.zeromail.org) (217.114.68.251) by 0 with SMTP; 1 Nov 2004 16:01:57 -0000 Received: from localhost (mate [127.0.0.1]) by smtpin.zeromail.org (Postfix) with ESMTP id B65352801EA for ; Mon, 1 Nov 2004 17:02:18 +0100 (CET) Received: from smtpin.zeromail.org ([217.114.68.251]) by localhost (mate [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31983-04 for ; Mon, 1 Nov 2004 17:02:18 +0100 (CET) Received: from sarai.indymedia.org (sarai.indymedia.org [207.229.92.161]) by smtpin.zeromail.org (Postfix) with ESMTP id 6F2EA28010A for ; Mon, 1 Nov 2004 17:02:16 +0100 (CET) Received: from [127.0.0.1] (localhost [127.0.0.1]) by sarai.indymedia.org (Postfix) with ESMTP id D0A5E45DB; Mon, 1 Nov 2004 06:43:51 -0800 (PST) X-Original-To: mailman-owner@lists.indymedia.org Delivered-To: mailman@sarai.indymedia.org Received: from md.mailserve.net (s4.qlc.co.in [69.59.172.204]) by sarai.indymedia.org (Postfix) with ESMTP id 8E2DE45FD for ; Mon, 1 Nov 2004 06:42:43 -0800 (PST) Received: from mail2.qlc.co.in (mail2.qlc.co.in [203.199.124.121]) by md.mailserve.net (Postfix) with ESMTP id E4EC71535DF for ; Mon, 1 Nov 2004 20:12:52 -0800 (PST) Received: from tiss.edu (unknown [202.141.154.108]) by mail2.qlc.co.in (Postfix) with ESMTP id B650D1C017 for ; Mon, 1 Nov 2004 20:19:23 +0530 (IST) Message-ID: <1099321413711.1.postmaster@tiss.edu> Date: Mon, 1 Nov 2004 20:33:33 +0530 From: Administrator To: X-Mailserver: Received using PostMaster Enterprise (v5.1.04) on [127.0.0.1] Linux (2.4.18-14) X-Mailman-Id: 1101-7pu X-Archived-At: http://lists.indymedia.org/mailman/mmid/mailman/2004-1101-7pu Subject: [Mailman] PostMaster Enterprise Alert - User Unknown X-BeenThere: mailman@lists.indymedia.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: mailman.lists.indymedia.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mailman-bounces@lists.indymedia.org Errors-To: mailman-bounces@lists.indymedia.org X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at zeromail.org *************************************** ** PostMaster Enterprise Alert ** System Generated Message ** Do Not Reply To This *************************************** ---- Message not delivered ---- User <> Unknown ---- Original message replaced by message headers ---- Date: Mon, 01 Nov 2004 05:09:35 -0800 From: mailman-owner@lists.indymedia.org Subject: lists.indymedia.org mailing list memberships reminder ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1059598&group_id=103 From noreply at sourceforge.net Wed Nov 3 18:09:11 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 3 18:09:18 2004 Subject: [ mailman-Bugs-1059633 ] E-Mail address obfuscation non-functional on subject Message-ID: Bugs item #1059633, was opened at 2004-11-03 18:09 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=1059633&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Alster (alster) Assigned to: Nobody/Anonymous (nobody) Summary: E-Mail address obfuscation non-functional on subject Initial Comment: Hi! I realized that the email address obfuscation a la "me at mydomain.com" (at-sign replaced by " at ") instead of "me@mydomain.com" (plain at-sign) does not take place if the email address is given in the subject line of an email. Especially spam and email address verification emails put email addresses into the subject line. While this is a bad habit, it still happens and simplifies (re-)harvesting of email addresses from pipermails' archives. Thanks, Alster ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1059633&group_id=103 From noreply at sourceforge.net Wed Nov 3 18:14:37 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 3 18:14:39 2004 Subject: [ mailman-Bugs-1059637 ] Leave choice on obfuscation method to sysadmin Message-ID: Bugs item #1059637, was opened at 2004-11-03 18:14 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=1059637&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Alster (alster) Assigned to: Nobody/Anonymous (nobody) Summary: Leave choice on obfuscation method to sysadmin Initial Comment: As far as I know, currently the way pipermail obfuscates email addresses is hardcoded to "user at domain.com". This is really easy to harvest. It may be a better idea to leave the method of obfuscation to the mailman (sys)admin (not list admin). This will result in increased diversity of obfuscation methods on the several pipermail setups and thus to decreased harvesting. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1059637&group_id=103 From noreply at sourceforge.net Wed Nov 3 23:23:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 3 23:23:19 2004 Subject: [ mailman-Feature Requests-1059834 ] daily digest: change mail body Message-ID: Feature Requests item #1059834, was opened at 2004-11-03 22:23 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1059834&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Common Man (commonman123) Assigned to: Nobody/Anonymous (nobody) Summary: daily digest: change mail body Initial Comment: Thank you for developing great program! Our web host administrator told us to write / report the missing setting to you directly. We are using Mailman's daily digest feature but there is missing one important setting to change daily digest mail body. We would like to move the list info (how to unsubscribe etc.) from begging of the mail body to the bottom of the mail. It is quite important for the daily digest readers because it is right now makes too complicated (not comfortable) to read the mail this way when every time you have to read the same beginning. Thank you ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1059834&group_id=103 From noreply at sourceforge.net Wed Nov 3 23:24:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 3 23:24:21 2004 Subject: [ mailman-Feature Requests-1059834 ] daily digest new setting: mail body change Message-ID: Feature Requests item #1059834, was opened at 2004-11-03 22:23 Message generated for change (Settings changed) made by commonman123 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1059834&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Common Man (commonman123) Assigned to: Nobody/Anonymous (nobody) >Summary: daily digest new setting: mail body change Initial Comment: Thank you for developing great program! Our web host administrator told us to write / report the missing setting to you directly. We are using Mailman's daily digest feature but there is missing one important setting to change daily digest mail body. We would like to move the list info (how to unsubscribe etc.) from begging of the mail body to the bottom of the mail. It is quite important for the daily digest readers because it is right now makes too complicated (not comfortable) to read the mail this way when every time you have to read the same beginning. Thank you ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1059834&group_id=103 From noreply at sourceforge.net Sun Nov 7 13:06:37 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Nov 7 13:06:47 2004 Subject: [ mailman-Patches-1057579 ] add urlhost/emailhost options to newlist Message-ID: Patches item #1057579, was opened at 2004-10-31 05:39 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1057579&group_id=103 Category: command line scripts Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add urlhost/emailhost options to newlist Initial Comment: Discussions in Mailman-Developers lead to add new options to bin/newlist in such a way that current urlhost/emailhost confusion may be cleared. $ newlist --urlhost=www.dom.ain --emailhost=mail.dom.ain listname We also keep @ notation for backward compatibility: $ newlist listname@www.dom.ain This is a draft patch for program part. Documentation is yet to be fixed. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-07 12:06 Message: Logged In: YES user_id=67709 checked in CVS. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-02 02:45 Message: Logged In: YES user_id=67709 update this patch for adding documents. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1057579&group_id=103 From noreply at sourceforge.net Mon Nov 8 11:47:59 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Nov 8 11:48:48 2004 Subject: [ mailman-Bugs-1041791 ] Bug in Mailman version 2.1.5 - help Message-ID: Bugs item #1041791, was opened at 2004-10-06 23:14 Message generated for change (Comment added) made by gdv You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1041791&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: FeniX (zmrozek) Assigned to: Nobody/Anonymous (nobody) Summary: Bug in Mailman version 2.1.5 - help Initial Comment: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 96, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 42, in main listinfo_overview() File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 88, in listinfo_overview if mlist.advertised: File "/usr/lib/mailman/Mailman/MailList.py", line 144, in __getattr__ raise AttributeError, name AttributeError: advertised Python information: Variable Value sys.version 2.3.4 (#2, Sep 24 2004, 08:39:09) [GCC 3. 3.4 (Debian 1:3.3.4-12)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_COOKIE openwebmail-loginname=jurek; openwebmail-httpcompress=0 SERVER_SOFTWARE Apache/1.3.31 (Debian GNU/Linux) mod_gzip/1.3.26.1a SCRIPT_NAME /mailman/listinfo SERVER_SIGNATURE REQUEST_METHOD GET SERVER_PROTOCOL HTTP/1.1 QUERY_STRING HTTP_TE deflate, gzip, chunked, identity, trailers HTTP_ACCEPT_CHARSET iso-8859-2, utf-8, utf-16, iso- 8859-1;q=0.6, *;q=0.1 HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.54 [pl] HTTP_CONNECTION Keep-Alive, TE SERVER_NAME eko.org.pl REMOTE_ADDR 156.17.228.163 SERVER_PORT 80 SERVER_ADDR 195.116.86.81 DOCUMENT_ROOT /httpd/htdocs/www.eko.wroc.pl PYTHONPATH /var/lib/mailman SCRIPT_FILENAME /httpd/cgi-bin/mailman/listinfo SERVER_ADMIN webmaster@eko.wroc.pl HTTP_HOST eko.org.pl HTTP_COOKIE2 $Version=1 HTTP_CACHE_CONTROL no-cache REQUEST_URI /mailman/listinfo HTTP_ACCEPT text/html, application/xml;q=0.9, application/xhtml+xml, image/png, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 2632 HTTP_ACCEPT_LANGUAGE pl;q=1.0,en;q=0.9 HTTP_ACCEPT_ENCODING deflate, gzip, x-gzip, identity, *;q=0 UNIQUE_ID QWRfL8N0VlEAACVGm7I ---------------------------------------------------------------------- Comment By: Gianluca Della Vedova (gdv) Date: 2004-11-08 11:47 Message: Logged In: YES user_id=345813 I confirm the above bug. It happened after an upgrade of Debian testing (every package in the system is a packaged version from a well-known mirror, no package is built from source in-house). the output of follows: dellavedova@hp700:~$ ls -l /var/lib/mailman/lists/* /var/lib/mailman/lists/biostatistica: total 960 -rw-rw---- 1 list list 483396 Nov 8 09:00 config.pck -rw-rw---- 1 list list 483987 Nov 7 12:00 config.pck.last -rw-rw---- 1 list list 391 Nov 8 09:57 pending.pck -rw-rw-r-- 1 root list 3104 Oct 4 12:04 request.pck /var/lib/mailman/lists/mailman: total 16 -rw-rw---- 1 list list 3380 Nov 8 09:00 config.pck -rw-rw---- 1 list list 3380 Nov 7 12:00 config.pck.last -rw-rw---- 1 root list 860 Oct 4 12:04 pending.pck -rw-rw-r-- 1 root list 24 Oct 4 12:04 request.pck /var/lib/mailman/lists/newsletter: total 128 -rw-rw---- 1 list list 8171 Apr 4 2003 config.db -rw-rw---- 1 list list 8171 Apr 4 2003 config.db.last -rw-rw---- 1 list list 36548 Nov 8 09:00 config.pck -rw-rw---- 1 list list 36227 Nov 7 12:00 config.pck.last -rw-rw-r-- 1 root list 4255 Mar 11 2003 handle_opts.html -rw-rw-r-- 1 root list 7080 Mar 19 2003 listinfo.html -rw-rw-r-- 1 root list 0 Feb 11 2003 next-digest -rw-rw-r-- 1 root list 0 Feb 11 2003 next-digest-topics -rw-rw-r-- 1 root list 7641 Mar 10 2003 options.html -rw-rw---- 1 www-data list 1124 Nov 8 09:59 pending.pck -rw-rw-r-- 1 www-data list 24 Nov 4 23:24 request.pck -rw-rw-r-- 1 root list 4233 Mar 10 2003 subscribe.html /var/lib/mailman/lists/statecon: total 904 -rw-rw---- 1 list list 447779 Nov 8 09:00 config.pck -rw-rw---- 1 list list 453152 Nov 7 12:00 config.pck.last -rw-rw---- 1 list list 744 Nov 8 09:57 pending.pck -rw-rw-r-- 1 root list 14629 Oct 4 12:04 request.pck ---------------------------------------------------------------------- Comment By: Vance Wheelock II (bongervw) Date: 2004-10-30 06:17 Message: Logged In: YES user_id=100213 I had the same issue after upgrading to 2.1.5.... This can be caused when you have a corrupted list or a list does not contain all of it's pieces. I have a small number of lists, so I ran the list_members script for each list until I found the offending list. In my case it was easy because it was a dummy "test" list that I could remove. If others have this issue on a valid list, then they will need to backup the lists files and recreate it. (someone else may have a beter way to fix the corruption depending upon what it is) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-10-13 15:06 Message: Logged In: YES user_id=67709 Can you explain more detail of the environment ? Is this your fresh install of mailman, or upgrading from older version ? Install from source or package ? What do you you when you exec 'ls -l /lists/*' ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1041791&group_id=103 From noreply at sourceforge.net Mon Nov 8 11:59:01 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Nov 8 11:59:03 2004 Subject: [ mailman-Bugs-1062346 ] Exim documentation has typeos Message-ID: Bugs item #1062346, was opened at 2004-11-08 10: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=1062346&group_id=103 Category: documentation Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: alain williams (addw) Assigned to: Nobody/Anonymous (nobody) Summary: Exim documentation has typeos Initial Comment: There are backslashes missing and an extra line in the ACL example on SMTP callback. The ACL: warn message = X-WhitelistedRCPT-nohdrfromcallback: Yes condition = ${if and {{match{$local_part}{(.*)-bounces\+.*}} {exists {MAILMAN_HOME/lists/$1/config.pck}}} {yes}{no}} {yes}{no}} should be: warn message = X-WhitelistedRCPT-nohdrfromcallback: Yes condition = ${if and {{match{$local_part}{(.*)-bounces\+.*}} {exists {MAILMAN_HOME/lists/$1/config.pck}}} {yes}{no}} Same for the 'accept' one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1062346&group_id=103 From noreply at sourceforge.net Mon Nov 8 12:06:45 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Nov 8 12:06:47 2004 Subject: [ mailman-Patches-1062352 ] Patch to fix exim documentation bug 1062346 Message-ID: Patches item #1062352, was opened at 2004-11-08 11:06 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1062352&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: alain williams (addw) Assigned to: Nobody/Anonymous (nobody) Summary: Patch to fix exim documentation bug 1062346 Initial Comment: This fixes the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1062352&group_id=103 From noreply at sourceforge.net Mon Nov 8 21:52:46 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Nov 8 21:52:49 2004 Subject: [ mailman-Bugs-1062663 ] empty charset in header crashes admindb.py Message-ID: Bugs item #1062663, was opened at 2004-11-08 20:52 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=1062663&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: empty charset in header crashes admindb.py Initial Comment: when a message contains a header like this: Content-Type: text/plain; charset= (note the empty charset) The admindb.py details page page gives an error. Traceback is below. Btw does this mean the charset value in the header is directly mapped to a module name to import? (sounds kinda scary...) I know the real fault is in the message (I'm not sure if the mime stripper caused this or a bad mailer), but maybe mailman shouldn't crash on this. Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 222, in main show_detailed_requests(mlist, form) File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 545, in show_detailed_requests show_post_requests(mlist, id, info, total, count, form) File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 611, in show_post_requests body = unicode(body, mcset).encode(lcset) File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') ValueError: Empty module name ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1062663&group_id=103 From noreply at sourceforge.net Wed Nov 10 00:35:37 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 10 00:35:41 2004 Subject: [ mailman-Bugs-1063491 ] Put an error message instead of a bug page Message-ID: Bugs item #1063491, was opened at 2004-11-09 23: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=1063491&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Laurent Rathle (lrathle) Assigned to: Nobody/Anonymous (nobody) Summary: Put an error message instead of a bug page Initial Comment: Hello, When you put a wrong email in Mailman (with accent, for exemple), and you want to list the subscribers on the web, Mailman show a bug message, which is not clear, since you can think it's the software that goes wrong. Is it possible to had a function that would display a web page saying "there is a worng email in the database", for exemple instead of the bug web page. Thank you, ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1063491&group_id=103 From noreply at sourceforge.net Wed Nov 10 10:04:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 10 10:07:50 2004 Subject: [ mailman-Bugs-974759 ] HTML email and attachment archiving inconsistencies Message-ID: Bugs item #974759, was opened at 2004-06-17 14:16 Message generated for change (Comment added) made by nickbower You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=974759&group_id=103 >Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nick Bower (nickbower) Assigned to: Nobody/Anonymous (nobody) Summary: HTML email and attachment archiving inconsistencies Initial Comment: With archiving set to on and content filtering off (default options everywhere), I've encountered inconsistencies with the mail archiving and multipart attachments. If I send a HTML email, the arhived message correctly shows the text/plain porition with a link to the HTML version. However if I send a HTML email with an image attachment, the archived message shows nothing except for the link to the image. The original message (in either plain text or HTML) is lost. I would have expected the same plain text view with now 2 links to both the HTML part and image attachment. I've tested this with Outlook and Evolution. Note that if I send 1 or more images attached to a plain text message, everything works as expected. Thanks, Nick ---------------------------------------------------------------------- >Comment By: Nick Bower (nickbower) Date: 2004-11-10 09:04 Message: Logged In: YES user_id=57135 Although this is a pipermail issue, no-one seems to be noticing pipermail bugs. Submitting to web queue. ---------------------------------------------------------------------- Comment By: Fergus Donohue (fergusdonohue) Date: 2004-08-20 14:55 Message: Logged In: YES user_id=1107982 This is happening to me on Mailman 2.1.5 on Solaris. It probably merits more than a P5 based on the numbers of users who send text and html messages from outlook? If anyone likes I can send a shell script that generates this behaviour by piping data to port 25. I've tested the patches for Scrubber.py but they don't rectify this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=974759&group_id=103 From noreply at sourceforge.net Wed Nov 10 13:38:24 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 10 13:38:31 2004 Subject: [ mailman-Bugs-974759 ] HTML email and attachment archiving inconsistencies Message-ID: Bugs item #974759, was opened at 2004-06-17 14:16 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=974759&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nick Bower (nickbower) Assigned to: Nobody/Anonymous (nobody) Summary: HTML email and attachment archiving inconsistencies Initial Comment: With archiving set to on and content filtering off (default options everywhere), I've encountered inconsistencies with the mail archiving and multipart attachments. If I send a HTML email, the arhived message correctly shows the text/plain porition with a link to the HTML version. However if I send a HTML email with an image attachment, the archived message shows nothing except for the link to the image. The original message (in either plain text or HTML) is lost. I would have expected the same plain text view with now 2 links to both the HTML part and image attachment. I've tested this with Outlook and Evolution. Note that if I send 1 or more images attached to a plain text message, everything works as expected. Thanks, Nick ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-10 12:38 Message: Logged In: YES user_id=67709 I think this bug was fixed in latest CVS (Release_2_1-maint). Please try upgrading from CVS. Note that you need to add '-r Release_2_1-maint' when checking out. ---------------------------------------------------------------------- Comment By: Nick Bower (nickbower) Date: 2004-11-10 09:04 Message: Logged In: YES user_id=57135 Although this is a pipermail issue, no-one seems to be noticing pipermail bugs. Submitting to web queue. ---------------------------------------------------------------------- Comment By: Fergus Donohue (fergusdonohue) Date: 2004-08-20 14:55 Message: Logged In: YES user_id=1107982 This is happening to me on Mailman 2.1.5 on Solaris. It probably merits more than a P5 based on the numbers of users who send text and html messages from outlook? If anyone likes I can send a shell script that generates this behaviour by piping data to port 25. I've tested the patches for Scrubber.py but they don't rectify this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=974759&group_id=103 From noreply at sourceforge.net Thu Nov 11 15:00:07 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Nov 11 15:00:10 2004 Subject: [ mailman-Bugs-1064494 ] Accessing list web page - bug report Message-ID: Bugs item #1064494, was opened at 2004-11-11 15: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=1064494&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ralphabf (mudd47) Assigned to: Nobody/Anonymous (nobody) Summary: Accessing list web page - bug report Initial Comment: Bug in Mailman version 2.1.4 Traceback: Traceback (most recent call last): File "/usr/lib/mailman/scripts/driver", line 68, in run_main immediate=1) File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py ", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 49, in __init__ self.__get_f() File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 67, in __get_f 1) File "/usr/lib/python2.3/codecs.py", line 566, in open file = __builtin__.open(filename, mode, buffering) IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' ------------------------------------------------------ -------------------------- Python information: Variable Value sys.version 2.3.3 (#2, Feb 17 2004, 11:45:40) [GCC 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------ -------------------------- Environment variables: Variable Value SERVER_SOFTWARE Apache- AdvancedExtranetServer/2.0.48 (Mandrake Linux/6.7.100mdk) SCRIPT_NAME /mailman/admin SERVER_SIGNATURE Apache- AdvancedExtranetServer/2.0.48 (Mandrake Linux/6.7.100mdk) Server at hyndan.gbg.abf.se Port 80 REQUEST_METHOD GET PATH_INFO /mailman SERVER_PROTOCOL HTTP/1.1 QUERY_STRING HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) HTTP_CONNECTION Keep-Alive SERVER_NAME hyndan.gbg.abf.se REMOTE_ADDR 62.127.120.98 PATH_TRANSLATED /var/www/html/mailman SERVER_PORT 80 SERVER_ADDR 192.168.1.111 DOCUMENT_ROOT /var/www/html PYTHONPATH /usr/lib/mailman SCRIPT_FILENAME /usr/lib/mailman/cgi-bin/admin SERVER_ADMIN root@localhost HTTP_HOST hyndan.gbg.abf.se REQUEST_URI /mailman/admin/mailman HTTP_ACCEPT */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 16872 HTTP_ACCEPT_LANGUAGE sv HTTP_ACCEPT_ENCODING gzip, deflate ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1064494&group_id=103 From noreply at sourceforge.net Sat Nov 13 01:15:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Nov 13 01:15:24 2004 Subject: [ mailman-Feature Requests-828564 ] per-user " Reply-To:" configuration Message-ID: Feature Requests item #828564, was opened at 2003-10-22 22:54 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=828564&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jorge Bernal (koke) Assigned to: Nobody/Anonymous (nobody) Summary: per-user "Reply-To:" configuration Initial Comment: In order to prevent the periodic flame about "Reply-To-harmful" and "Reply-To-is-good", it would be a great feature if any user could choose if he/she wants the "Reply-To" header to be modified or not ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-13 00:15 Message: Logged In: YES user_id=18417 Duplicate of 788314? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=828564&group_id=103 From noreply at sourceforge.net Sat Nov 13 01:16:00 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Nov 13 01:16:04 2004 Subject: [ mailman-Feature Requests-788314 ] personal option for explicit reply-to header Message-ID: Feature Requests item #788314, was opened at 2003-08-13 20:22 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=788314&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: personal option for explicit reply-to header Initial Comment: Some list members have a broken email reader that will not give them a list reply option. Outlook for instance. People using some email readers just don't use it, because the functionality is hidden (like many KMail users). They beg the adminstrator to mangle the reply-to header. Other users of course find that harmful. A per user (and per list?) option to set an explicit reply-to header to the list seems to be a good solution. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-13 00:15 Message: Logged In: YES user_id=18417 Duplicate of 828564? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=788314&group_id=103 From noreply at sourceforge.net Sat Nov 13 11:48:35 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Nov 13 11:48:45 2004 Subject: [ mailman-Patches-984682 ] header is not converted to unicode when sending reminder Message-ID: Patches item #984682, was opened at 2004-07-03 18:07 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=984682&group_id=103 Category: command line scripts Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 5 Submitted By: Arkadiusz Miskiewicz (arekm) Assigned to: Tokio Kikuchi (tkikuchi) Summary: header is not converted to unicode when sending reminder Initial Comment: [root@anduril cron]# su - mailman -s /bin/sh -c "python -S /var/lib/mailman/cron/mailpasswds -l pld-rc-scripts" Traceback (most recent call last): File "/var/lib/mailman/cron/mailpasswds", line 239, in ? main() File "/var/lib/mailman/cron/mailpasswds", line 214, in main text += (header + '\n' + NL.join(table)) UnicodeDecodeError: 'ascii' codec can't decode byte 0xb3 in position 44: ordinal not in range(128) the problem is that header is created: header = '%-40s %-10s\n%-40s %-10s' % ( _('List'), _('Password // URL'), '----', '--------') but for example Password in Polish contains non-ascii characters so this patch is needed: # Coerce everything to Unicode +header = tounicode(header, enc) text = tounicode(text, enc) table = [tounicode(_t, enc) for _t in table] This fixes problem for me. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-13 10:48 Message: Logged In: YES user_id=67709 fixed in CVS Revision 2.13.2.4 ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-02 04:25 Message: Logged In: YES user_id=67709 I'll take this because it's an i18n issue. We may need more patch because passing unicode body to email is broken in japanese environment. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=984682&group_id=103 From noreply at sourceforge.net Sun Nov 14 00:57:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Nov 14 00:57:56 2004 Subject: [ mailman-Patches-970873 ] typo in english template user options page Message-ID: Patches item #970873, was opened at 2004-06-11 04:40 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=970873&group_id=103 Category: Web UI Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 5 Submitted By: Jim Tittsler (jtittsler) Assigned to: Nobody/Anonymous (nobody) Summary: typo in english template user options page Initial Comment: says to delivery such non-matching messages to you. should be says to deliver such non-matching messages to you. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-13 23:57 Message: Logged In: YES user_id=67709 fixed in CVS ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=970873&group_id=103 From noreply at sourceforge.net Sun Nov 14 01:27:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Nov 14 01:27:34 2004 Subject: [ mailman-Patches-850805 ] Aggressive anti email address harvesting measure Message-ID: Patches item #850805, was opened at 2003-11-28 16:23 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&group_id=103 Category: Pipermail >Group: Mailman 2.2 / 3.0 Status: Open >Resolution: Postponed Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Aggressive anti email address harvesting measure Initial Comment: This patch is prompted by discussion on the mailman- developers list won the following subject: Re: [Mailman-Developers] bugtraq submission warning: email address harvesting exploit For those with deep concerns about email address harvesting this patch offers a more aggressive masking of email addresses in Mailman mail archive files. The patch modifes two files in the standard Mailman distribution: Mailman/Defaults.py and Mailman/Cgi/ private.py and can be applied using the following command from within the Mailman build directory: path -p1 < path-to-patch-file It would be fairly trivial to make enabling this feature per- list configurable rather than it being a site admin decision and I will enhance this patch for that purpose if people show an interest in it being done. The following notes about the patch can be found in Defaults.py. Rather idiosyncratically most of the operational elements of this patch are in that file. My reasoning behind this decision is that if people want to fool with the regexes that are at the heart of this patch they can see what will be affected by the changes more readily if the related bits are in the same place. ##### # Anti-spam email address harvesting prevention measures. # # These measures are to limit the ability of spam generators to acquire # email address from archived material in Mailman's list archives. # Implementation is via a dynamic search and replace for email # addresses, appearing in files of MIME type text/html or text/plain, as # those files are requested. The underlying archive file content as # generated by the archiving software remains unchanged. # # The implementation requires that archive files are all delivered by a # modified private.py CGI script which only requires user authentication # if the list whose archive material is being requested is set up as a private # list. In order to get public archives served by private.py a RewriteRule # like this: # # RewriteRule ^/pipermail/(.*) /mailman/private/$1 [PT] # # needs to be used in the Apache httpd.conf to transparently redirect # public arechive file requests. # # When email addresses are found, the domain part of the addressed is replaced # with a string of 'x' characters. If the local part of the address appears to # have been VERP'ed then the VERP information is similarly obscured. This is # a fairly brutal set of irreversible modifications to any email addresses in # the returned text and will break any mailto: links in the text. # # Th eamil address regex looks for either an '@' character or its HTML escaped # version '%40' as the local-part/domain separator. You should set # ARCHIVER_OBSCURES_EMAILADDRS = 0 and run bin/arch to rebuild existing archives # to prevent that feature interfering with the operation of these harvesting # prevention measures. # # If you decide to change the regexes then copy all of this stuff into # mm_cfg.py and make the changes there. # ##### ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-14 00:27 Message: Logged In: YES user_id=67709 It looks nice but it may be too much for 2.1.x where the archives are generated static. Also, I'm a little bit anxious writing such a function in Defaults.py. It would be better to include this feature in 3.0 or later. ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 09:52 Message: Logged In: YES user_id=696559 Ohh, sorry, the patch really wasn't applied. After proper installation, I can confirm it works fine. ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 00:00 Message: Logged In: YES user_id=696559 What sould I do with this error caused by the patch? Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/private.py", line 165, in main sys.stdout.write(mm_cfg.deny_harvest(f.read())) AttributeError: 'module' object has no attribute 'deny_harvest' ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-11-30 07:02 Message: Logged In: YES user_id=75166 As pointed out on the mailman-developers list, potential users of this patch should be aware that the simple approach to masking email addresses used by this patch will also capture and munge any other strings in the archive data that resemble email addresses. This can include mailto URLs, other URLs and Message ids. This side-effect may make the patch unsuitable for use with your system, although you also need to consider that the patch does not irreversibly change the source pipermail archived material held on the server; the changes are only made in the copy of the archive material sent to the requesting browser by the server. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&group_id=103 From noreply at sourceforge.net Sun Nov 14 01:28:58 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Nov 14 01:29:04 2004 Subject: [ mailman-Patches-850805 ] Aggressive anti email address harvesting measure Message-ID: Patches item #850805, was opened at 2003-11-28 16:23 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&group_id=103 Category: Pipermail >Group: Mailman 2.1 Status: Open Resolution: Postponed Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Aggressive anti email address harvesting measure Initial Comment: This patch is prompted by discussion on the mailman- developers list won the following subject: Re: [Mailman-Developers] bugtraq submission warning: email address harvesting exploit For those with deep concerns about email address harvesting this patch offers a more aggressive masking of email addresses in Mailman mail archive files. The patch modifes two files in the standard Mailman distribution: Mailman/Defaults.py and Mailman/Cgi/ private.py and can be applied using the following command from within the Mailman build directory: path -p1 < path-to-patch-file It would be fairly trivial to make enabling this feature per- list configurable rather than it being a site admin decision and I will enhance this patch for that purpose if people show an interest in it being done. The following notes about the patch can be found in Defaults.py. Rather idiosyncratically most of the operational elements of this patch are in that file. My reasoning behind this decision is that if people want to fool with the regexes that are at the heart of this patch they can see what will be affected by the changes more readily if the related bits are in the same place. ##### # Anti-spam email address harvesting prevention measures. # # These measures are to limit the ability of spam generators to acquire # email address from archived material in Mailman's list archives. # Implementation is via a dynamic search and replace for email # addresses, appearing in files of MIME type text/html or text/plain, as # those files are requested. The underlying archive file content as # generated by the archiving software remains unchanged. # # The implementation requires that archive files are all delivered by a # modified private.py CGI script which only requires user authentication # if the list whose archive material is being requested is set up as a private # list. In order to get public archives served by private.py a RewriteRule # like this: # # RewriteRule ^/pipermail/(.*) /mailman/private/$1 [PT] # # needs to be used in the Apache httpd.conf to transparently redirect # public arechive file requests. # # When email addresses are found, the domain part of the addressed is replaced # with a string of 'x' characters. If the local part of the address appears to # have been VERP'ed then the VERP information is similarly obscured. This is # a fairly brutal set of irreversible modifications to any email addresses in # the returned text and will break any mailto: links in the text. # # Th eamil address regex looks for either an '@' character or its HTML escaped # version '%40' as the local-part/domain separator. You should set # ARCHIVER_OBSCURES_EMAILADDRS = 0 and run bin/arch to rebuild existing archives # to prevent that feature interfering with the operation of these harvesting # prevention measures. # # If you decide to change the regexes then copy all of this stuff into # mm_cfg.py and make the changes there. # ##### ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-14 00:28 Message: Logged In: YES user_id=67709 Sorry, patch itself is for 2.1 (not 3.0). ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-14 00:27 Message: Logged In: YES user_id=67709 It looks nice but it may be too much for 2.1.x where the archives are generated static. Also, I'm a little bit anxious writing such a function in Defaults.py. It would be better to include this feature in 3.0 or later. ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 09:52 Message: Logged In: YES user_id=696559 Ohh, sorry, the patch really wasn't applied. After proper installation, I can confirm it works fine. ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 00:00 Message: Logged In: YES user_id=696559 What sould I do with this error caused by the patch? Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/private.py", line 165, in main sys.stdout.write(mm_cfg.deny_harvest(f.read())) AttributeError: 'module' object has no attribute 'deny_harvest' ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-11-30 07:02 Message: Logged In: YES user_id=75166 As pointed out on the mailman-developers list, potential users of this patch should be aware that the simple approach to masking email addresses used by this patch will also capture and munge any other strings in the archive data that resemble email addresses. This can include mailto URLs, other URLs and Message ids. This side-effect may make the patch unsuitable for use with your system, although you also need to consider that the patch does not irreversibly change the source pipermail archived material held on the server; the changes are only made in the copy of the archive material sent to the requesting browser by the server. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&group_id=103 From noreply at sourceforge.net Sun Nov 14 01:35:43 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Nov 14 01:35:47 2004 Subject: [ mailman-Patches-674433 ] Add post_id information to messages Message-ID: Patches item #674433, was opened at 2003-01-25 03:09 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674433&group_id=103 Category: None Group: Mailman 2.1 Status: Open >Resolution: Wont Fix Priority: 3 Submitted By: Steve Huston (srhuston) Assigned to: Nobody/Anonymous (nobody) Summary: Add post_id information to messages Initial Comment: This patch will add the value of mlist.post_id to the mail during processing. It adds a X-Post-ID header, which can then be searched for and placed in the header/footer of the message (non-digest only). It will also grab this information to put it in the archives, so if you use a searchable archive you can search for a message by post_id. This part is a little 'iffy'. The patch assumes you have the ht://Dig patches installed, but should work fine without them; will likely complain about templates/en/article.html and templates/en/htdig-conf.txt There is also added the ability to inflate the post_id value from the "General" section in the GUI. It makes sure you keep the value as a float, as well as only lets you increase it. This is handy if you are importing messages from an old archive and need to start the post_id at a larger number so as not to interfere with old messages. Left to do as of this writing: i18n (somebody?), documentation in Gui/General.py explaining post_id better (and why you might want/need to mess with it), documentation in Gui/NonDigest.py or templates/en/headfoot.html explaining %(post_id)s variable. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-14 00:35 Message: Logged In: YES user_id=67709 Now you can add post_id in subject_prefix if you get the latest Release_2_1-maint branch from CVS. (You should put [listname %d] in subject_prefix to activate the numbering.) This patch may be replaced by the subject-numbering feature described above. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674433&group_id=103 From noreply at sourceforge.net Sun Nov 14 01:41:16 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Nov 14 01:41:22 2004 Subject: [ mailman-Patches-850805 ] Aggressive anti email address harvesting measure Message-ID: Patches item #850805, was opened at 2003-11-28 17:23 Message generated for change (Comment added) made by olaf You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: Postponed Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Aggressive anti email address harvesting measure Initial Comment: This patch is prompted by discussion on the mailman- developers list won the following subject: Re: [Mailman-Developers] bugtraq submission warning: email address harvesting exploit For those with deep concerns about email address harvesting this patch offers a more aggressive masking of email addresses in Mailman mail archive files. The patch modifes two files in the standard Mailman distribution: Mailman/Defaults.py and Mailman/Cgi/ private.py and can be applied using the following command from within the Mailman build directory: path -p1 < path-to-patch-file It would be fairly trivial to make enabling this feature per- list configurable rather than it being a site admin decision and I will enhance this patch for that purpose if people show an interest in it being done. The following notes about the patch can be found in Defaults.py. Rather idiosyncratically most of the operational elements of this patch are in that file. My reasoning behind this decision is that if people want to fool with the regexes that are at the heart of this patch they can see what will be affected by the changes more readily if the related bits are in the same place. ##### # Anti-spam email address harvesting prevention measures. # # These measures are to limit the ability of spam generators to acquire # email address from archived material in Mailman's list archives. # Implementation is via a dynamic search and replace for email # addresses, appearing in files of MIME type text/html or text/plain, as # those files are requested. The underlying archive file content as # generated by the archiving software remains unchanged. # # The implementation requires that archive files are all delivered by a # modified private.py CGI script which only requires user authentication # if the list whose archive material is being requested is set up as a private # list. In order to get public archives served by private.py a RewriteRule # like this: # # RewriteRule ^/pipermail/(.*) /mailman/private/$1 [PT] # # needs to be used in the Apache httpd.conf to transparently redirect # public arechive file requests. # # When email addresses are found, the domain part of the addressed is replaced # with a string of 'x' characters. If the local part of the address appears to # have been VERP'ed then the VERP information is similarly obscured. This is # a fairly brutal set of irreversible modifications to any email addresses in # the returned text and will break any mailto: links in the text. # # Th eamil address regex looks for either an '@' character or its HTML escaped # version '%40' as the local-part/domain separator. You should set # ARCHIVER_OBSCURES_EMAILADDRS = 0 and run bin/arch to rebuild existing archives # to prevent that feature interfering with the operation of these harvesting # prevention measures. # # If you decide to change the regexes then copy all of this stuff into # mm_cfg.py and make the changes there. # ##### ---------------------------------------------------------------------- Comment By: O.S. (olaf) Date: 2004-11-14 01:41 Message: Logged In: YES user_id=11209 please, make these harvesting prevention measures per list configurable. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-14 01:28 Message: Logged In: YES user_id=67709 Sorry, patch itself is for 2.1 (not 3.0). ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-14 01:27 Message: Logged In: YES user_id=67709 It looks nice but it may be too much for 2.1.x where the archives are generated static. Also, I'm a little bit anxious writing such a function in Defaults.py. It would be better to include this feature in 3.0 or later. ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 11:52 Message: Logged In: YES user_id=696559 Ohh, sorry, the patch really wasn't applied. After proper installation, I can confirm it works fine. ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 02:00 Message: Logged In: YES user_id=696559 What sould I do with this error caused by the patch? Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/private.py", line 165, in main sys.stdout.write(mm_cfg.deny_harvest(f.read())) AttributeError: 'module' object has no attribute 'deny_harvest' ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-11-30 08:02 Message: Logged In: YES user_id=75166 As pointed out on the mailman-developers list, potential users of this patch should be aware that the simple approach to masking email addresses used by this patch will also capture and munge any other strings in the archive data that resemble email addresses. This can include mailto URLs, other URLs and Message ids. This side-effect may make the patch unsuitable for use with your system, although you also need to consider that the patch does not irreversibly change the source pipermail archived material held on the server; the changes are only made in the copy of the archive material sent to the requesting browser by the server. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&group_id=103 From noreply at sourceforge.net Sun Nov 14 12:18:34 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Nov 14 12:18:37 2004 Subject: [ mailman-Patches-807016 ] dutch translation breaks e-mail confirmation instructions Message-ID: Patches item #807016, was opened at 2003-09-16 09:14 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=807016&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 5 Submitted By: Ward Vandewege (ward) Assigned to: Nobody/Anonymous (nobody) Summary: dutch translation breaks e-mail confirmation instructions Initial Comment: The Dutch translation in templates/nl/invite.txt translates the 'confirm' command for e-mail replies to an invitation by list owners into Dutch. Mailman does not respond to Dutch commands, so this breaks Mailman. The attached patch fixes this. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-14 11:18 Message: Logged In: YES user_id=67709 fixed in CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=807016&group_id=103 From noreply at sourceforge.net Sun Nov 14 12:26:48 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Nov 14 12:26:53 2004 Subject: [ mailman-Patches-955819 ] fix: [ 926034 ] Crashes on encoding errors Message-ID: Patches item #955819, was opened at 2004-05-18 11:14 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=955819&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K?roly Segesdi (vm303) Assigned to: Nobody/Anonymous (nobody) Summary: fix: [ 926034 ] Crashes on encoding errors Initial Comment: Actually the bug title is wrong, the problem is (I think) python not supporting windows-1250 and windows-1252. The problem can be fixed in the email library in $MAILMANDIR/pythonlib/email/Header.py I don't know if newer pythons (afaik python 2.3 contains this email package and maybe it does handle windows codepages) still suffer the same problem. So here's my solution for mailman-2.1.3 (I think it's applicable to 2.1.4 too) and python 2.2.2: --- Header.py.orig 2003-03-30 22:39:05.000000000 +0200 +++ Header.py 2004-05-18 12:01:35.000000000 +0200 @@ -284,7 +284,7 @@ outcodec = charset.output_codec or 'us-ascii' s = s.encode(outcodec, errors) break - except UnicodeError: + except (UnicodeError, LookupError): pass else: assert False, 'utf-8 conversion failed' this way if s.encode does not understand the original encoding (like windows-1250 or windows-1252) then it resorts to use utf-8 ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-14 11:26 Message: Logged In: YES user_id=67709 This patch is for email package which belongs to Python language distribution. Please submit this report to the Python patch/bug tracker. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=955819&group_id=103 From noreply at sourceforge.net Mon Nov 15 15:01:54 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Nov 15 15:01:59 2004 Subject: [ mailman-Feature Requests-828564 ] per-user " Reply-To:" configuration Message-ID: Feature Requests item #828564, was opened at 2003-10-23 00:54 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=828564&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jorge Bernal (koke) Assigned to: Nobody/Anonymous (nobody) Summary: per-user "Reply-To:" configuration Initial Comment: In order to prevent the periodic flame about "Reply-To-harmful" and "Reply-To-is-good", it would be a great feature if any user could choose if he/she wants the "Reply-To" header to be modified or not ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-11-15 15:01 Message: Logged In: YES user_id=113859 Yes, 788314 was there earlier. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-13 01:15 Message: Logged In: YES user_id=18417 Duplicate of 788314? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=828564&group_id=103 From noreply at sourceforge.net Mon Nov 15 15:02:59 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Nov 15 15:03:04 2004 Subject: [ mailman-Feature Requests-788314 ] personal option for explicit reply-to header Message-ID: Feature Requests item #788314, was opened at 2003-08-13 22:22 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=788314&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: personal option for explicit reply-to header Initial Comment: Some list members have a broken email reader that will not give them a list reply option. Outlook for instance. People using some email readers just don't use it, because the functionality is hidden (like many KMail users). They beg the adminstrator to mangle the reply-to header. Other users of course find that harmful. A per user (and per list?) option to set an explicit reply-to header to the list seems to be a good solution. ---------------------------------------------------------------------- >Comment By: Bernhard Reiter (ber) Date: 2004-11-15 15:02 Message: Logged In: YES user_id=113859 This is not the duplicate, but the original. ;-) ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-13 01:15 Message: Logged In: YES user_id=18417 Duplicate of 828564? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=788314&group_id=103 From noreply at sourceforge.net Fri Nov 19 11:34:49 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Nov 19 11:34:53 2004 Subject: [ mailman-Bugs-1069319 ] Digests not sent Message-ID: Bugs item #1069319, was opened at 2004-11-19 10:34 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=1069319&group_id=103 Category: mail delivery Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Tom Allen (djpeanut) Assigned to: Nobody/Anonymous (nobody) Summary: Digests not sent Initial Comment: Hi, I run a very active mailing list with digest mode enabled as the default for all members. The digest were set to send daily when not empty and did so from the 5th Oct to the 25th Oct without any problems. However, at this point the digests inexplicably stopped being sent automatically. No settings were changed. I've checked all the settings in the digest page but they are fine, and the only way I can get a digest to send is to do it manually. I am running version 2.1.5. Nearly a hundred other mailing lists are running on the machine and to my knowledge, they are all unaffected. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1069319&group_id=103 From noreply at sourceforge.net Fri Nov 19 14:29:40 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Nov 19 14:29:51 2004 Subject: [ mailman-Bugs-1069319 ] Digests not sent Message-ID: Bugs item #1069319, was opened at 2004-11-19 10:34 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1069319&group_id=103 Category: mail delivery Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Tom Allen (djpeanut) Assigned to: Nobody/Anonymous (nobody) Summary: Digests not sent Initial Comment: Hi, I run a very active mailing list with digest mode enabled as the default for all members. The digest were set to send daily when not empty and did so from the 5th Oct to the 25th Oct without any problems. However, at this point the digests inexplicably stopped being sent automatically. No settings were changed. I've checked all the settings in the digest page but they are fine, and the only way I can get a digest to send is to do it manually. I am running version 2.1.5. Nearly a hundred other mailing lists are running on the machine and to my knowledge, they are all unaffected. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-19 13:29 Message: Logged In: YES user_id=67709 Looks like one of the messages stored in lists//digest.mbox is causing a error and stop the digest processing. If you can find the cause of error, you can edit the mbox file and issue cron/senddigest command, I think. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1069319&group_id=103 From noreply at sourceforge.net Sat Nov 20 15:20:50 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Nov 20 15:20:54 2004 Subject: [ mailman-Feature Requests-1070016 ] Better way to manage google & co Message-ID: Feature Requests item #1070016, was opened at 2004-11-20 15:20 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=1070016&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: Better way to manage google & co Initial Comment: It`s possible to disallow google to index a public web-archive of a mailinglist by a robots.txt. But it would be much nicer if a admin could change this behavior in the MM-admin-config-interface. If a flag like "robots_allow_index" is set to NO, pipermail should add a HTML-Header to each html-page generated by pipermail. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1070016&group_id=103 From noreply at sourceforge.net Mon Nov 22 00:29:02 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Nov 22 00:29:05 2004 Subject: [ mailman-Bugs-1070692 ] Uncaught runner exception: frexp() result out of range Message-ID: Bugs item #1070692, was opened at 2004-11-22 00: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=1070692&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Pokemoen (pokemoen) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception: frexp() result out of range Initial Comment: debian, x86, mailman Version: 2.1.5-4, python 2.3.4-13 after upgrading mailman, when sending a mail (from a svn-hook or mutt) i get the folling error : (taken from /var/log/mailman/error) ----------------------------------------------------------------------- Nov 22 01:08:15 2004 (15323) Uncaught runner exception: frexp() result out of range Nov 22 01:08:15 2004 (15323) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Handlers/ToOutgoing.py", line 55, in process outq.enqueue(msg, msgdata, listname=mlist.internal_name()) File "/var/lib/mailman/Mailman/Queue/Switchboard.py", line 129, in enqueue cPickle.dump(data, fp, protocol) SystemError: frexp() result out of range Dec 13 21:05:24 1901 (15323) SHUNTING: 1101082094.6941769+f15ffd34953b7dac540e2bfd3f041d0c8adcb9c1 ----------------------------------------------------------------------- this happens also after a purge & reinstall, also checkout the cool date on the last line :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1070692&group_id=103 From noreply at sourceforge.net Mon Nov 22 00:30:21 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Nov 22 00:30:34 2004 Subject: [ mailman-Bugs-1069319 ] Digests not sent Message-ID: Bugs item #1069319, was opened at 2004-11-19 10:34 Message generated for change (Comment added) made by djpeanut You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1069319&group_id=103 Category: mail delivery Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Tom Allen (djpeanut) Assigned to: Nobody/Anonymous (nobody) Summary: Digests not sent Initial Comment: Hi, I run a very active mailing list with digest mode enabled as the default for all members. The digest were set to send daily when not empty and did so from the 5th Oct to the 25th Oct without any problems. However, at this point the digests inexplicably stopped being sent automatically. No settings were changed. I've checked all the settings in the digest page but they are fine, and the only way I can get a digest to send is to do it manually. I am running version 2.1.5. Nearly a hundred other mailing lists are running on the machine and to my knowledge, they are all unaffected. ---------------------------------------------------------------------- >Comment By: Tom Allen (djpeanut) Date: 2004-11-21 23:30 Message: Logged In: YES user_id=701435 I have heard that this problem is actually affecting all mailing lists on the server. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-19 13:29 Message: Logged In: YES user_id=67709 Looks like one of the messages stored in lists//digest.mbox is causing a error and stop the digest processing. If you can find the cause of error, you can edit the mbox file and issue cron/senddigest command, I think. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1069319&group_id=103 From noreply at sourceforge.net Mon Nov 22 22:47:06 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Nov 22 22:47:10 2004 Subject: [ mailman-Feature Requests-1071305 ] option to turn off daily reminders Message-ID: Feature Requests item #1071305, was opened at 2004-11-22 16:47 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=1071305&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: primate (primate) Assigned to: Nobody/Anonymous (nobody) Summary: option to turn off daily reminders Initial Comment: I am running a list set to immediately send administrative requests (admin_immed_notify set to yes), but I am getting daily notices as well. I don't want to receive daily notices. The immediate notices are sufficient. Nor do I see the logic in filling my inbox with daily notices when I'm not around or haven't had a chance to process the immediate notices that are already sitting there. Seeing that there is no way to do this without changing the code, and that many Mailman users are not Python programmers or do not have the permission to make such changes on the server they are using, I think it would be best if this was made an option that could be set through the web interface for each list. That way administrators could choose immediate notifications, daily summaries, or both. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1071305&group_id=103 From noreply at sourceforge.net Tue Nov 23 04:34:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Nov 23 04:34:06 2004 Subject: [ mailman-Bugs-1071427 ] Changing bounce_score_threshold punts subscribers Message-ID: Bugs item #1071427, was opened at 2004-11-22 22:34 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=1071427&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: Changing bounce_score_threshold punts subscribers Initial Comment: As described in my post to mailman-users on Nov 16th. ===== I'm using Mailman 2.1.5. I ran into a situation today where a list owner changed the bounce_score_threshold from 7 to 3, and 55 subscribers were disabled when cron/disabled ran. Most of these users haven't seen a bounce in at least weeks, in some cases years, but they all did have bounce scores over 3 and under 7. I'm unsure exactly why this happened, I thought there were things in place to handle this (removing stale bounce info, bounce probe emails). From my mail logs it looks like Mailman sent an email to the subscriber and the list owner at the same time. I don't know what was in the mail to the subscriber, but the list owner got this: ===== Subject: Bounce action notification Date: Tue, 16 Nov 2004 09:00:18 -0500 From: mailman@lists.samurai.com To: trawlers-and-trawlering-owner@lists.samurai.com This is a Mailman mailing list bounce action notice: List: Trawlers-and-trawlering Member: [elided] Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman@lists.samurai.com. ------------------------------------------------------------------------ [disabled by periodic sweep and cull, no message available] ===== In the Mailman bounce log for that same address I see: Nov 16 09:00:18 2004 (89086) trawlers-and-trawlering: [elided] disabling due to probe bounce received The last info I have for that address in the bounce logs before this is: Oct 30 00:07:48 2004 (748) [elided]: trawlers-and-trawlering current bounce score: 4.0 >From what I can see all of the 55 subscribers disabled today are digest subscribers, but their digest is being successfully delivered every day. ===== ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1071427&group_id=103 From noreply at sourceforge.net Tue Nov 23 13:44:54 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Nov 23 13:44:57 2004 Subject: [ mailman-Patches-1071669 ] Danish message catalog update Message-ID: Patches item #1071669, was opened at 2004-11-23 13:44 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=1071669&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tom G. Christensen (tgc99) Assigned to: Nobody/Anonymous (nobody) Summary: Danish message catalog update Initial Comment: Bring the Danish message catalog in line with Release_2.1-maint. - All fuzzy translations have been fixed - All missing translations have been added - Misc updates to existing translations ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1071669&group_id=103 From noreply at sourceforge.net Tue Nov 23 19:38:40 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Nov 23 19:38:43 2004 Subject: [ mailman-Bugs-1072002 ] admin_member_chunksize not available in GUI or config_list Message-ID: Bugs item #1072002, was opened at 2004-11-23 10:38 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=1072002&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: admin_member_chunksize not available in GUI or config_list Initial Comment: admin_member_chunksize is set from DEFAULT_ADMIN_MEMBER_CHUNKSIZE when a list is created, but it is not visible in the admin GUI or bin/config_list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072002&group_id=103 From noreply at sourceforge.net Wed Nov 24 00:48:39 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 24 00:48:52 2004 Subject: [ mailman-Patches-1071669 ] Danish message catalog update Message-ID: Patches item #1071669, was opened at 2004-11-23 12:44 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1071669&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tom G. Christensen (tgc99) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: Danish message catalog update Initial Comment: Bring the Danish message catalog in line with Release_2.1-maint. - All fuzzy translations have been fixed - All missing translations have been added - Misc updates to existing translations ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1071669&group_id=103 From noreply at sourceforge.net Wed Nov 24 02:16:07 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 24 02:16:10 2004 Subject: [ mailman-Bugs-1072217 ] CookieError on addresses with plus and/or equal signs Message-ID: Bugs item #1072217, was opened at 2004-11-24 02: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=1072217&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Juanma Barranquero (lektu) Assigned to: Nobody/Anonymous (nobody) Summary: CookieError on addresses with plus and/or equal signs Initial Comment: The Web/CGI interface to mailmain allows the user to set addresses where the "name" part includes "+" and "=" chars, but chokes afterwards when trying to log in again with such addresses (which are, I think, perfectly fine). For example, I registererd to the mod_python list as xxx@yyy.com; after a while I changed it to xxx+list=mod-python@yyy.com, which worked all right. But trying to access the web interface brings: Bug in Mailman version 2.1.4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/options.py", line 226, in main password, user): File "/var/mailman/Mailman/SecurityManager.py", line 226, in WebAuthenticate print self.MakeCookie(ac, user) File "/var/mailman/Mailman/SecurityManager.py", line 240, in MakeCookie c[key] = binascii.hexlify(marshal.dumps((issued, mac))) File "/usr/lib/python2.3/Cookie.py", line 581, in __setitem__ self.__set(key, rval, cval) File "/usr/lib/python2.3/Cookie.py", line 574, in __set M.set(key, real_value, coded_value) File "/usr/lib/python2.3/Cookie.py", line 453, in set raise CookieError("Illegal key value: %s" % key) CookieError: Illegal key value: mod_python+user+xxx+list=mod-python--at--yyy.com [etc, etc] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072217&group_id=103 From noreply at sourceforge.net Wed Nov 24 18:22:49 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 24 18:22:52 2004 Subject: [ mailman-Feature Requests-1072618 ] digest sent time set per list Message-ID: Feature Requests item #1072618, was opened at 2004-11-24 09:22 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=1072618&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: rst (r_st) Assigned to: Nobody/Anonymous (nobody) Summary: digest sent time set per list Initial Comment: List owners should have the ability to determine on a per-list basis the time that daily digests are sent. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1072618&group_id=103 From noreply at sourceforge.net Wed Nov 24 21:21:31 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 24 21:21:34 2004 Subject: [ mailman-Bugs-1072750 ] Error after cancel invitation Message-ID: Bugs item #1072750, was opened at 2004-11-24 21:21 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=1072750&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: schmartin (schmartin) Assigned to: Nobody/Anonymous (nobody) Summary: Error after cancel invitation Initial Comment: Bug in Mailman version 2.1.5c2 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/www/mailman/scripts/driver", line 87, in run_main main() File "/var/www/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/var/www/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/var/www/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError Python information: Variable Value sys.version 2.2.2 (#1, Feb 24 2003, 19:13:11) [GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-4)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value PATH_INFO /leiterrunde CONTENT_LENGTH 116 CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://www.postfuchs.de/mailman/confirm/leiterrunde/06ca753186f732c16d5ad6b2d34466acd318d245 SCRIPT_FILENAME /var/www/mailman/cgi-bin/confirm PYTHONPATH /var/www/mailman SERVER_SOFTWARE Apache/2.0.48 (RedHat 9/Server4You) SERVER_ADMIN root@localhost SCRIPT_NAME /mailman/confirm REQUEST_METHOD POST HTTP_HOST www.postfuchs.de HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING PATH_TRANSLATED /var/www/mailman/leiterrunde REQUEST_URI /mailman/confirm/leiterrunde HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.3) Gecko/20040910(248152) HTTP_CONNECTION keep-alive SERVER_NAME www.postfuchs.de REMOTE_ADDR 217.83.83.186 REMOTE_PORT 2178 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 UNIQUE_ID sv-CND5L0I0AADkk-u8AAAAG SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 62.75.208.141 DOCUMENT_ROOT /var/www/mailman ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072750&group_id=103 From noreply at sourceforge.net Wed Nov 24 23:15:32 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Nov 24 23:15:36 2004 Subject: [ mailman-Bugs-1070692 ] Uncaught runner exception: frexp() result out of range Message-ID: Bugs item #1070692, was opened at 2004-11-22 00:28 Message generated for change (Comment added) made by pokemoen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1070692&group_id=103 Category: mail delivery Group: 2.1 beta >Status: Deleted Resolution: None Priority: 5 Submitted By: Pokemoen (pokemoen) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception: frexp() result out of range Initial Comment: debian, x86, mailman Version: 2.1.5-4, python 2.3.4-13 after upgrading mailman, when sending a mail (from a svn-hook or mutt) i get the folling error : (taken from /var/log/mailman/error) ----------------------------------------------------------------------- Nov 22 01:08:15 2004 (15323) Uncaught runner exception: frexp() result out of range Nov 22 01:08:15 2004 (15323) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Handlers/ToOutgoing.py", line 55, in process outq.enqueue(msg, msgdata, listname=mlist.internal_name()) File "/var/lib/mailman/Mailman/Queue/Switchboard.py", line 129, in enqueue cPickle.dump(data, fp, protocol) SystemError: frexp() result out of range Dec 13 21:05:24 1901 (15323) SHUNTING: 1101082094.6941769+f15ffd34953b7dac540e2bfd3f041d0c8adcb9c1 ----------------------------------------------------------------------- this happens also after a purge & reinstall, also checkout the cool date on the last line :) ---------------------------------------------------------------------- >Comment By: Pokemoen (pokemoen) Date: 2004-11-24 23:15 Message: Logged In: YES user_id=1021709 python seems to have magicly fixed itself and i can't reproduce it anymore. please ignore until it comes up again. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1070692&group_id=103 From noreply at sourceforge.net Thu Nov 25 13:46:14 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Nov 25 13:46:17 2004 Subject: [ mailman-Bugs-1072217 ] CookieError on addresses with plus and/or equal signs Message-ID: Bugs item #1072217, was opened at 2004-11-24 01:16 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072217&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Juanma Barranquero (lektu) Assigned to: Nobody/Anonymous (nobody) Summary: CookieError on addresses with plus and/or equal signs Initial Comment: The Web/CGI interface to mailmain allows the user to set addresses where the "name" part includes "+" and "=" chars, but chokes afterwards when trying to log in again with such addresses (which are, I think, perfectly fine). For example, I registererd to the mod_python list as xxx@yyy.com; after a while I changed it to xxx+list=mod-python@yyy.com, which worked all right. But trying to access the web interface brings: Bug in Mailman version 2.1.4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/options.py", line 226, in main password, user): File "/var/mailman/Mailman/SecurityManager.py", line 226, in WebAuthenticate print self.MakeCookie(ac, user) File "/var/mailman/Mailman/SecurityManager.py", line 240, in MakeCookie c[key] = binascii.hexlify(marshal.dumps((issued, mac))) File "/usr/lib/python2.3/Cookie.py", line 581, in __setitem__ self.__set(key, rval, cval) File "/usr/lib/python2.3/Cookie.py", line 574, in __set M.set(key, real_value, coded_value) File "/usr/lib/python2.3/Cookie.py", line 453, in set raise CookieError("Illegal key value: %s" % key) CookieError: Illegal key value: mod_python+user+xxx+list=mod-python--at--yyy.com [etc, etc] ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-25 12:46 Message: Logged In: YES user_id=67709 I've just fixed this in CVS (Release_2_1-maint). SecurityManager.py revision 2.20.2.5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072217&group_id=103 From noreply at sourceforge.net Thu Nov 25 16:15:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Nov 25 16:15:14 2004 Subject: [ mailman-Feature Requests-1073232 ] Reject/discard decisions before hold... Message-ID: Feature Requests item #1073232, was opened at 2004-11-25 15:15 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=1073232&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Reject/discard decisions before hold... Initial Comment: Folks, It would be really nice if Mailman could intelligently make reject/ discard decisions before looking at decisions which would result in a "hold" action. For example, if the list is configured for a maximum message size of 40KB and reject any message over that size, but postings from non-members are held for moderation, then it would be nice if a non-member posting a message over 40KB in size got an auto- reject for being too large as opposed to being held for moderation because it's from a non-member. Same for discard -- make these decisions before looking at ones that could result in a "hold". This would make the lives of moderators and list server managers much nicer, since a lot of spam could be rejected or discarded outright, and we'd never need to see it or deal with it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1073232&group_id=103 From noreply at sourceforge.net Thu Nov 25 16:16:43 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Nov 25 16:17:15 2004 Subject: [ mailman-Feature Requests-1070016 ] Better way to manage google & co Message-ID: Feature Requests item #1070016, was opened at 2004-11-20 14:20 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1070016&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: Better way to manage google & co Initial Comment: It`s possible to disallow google to index a public web-archive of a mailinglist by a robots.txt. But it would be much nicer if a admin could change this behavior in the MM-admin-config-interface. If a flag like "robots_allow_index" is set to NO, pipermail should add a HTML-Header to each html-page generated by pipermail. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 15:16 Message: Logged In: YES user_id=18417 Actually, on another project I'm working on, we've found that robots.txt doesn't seem to stop Google. They index the page anyway. It would definitely be nice if we could find other ways to stop them from doing that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1070016&group_id=103 From noreply at sourceforge.net Thu Nov 25 16:26:19 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Nov 25 16:26:27 2004 Subject: [ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option Message-ID: Feature Requests item #923122, was opened at 2004-03-25 14:01 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: reply_goes_to_list allow poster+list option Initial Comment: Right now, the reply_goes_to_list option allows (a) poster, (b), list, and (c) explicit. How about (d) poster AND list? That is, insert/override a reply-to: header containing both the list name, and the original reply-to (if present, else From: address). For extra credit, omit the original poster if they are a list member. This would be very useful for a number of lists I maintain, where 90% of the traffic is among the list members (hence having a simple reply go to the list), yet a few messages come in from the outside world (hence including the original poster's address). I'm using mailman 2.1.4 on GNU/Linux. Thanks, karl@freefriends.org ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 15:26 Message: Logged In: YES user_id=18417 I don't think this is possible. "Reply-to:" goes back to one address, not two. The action of having multiple "Reply-to:" headers is also undefined, and some clients may work the way you want, while others may work in ways you do not. Pretty much everything to do with "Reply-to:" is really a client problem, and needs to be solved there. See for details. ---------------------------------------------------------------------- Comment By: URA Hiroshi (ura) Date: 2004-05-10 10:44 Message: Logged In: YES user_id=1007264 I uploaded the patch by different method. see following URL: http://sourceforge.net/tracker/index.php?func=detail&aid=951167&group_id=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 From noreply at sourceforge.net Thu Nov 25 16:28:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Nov 25 16:28:33 2004 Subject: [ mailman-Feature Requests-893870 ] allow signed postings from non-subscribers Message-ID: Feature Requests item #893870, was opened at 2004-02-10 04:51 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=893870&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ben Elliston (elliston) Assigned to: Nobody/Anonymous (nobody) Summary: allow signed postings from non-subscribers Initial Comment: It would be great if Mailman could permit posting from non-subscribers if the incoming message can be verified based on a per-list or site-wide GPG keyring. If per-list keyring could have a GPG key of the list owner, who in turn can sign keys of people they trust to post to the list. Furthermore, such posters could subscribe by email without needing to confirm. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 15:28 Message: Logged In: YES user_id=18417 Mailman has nothing to do with PGP. It can allow messages to include certain MIME bodypart types which would include signatures, but that would not include having the server validate those signatures. If you want tighter integration between Mailman and PGP, that's a separate matter, and should probably be a different RFE. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=893870&group_id=103 From noreply at sourceforge.net Thu Nov 25 19:18:40 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Nov 25 19:18:46 2004 Subject: [ mailman-Feature Requests-1041963 ] Members of sub-lists can't post to umbrella list Message-ID: Feature Requests item #1041963, was opened at 2004-10-07 03:37 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1041963&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Evan Prodromou (evanprodromou) Assigned to: Nobody/Anonymous (nobody) Summary: Members of sub-lists can't post to umbrella list Initial Comment: Consider list1 and list2 on the same Mailman server. The admin creates a third list, list3, to act as an umbrella list for both lists. If the admin configures list3 so that only list members can post, members of list1 or list2 can't post to the list. This is a FAQ'd problem with a workaround: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.005.htp The problem should be fixed so that the workaround isn't needed. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 18:18 Message: Logged In: YES user_id=18417 I think that this issue is addressed by Jim Tittsler's patch at . I'm trying now to see if this has been uploaded to the Mailman SourceForge Patch tracker, and if not I'll try to get Jim to upload it himself. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-10-13 13:09 Message: Logged In: YES user_id=67709 This is more a feature request than a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1041963&group_id=103 From noreply at sourceforge.net Thu Nov 25 19:19:45 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Nov 25 19:19:51 2004 Subject: [ mailman-Patches-951167 ] patch for #923122 reply_goes_to_list allow poster+list ... Message-ID: Patches item #951167, was opened at 2004-05-10 10:36 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=951167&group_id=103 Category: mail delivery Group: None Status: Open Resolution: None Priority: 5 Submitted By: URA Hiroshi (ura) Assigned to: Nobody/Anonymous (nobody) Summary: patch for #923122 reply_goes_to_list allow poster+list ... Initial Comment: This is patch for #923122 reply_goes_to_list allow poster+list option. http://sourceforge.net/tracker/index.php?func=detail&aid=923122&group_id=103&atid=350103 The patch introduces a new variable `add_poster_to_reply_to' per list. If `add_poster_to_reply_to' is `Yes' and poster isn't member of list, address to poster is added to Reply-To header. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 18:19 Message: Logged In: YES user_id=18417 The "Reply-to:" header is only supposed to include one address. The handling of multiple addresses in this header is undefined, and some clients may handle that correctly, while others almost certainly won't. I don't think that this patch is a good idea. Ultimately, all problems with "Reply-To:" are clients problems, see . ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=951167&group_id=103 From noreply at sourceforge.net Thu Nov 25 19:20:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Nov 25 19:20:09 2004 Subject: [ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option Message-ID: Feature Requests item #923122, was opened at 2004-03-25 14:01 Message generated for change (Comment added) made by kberry You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: reply_goes_to_list allow poster+list option Initial Comment: Right now, the reply_goes_to_list option allows (a) poster, (b), list, and (c) explicit. How about (d) poster AND list? That is, insert/override a reply-to: header containing both the list name, and the original reply-to (if present, else From: address). For extra credit, omit the original poster if they are a list member. This would be very useful for a number of lists I maintain, where 90% of the traffic is among the list members (hence having a simple reply go to the list), yet a few messages come in from the outside world (hence including the original poster's address). I'm using mailman 2.1.4 on GNU/Linux. Thanks, karl@freefriends.org ---------------------------------------------------------------------- >Comment By: karl berry (kberry) Date: 2004-11-25 18:20 Message: Logged In: YES user_id=33248 I'm trying to help my users avoid a fairly common mistake, not engage in arguments about standards. Fine, Reply-to: list, poster may not work for the population of some lists. So those lists won't enable it. Meanwhile, it will help some people and lists, and there's no other way to accomplish the behavior (that I know of). It's trivial to add and a tiny change in the user interface. I am not asking for per-user control of this, which is what the FAQ entry you cited mostly discusses. Obviously some compromise has already been made with the "reply-to considered harmful" stance. (For which I am very thankful, because it is very useful.) ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 15:26 Message: Logged In: YES user_id=18417 I don't think this is possible. "Reply-to:" goes back to one address, not two. The action of having multiple "Reply-to:" headers is also undefined, and some clients may work the way you want, while others may work in ways you do not. Pretty much everything to do with "Reply-to:" is really a client problem, and needs to be solved there. See for details. ---------------------------------------------------------------------- Comment By: URA Hiroshi (ura) Date: 2004-05-10 10:44 Message: Logged In: YES user_id=1007264 I uploaded the patch by different method. see following URL: http://sourceforge.net/tracker/index.php?func=detail&aid=951167&group_id=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 From noreply at sourceforge.net Thu Nov 25 19:32:51 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Nov 25 19:32:58 2004 Subject: [ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option Message-ID: Feature Requests item #923122, was opened at 2004-03-25 14:01 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: reply_goes_to_list allow poster+list option Initial Comment: Right now, the reply_goes_to_list option allows (a) poster, (b), list, and (c) explicit. How about (d) poster AND list? That is, insert/override a reply-to: header containing both the list name, and the original reply-to (if present, else From: address). For extra credit, omit the original poster if they are a list member. This would be very useful for a number of lists I maintain, where 90% of the traffic is among the list members (hence having a simple reply go to the list), yet a few messages come in from the outside world (hence including the original poster's address). I'm using mailman 2.1.4 on GNU/Linux. Thanks, karl@freefriends.org ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 18:32 Message: Logged In: YES user_id=18417 The problem is that this idea is likely to cause a number of programs to break, probably pretty badly. I think this is a very bad idea. We don't want to be doing things to encourage people to break the standards, especially since most people who would use this option would not understand the true scope of the problem. Using two "Reply-to:" headers doesn't resolve this issue, either. If you want to munge the "Reply-to:" header to point back to the list, then Mailman gives you the ability to do that. It's a bad idea, for the reasons laid out in the FAQ, but you do have that capability. ---------------------------------------------------------------------- Comment By: karl berry (kberry) Date: 2004-11-25 18:20 Message: Logged In: YES user_id=33248 I'm trying to help my users avoid a fairly common mistake, not engage in arguments about standards. Fine, Reply-to: list, poster may not work for the population of some lists. So those lists won't enable it. Meanwhile, it will help some people and lists, and there's no other way to accomplish the behavior (that I know of). It's trivial to add and a tiny change in the user interface. I am not asking for per-user control of this, which is what the FAQ entry you cited mostly discusses. Obviously some compromise has already been made with the "reply-to considered harmful" stance. (For which I am very thankful, because it is very useful.) ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 15:26 Message: Logged In: YES user_id=18417 I don't think this is possible. "Reply-to:" goes back to one address, not two. The action of having multiple "Reply-to:" headers is also undefined, and some clients may work the way you want, while others may work in ways you do not. Pretty much everything to do with "Reply-to:" is really a client problem, and needs to be solved there. See for details. ---------------------------------------------------------------------- Comment By: URA Hiroshi (ura) Date: 2004-05-10 10:44 Message: Logged In: YES user_id=1007264 I uploaded the patch by different method. see following URL: http://sourceforge.net/tracker/index.php?func=detail&aid=951167&group_id=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 From noreply at sourceforge.net Thu Nov 25 19:40:55 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Nov 25 19:41:00 2004 Subject: [ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option Message-ID: Feature Requests item #923122, was opened at 2004-03-25 14:01 Message generated for change (Comment added) made by kberry You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 Category: None Group: None >Status: Closed Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: reply_goes_to_list allow poster+list option Initial Comment: Right now, the reply_goes_to_list option allows (a) poster, (b), list, and (c) explicit. How about (d) poster AND list? That is, insert/override a reply-to: header containing both the list name, and the original reply-to (if present, else From: address). For extra credit, omit the original poster if they are a list member. This would be very useful for a number of lists I maintain, where 90% of the traffic is among the list members (hence having a simple reply go to the list), yet a few messages come in from the outside world (hence including the original poster's address). I'm using mailman 2.1.4 on GNU/Linux. Thanks, karl@freefriends.org ---------------------------------------------------------------------- >Comment By: karl berry (kberry) Date: 2004-11-25 18:40 Message: Logged In: YES user_id=33248 Whatever. There's obviously no point in debating it, since you think it is so terribly horrible and I don't see the problem with helping users, regardless of what "standards" would like to impose on us. So I'll try to mark this closed, and we can get on with our lives. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 18:32 Message: Logged In: YES user_id=18417 The problem is that this idea is likely to cause a number of programs to break, probably pretty badly. I think this is a very bad idea. We don't want to be doing things to encourage people to break the standards, especially since most people who would use this option would not understand the true scope of the problem. Using two "Reply-to:" headers doesn't resolve this issue, either. If you want to munge the "Reply-to:" header to point back to the list, then Mailman gives you the ability to do that. It's a bad idea, for the reasons laid out in the FAQ, but you do have that capability. ---------------------------------------------------------------------- Comment By: karl berry (kberry) Date: 2004-11-25 18:20 Message: Logged In: YES user_id=33248 I'm trying to help my users avoid a fairly common mistake, not engage in arguments about standards. Fine, Reply-to: list, poster may not work for the population of some lists. So those lists won't enable it. Meanwhile, it will help some people and lists, and there's no other way to accomplish the behavior (that I know of). It's trivial to add and a tiny change in the user interface. I am not asking for per-user control of this, which is what the FAQ entry you cited mostly discusses. Obviously some compromise has already been made with the "reply-to considered harmful" stance. (For which I am very thankful, because it is very useful.) ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 15:26 Message: Logged In: YES user_id=18417 I don't think this is possible. "Reply-to:" goes back to one address, not two. The action of having multiple "Reply-to:" headers is also undefined, and some clients may work the way you want, while others may work in ways you do not. Pretty much everything to do with "Reply-to:" is really a client problem, and needs to be solved there. See for details. ---------------------------------------------------------------------- Comment By: URA Hiroshi (ura) Date: 2004-05-10 10:44 Message: Logged In: YES user_id=1007264 I uploaded the patch by different method. see following URL: http://sourceforge.net/tracker/index.php?func=detail&aid=951167&group_id=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 From noreply at sourceforge.net Fri Nov 26 02:31:30 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Nov 26 02:31:36 2004 Subject: [ mailman-Bugs-1072750 ] Error after cancel invitation Message-ID: Bugs item #1072750, was opened at 2004-11-24 20:21 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072750&group_id=103 Category: (un)subscribing Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: schmartin (schmartin) Assigned to: Nobody/Anonymous (nobody) Summary: Error after cancel invitation Initial Comment: Bug in Mailman version 2.1.5c2 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/www/mailman/scripts/driver", line 87, in run_main main() File "/var/www/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/var/www/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/var/www/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError Python information: Variable Value sys.version 2.2.2 (#1, Feb 24 2003, 19:13:11) [GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-4)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value PATH_INFO /leiterrunde CONTENT_LENGTH 116 CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://www.postfuchs.de/mailman/confirm/leiterrunde/06ca753186f732c16d5ad6b2d34466acd318d245 SCRIPT_FILENAME /var/www/mailman/cgi-bin/confirm PYTHONPATH /var/www/mailman SERVER_SOFTWARE Apache/2.0.48 (RedHat 9/Server4You) SERVER_ADMIN root@localhost SCRIPT_NAME /mailman/confirm REQUEST_METHOD POST HTTP_HOST www.postfuchs.de HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING PATH_TRANSLATED /var/www/mailman/leiterrunde REQUEST_URI /mailman/confirm/leiterrunde HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.3) Gecko/20040910(248152) HTTP_CONNECTION keep-alive SERVER_NAME www.postfuchs.de REMOTE_ADDR 217.83.83.186 REMOTE_PORT 2178 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 UNIQUE_ID sv-CND5L0I0AADkk-u8AAAAG SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 62.75.208.141 DOCUMENT_ROOT /var/www/mailman ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-26 01:31 Message: Logged In: YES user_id=67709 This bug was already fixed in CVS Release_2_1-maint tree (See bug ID 981188). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072750&group_id=103 From noreply at sourceforge.net Fri Nov 26 02:36:27 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Nov 26 02:36:32 2004 Subject: [ mailman-Bugs-1064494 ] Accessing list web page - bug report Message-ID: Bugs item #1064494, was opened at 2004-11-11 14:00 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1064494&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ralphabf (mudd47) Assigned to: Nobody/Anonymous (nobody) Summary: Accessing list web page - bug report Initial Comment: Bug in Mailman version 2.1.4 Traceback: Traceback (most recent call last): File "/usr/lib/mailman/scripts/driver", line 68, in run_main immediate=1) File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py ", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 49, in __init__ self.__get_f() File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 67, in __get_f 1) File "/usr/lib/python2.3/codecs.py", line 566, in open file = __builtin__.open(filename, mode, buffering) IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' ------------------------------------------------------ -------------------------- Python information: Variable Value sys.version 2.3.3 (#2, Feb 17 2004, 11:45:40) [GCC 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------ -------------------------- Environment variables: Variable Value SERVER_SOFTWARE Apache- AdvancedExtranetServer/2.0.48 (Mandrake Linux/6.7.100mdk) SCRIPT_NAME /mailman/admin SERVER_SIGNATURE Apache- AdvancedExtranetServer/2.0.48 (Mandrake Linux/6.7.100mdk) Server at hyndan.gbg.abf.se Port 80 REQUEST_METHOD GET PATH_INFO /mailman SERVER_PROTOCOL HTTP/1.1 QUERY_STRING HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) HTTP_CONNECTION Keep-Alive SERVER_NAME hyndan.gbg.abf.se REMOTE_ADDR 62.127.120.98 PATH_TRANSLATED /var/www/html/mailman SERVER_PORT 80 SERVER_ADDR 192.168.1.111 DOCUMENT_ROOT /var/www/html PYTHONPATH /usr/lib/mailman SCRIPT_FILENAME /usr/lib/mailman/cgi-bin/admin SERVER_ADMIN root@localhost HTTP_HOST hyndan.gbg.abf.se REQUEST_URI /mailman/admin/mailman HTTP_ACCEPT */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 16872 HTTP_ACCEPT_LANGUAGE sv HTTP_ACCEPT_ENCODING gzip, deflate ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-26 01:36 Message: Logged In: YES user_id=67709 It says "Permission denied: '/var/lib/mailman/logs/error'" . Check your logs directory permission by bin/check_perms and fix. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1064494&group_id=103 From noreply at sourceforge.net Fri Nov 26 02:44:21 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Nov 26 02:44:30 2004 Subject: [ mailman-Bugs-1069319 ] Digests not sent Message-ID: Bugs item #1069319, was opened at 2004-11-19 10:34 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1069319&group_id=103 Category: mail delivery Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Tom Allen (djpeanut) Assigned to: Nobody/Anonymous (nobody) Summary: Digests not sent Initial Comment: Hi, I run a very active mailing list with digest mode enabled as the default for all members. The digest were set to send daily when not empty and did so from the 5th Oct to the 25th Oct without any problems. However, at this point the digests inexplicably stopped being sent automatically. No settings were changed. I've checked all the settings in the digest page but they are fine, and the only way I can get a digest to send is to do it manually. I am running version 2.1.5. Nearly a hundred other mailing lists are running on the machine and to my knowledge, they are all unaffected. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-26 01:44 Message: Logged In: YES user_id=67709 Then, make sure the cron(d) process is running. ---------------------------------------------------------------------- Comment By: Tom Allen (djpeanut) Date: 2004-11-21 23:30 Message: Logged In: YES user_id=701435 I have heard that this problem is actually affecting all mailing lists on the server. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-19 13:29 Message: Logged In: YES user_id=67709 Looks like one of the messages stored in lists//digest.mbox is causing a error and stop the digest processing. If you can find the cause of error, you can edit the mbox file and issue cron/senddigest command, I think. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1069319&group_id=103 From noreply at sourceforge.net Fri Nov 26 07:22:34 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Nov 26 07:22:37 2004 Subject: [ mailman-Patches-1073556 ] fix for some malicious messages Message-ID: Patches item #1073556, was opened at 2004-11-26 15:22 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=1073556&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: fix for some malicious messages Initial Comment: Some malicious messages (most of them are spam or auto-generated messages) cause shunting. - Message containing null byte(s) bound for -request address. - Message with message/delivery-status part and without text/plain part bound for -confirm address or list address. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1073556&group_id=103 From noreply at sourceforge.net Sat Nov 27 14:53:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Nov 27 14:53:07 2004 Subject: [ mailman-Feature Requests-1074197 ] Web interface to sync_members Message-ID: Feature Requests item #1074197, was opened at 2004-11-27 08:53 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=1074197&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Matthew Saltzman (cumthsc) Assigned to: Nobody/Anonymous (nobody) Summary: Web interface to sync_members Initial Comment: It would be useful to extend the Membership Management page to support sync_members. We use mailman to run a number of members-only lists for a professional society. The membership database is kept on a separate system, and lists of current members are produced for the various lists at regular intervals. It would be easier for our non-technical office staff to keep the mailing list memberships in sync with the main database if they could upload the member list through the Web rather than having to upload the file with FTP and use sudo and shell commands to do the synching. We could mass-delete and mass-subscribe, but it would be more convenient to do it in one step. Also, for some of the lists, new members should receive notification that they have been subscribed, but carry-over members should not get such notification. The only way to do that with add_members is to add in two steps or to make two files with members to be deleted and members to be added, leaving the carry-over members subscribed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1074197&group_id=103 From noreply at sourceforge.net Mon Nov 29 10:01:21 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Nov 29 10:01:31 2004 Subject: [ mailman-Patches-1071669 ] Danish message catalog update Message-ID: Patches item #1071669, was opened at 2004-11-23 13:44 Message generated for change (Comment added) made by tgc99 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1071669&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tom G. Christensen (tgc99) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Danish message catalog update Initial Comment: Bring the Danish message catalog in line with Release_2.1-maint. - All fuzzy translations have been fixed - All missing translations have been added - Misc updates to existing translations ---------------------------------------------------------------------- >Comment By: Tom G. Christensen (tgc99) Date: 2004-11-29 10:01 Message: Logged In: YES user_id=1159458 Patch updated to apply cleanly on top of CVS as of 2004-11-29 08:49+100. It also fixes two new fuzzies. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1071669&group_id=103 From noreply at sourceforge.net Tue Nov 30 01:45:48 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Nov 30 01:45:51 2004 Subject: [ mailman-Bugs-1075686 ] footer added to quoted-printable mail isn't encoded Message-ID: Bugs item #1075686, was opened at 2004-11-30 01:45 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=1075686&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Felix Palmen (tentakel) Assigned to: Nobody/Anonymous (nobody) Summary: footer added to quoted-printable mail isn't encoded Initial Comment: When Mailman adds a footer to a mail with Content-Transfer-Encoding quoted-printable, it doesn't encode the footer in quoted-printable, so spaces (and other characters?) are messed up. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1075686&group_id=103 From noreply at sourceforge.net Tue Nov 30 22:09:11 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Nov 30 22:09:15 2004 Subject: [ mailman-Bugs-1062663 ] empty charset in header crashes admindb.py Message-ID: Bugs item #1062663, was opened at 2004-11-08 21:52 Message generated for change (Comment added) made by idogan You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1062663&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: empty charset in header crashes admindb.py Initial Comment: when a message contains a header like this: Content-Type: text/plain; charset= (note the empty charset) The admindb.py details page page gives an error. Traceback is below. Btw does this mean the charset value in the header is directly mapped to a module name to import? (sounds kinda scary...) I know the real fault is in the message (I'm not sure if the mime stripper caused this or a bad mailer), but maybe mailman shouldn't crash on this. Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 222, in main show_detailed_requests(mlist, form) File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 545, in show_detailed_requests show_post_requests(mlist, id, info, total, count, form) File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 611, in show_post_requests body = unicode(body, mcset).encode(lcset) File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') ValueError: Empty module name ---------------------------------------------------------------------- Comment By: idogan (idogan) Date: 2004-11-30 22:09 Message: Logged In: YES user_id=1169233 I have exactly the same problem: Nov 30 21:53:09 2004 admin(21885): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(21885): [----- Mailman Version: 2.1.5 -----] admin(21885): [----- Traceback ------] admin(21885): Traceback (most recent call last): admin(21885): File "/opt/mailman/scripts/driver", line 87, in run_main admin(21885): main() admin(21885): File "/opt/mailman/Mailman/Cgi/admindb.py", line 163, in main admin(21885): process_form(mlist, doc, cgidata) admin(21885): File "/opt/mailman/Mailman/Cgi/admindb.py", line 711, in process_form admin(21885): forward, forwardaddr) admin(21885): File "/opt/mailman/Mailman/ListAdmin.py", line 159, in HandleRequest admin(21885): forward, addr) admin(21885): File "/opt/mailman/Mailman/ListAdmin.py", line 345, in __handlepost admin(21885): syslog('vette', note) admin(21885): File "/opt/mailman/Mailman/Logging/Syslog.py", line 40, in write admin(21885): self.write_ex(kind, msg, args, kws) admin(21885): File "/opt/mailman/Mailman/Logging/Syslog.py", line 58, in write_ex admin(21885): logf.write(msg + '\n') admin(21885): File "/opt/mailman/Mailman/Logging/StampedLogger.py", line 73, in write admin(21885): Logger.write(self, "%s %s" % (prefix, msg)) admin(21885): File "/opt/mailman/Mailman/Logging/Logger.py", line 91, in write admin(21885): f.write(msg) admin(21885): UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 90: ordinal not in range(128) admin(21885): [----- Python Information -----] admin(21885): sys.version = 2.3.4 (#1, Nov 10 2004, 13:08:40) [C] admin(21885): sys.executable = /opt/csw/bin/python admin(21885): sys.prefix = /opt/csw admin(21885): sys.exec_prefix = /opt/csw admin(21885): sys.path = /opt/csw admin(21885): sys.platform = sunos5 admin(21885): [----- Environment Variables -----] admin(21885): HTTP_COOKIE: eth+admin=2802000000694eddac41732800000031336161396238633262356333316431613335633033383739313330326164303462643162393164 admin(21885): SERVER_SOFTWARE: Apache/2.0.52 (Unix) admin(21885): SCRIPT_NAME: /mailman/admindb admin(21885): SERVER_SIGNATURE:
Apache/2.0.52 (Unix) Server at lists.dogan.ch Port 443
admin(21885): admin(21885): REQUEST_METHOD: POST admin(21885): HTTP_KEEP_ALIVE: 300 admin(21885): SERVER_PROTOCOL: HTTP/1.1 admin(21885): QUERY_STRING: admin(21885): CONTENT_LENGTH: 433 admin(21885): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7 admin(21885): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041108 admin(21885): HTTP_CONNECTION: keep-alive admin(21885): HTTP_REFERER: https://lists.dogan.ch/mailman/admindb/eth admin(21885): SERVER_NAME: lists.dogan.ch admin(21885): REMOTE_ADDR: 213.144.141.146 admin(21885): PATH_TRANSLATED: /var/www/lists.dogan.ch/htdocs/eth admin(21885): SERVER_PORT: 443 admin(21885): SERVER_ADDR: 213.144.137.44 admin(21885): DOCUMENT_ROOT: /var/www/lists.dogan.ch/htdocs admin(21885): PYTHONPATH: /opt/mailman admin(21885): SCRIPT_FILENAME: /opt/mailman/cgi-bin/admindb admin(21885): SERVER_ADMIN: ihsan@dogan.ch admin(21885): HTTP_HOST: lists.dogan.ch admin(21885): HTTPS: on admin(21885): REQUEST_URI: /mailman/admindb/eth admin(21885): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 admin(21885): GATEWAY_INTERFACE: CGI/1.1 admin(21885): REMOTE_PORT: 64543 admin(21885): HTTP_ACCEPT_LANGUAGE: de,tr;q=0.7,en;q=0.3 admin(21885): CONTENT_TYPE: application/x-www-form-urlencoded admin(21885): HTTP_ACCEPT_ENCODING: gzip,deflate admin(21885): PATH_INFO: /eth Nov 30 21:53:20 2004 admin(21886): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(21886): [----- Mailman Version: 2.1.5 -----] admin(21886): [----- Traceback ------] admin(21886): Traceback (most recent call last): admin(21886): File "/opt/mailman/scripts/driver", line 87, in run_main admin(21886): main() admin(21886): File "/opt/mailman/Mailman/Cgi/admindb.py", line 163, in main admin(21886): process_form(mlist, doc, cgidata) admin(21886): File "/opt/mailman/Mailman/Cgi/admindb.py", line 711, in process_form admin(21886): forward, forwardaddr) admin(21886): File "/opt/mailman/Mailman/ListAdmin.py", line 159, in HandleRequest admin(21886): forward, addr) admin(21886): File "/opt/mailman/Mailman/ListAdmin.py", line 345, in __handlepost admin(21886): syslog('vette', note) admin(21886): File "/opt/mailman/Mailman/Logging/Syslog.py", line 40, in write admin(21886): self.write_ex(kind, msg, args, kws) admin(21886): File "/opt/mailman/Mailman/Logging/Syslog.py", line 58, in write_ex admin(21886): logf.write(msg + '\n') admin(21886): File "/opt/mailman/Mailman/Logging/StampedLogger.py", line 73, in write admin(21886): Logger.write(self, "%s %s" % (prefix, msg)) admin(21886): File "/opt/mailman/Mailman/Logging/Logger.py", line 91, in write admin(21886): f.write(msg) admin(21886): UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 90: ordinal not in range(128) admin(21886): [----- Python Information -----] admin(21886): sys.version = 2.3.4 (#1, Nov 10 2004, 13:08:40) [C] admin(21886): sys.executable = /opt/csw/bin/python admin(21886): sys.prefix = /opt/csw admin(21886): sys.exec_prefix = /opt/csw admin(21886): sys.path = /opt/csw admin(21886): sys.platform = sunos5 admin(21886): [----- Environment Variables -----] admin(21886): HTTP_COOKIE: eth+admin=2802000000694eddac41732800000031336161396238633262356333316431613335633033383739313330326164303462643162393164 admin(21886): SERVER_SOFTWARE: Apache/2.0.52 (Unix) admin(21886): SCRIPT_NAME: /mailman/admindb admin(21886): SERVER_SIGNATURE:
Apache/2.0.52 (Unix) Server at lists.dogan.ch Port 443
admin(21886): admin(21886): REQUEST_METHOD: POST admin(21886): HTTP_KEEP_ALIVE: 300 admin(21886): SERVER_PROTOCOL: HTTP/1.1 admin(21886): QUERY_STRING: admin(21886): CONTENT_LENGTH: 433 admin(21886): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7 admin(21886): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041108 admin(21886): HTTP_CONNECTION: keep-alive admin(21886): HTTP_REFERER: https://lists.dogan.ch/mailman/admindb/eth admin(21886): SERVER_NAME: lists.dogan.ch admin(21886): REMOTE_ADDR: 213.144.141.146 admin(21886): PATH_TRANSLATED: /var/www/lists.dogan.ch/htdocs/eth admin(21886): SERVER_PORT: 443 admin(21886): SERVER_ADDR: 213.144.137.44 admin(21886): DOCUMENT_ROOT: /var/www/lists.dogan.ch/htdocs admin(21886): HTTP_PRAGMA: no-cache admin(21886): PYTHONPATH: /opt/mailman admin(21886): SCRIPT_FILENAME: /opt/mailman/cgi-bin/admindb admin(21886): SERVER_ADMIN: ihsan@dogan.ch admin(21886): HTTP_HOST: lists.dogan.ch admin(21886): HTTPS: on admin(21886): HTTP_CACHE_CONTROL: no-cache admin(21886): REQUEST_URI: /mailman/admindb/eth admin(21886): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 admin(21886): GATEWAY_INTERFACE: CGI/1.1 admin(21886): REMOTE_PORT: 64543 admin(21886): HTTP_ACCEPT_LANGUAGE: de,tr;q=0.7,en;q=0.3 admin(21886): CONTENT_TYPE: application/x-www-form-urlencoded admin(21886): HTTP_ACCEPT_ENCODING: gzip,deflate admin(21886): PATH_INFO: /eth ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1062663&group_id=103