Mailman 3 November 2004 - Mailman-coders

[ mailman-Patches-1062352 ] Patch to fix exim documentation bug 1062346
by SourceForge.net 08 Nov '04

08 Nov '04

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_… 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_…

1 0

[ mailman-Bugs-1062346 ] Exim documentation has typeos
by SourceForge.net 08 Nov '04

08 Nov '04

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_… 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_…

1 0

[ mailman-Bugs-1041791 ] Bug in Mailman version 2.1.5 - help
by SourceForge.net 08 Nov '04

08 Nov '04

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_… 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(a)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 <prefix>/lists/*' ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1041791&group_…

1 0

[ mailman-Patches-1057579 ] add urlhost/emailhost options to newlist
by SourceForge.net 07 Nov '04

07 Nov '04

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_… 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(a)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_…

1 0

[ mailman-Feature Requests-1059834 ] daily digest new setting: mail body change
by SourceForge.net 03 Nov '04

03 Nov '04

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_… 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_…

1 0

[ mailman-Feature Requests-1059834 ] daily digest: change mail body
by SourceForge.net 03 Nov '04

03 Nov '04

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_… 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_…

1 0

[ mailman-Bugs-1059637 ] Leave choice on obfuscation method to sysadmin
by SourceForge.net 03 Nov '04

03 Nov '04

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_… 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_…

1 0

[ mailman-Bugs-1059633 ] E-Mail address obfuscation non-functional on subject
by SourceForge.net 03 Nov '04

03 Nov '04

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_… 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(a)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_…

1 0

[ mailman-Bugs-1059598 ] Uncatched bounces by "PostMaster Enterprise" MTA
by SourceForge.net 03 Nov '04

03 Nov '04

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_… 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: <mailman-bounces(a)lists.indymedia.org> Delivered-To: alster(a)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 <alster(a)zeromail.org>; 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 <alster(a)zeromail.org>; 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 <alster(a)zeromail.org>; 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(a)lists.indymedia.org Delivered-To: mailman(a)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 <mailman-owner(a)lists.indymedia.org>; 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 <mailman-owner(a)lists.indymedia.org>; 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 <mailman-owner(a)lists.indymedia.org>; Mon, 1 Nov 2004 20:19:23 +0530 (IST) Message-ID: <1099321413711.1.postmaster(a)tiss.edu> Date: Mon, 1 Nov 2004 20:33:33 +0530 From: Administrator <admin(a)tiss.edu> To: <mailman-owner(a)lists.indymedia.org> 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(a)lists.indymedia.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: mailman.lists.indymedia.org List-Unsubscribe: <http://lists.indymedia.org/cgi-bin/mailman/listinfo/mailman>, <mailto:mailman-request@lists.indymedia.org?subject=unsubscribe> List-Archive: <https://lists.indymedia.org/cgi-bin/mailman/private/mailman> List-Post: <mailto:mailman@lists.indymedia.org> List-Help: <mailto:mailman-request@lists.indymedia.org?subject=help> List-Subscribe: <http://lists.indymedia.org/cgi-bin/mailman/listinfo/mailman>, <mailto:mailman-request@lists.indymedia.org?subject=subscribe> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mailman-bounces(a)lists.indymedia.org Errors-To: mailman-bounces(a)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 <<swagato(a)tiss.edu>> Unknown ---- Original message replaced by message headers ---- Date: Mon, 01 Nov 2004 05:09:35 -0800 From: mailman-owner(a)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_…

1 0

[ mailman-Feature Requests-1059566 ] Message number assignment during archiving with pipermail...
by SourceForge.net 03 Nov '04

03 Nov '04

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_… 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_…

1 0