From noreply at sourceforge.net Mon Aug 2 19:34:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 2 19:37:29 2004 Subject: [ mailman-Bugs-871050 ] Uncought runner exception: Empty module name Message-ID: Bugs item #871050, was opened at 2004-01-05 17:03 Message generated for change (Comment added) made by hallcp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Fernando Barajas (fbarajas) Assigned to: Nobody/Anonymous (nobody) Summary: Uncought runner exception: Empty module name Initial Comment: Hi! I run several lists on mailman, and all of the lists are working OK, but suddently one of them (named fc_general) stopped working, and I get the following in logs/error every time I try to post to the fc_general list: Jan 05 11:03:48 2004 (8451) Uncaught runner exception: Empty module name Jan 05 11:03:48 2004 (8451) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_dige sts msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/var/tmp/python2-2.2.3- root/usr/lib/python2.2/encodings/__init__.py", li ne 51, in search_function ValueError: Empty module name Jan 05 11:03:48 2004 (8451) SHUNTING: 1073322225.130398+2e61b88872c9af343bce1927 de7443b7500f2622 The rest of my lists work correctly. I was using 2.1.2, but today I upgraded to 2.1.4 and it's still failing. What can I do? Thanks! ---------------------------------------------------------------------- Comment By: Charles Hall (hallcp) Date: 2004-08-02 17:34 Message: Logged In: YES user_id=747417 In my case the quick fix was to delete the existing "digest.mbox" file. (Look in ~mailman/lists/your_list/digest.mbox) I guess a bogus email snuck in there that breaks Python's character handling. Your digest subscribers will be unhappy but at least your list is up again. ---------------------------------------------------------------------- Comment By: Dan Langille (junkmale) Date: 2004-02-05 16:10 Message: Logged In: YES user_id=27858 I am having a simlar problem. Mail comes in, but never goes out to the list. Everthing is shunted. I found this "patch" http://www.mail-archive.com/mailman-developers@python. org/msg06317.html and applied it. Then I ran unshunt. That's when this appeared in mailman/logs/error Feb 05 07:57:07 2004 (27060) Dequeuing message destined for missing list: planners Feb 05 07:57:07 2004 (27060) Uncaught runner exception: Empty module name Feb 05 07:57:07 2004 (27060) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 90, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 131, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 304, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 311, in process t = t.encode(charset, 'replace') File "/usr/local/lib/python2.3/encodings/__init__.py", line 84, in search_function globals(), locals(), _import_tail) ValueError: Empty module name ---------------------------------------------------------------------- Comment By: Jochen Witte (zebaoth) Date: 2004-01-27 11:09 Message: Logged In: YES user_id=565663 I use 2.1.3 and have the same problem. Any solution in sight? ---------------------------------------------------------------------- Comment By: Marcel Meyer (meyerm) Date: 2004-01-14 10:56 Message: Logged In: YES user_id=66911 Hi, was this somehow resolved?? I just found to have the same problems! What can I do that the messages (the shunt directory is now 1,5 MB big! [not the contents of the dir, but the dir inode itself...!!] ) are written into the archives without loosing anything? unshunt just puts them back into the shunt directory. Is there some patch - anything? Thanks a lot Marcel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&group_id=103 From noreply at sourceforge.net Tue Aug 3 11:03:06 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 3 11:03:09 2004 Subject: [ mailman-Bugs-1002486 ] error creating mailing lists Message-ID: Bugs item #1002486, was opened at 2004-08-03 09:03 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=1002486&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: souji (soujisan) Assigned to: Nobody/Anonymous (nobody) Summary: error creating mailing lists Initial Comment: i have this errors when i create a new list using web interface, everything else seems to be working fine, i can admin list, create list in command line, .... any news about how to fix this problem.. plz e-mail to me Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 187, in process_request mlist.Create(listname, owner, pw, langs, emailhost) File "/usr/local/mailman/Mailman/MailList.py", line 457, in Create self.InitVars(name, admin, crypted_password) File "/usr/local/mailman/Mailman/MailList.py", line 372, in InitVars baseclass.InitVars(self) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/test1.mbox' Python information: Variable Value sys.version 2.3.3 (#1, Apr 12 2004, 23:50:32) [GCC 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1002486&group_id=103 From noreply at sourceforge.net Tue Aug 3 11:39:57 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 3 11:40:13 2004 Subject: [ mailman-Patches-444879 ] Archive indexer control to improve index Message-ID: Patches item #444879, was opened at 2001-07-26 18:01 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Archive indexer control to improve index Initial Comment: This patch is applicable to Mailman 2.0.6 release and supercedes ealier patches 401669 and 402422. This patch should improve the quality of search results returned by search engines such as htdig (http://www.htdig.org) where the seach engine's index builder responds to strings embedded in the html pages that are the subject of the indexing. The changes in this patch: 1. allow strings for enabling and disabling indexing to be defined in mm_cfg.py. 2. embeds those strings in the pages generated as the html version of a list's archive. By default nothing in the html changes. To get the desired effect, you must define ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in mm_cfg.py You probably want to run this patch as follows: cd <mailman 2.0.6 untarred and unzipped directory> patch -p1 < <this patch file> See also the associated patch for integrating the htdig search software with mailman's internal archiver ouput. ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2004-08-03 09:39 Message: Logged In: YES user_id=75166 indexing-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-03 09:20 Message: Logged In: YES user_id=75166 indexing-2.1.4-0.1.patch is a MM 2.1.4 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:10 Message: Logged In: YES user_id=75166 indexing-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:37 Message: Logged In: YES user_id=75166 indexing-2.1.2-0.1.patch.gz no longer needs patch #661138 to be applied as that patch was incorporated in the MM 2.1.2 release ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:34 Message: Logged In: YES user_id=75166 indexing-2.1.2-0.1.patch.gz is revised for MM 2.1.2 compatibility. Before applying thisversion of the patch you must also apply Bug fix patch #728836 to the source distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 15:49 Message: Logged In: YES user_id=75166 indexing-2.1.1-0.1.patch.gz introduces no functional change but applies without offset warnings to MM 2.1.1 Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:05 Message: Logged In: YES user_id=75166 indexing-2.1-0.1.patch is a revised version of the patch that is compatible with MM 2.1. Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:55 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:53 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:52 Message: Logged In: YES user_id=75166 indexing-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 10:22 Message: Logged In: YES user_id=75166 indexing-2.1b5-0.1.patch is a revised version of the patch that is compatible with MM 2.1b5 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:40 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:39 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:46 Message: Logged In: YES user_id=75166 indexing-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:32 Message: Logged In: YES user_id=75166 An additional file, README.NOINDEXtags is added to indexing-2.0.13-0.3.patch version that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:19 Message: Logged In: YES user_id=75166 An error when building the indexing-2.1b2-0.1.patch meant that copies of the originals of two of the files modified by this version of the patch were added when the patch was run. indexing-2.1b2-0.1.patch removes this error. However, the original error is benign and can be corrected by deleting the extra files HyperArch.py.orig and Defaults.py.in.orig. An additional file, README.NOINDEXtags is added that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:19 Message: Logged In: YES user_id=12800 Another question: is there no standard (de-facto or otherwise) for generic markup that tells indexers not to index a particular section? IOW, for ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is there some generic value that would instruct most (all?) indexers to ignore that section? Or does it necessarily have to be indexer specific? I'm thinking of the situation where you might have ht://Dig installed locally, but your archives are still being spidered by external indexers. It would be good if something more generic could be added to Defaults.py.in ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:14 Message: Logged In: YES user_id=12800 Looking at the 2.1b2 patch, why does it try to create HyperArch.py.orig and Defaults.py.in.orig? Are those included in the patch by mistake? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:08 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:33 Message: Logged In: YES user_id=75166 indexing-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:23 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:11 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch should apply without problems to MM 2.0.12 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:50 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:53 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch should apply without problems to MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:43 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:14 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002. Corrects problem noted or 5 Mar 2002 by nobody ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-05 21:41 Message: Logged In: NO When applying this patch I get an error with Hunk 1 and Defaults.py is not updated. This happens with the a clean download of the latest cvs installation (5 Mar 2002). Any ideas what the problem is? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:53 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:48 Message: Logged In: YES user_id=75166 indexing-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:07 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:03 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.7 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 From noreply at sourceforge.net Tue Aug 3 11:45:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 3 11:45:41 2004 Subject: [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 Category: Unofficial 2.0 patch Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Integration of Mailman & htdig for archi Initial Comment: This patch is applicable to Mailman 2.0.6 release that has had search enhancement patch 444879 patch installed - if your Defaults.py has the ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in it then you've got that patch. It replaces earlier patches 401670 and 402423 and is mainly to correct some problems arising from fixes introduced into Mailman by bug fix releases since the 402423 patch. This patch integrates htdig with Mailman and provides: 1. per list search facility with a search form on the list's TOC page. 2. maintenance of privacy of private archives which requires the user to establish their credentials via the normal private archive access before any access via htdig is allowed. 3. a common base URL for both public and private archive access via htsearch results so that htdig indices are unaffected by changingan archive from private to public and vice versa. All access to archives via htdig is controlled by a new wrapped cgi- bin script called htdig.py. 4. a new cron activated script and extra crontab entry which runs htdig regularly to maintain the per list search indices. 5. automatic creation, deletion and maintenance of htdig configuration files and such. Beyond installing htdig and telling Mailman where it is via mm_cfg you do not have to do any other setup. Well not quite you do have to set up a single per installation symlink to allow htdig to find the automatically generated per list htdig configuration files. You probably want to run this patch as follows: cd <mailman 2.0.6 untarred and unzipped directory> patch -p1 < <this patch file> ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2004-08-03 09:45 Message: Logged In: YES user_id=75166 htdig-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-03 09:16 Message: Logged In: YES user_id=75166 htdig-2.1.4-0.1.patch is a MM 2.1.4 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-12-15 16:13 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.5.patch modifies htdig.py and private.py; the security changes introduced by htdig-2.1.3-0.2 patch to these scripts incorrectly blocked access to the listname.mbox/listname.mbox file. The 0.5 revision of the patch corrects this error. This problem and a suggested fix were pointed out to me in a private email by Stephan Berndts stb-mm at spline.de ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-22 14:55 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.4.patch provides minor improvements in handling of HTTP request handled by htidg.py which lead to the user receiving an authentication challenge. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-19 21:13 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.3.patch.gz add minor private archive security improvements to the patch for MM 2.1.3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:14 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-06 17:47 Message: Logged In: YES user_id=75166 last comment should have read: htdig-2.1.2-0.4.patch.gz corrects an error in 2 scripts, mmsearch.py and remote_mmsearch, which caused an exception if list archives were being accessed via HTTPS and a search was performed. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-06 17:45 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.3.patch.gz corrects an error in 2 scripts, mmsearch.py and remote_mmsearch, which caused an exception if list archives were being accessed via HTTPS and a search was performed. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-01 19:00 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.3.patch.gz adds some minor performance improvement in template handling in MM 2.1.2 You should consider also applying this bug-fis patch: [ 730769 ] template access hierarchy is broken http://sourceforge.net/tracker/index.php? func=detail&aid=730769&group_id=103&atid=100103 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 15:44 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.2.patch.gz corrects error in file uploaded as htdig-2.1.2-0.1.patch.gz. Sorry for any inconvenience. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:46 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.1.patch.gz is a revised version for MM 2.1.2 compatibility. It also incoporates a previosuly unpublished change to overcome a potential problem with htdig excluced urls - see the INSTALL.htdig-mm file for more information ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-21 18:29 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.4.patch.gz fixes a problem with mmsearch handling multi-page search results from htsearch. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-21 17:54 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.3.patch.gz fixes a fault when mmsearch.py is rasing an excpetion because it has had a problem running htsearch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-20 14:10 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.2.patch.gz close a security exploit which allows leakage of information held in htdig's per-list search indexes to users not authorized to view private list archives. Read file INSTALL.htdig-mm installed by this patch for details and instructions for upgrading MM installations using earlier versions of this patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 15:50 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.1.patch.gz introduces no functional change but applies without offset warnings to MM 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-05 18:12 Message: Logged In: YES user_id=75166 It seems it is possible, if this patch is installed, for a list's htdig conf file and the list specific htdig index db files to be read directly through the web interface for list archives. Even if this patch isn't installed it seems a list's pipermail.pck file can also be read directly through the web interface for list archives. This seems to be true for accesses via /pipermail for public lists and via /mailman/private for private lists. The problem does not occur for htdig search results accessed via /mailman/htdig as the htdig.py script is more protective than private.py Broadly speaking the data affected is availble to a user in normal operation which is why I do not consider the issue to be a security breach as such. Adding the following RewriteRule to Apache's httpd.conf prevents the situation, assuming you got the RewriteEngine On: RewriteRule ^(/pipermail/.*)/(pipermail.pck|htdig/[^/]*)$ $1/index.html [F] RewriteRule ^(/mailman/private/.*)/(pipermail.pck|htdig/[^/]*)$ $1/index.htm l [F] You could, of course, substitute an R flag for the F flag on the RewriteRules and be more hacker friendly. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-22 14:20 Message: Logged In: YES user_id=75166 htdig-2.1-0.3.patch corrects yet another bug in htdig.py. Hope that all of them! Stops use of obsolete config variable DEFAULT_HOST in several files. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:18 Message: Logged In: YES user_id=75166 htdig-2.1-0.2.patch corrects a bug in htdig.py and deals with an adverse interaction between htdig.py and a bug in $prefix/scripts/driver (see #668685 for a patch to fix this). It also improves the content type and security handling by htdig.py for MM 2.1 version of patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:14 Message: Logged In: YES user_id=75166 Uploaded wrong file mailer-2.0.13-0.4.patch on last attempt. Should have been htdig-2.0.13-0.4.patch which improves the content type and security handling by htdig.py for MM 2.0.13 version of patch. Please ignore mailer-2.0.13-0.4.patch file ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:09 Message: Logged In: YES user_id=75166 mailer-2.0.13-0.4.patch improves the content type and security handling by htdig.py for MM 2.0.13 version of patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:07 Message: Logged In: YES user_id=75166 htdig-2.1-0.1.patch is a revised version of the patch that is compatible with MM 2.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:48 Message: Logged In: YES user_id=75166 htdig-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-04 10:53 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.3.patch corrects a minor typo in text appearing in the list TOC after the patch is applied. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 10:24 Message: Logged In: YES user_id=75166 htdig-2.1b5-0.1.patch is a revised version of the patch that is compatible with MM 2.1b5 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:43 Message: Logged In: YES user_id=75166 htdig-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-14 11:50 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.3.patch removes use of the file() function, used instead of the open() function, in three cron scripts added by the patch. Use of the file() function created an unnecessary dependency on Python 2.2 ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-12 16:51 Message: Logged In: YES user_id=624179 Got a workaround! The line referred to in the traceback: file(rundig_run_file, 'w').close() is used to create a 'rundig_last_run' file of lenght 0 bytes Creating this manually (or copying it) means the line isn't called and everything seems to work. Either file() is not a valid function call or my python is broken - I'm not literate enough in python to know the answer though! ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-06 14:18 Message: Logged In: YES user_id=624179 Just rebuilt MM as 2.1b3 with htdig. Upgraded lists which had htdig before work fine New lists give the obvious error: Unable to read word database file Did you run htmerge? Running the cronjob doesn't fix as it used to, message is: Output from command /usr/bin/python - S /usr/local/mailman/cron/nightly_htdig .. Traceback (most recent call last): File "/usr/local/mailman/cron/nightly_htdig", line 153, in ? main() File "/usr/local/mailman/cron/nightly_htdig", line 118, in main file(rundig_run_file, 'w').close() NameError: global name 'file' is not defined The archive/htdig folder only contains the xx.conf file, but no db.xx files If I copy in db.xx files from another list then the problem goes away (except I've now got an invalid set of references!) Is this my elementary error or is it more sinister?! ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-15 11:02 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.2.patch corrects a dumb syntax error in htdig- 2.1b3-0.1.patch which will typically show up as logged errors in the operation of the ArchRunner qrunner at line 721 of HyperArch.py ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:51 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 16:33 Message: Logged In: YES user_id=12800 I've sent Richard some comments off-line about this patch. Meta comments: the 2.0.x patches can't be officially supported, but I'm going to create an unofficial patches page off the wiki for where the 2.0 patches can be migrated. I think this patch set is too big for MM2.1, but if it's cleaned up as per my private message, let's re-evaluate it for MM2.2 (or 3.0). ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:11 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:35 Message: Logged In: YES user_id=75166 htdig-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:25 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 15:07 Message: Logged In: YES user_id=75166 Do not use htdig-2.0.12-0.1.patch there is an error in it. Use htdig-2.0.12-0.2.patch instead ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:10 Message: Logged In: YES user_id=75166 htdig-2.0.12-0.1.patch is a revised version of the patch that applies without complaint to MM 2.0.12. It also add a facility for adding site wide htdig configuration attributes to all list specific htdig configuration files. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:59 Message: Logged In: YES user_id=75166 htdig-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 This version removes an incompatibility with Python 2.2 which caused warning messages to be generated when any of the family cron/nightly_htdig scripts were run. Some guidance on file access permissions for some htdig database files needed by rundig have been added to installation notes. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:59 Message: Logged In: YES user_id=75166 htdig-2.0.10-0.1.patch is a revised version of the patch that is compatible with MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:46 Message: Logged In: YES user_id=75166 htdig-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:22 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002 Known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:56 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:58 Message: Logged In: YES user_id=75166 htdig-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 17:33 Message: Logged In: YES user_id=75166 The htdig-2.0.8-0.1.patch version of the patch resolves a problem that can arise with htdig indexing if the web_page_url for a list uses other than the http addressing (some folks want to use https). While specified as for MM 2.0.8 the revised patch should work OK with 2.0.7, 2.0.6 and probably back as far as 2.0.3. If you do not have the requirement for using other than http addressing in you lists web_page_urls it probably isn't worth the trouble of upgrading to this patch level. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:08 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:00 Message: Logged In: YES user_id=75166 This patch should also apply without problems to Mm 2.0.7 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-09 11:54 Message: Logged In: YES user_id=75166 The htdig-2.0.6-03.patch version of the patch makes some previously hard-coded things configurable and enhances the capability to run the htdig searches and indexing on a different machine to the one delivering Mailman and Mailman's web UI. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 From noreply at sourceforge.net Tue Aug 3 11:56:21 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 3 11:56:33 2004 Subject: [ mailman-Patches-644797 ] Revised mailer exit status Message-ID: Patches item #644797, was opened at 2002-11-27 15:56 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Revised mailer exit status Initial Comment: This patch modifies the Python scripts in $prefix/scripts/ that are used by the MTA to deliver incoming mail to Mailman. The exit statuses now returned are drawn from the mail related values defined in /usr/include/sysexits.h This allows the MTA to return more meaningful responses to the sender when rejecting mail. It also allows a more sympathetic treatment of mail in the event that the Python script suffers an unexpected exception when handling incoming email. Such exceptions are now logged to MM's $prefix/logs/erro in all but the most extreme error cases and the internal information about the Python exception is not passed into the response to the sender. There are two patch versions; one for MM 2.0.13 and the other for MM 2.1b5 in the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2004-08-03 09:56 Message: Logged In: YES user_id=75166 exitstatus-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:14 Message: Logged In: YES user_id=75166 exitstatus-2.1.3-0.1.patch can be used with MM 2.1.4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:39 Message: Logged In: YES user_id=75166 exitstatus-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:40 Message: Logged In: YES user_id=75166 exitstatus-2.1.2-0.1.patch is a revision of the patch for MM 2.1.2 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:42 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is alos applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:30 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is a revision of the patch for MM 2.1 compatibility ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-24 03:29 Message: Logged In: YES user_id=12800 Sorry Richard, I have to defer this one. It's too much for me to think about for MM2.1. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:58 Message: Logged In: YES user_id=75166 exitstatus-2.1b6-0.1.patch is a revision of the patch for MM 2.1b6 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 15:58 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 From noreply at sourceforge.net Tue Aug 3 11:59:25 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 3 11:59:28 2004 Subject: [ mailman-Bugs-1002486 ] error creating mailing lists - [permision errors] Message-ID: Bugs item #1002486, was opened at 2004-08-03 09:03 Message generated for change (Settings changed) made by soujisan You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1002486&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: souji (soujisan) Assigned to: Nobody/Anonymous (nobody) >Summary: error creating mailing lists - [permision errors] Initial Comment: i have this errors when i create a new list using web interface, everything else seems to be working fine, i can admin list, create list in command line, .... any news about how to fix this problem.. plz e-mail to me Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 187, in process_request mlist.Create(listname, owner, pw, langs, emailhost) File "/usr/local/mailman/Mailman/MailList.py", line 457, in Create self.InitVars(name, admin, crypted_password) File "/usr/local/mailman/Mailman/MailList.py", line 372, in InitVars baseclass.InitVars(self) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/test1.mbox' Python information: Variable Value sys.version 2.3.3 (#1, Apr 12 2004, 23:50:32) [GCC 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1002486&group_id=103 From noreply at sourceforge.net Tue Aug 3 12:02:51 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 3 12:02:56 2004 Subject: [ mailman-Patches-760567 ] moderation request message content Message-ID: Patches item #760567, was opened at 2003-06-25 15:25 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=760567&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: moderation request message content Initial Comment: This patch makes per-list configurable the inclusion of the body of messages that require moderation in the request messages sent to list moderators. This patch has similar objectives to those of patch #593674 but is a simpler implementation. This adds one list attribute, which can be set or unset via the web admin GUI, and which controls whether the moderated message body is included in the moderator request. Apply the attached patch file with the MM build directory as the current working directory using the command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2004-08-03 10:02 Message: Logged In: YES user_id=75166 modinc-2.1.5-0.1.patch is a MM 2.1.5 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:28 Message: Logged In: YES user_id=75166 modinc-2.1.4-0.1.patch is a MM 2.1.4 compatible veriosn of this patch ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-24 17:29 Message: Logged In: YES user_id=12800 I'm going to defer this one until 2.1.5 since I don't want to add any new list attributes at this late date. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:43 Message: Logged In: YES user_id=75166 modinc-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-25 17:21 Message: Logged In: YES user_id=75166 Missed one changed file from initial patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=760567&group_id=103 From noreply at sourceforge.net Tue Aug 3 12:04:47 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 3 12:04:54 2004 Subject: [ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration patch Message-ID: Patches item #820723, was opened at 2003-10-09 16:19 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman/pipermail/MHonArc integration patch Initial Comment: This patch tightly integrates the MHonArc mail-to-HTML convertor with Mailman and its internal pipermail archiving code. The purpose of the patch is to produce a fusion of (hopefully) the best features of pipermail and MHonArc for handling Mailman mailing list archives. For more detail see patch content or http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2004-08-03 10:04 Message: Logged In: YES user_id=75166 mhonarc-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-19 23:53 Message: Logged In: YES user_id=696559 I've applied this patch(mhonarc-2.1.4-0.1.patch.gz) and it works great for me. Would someone apply to offcial cvs tree? Thanks. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:32 Message: Logged In: YES user_id=75166 mhonarc-2.1.4-0.1.patch is a MM 2.1.4 compatible version of this patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-22 14:32 Message: Logged In: YES user_id=75166 mhonarc-2.1.3-0.6.patch better supports the use of MHonArc -saveresources option. Also fixes minor HTML syntax error in mhonarc.mrc and author.mrc that affected generated date and author index pages. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-14 05:49 Message: Logged In: YES user_id=75166 With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself defined in Defaults.py is the empty string and, until this is changed, the option to select MHonArc instead of pipermail for per-list archiving is not offered on the web admin GUI. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-10 17:51 Message: Logged In: YES user_id=75166 Under some circumstances, when a single message is passed to MHonArc for archiving via a pipe, MHonArc may finish its processing and exit, closing its STDIN before the Mailman process that invoked it has finished output of the message to the pipe. Mistakenly, the patched pipermail code treated this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103 From noreply at sourceforge.net Tue Aug 3 12:08:47 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 3 12:08:52 2004 Subject: [ mailman-Bugs-1002486 ] error creating mailing lists - [permision errors - fixed] Message-ID: Bugs item #1002486, was opened at 2004-08-03 09:03 Message generated for change (Settings changed) made by soujisan You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1002486&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: souji (soujisan) Assigned to: Nobody/Anonymous (nobody) >Summary: error creating mailing lists - [permision errors - fixed] Initial Comment: i have this errors when i create a new list using web interface, everything else seems to be working fine, i can admin list, create list in command line, .... any news about how to fix this problem.. plz e-mail to me Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 187, in process_request mlist.Create(listname, owner, pw, langs, emailhost) File "/usr/local/mailman/Mailman/MailList.py", line 457, in Create self.InitVars(name, admin, crypted_password) File "/usr/local/mailman/Mailman/MailList.py", line 372, in InitVars baseclass.InitVars(self) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/test1.mbox' Python information: Variable Value sys.version 2.3.3 (#1, Apr 12 2004, 23:50:32) [GCC 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1002486&group_id=103 From noreply at sourceforge.net Tue Aug 3 12:43:31 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 3 12:43:35 2004 Subject: [ mailman-Patches-644810 ] Sendmail mailer in Python Message-ID: Patches item #644810, was opened at 2002-11-27 16:27 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Sendmail mailer in Python Initial Comment: This patch provide a Python implementation (with C wrapper) of a Sendmail mailer, if Sendmail is your MTA of choice, which removes the necessity of maintining an aliases database on your Mailman server. All subject to a bunch of conditions most prominent of which is that the server has to be pretty much dedicated to MM. This patch draws on an original contribution by David Champion <dgc@uchicago.edu> which is included in the contrib directory of the Mailman 2.1b distribution as mm-handler. See the README.SENDMAIL.mailer installed by this patch for differences between this and David's Perl original and more information of what you are getting into if you use this patch. Versions of the patch for MM 2.0.13 and MM 2.1b5 are available. This patch requires patch 644797 to be installed before it. In the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2004-08-03 10:43 Message: Logged In: YES user_id=75166 mailer-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:23 Message: Logged In: YES user_id=75166 mailer-2.1.3-0.2.patch can be used with MM 2.1.4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:20 Message: Logged In: YES user_id=75166 mailer-2.1.3-0.1.patch can be used with MM 2.1.4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:33 Message: Logged In: YES user_id=75166 mailer-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:31 Message: Logged In: YES user_id=75166 mailer-2.1.2-0.1.patch.gz removes support for MM 2.0.13 mail aliases from the mailer and is MM 2.1.2 compatible ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:50 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch is also applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-16 15:30 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch and mailer-2.0.13-0.4.patch have VERP handling added and a new feature to rejct delivery of mail to existing lists by adding the lists names to a SUSPENDED_LISTS dictionary variable defined in mm_cfg.py. This is equivalent to deleting list aliases from the aliases file, while leaving the list itself in place, in a conventional sendmail configuration. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-03 18:19 Message: Logged In: YES user_id=75166 the mm_mailer script in mailer-2.1-0.2.patch now handles VERP'ed return addresses in bounced mail which I missed in the original implementation ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:34 Message: Logged In: YES user_id=75166 mailer-2.1-0.1.patch is a revision of the patch for MM 2.1 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 12:16 Message: Logged In: YES user_id=75166 mailer-2.1b6-0.1.patch is MM 2.1b6 compatible. It also folds the case of listname and servername for compaiblity with MMs naive belief that listnames are case all lower case. case "(Email addresses are not case sensitive, but they are sensitive to almost everything else :-)" ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-03 17:37 Message: Logged In: YES user_id=75166 Fix for permissions related exceptions being generated by the subprocess spawned by mm_mailer script ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-03 17:36 Message: Logged In: YES user_id=75166 Fix for permissions related exceptions being generated by the subprocess spawned by mm_mailer script. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 16:29 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 From noreply at sourceforge.net Tue Aug 3 13:56:31 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 3 13:56:37 2004 Subject: [ mailman-Bugs-930819 ] Focus form entry onload in admlogin.html Message-ID: Bugs item #930819, was opened at 2004-04-07 05:13 Message generated for change (Comment added) made by kink You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930819&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Christian Reis (kiko_async) Assigned to: Nobody/Anonymous (nobody) Summary: Focus form entry onload in admlogin.html Initial Comment: I run quite a few mailing lists, and boy is it annoying to have to click on each and every password box in the administration login page. So here's a patch that fixes the pages to use DOM-compliant javascript to focus the field (which is provably harmless in JS-deprived situations) ---------------------------------------------------------------------- Comment By: Thijs Kinkhorst (kink) Date: 2004-08-03 13:56 Message: Logged In: YES user_id=285765 I'd really like to "vote" for this patch, since the change is very small but would make our life a bit easier. ---------------------------------------------------------------------- Comment By: Christian Reis (kiko_async) Date: 2004-04-07 05:14 Message: Logged In: YES user_id=222305 Tested and working locally: http://www.async.com.br/mailman/admin/kiwi ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930819&group_id=103 From noreply at sourceforge.net Wed Aug 4 08:26:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 4 08:26:30 2004 Subject: [ mailman-Patches-1003070 ] Decode original subject in post acknowledgement Message-ID: Patches item #1003070, was opened at 2004-08-04 15:26 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=1003070&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: Decode original subject in post acknowledgement Initial Comment: Original subject line in post acknowledgement message will be decoded and be converted. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1003070&group_id=103 From noreply at sourceforge.net Wed Aug 4 21:12:25 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 4 21:12:32 2004 Subject: [ mailman-Bugs-715581 ] plain text digest bug in appending messages Message-ID: Bugs item #715581, was opened at 2003-04-04 16:50 Message generated for change (Comment added) made by ashawley You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: plain text digest bug in appending messages Initial Comment: Sometimes, messages are incorrectly appended in the plain digests, which cause 2 or more messages to be attached to 1. For example, I got a digest which mentions one message in the Topic list, but at the end of this message, the next message is "glued" to the bottom of it: (...top of first message...) --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!From EMAILADDR@aol.com Fri Mar 28 14:04:32 2003 Return-Path: <EMAILADDR@aol.com> Delivered-To: fans@list.miss-janet.com (...second message continues with all it's headers and content) As you can see, the "From..." of the second message starts directly after the last character of the first message. Here's a second example: (... top of first message...) peace out: -oscarFrom EMAILADDR@aol.com Tue Apr 1 15:04:42 2003 Return-Path: <EMAILADDR@aol.com> Delivered-To: fans@list.miss-janet.com (..second message continues...) Again, the "From..." from the next message is glued to the previous message. Is this a simple missing end of line issue or is it more complicated? I can't seem to see a good pattern in it... Ricardo. ---------------------------------------------------------------------- Comment By: Aaron Hawley (ashawley) Date: 2004-08-04 14:12 Message: Logged In: YES user_id=25294 why was this bug closed, is it fixed in CVS? ---------------------------------------------------------------------- Comment By: Fred Bone (fjpb) Date: 2004-01-21 13:09 Message: Logged In: YES user_id=956771 Is the first message originally in quoted-printable, with no concluding blank line? I have seen quite a lot of concatenated messages lately, and in every instance that I've checked the first message is QP, is multipart/alternative with the other part in html (stripped for digest), and has the boundary immediately after the last line of the QP part. The problem affects MIME-digests as well as plaintext ones. I have no clue how it might be fixed, or even where things are going wrong, but maybe someone else can get a handle on it from this info. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_id=103 From noreply at sourceforge.net Thu Aug 5 19:54:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Aug 5 19:54:25 2004 Subject: [ mailman-Bugs-1004091 ] "-1 Mailman moderator request(s) waiting" Message-ID: Bugs item #1004091, was opened at 2004-08-05 10:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1004091&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Lucian Smith (luciansmith) Assigned to: Nobody/Anonymous (nobody) Summary: "-1 Mailman moderator request(s) waiting" Initial Comment: Mailman mailed this to me today. I have no idea why. I'm running 2.1.5: --------- From: mailman-bounces@evolution.genetics.washington.edu To: mailman-owner@evolution.genetics.washington.edu Subject: -1 Mailman moderator request(s) waiting Date: Thu, 05 Aug 2004 08:00:01 -0700 Sender: mailman-bounces@gs.washington.edu Message-ID: The Mailman@evolution.genetics.washington.edu mailing list has -1 request(s) waiting for your consideration at: http://evolution.genetics.washington.edu/mailman/admindb/mailman Please attend to this at your earliest convenience. This notice of pending requests, if any, will be sent out daily. --------- First of all, the URL given doesn't work (it takes me to the general http://evolution.gs.washington.edu/mailman/listinfo page), secondly, I don't think 'mailman' is an actual mailing list that we have, and thirdly, 'negative one'? That's just wacky. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1004091&group_id=103 From noreply at sourceforge.net Fri Aug 6 23:28:42 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 6 23:28:47 2004 Subject: [ mailman-Patches-1004885 ] digest crashes on gpg signed message Message-ID: Patches item #1004885, was opened at 2004-08-06 16:28 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=1004885&group_id=103 Category: command line scripts Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Stephen Baker (sbbaker65) Assigned to: Nobody/Anonymous (nobody) Summary: digest crashes on gpg signed message Initial Comment: Digest processing crashed when it encountered a gpg signed message created in evolution. Environment: Mail client Evolution: 1.4.5 GnuPG: 1.2.3 Mail server Mailman: 2.2a0 Python: 2.3a0 Sendmail: 8.12.8 SunOS: 5.7 Correction: Scrubber.py:74 def guess_extension(ctype, ext): # mimetypes maps multiple extensions to the same type, e.g. .doc, .dot, # and .wiz are all mapped to application/msword. This sucks for finding # the best reverse mapping. If the extension is one of the giving # mappings, we'll trust that, otherwise we'll just guess. :/ all = guess_all_extensions(ctype, strict=0) + if all == None: + all = [] if ext in all: return ext return all and all[0] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1004885&group_id=103 From noreply at sourceforge.net Sat Aug 7 19:16:34 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Aug 7 19:16:37 2004 Subject: [ mailman-Bugs-1005198 ] Error Accessing Web Interface Message-ID: Bugs item #1005198, was opened at 2004-08-07 10:16 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1005198&group_id=103 Category: Web/CGI Group: 2.1 alpha Status: Open Resolution: None Priority: 5 Submitted By: BobCassidy (bcassid) Assigned to: Nobody/Anonymous (nobody) Summary: Error Accessing Web Interface Initial Comment: >From the Mailman Administrator Authentication page for any of our lists, after entering the List Administrator Password, and clicking on Let me in, we get the following: Bug in Mailman version 2.1.2 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/share/mailman/scripts/driver", line 87, in run_main main() File "/usr/share/mailman/Mailman/Cgi/admin.py", line 194, in main mlist.Save() File "/usr/share/mailman/Mailman/MailList.py", line 515, in Save self.__save(dict) File "/usr/share/mailman/Mailman/MailList.py", line 487, in __save os.unlink(fname_last) OSError: [Errno 22] Invalid argument: '/private/var/mailman/lists/ techcoach/config.pck.last' Python information: Variable Value sys.version 2.3 (#1, Sep 13 2003, 00:49:11) [GCC 3.3 20030304 (Apple Computer, Inc. build 1495)] sys.executable /usr/bin/python sys.prefix /System/Library/Frameworks/Python.framework/Versions/2.3 sys.exec_prefix /System/Library/Frameworks/Python.framework/Versions/2.3 sys.path /System/Library/Frameworks/Python.framework/Versions/2.3 sys.platform darwin Environment variables: Variable Value HTTP_REFERER http://www.somerton.k12.az.us/mailman/admin/techcoach SERVER_SOFTWARE Apache/1.3.29 (Darwin) DAV/1.0.3 PHP/4.3.2 SCRIPT_NAME /mailman/admin SERVER_SIGNATURE Apache/1.3.29 Server at www.somerton.k12.az.us Port 80 REQUEST_METHOD POST PATH_INFO /techcoach SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 38 HTTP_USER_AGENT Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/ 125.2 (KHTML, like Gecko) Safari/125.8 HTTP_CONNECTION close SERVER_NAME www.somerton.k12.az.us REMOTE_ADDR 69.166.111.68 PATH_TRANSLATED /Library/WebServer/Documents/techcoach SERVER_PORT 80 SERVER_ADDR 207.246.48.2 DOCUMENT_ROOT /Library/WebServer/Documents PYTHONPATH /usr/share/mailman SCRIPT_FILENAME /usr/share/mailman/cgi-bin/admin SERVER_ADMIN webmaster@somerton.k12.az.us SCRIPT_URI http://www.somerton.k12.az.us/mailman/admin/techcoach HTTP_HOST www.somerton.k12.az.us SCRIPT_URL /mailman/admin/techcoach REQUEST_URI /mailman/admin/techcoach HTTP_ACCEPT */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 36046 HTTP_ACCEPT_LANGUAGE en-us, ja;q=0.33, en;q=0.67 __CF_USER_TEXT_ENCODING 0x46:0:0 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip, deflate;q=1.0, identity;q=0.5, *;q=0 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1005198&group_id=103 From noreply at sourceforge.net Tue Aug 10 21:20:23 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 10 21:20:27 2004 Subject: [ mailman-Bugs-1006797 ] Bug when trying to create new list through web interface. Message-ID: Bugs item #1006797, was opened at 2004-08-10 19:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1006797&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: zjs2k (zjs2k) Assigned to: Nobody/Anonymous (nobody) Summary: Bug when trying to create new list through web interface. Initial Comment: When I try to get in the following page, I was told I hit a bug: http://www.mydomain.com/mailman/create/ Here are the info: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 63, in run_main from Mailman.Logging.StampedLogger import StampedLogger File "/usr/local/mailman/Mailman/Logging/StampedLogger. py", line 18, in ? import time ImportError: No module named time ------------------------------------------------------- ------------------------- Python information: Variable Value sys.version 2.3.4 (#1, Aug 10 2004, 17:54:43) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /root/Python-2.3.4/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 ------------------------------------------------------- ------------------------- Environment variables: Variable Value SCRIPT_NAME /mailman/create SERVER_SIGNATURE REQUEST_METHOD GET SERVER_PROTOCOL HTTP/1.1 QUERY_STRING HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) HTTP_CONNECTION Keep-Alive SERVER_PORT 80 PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/admin REQUEST_URI /mailman/admin HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/x-shockwave-flash, */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 2494 HTTP_ACCEPT_LANGUAGE en-us HTTP_ACCEPT_ENCODING gzip, deflate ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1006797&group_id=103 From noreply at sourceforge.net Wed Aug 11 00:54:27 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 11 00:54:30 2004 Subject: [ mailman-Bugs-1006918 ] Bug when creating new (first) list Message-ID: Bugs item #1006918, was opened at 2004-08-10 22:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1006918&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Allan Stuart Meidlein (meidleina) Assigned to: Nobody/Anonymous (nobody) Summary: Bug when creating new (first) list 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 "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 226, in process_request sys.modules[modname].create(mlist, cgi=1) File "/usr/local/mailman/Mailman/MTA/Postfix.py", line 232, in create _update_maps() File "/usr/local/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /usr/local/mailman/data/aliases (status: 1, Operation not permitted) Python information: Variable Value sys.version 2.3.4 (#2, Aug 9 2004, 14:24:36) [GCC 3.3.3 [FreeBSD] 20031106] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd5 Environment variables: Variable Value HTTP_COOKIE mailman+admin=280200000069b23c1941732800000061636461363639303732663038636131613939626634313833623630646434633837373461396637; phpbb2mysql_data=a%3A0%3A%7B%7D; phpbb2mysql_sid=80ae4896c2126063ee2215126b198a2e SERVER_SOFTWARE Apache/2.0.50 (FreeBSD) PHP/4.3.8 SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache/2.0.50 (FreeBSD) PHP/4.3.8 Server at www.mydomain.com Port 80 REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 150 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; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 HTTP_CONNECTION keep-alive HTTP_REFERER http://www.mydomain.com/mailman/create SERVER_NAME www.mydomain.com REMOTE_ADDR 345.678.901.234 SERVER_PORT 80 SERVER_ADDR 123.456.789.012 DOCUMENT_ROOT /usr/home/sjg/sjgftp/web-site PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/create SERVER_ADMIN webmaster@mydomain.com HTTP_HOST www.mydomain.com REQUEST_URI /mailman/create HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 64283 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate UNIQUE_ID eEFizcz0P8kAAAmTDikAAAAC ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1006918&group_id=103 From noreply at sourceforge.net Wed Aug 11 01:23:14 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 11 01:23:22 2004 Subject: [ mailman-Bugs-1006918 ] Bug when creating new (first) list Message-ID: Bugs item #1006918, was opened at 2004-08-10 22:54 Message generated for change (Comment added) made by meidleina You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1006918&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Allan Stuart Meidlein (meidleina) Assigned to: Nobody/Anonymous (nobody) Summary: Bug when creating new (first) list 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 "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 226, in process_request sys.modules[modname].create(mlist, cgi=1) File "/usr/local/mailman/Mailman/MTA/Postfix.py", line 232, in create _update_maps() File "/usr/local/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /usr/local/mailman/data/aliases (status: 1, Operation not permitted) Python information: Variable Value sys.version 2.3.4 (#2, Aug 9 2004, 14:24:36) [GCC 3.3.3 [FreeBSD] 20031106] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd5 Environment variables: Variable Value HTTP_COOKIE mailman+admin=280200000069b23c1941732800000061636461363639303732663038636131613939626634313833623630646434633837373461396637; phpbb2mysql_data=a%3A0%3A%7B%7D; phpbb2mysql_sid=80ae4896c2126063ee2215126b198a2e SERVER_SOFTWARE Apache/2.0.50 (FreeBSD) PHP/4.3.8 SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache/2.0.50 (FreeBSD) PHP/4.3.8 Server at www.mydomain.com Port 80 REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 150 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; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 HTTP_CONNECTION keep-alive HTTP_REFERER http://www.mydomain.com/mailman/create SERVER_NAME www.mydomain.com REMOTE_ADDR 345.678.901.234 SERVER_PORT 80 SERVER_ADDR 123.456.789.012 DOCUMENT_ROOT /usr/home/sjg/sjgftp/web-site PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/create SERVER_ADMIN webmaster@mydomain.com HTTP_HOST www.mydomain.com REQUEST_URI /mailman/create HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 64283 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate UNIQUE_ID eEFizcz0P8kAAAmTDikAAAAC ---------------------------------------------------------------------- >Comment By: Allan Stuart Meidlein (meidleina) Date: 2004-08-10 23:23 Message: Logged In: YES user_id=13862 This error occurs, but it appears that the list is created (minus the email saying so). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1006918&group_id=103 From noreply at sourceforge.net Wed Aug 11 15:29:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 11 15:29:12 2004 Subject: [ mailman-Bugs-1007263 ] checkdbs cron error starting with v2.1.5 Message-ID: Bugs item #1007263, was opened at 2004-08-11 08: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=1007263&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: moyman (moyman) Assigned to: Nobody/Anonymous (nobody) Summary: checkdbs cron error starting with v2.1.5 Initial Comment: I just started getting these errors after upgrading from 2.1.3 to 2.1.5: drydock:.../lists/purdueagparent-list/en[34]# pwd /usr/local/mailman/lists/purdueagparent-list/en drydock:.../lists/purdueagparent-list/en[35]# ls -las total 14 2 drwx--l--- 2 nobody mailman 512 Aug 6 10:32 ./ 2 drwxrwsr-x 3 root mailman 512 Aug 10 12:00 ../ 10 -rw------- 1 nobody mailman 4153 Aug 6 10:32 listinfo.html So the file it complains of doesn't exist. I have received this for 2 lists so far? --mike ------- Forwarded Message Date: Wed, 11 Aug 2004 08:00:21 -0500 (EST) From: List Serve To: listman@ecn.purdue.edu Subject: Output from "cron" command Your "cron" job on drydock.ecn.purdue.edu /var/local/python/bin/python -S /usr/local/mailman/cron/checkdbs produced the following output: Traceback (most recent call last): File "/usr/local/mailman/cron/checkdbs", line 178, in ? main() File "/usr/local/mailman/cron/checkdbs", line 108, in main }, mlist=mlist) File "/usr/local/mailman/Mailman/Utils.py", line 509, in maketext return findtext(templatefile, dict, raw, lang, mlist)[0] File "/usr/local/mailman/Mailman/Utils.py", line 468, in findtext fp = open(filename) IOError: [Errno 13] Permission denied: '/usr/local/mailman/lists/purdueagparent-list/en/checkdbs.txt' ------- End of Forwarded Message ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1007263&group_id=103 From noreply at sourceforge.net Wed Aug 11 16:18:01 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 11 16:18:03 2004 Subject: [ mailman-Bugs-1007298 ] Bad email address parsing Message-ID: Bugs item #1007298, was opened at 2004-08-11 15:18 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=1007298&group_id=103 Category: None Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Donal K. Fellows (dkf) Assigned to: Nobody/Anonymous (nobody) Summary: Bad email address parsing Initial Comment: When I send messages to a subscriber-only mailing list (on SourceForge) that I subscribe to, they still sometimes get held waiting for admin approval. The email address that I use is: Donal K. Fellows and mailman holds the message because it thinks the email address is donalk.fellows (with no spaces) and not the bit in angle brackets. Examining the headers of the message that was sent, I see that the problem messages are missing double-quotes from around my real name (it seems that I've found a buggy email client) but since everything else (including Exim and Mozilla) accepts the message just fine, I think that something's not right with your email address parsing. The precise version of mailman being used is 2.0.9 apparently, if that helps. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1007298&group_id=103 From noreply at sourceforge.net Wed Aug 11 20:53:21 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 11 20:53:26 2004 Subject: [ mailman-Patches-1007477 ] list_members filter by moderated/unmoderated Message-ID: Patches item #1007477, was opened at 2004-08-11 18:53 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=1007477&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jeff Bailey (jbailey999) Assigned to: Nobody/Anonymous (nobody) Summary: list_members filter by moderated/unmoderated Initial Comment: list_members should have the ability to see who can post and who can't. MM2.0 made it easy to find this inforamtion, so this is a regression. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1007477&group_id=103 From noreply at sourceforge.net Thu Aug 12 04:54:17 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Aug 12 04:54:20 2004 Subject: [ mailman-Bugs-1007706 ] Reply-To not preserved if it contains 2 addresses or more Message-ID: Bugs item #1007706, was opened at 2004-08-11 22:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1007706&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ambrose C. LI (acli) Assigned to: Nobody/Anonymous (nobody) Summary: Reply-To not preserved if it contains 2 addresses or more Initial Comment: If I send a piece of mail to a mailman (2.1.4) managed list with a Reply-To in the form Reply-To: foo@example.org, bar@example.org the mail, when actually delivered, will only contain Reply-To: foo@example.org i.e., only the first address in Reply-To will be preserved; the rest is discarded. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1007706&group_id=103 From noreply at sourceforge.net Thu Aug 12 21:49:06 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Aug 12 21:49:11 2004 Subject: [ mailman-Bugs-1007706 ] Reply-To not preserved if it contains 2 addresses or more Message-ID: Bugs item #1007706, was opened at 2004-08-11 22:54 Message generated for change (Settings changed) made by acli You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1007706&group_id=103 Category: None Group: 2.1 (stable) >Status: Deleted >Resolution: Invalid Priority: 5 Submitted By: Ambrose C. LI (acli) Assigned to: Nobody/Anonymous (nobody) Summary: Reply-To not preserved if it contains 2 addresses or more Initial Comment: If I send a piece of mail to a mailman (2.1.4) managed list with a Reply-To in the form Reply-To: foo@example.org, bar@example.org the mail, when actually delivered, will only contain Reply-To: foo@example.org i.e., only the first address in Reply-To will be preserved; the rest is discarded. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1007706&group_id=103 From noreply at sourceforge.net Fri Aug 13 20:09:19 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 13 20:09:22 2004 Subject: [ mailman-Patches-1008865 ] patch to add 'Spam' dispostion Message-ID: Patches item #1008865, was opened at 2004-08-13 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=300103&aid=1008865&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Chris Cogdon (chriscog) Assigned to: Nobody/Anonymous (nobody) Summary: patch to add 'Spam' dispostion Initial Comment: This patch will add a 'Spam' disposition option to the admindb page (and the associuated handlers). Selecting 'Spam' will both forward the mail to a pre-programmed spam handler address (eg: spamcop, or spamassassin's bayesian filter), and discard the mail. This is MUCH easier than hitting 'defer', 'forward', and pasting an address; one wants to spend as little time as possible handling spam. Note that this patch does NOT handle any i18n issues. I don't know how to do that... if given some pointers on how, I'm most happy to, though. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1008865&group_id=103 From noreply at sourceforge.net Fri Aug 13 20:10:13 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 13 20:10:19 2004 Subject: [ mailman-Patches-1008865 ] patch to add 'Spam' disposition Message-ID: Patches item #1008865, was opened at 2004-08-13 18:09 Message generated for change (Settings changed) made by chriscog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1008865&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Chris Cogdon (chriscog) Assigned to: Nobody/Anonymous (nobody) >Summary: patch to add 'Spam' disposition Initial Comment: This patch will add a 'Spam' disposition option to the admindb page (and the associuated handlers). Selecting 'Spam' will both forward the mail to a pre-programmed spam handler address (eg: spamcop, or spamassassin's bayesian filter), and discard the mail. This is MUCH easier than hitting 'defer', 'forward', and pasting an address; one wants to spend as little time as possible handling spam. Note that this patch does NOT handle any i18n issues. I don't know how to do that... if given some pointers on how, I'm most happy to, though. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1008865&group_id=103 From noreply at sourceforge.net Fri Aug 13 23:45:26 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 13 23:45:29 2004 Subject: [ mailman-Patches-1008983 ] qrunner w/ multiple slices crashing. Message-ID: Patches item #1008983, was opened at 2004-08-13 16:45 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=1008983&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Brian Greenberg (grnbrg) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner w/ multiple slices crashing. Initial Comment: When running qrunner with multiple instances of a particular class (ie: qrunner -r OutgoingRunner:0:4 -r OutgoingRunner:1:4 -r OutgoingRunner:2:4 -r OutgoingRunner:3:4 ) the qrunner processes for this class will periodically crash, leaving the following traces: logs/qrunner: Aug 13 15:27:51 2004 (29188) Master qrunner detected subprocess exit (pid: 23829, sig: None, sts: 1, class: OutgoingRunner, slice: 1/4) [restarting] logs/error: Aug 13 15:27:51 2004 qrunner(23829): Traceback (most recent call last): Aug 13 15:27:51 2004 qrunner(23829): File "/usr/local/mailman/bin/qrunner", line 270, in ? Aug 13 15:27:51 2004 qrunner(23829): main() Aug 13 15:27:51 2004 qrunner(23829): File "/usr/local/mailman/bin/qrunner", line 230, in main Aug 13 15:27:51 2004 qrunner(23829): qrunner.run() Aug 13 15:27:51 2004 qrunner(23829): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 70, in run Aug 13 15:27:51 2004 qrunner(23829): filecnt = self._oneloop() Aug 13 15:27:51 2004 qrunner(23829): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop Aug 13 15:27:51 2004 qrunner(23829): msg, msgdata = self._switchboard.dequeue(filebase) Aug 13 15:27:51 2004 qrunner(23829): File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 143, in dequeue Aug 13 15:27:51 2004 qrunner(23829): fp = open(filename) Aug 13 15:27:51 2004 qrunner(23829): IOError : [Errno 2] No such file or directory: '/var/priv/mail/mailman/qfiles/out/1092428866.8410051+70dcb0bb96e6460d8cd2a a8103cce318cfa3ed1f.pck' This is caused by a logic error in mailman/Mailman/Queues/Switchboard.py:files. Specifically, when there are not multiple slices running for a particular qrunner class, self.__upper and self.__lower are both set to None in Switchboard.py:__init__. Switchboard.py:files contains the statement: if not lower or (lower <= long(digest, 16) < upper): times[float](when)] = filebase ie: if there is only one slice (because "lower" is not "None") or if this filename is within the range of the slice that this qrunner is managing, then add it to the list. The problem is that the first slice of any multi-slice qrunner has a lower bound of "0". This means that slice "0" of any multi-slice qrunner will act on *all* files in a given queue, which in turn results in race conditions wherein slice 0 and slice n will begin to process a message, one will complete processing and remove the file, and the other will crash. Patch: *** Switchboard.py Fri Aug 13 16:43:12 2004 --- Switchboard.py_new Fri Aug 13 16:43:48 2004 *************** *** 164,170 **** when, digest = filebase.split('+') # Throw out any files which don't match our bitrange. BAW: test # performance and end-cases of this algorithm. ! if not lower or (lower <= long(digest, 16) < upper): times[float(when)] = filebase # FIFO sort keys = times.keys() --- 164,170 ---- when, digest = filebase.split('+') # Throw out any files which don't match our bitrange. BAW: test # performance and end-cases of this algorithm. ! if (lower == upper) or (lower <= long(digest, 16) < upper): times[float(when)] = filebase # FIFO sort keys = times.keys() Brian Greenberg -- grnbrg@cc.umanitoba.ca ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1008983&group_id=103 From noreply at sourceforge.net Fri Aug 13 23:47:21 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 13 23:47:27 2004 Subject: [ mailman-Patches-1008983 ] qrunner w/ multiple slices crashing. Message-ID: Patches item #1008983, was opened at 2004-08-13 16:45 Message generated for change (Settings changed) made by grnbrg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1008983&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None >Priority: 7 Submitted By: Brian Greenberg (grnbrg) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner w/ multiple slices crashing. Initial Comment: When running qrunner with multiple instances of a particular class (ie: qrunner -r OutgoingRunner:0:4 -r OutgoingRunner:1:4 -r OutgoingRunner:2:4 -r OutgoingRunner:3:4 ) the qrunner processes for this class will periodically crash, leaving the following traces: logs/qrunner: Aug 13 15:27:51 2004 (29188) Master qrunner detected subprocess exit (pid: 23829, sig: None, sts: 1, class: OutgoingRunner, slice: 1/4) [restarting] logs/error: Aug 13 15:27:51 2004 qrunner(23829): Traceback (most recent call last): Aug 13 15:27:51 2004 qrunner(23829): File "/usr/local/mailman/bin/qrunner", line 270, in ? Aug 13 15:27:51 2004 qrunner(23829): main() Aug 13 15:27:51 2004 qrunner(23829): File "/usr/local/mailman/bin/qrunner", line 230, in main Aug 13 15:27:51 2004 qrunner(23829): qrunner.run() Aug 13 15:27:51 2004 qrunner(23829): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 70, in run Aug 13 15:27:51 2004 qrunner(23829): filecnt = self._oneloop() Aug 13 15:27:51 2004 qrunner(23829): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop Aug 13 15:27:51 2004 qrunner(23829): msg, msgdata = self._switchboard.dequeue(filebase) Aug 13 15:27:51 2004 qrunner(23829): File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 143, in dequeue Aug 13 15:27:51 2004 qrunner(23829): fp = open(filename) Aug 13 15:27:51 2004 qrunner(23829): IOError : [Errno 2] No such file or directory: '/var/priv/mail/mailman/qfiles/out/1092428866.8410051+70dcb0bb96e6460d8cd2a a8103cce318cfa3ed1f.pck' This is caused by a logic error in mailman/Mailman/Queues/Switchboard.py:files. Specifically, when there are not multiple slices running for a particular qrunner class, self.__upper and self.__lower are both set to None in Switchboard.py:__init__. Switchboard.py:files contains the statement: if not lower or (lower <= long(digest, 16) < upper): times[float](when)] = filebase ie: if there is only one slice (because "lower" is not "None") or if this filename is within the range of the slice that this qrunner is managing, then add it to the list. The problem is that the first slice of any multi-slice qrunner has a lower bound of "0". This means that slice "0" of any multi-slice qrunner will act on *all* files in a given queue, which in turn results in race conditions wherein slice 0 and slice n will begin to process a message, one will complete processing and remove the file, and the other will crash. Patch: *** Switchboard.py Fri Aug 13 16:43:12 2004 --- Switchboard.py_new Fri Aug 13 16:43:48 2004 *************** *** 164,170 **** when, digest = filebase.split('+') # Throw out any files which don't match our bitrange. BAW: test # performance and end-cases of this algorithm. ! if not lower or (lower <= long(digest, 16) < upper): times[float(when)] = filebase # FIFO sort keys = times.keys() --- 164,170 ---- when, digest = filebase.split('+') # Throw out any files which don't match our bitrange. BAW: test # performance and end-cases of this algorithm. ! if (lower == upper) or (lower <= long(digest, 16) < upper): times[float(when)] = filebase # FIFO sort keys = times.keys() Brian Greenberg -- grnbrg@cc.umanitoba.ca ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1008983&group_id=103 From noreply at sourceforge.net Fri Aug 20 16:27:29 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 20 16:27:32 2004 Subject: [ mailman-Bugs-1012925 ] cc rejects to admins Message-ID: Bugs item #1012925, was opened at 2004-08-20 07:27 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=1012925&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Aahz (aahz) Assigned to: Nobody/Anonymous (nobody) Summary: cc rejects to admins Initial Comment: It'd be useful if you could optionally cc reject messages to the admin address of a list (so that multiple admins keep track of what's going on). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1012925&group_id=103 From noreply at sourceforge.net Fri Aug 20 16:55:33 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 20 16:55:52 2004 Subject: [ mailman-Bugs-974759 ] HTML email and attachment archiving inconsistencies Message-ID: Bugs item #974759, was opened at 2004-06-17 15:16 Message generated for change (Comment added) made by fergusdonohue You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=974759&group_id=103 Category: Pipermail 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: Fergus Donohue (fergusdonohue) Date: 2004-08-20 15: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 Fri Aug 20 21:23:08 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 20 21:23:11 2004 Subject: [ mailman-Bugs-1013079 ] spam filters get removed when changing other privacy pages Message-ID: Bugs item #1013079, was opened at 2004-08-20 15:23 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1013079&group_id=103 Category: security/privacy Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Ralph Siemsen (ralphs) Assigned to: Nobody/Anonymous (nobody) Summary: spam filters get removed when changing other privacy pages Initial Comment: Error report on behalf of Russell King (rmk+bugzilla@arm.linux.org.uk): Description of problem: If you enter some header_filter_rules in the mailman admin pages (Privacy->Spam filters) and click "submit" they are added to the list configuration database. However, if you now go to one of the other Privacy pages and click "submit" and return to the Spam Filters page, you'll find that your header_filter_rules settings have been removed. This appears to be caused by the handleForm function in ~mailman/Mailman/Gui/Privacy.py not checking to see which subsection is being submitted before processing the data for and setting the mlist.header_filter_rules list configuration variable. Version-Release number of selected component (if applicable): mailman-2.1.5-7 How reproducible: Always Steps to Reproduce: 1. Create list. 2. Go to the Privacy->Spam filters page, add some header_filter_rules and hit submit. 3. Go to the Privacy->Sender filters page but don't hit submit 4. Go back to Spam filters and note that they're still present 5. Return to Sender filters and hit submit 6. Go back to Spam filters and note that they've been removed. Actual Results: All spam filters are removed. Expected Results: Spam filter settings should be retained. Also reported to redhat bugzilla: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=130479 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1013079&group_id=103 From noreply at sourceforge.net Fri Aug 20 23:55:05 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Aug 20 23:55:09 2004 Subject: [ mailman-Bugs-902646 ] UnicodeEncodeError submitting admin request Message-ID: Bugs item #902646, was opened at 2004-02-23 07:41 Message generated for change (Comment added) made by evarlast You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=902646&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Maurice Snellen (kiap) Assigned to: Nobody/Anonymous (nobody) Summary: UnicodeEncodeError submitting admin request Initial Comment: When submitting an admin request to have a number of addresses set to 'Ignore' processing the list of mails received from addresses not subscribed to the list, the following error is received by the list moderator. I have confirmed that the same error occurs with the site admin password. 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/nlbdsmorg/scripts/driver", line 87, in run_main main() File "/var/mailman/nlbdsmorg/Mailman/Cgi/admindb.py", line 163, in main process_form(mlist, doc, cgidata) File "/var/mailman/nlbdsmorg/Mailman/Cgi/admindb.py", line 694, in process_form forward, forwardaddr) File "/var/mailman/nlbdsmorg/Mailman/ListAdmin.py", line 184, in HandleRequest forward, addr) File "/var/mailman/nlbdsmorg/Mailman/ListAdmin.py", line 373, in __handlepost syslog('vette', note) File "/var/mailman/nlbdsmorg/Mailman/Logging/Syslog. py", line 40, in write self.write_ex(kind, msg, args, kws) File "/var/mailman/nlbdsmorg/Mailman/Logging/Syslog. py", line 58, in write_ex logf.write(msg + '\n') File "/var/mailman/nlbdsmorg/Mailman/Logging/StampedLogger. py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/var/mailman/nlbdsmorg/Mailman/Logging/Logger. py", line 91, in write f.write(msg) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 116: ordinal not in range(128) ------------------------------------------------------- --------------------- ---- Python information: Variable Value sys.version 2.3.3 (#1, Jan 23 2004, 17:15:25) [GCC 2.95. 3 20010315 (release)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------- --------------------- ---- Environment variables: Variable Value HTTP________________ ~~~~~ ~~~~~~~ HTTP_COOKIE bvj-operators+admin=2802000000690d3539407328000000 35313635333439656563666564 306432636330623136376634653138666139366537323037 626334 SERVER_SOFTWARE Apache/1.3.27 (Unix) PHP/4.3.2 mod_ssl/2.8.14 OpenSSL/0.9.7b SCRIPT_NAME /mailman/admindb SERVER_SIGNATURE Apache/1.3.27 Server at nl-bdsm. org Port 80 REQUEST_METHOD POST PATH_INFO /bvj-operators SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 891 HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322) HTTP_CONNECTION Keep-Alive SERVER_NAME nl-bdsm.org REMOTE_ADDR 80.126.99.148 PATH_TRANSLATED /var/www/prod/nl-bdsm. org/bvj-operators SERVER_PORT 80 SERVER_ADDR 212.238.194.176 DOCUMENT_ROOT /var/www/prod/nl-bdsm.org PYTHONPATH /var/mailman/nlbdsmorg SCRIPT_FILENAME /var/mailman/nlbdsmorg/cgi-bin/admindb SERVER_ADMIN webmaster@nl-bdsm.org HTTP_HOST nl-bdsm.org HTTP_CACHE_CONTROL no-cache REQUEST_URI /mailman/admindb/bvj-operators HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/x-shockwave-flash, */* HTTP________ ~~~~: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~ GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 1245 HTTP_ACCEPT_LANGUAGE nl CONTENT_TYPE application/x-www-form-urlencoded ---------------------------------------------------------------------- Comment By: Jay R. Wren (evarlast) Date: 2004-08-20 17:55 Message: Logged In: YES user_id=11353 looks like the email message has some unicode characters and the handlers aren't working properly. I implemented this work around in /usr/lib/mailman/Mailman/Logging (or equiv) to just disable the unicode message conversion. In all honesty, I couldn't find where this log was being written anyway, but admittedly, I only spend 5 min or so with it. --- Logger.py~ 2004-08-20 17:23:46.597760277 -0400 +++ Logger.py 2004-08-20 17:23:50.501714186 -0400 @@ -84,8 +84,8 @@ f.flush() def write(self, msg): - if isinstance(msg, StringType): - msg = unicode(msg, self.__encoding) + #if isinstance(msg, StringType): + # msg = unicode(msg, self.__encoding) f = self.__get_f() try: f.write(msg) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=902646&group_id=103 From noreply at sourceforge.net Mon Aug 23 23:39:32 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Aug 23 23:39:35 2004 Subject: [ mailman-Bugs-1014750 ] need to sort by domain before submitting to MTA Message-ID: Bugs item #1014750, was opened at 2004-08-23 17:39 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=1014750&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: need to sort by domain before submitting to MTA Initial Comment: I have a number of (large) lists that have a number of users at the same domain, but are submitted to the MTA in chunks of 10 to insure the list performs reasonably. The users at the same domain end up in different queue files of my MTA, and spark a large number of SMTP connections to their SMTP servers that could be minimized if the @ that is passed to the MTA is sorted by domain. Then I could have one SMTP transaction with them that delivers 10 messages. I'm no python expert, but figure sorting of this type should be fairly simple, and will reduce the amount my SMTP server abuses these other SMTP servers, which will be a good thing(tm), as well as save bandwidth.. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1014750&group_id=103 From noreply at sourceforge.net Tue Aug 24 09:58:20 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 24 09:59:00 2004 Subject: [ mailman-Patches-891491 ] Scrubber.py patch Message-ID: Patches item #891491, was opened at 2004-02-06 01:26 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=891491&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 8 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber.py patch Initial Comment: Scrubber.py has number of bugs for processing various types of attachment and languages and many have submitted patches to fix them. This patch item is opened to collect such patches for convenience. This patch corrects: - if an attached text is composed by win notepad, it has no charset specified and actual charset may be different from message/list charset. This sometimes cause error in composing digest message. - sometimes, null charset is represented by '' as well as None. - embedded rfc-2822 message is lost if you don't use msg.walk() - special problem with japanese charsets. - t (stringfied part) may be None which you can't append a '\n'. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-08-24 07:58 Message: Logged In: YES user_id=67709 added a fix for the case of lcset_out <> lcset. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-04-14 18:53 Message: Logged In: YES user_id=113859 Thanks for working on the patch. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-02-25 10:42 Message: Logged In: YES user_id=67709 uploading revised patch. Now fixes a few more bugs which try to decode scrub plain text message and result in mojibake. Also, japanese filename tend to become so long that system limit may exceeded because of mime encoding, so add an option not to use the filename in the message but to use 'attachment' as filename. Because this patch spans two files (Defaults.py.in and Handlers/Scrubber.py) you have to cd mailman and patch -p1 < this_patch. (Well, I think it is -p1. If it didn't work, try -p0 ;-) ---------------------------------------------------------------------- Comment By: Jonathan Larmour (jifl) Date: 2004-02-22 17:25 Message: Logged In: YES user_id=817601 I strongly recommend applying this patch. I received a mail bounce on a list with an empty charset in a part (i.e. "charset=") and it caused /var/mailman/cron/senddigest and thus all digest processing to fail because of this error: Traceback (most recent call last): File "/var/mailman/cron/senddigests", line 94, in ? main() File "/var/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/var/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') which is something this patch fixes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=891491&group_id=103 From noreply at sourceforge.net Tue Aug 24 11:01:29 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 24 11:01:33 2004 Subject: [ mailman-Bugs-1015096 ] UnicodeEncodeError rejecting smap through web admin Message-ID: Bugs item #1015096, was opened at 2004-08-24 12:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1015096&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Niclas Ek (nikke_ek) Assigned to: Nobody/Anonymous (nobody) Summary: UnicodeEncodeError rejecting smap through web admin Initial Comment: While trying to discard spam from a list: https://server/admin/list -> Tend to pending moderator requests -> Discard an error message will appear: 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 "/home/mailman/scripts/driver", line 87, in run_main main() File "/home/mailman/Mailman/Cgi/admindb.py", line 163, in main process_form(mlist, doc, cgidata) File "/home/mailman/Mailman/Cgi/admindb.py", line 711, in process_form forward, forwardaddr) File "/home/mailman/Mailman/ListAdmin.py", line 159, in HandleRequest forward, addr) File "/home/mailman/Mailman/ListAdmin.py", line 345, in __handlepost syslog('vette', note) File "/home/mailman/Mailman/Logging/Syslog.py", line 40, in write self.write_ex(kind, msg, args, kws) File "/home/mailman/Mailman/Logging/Syslog.py", line 58, in write_ex logf.write(msg + '\n') File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 91, in write f.write(msg) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 122: ordinal not in range(128) Python information: Variable Value sys.version 2.3.4 (#2, Jul 5 2004, 09:15:05) [GCC 3.3.4 (Debian 1:3.3.4-2)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1015096&group_id=103 From noreply at sourceforge.net Wed Aug 25 03:11:12 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 25 03:11:18 2004 Subject: [ mailman-Bugs-1015709 ] change subs. address while logged in - error on logout Message-ID: Bugs item #1015709, was opened at 2004-08-24 20:11 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1015709&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matt Crawford (crawdad) Assigned to: Nobody/Anonymous (nobody) Summary: change subs. address while logged in - error on logout Initial Comment: A user used the web interface to change his email address for all lists, and replied to the confirmation email. Then he logged out of the web interface, eliciting this error 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 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/var/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/var/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/var/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/var/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: HIS@OLD.EMAIL.ADDRESS.HERE ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1015709&group_id=103 From noreply at sourceforge.net Wed Aug 25 11:20:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 25 11:20:12 2004 Subject: [ mailman-Bugs-1015867 ] HTML archive generation failed if language set to Finnish Message-ID: Bugs item #1015867, was opened at 2004-08-25 12:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1015867&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ville Savolainen (villes) Assigned to: Nobody/Anonymous (nobody) Summary: HTML archive generation failed if language set to Finnish Initial Comment: In version 2.1.5 of Mailman I discovered following behaviour while creating HTML-archive with bin/arch. If list language is set to Finnish web archive creating failed and index.html size is 0. But after I change language to English (or any other language), everything works fine. I tried same thing with other lists and different emails and found same behaviour. (Language English) /l/mailman/data/logs # ../../bin/arch just-somelist #00000 <20040823142555.GJ20173@vipunen.hut.fi> figuring article archives 2004 Updating index files for archive [2004] Date Subject Author Thread Computing threaded index Updating HTML for article 1 Pickling archive state into /l/mailman/data/archives/private/just-somelist/pipermail.pck (Language Finnish) /l/mailman/data/logs # ../../bin/arch just-somelist #00000 <20040823142555.GJ20173@vipunen.hut.fi> tutkitaan artikkeliarkistoa 2004 P?ivitet??n indeksi-tiedostot arkistolle [2004] Date Subject Author Ketju Luodaan viestipuuta P?ivitet??n HTML-sivut artikkelille 1 Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/l/mailman/latest/Mailman/Archiver/pipermail.py", line 313, in close self.write_TOC() File "/l/mailman/latest/Mailman/Archiver/HyperArch.py", line 1051, in write_TOC toc.write(self.html_TOC()) File "/l/mailman/latest/Mailman/Archiver/HyperArch.py", line 740, in html_TOC accum.append(self.html_TOC_entry(a)) File "/l/mailman/latest/Mailman/Archiver/HyperArch.py", line 766, in html_TOC_entry templ = '[ ' + _('Text%(sz)s') + ']' File "/l/mailman/latest/Mailman/i18n.py", line 89, in _ return tns % dict ValueError: unsupported format character '?' (0xffffffe4) at index 11 zsh: 24651 exit 1 ../../bin/arch just-somelist ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1015867&group_id=103 From noreply at sourceforge.net Wed Aug 25 17:39:29 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Aug 25 17:39:41 2004 Subject: [ mailman-Patches-871062 ] A MemberAdaptor for LDAP-based membership Message-ID: Patches item #871062, was opened at 2004-01-05 17:09 Message generated for change (Comment added) made by mawhin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K. A. Krueger (fubarobfusco) Assigned to: Nobody/Anonymous (nobody) Summary: A MemberAdaptor for LDAP-based membership Initial Comment: This is a module, LDAPMemberships, which extends MemberAdaptor to support membership lists based on a search in an enterprise LDAP directory. With this module, you can make mailing lists which, rather than having a list of member addresses stored in the list, query your LDAP server for member addresses whenever necessary. For instance, if you wish to have a mailing list of all the Vice Presidents in your company, you can express this as an LDAP search: "(title=Vice President*)" and create a mailing list which performs this search and delivers mail to the resulting user accounts when a message is sent to it. This way, rather than manually adding new Vice Presidents to the mailing list, you can simply have Human Resources update the LDAP records, and the change will immediately take effect for the mailing list. Mailman lists with LDAP-based membership can still have moderators, list policies, and the other usual features of Mailman lists. There are a few missing features; notably: 1. There is no bounce processing. 2. There are no per-user preferences. 3. The Web interface still allows you to try setting user preferences, but if you do you will get a stack thrown at you. (Only the "readable" interface of MemberAdaptor is implemented.) 4. The LDAP settings of a list (e.g. LDAP server and search string) are only administrable by editing its "extend.py" file, not over the Web. 5. There is no digest mode. To use this module, you must have the "ldap" Python module installed (aka "python-ldap"). Then just put LDAPMemberships.py in the "Mailman" directory (~mailman/Mailman), create a new list, and write an "extend.py" file in the list directory like so: ##### from Mailman.LDAPMemberships import LDAPMemberships def extend(list): ldap = LDAPMemberships(list) ldap.ldapsearch = "(title=Vice President*)" # members search string ldap.ldapserver = "ldap.example.net" # your enterprise LDAP server ldap.ldapbasedn = "dc=Example dc=net" # your LDAP base DN ldap.ldapbinddn = '' # a bind DN which can read people's 'mail' field ldap.ldappasswd = '' # the password for the bind DN list._memberadaptor = ldap ##### This module has been tested at my site and is in production on a Mailman 2.1.2 installation. ---------------------------------------------------------------------- Comment By: martin whinnery (mawhin) Date: 2004-08-25 15:39 Message: Logged In: YES user_id=90418 I've hacked your work about to get it to handle lists based on group membership instead. You may find it worthwhile. http://webserver.offal.homelinux.org/LDAPMemberAdaptor/V3.0/LDAPMemberAdaptor/ This version's nasty, but you'll get the idea. Wanna roll it into yours? Mart ---------------------------------------------------------------------- Comment By: Aleksander Adamowski (the_olo) Date: 2004-04-05 13:47 Message: Logged In: YES user_id=244001 I suggest this patch to allow senders use any source address they might have set in LDAP (the 'mail' attribute can have multiple values!) --- LDAPMemberships.py.orig 2004-04-01 12:31:54.000000000 +0200 +++ LDAPMemberships.py 2004-04-05 15:40:03.000000000 +0200 @@ -115,7 +115,9 @@ # mail is unique mail = attrs['mail'][0].strip() self.__members.append(mail) - self.__member_map[mail] = mail + # mail can have multiple values + for secondarymail in attrs['mail']: + self.__member_map[secondarymail.strip()] = mail if attrs.has_key('mailalternateaddress'): malts = attrs['mailalternateaddress'] for malt in malts: ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-03-31 03:59 Message: Logged In: YES user_id=944208 Well, Mailman does a lot more than just keep track of who's subscribed -- for instance, restricted posters, list moderation, archiving. LDAPMemberships is not meant to be useful for Internet mailing lists with people signing up for them, but rather for institutional or enterprise lists. These have a lot of the same requirements (moderation etc.) as Internet lists, but don't need subscription/unsubscription -- since employees are usually required to be on them. My workplace is using this (well, actually a later version than the one I've uploaded here) as a replacement for an LDAP mailing-list feature in Netscape SuiteSpot now that we have migrated away from that system. We -also- use LDAP-based aliases (in Postfix, not Sendmail, actually) -- but for some things we need the moderation and other facilities that Mailman has. For instance, we have an announcements list that goes to all regular employees. A simple alias would allow anyone to send stuff to it, and certain senior scientists would love to send big PDFs to everyone. A Mailman list with LDAPMemberships can have sender restrictions so that only our IT Director and our mail systems admin can approve posts to it. Archiving is also quite useful for announcements lists. ---------------------------------------------------------------------- Comment By: Chris Drumgoole (cdrum) Date: 2004-03-31 03:38 Message: Logged In: YES user_id=429400 why use this when you can just use Sendmail's LDAP -> Alias functions? No need for a mailing list program like mailman.. right? ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-26 20:35 Message: Logged In: YES user_id=944208 Yet another new version (0.3) of LDAPMemberships.py. This one fixes some ambiguities with LDAP record handling, particularly for users with multiple "cn" values, and those who send mail as their "mailalternateaddress" field address rather than their "mail" field. If anyone is actually using this, please email me and let me know :) ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-20 16:53 Message: Logged In: YES user_id=944208 I've uploaded a new version (0.2) of LDAPMemberships.py. This one is some ungodly number of times faster, as it does not do redundant LDAP queries in a single load. ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-05 17:18 Message: Logged In: YES user_id=944208 Er. SF ate the indentation on my "extend.py" example in the patch description. All of the lines after "def extend(list):" are meant to be indented once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 From noreply at sourceforge.net Tue Aug 31 12:16:50 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 31 12:16:53 2004 Subject: [ mailman-Bugs-1019550 ] Bug in base64MIME.py Message-ID: Bugs item #1019550, was opened at 2004-08-31 12: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=1019550&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Manuel Pedreira (kour) Assigned to: Nobody/Anonymous (nobody) Summary: Bug in base64MIME.py 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 "/usr/local/mailman/scripts/driver", line 80, in run_main pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) File "/usr/local/mailman/Mailman/Cgi/listinfo.py", line 26, in ? from Mailman import Utils File "/usr/local/mailman/Mailman/Utils.py", line 37, in ? import email.Header File "/usr/local/mailman/pythonlib/email/Header.py", line 11, in ? import email.base64MIME File "/usr/local/mailman/pythonlib/email/base64MIME.py", line 31, in ? from email._compat22 import _floordiv ImportError: cannot import name _floordiv ------------------------------------------------------- ------------------------- Python information: Variable Value sys.version 2.1.3 (#1, Sep 7 2002, 15:29:56) [GCC 2.95.4 20011002 (Debian prerelease)] sys.executable /usr/bin/python2.1 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------- ------------------------- Environment variables: Variable Value DOCUMENT_ROOT /wwroot/listas.gulo.org/ SERVER_ADDR 193.147.87.51 SERVER_PORT 80 REMOTE_ADDR **.**.**.** SERVER_SOFTWARE Apache/2.0.48 (Unix) PHP/4.3.3 mod_ssl/2.0.48 OpenSSL/0.9.6c HTTP_VIA 1.0 VENUS1 HTTP_ACCEPT_LANGUAGE es GATEWAY_INTERFACE CGI/1.1 SERVER_NAME listas.gulo.org HTTP_CONNECTION Keep-Alive HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; MyIE2; .NET CLR 1.1.4322) HTTP_ACCEPT */* REQUEST_URI /mailman/listinfo QUERY_STRING SERVER_PROTOCOL HTTP/1.0 HTTP_HOST listas.gulo.org REQUEST_METHOD GET SERVER_SIGNATURE HTTP_IF_MODIFIED_SINCE Tue, 31 Aug 2004 09:41:13 GMT SCRIPT_NAME /mailman/listinfo SERVER_ADMIN admin(at)gulo.org SCRIPT_FILENAME /usr/local/mailman/cgi-bin/listinfo PYTHONPATH /usr/local/mailman HTTP_COOKIE PHPSESSID=0fb5eb2692415f078d387a9225b8086e REMOTE_PORT 36105 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1019550&group_id=103 From noreply at sourceforge.net Tue Aug 31 23:10:29 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Aug 31 23:10:49 2004 Subject: [ mailman-Bugs-1020013 ] spam filters get removed when changing other privacy pages Message-ID: Bugs item #1020013, was opened at 2004-08-31 16:10 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=1020013&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: John Dennis (johndennis) Assigned to: Nobody/Anonymous (nobody) Summary: spam filters get removed when changing other privacy pages Initial Comment: This was filed in the Red Hat bugzilla as: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=130479 Promoting to upstream Summary is: If you enter some header_filter_rules in the mailman admin pages (Privacy->Spam filters) and click "submit" they are added to the list configuration database. However, if you now go to one of the other Privacy pages and click "submit" and return to the Spam Filters page, you'll find that your header_filter_rules settings have been removed. This appears to be caused by the handleForm function in ~mailman/Mailman/Gui/Privacy.py not checking to see which subsection is being submitted before processing the data for and setting the mlist.header_filter_rules list configuration variable. Version-Release number of selected component (if applicable): mailman-2.1.5 How reproducible: Always Steps to Reproduce: 1. Create list. 2. Go to the Privacy->Spam filters page, add some header_filter_rules and hit submit. 3. Go to the Privacy->Sender filters page but don't hit submit 4. Go back to Spam filters and note that they're still present 5. Return to Sender filters and hit submit 6. Go back to Spam filters and note that they've been removed. Actual Results: All spam filters are removed. Expected Results: Spam filter settings should be retained. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1020013&group_id=103