From noreply at sourceforge.net Sun Jun 1 02:37:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 1 04:37:49 2003 Subject: [ mailman-Bugs-746924 ] Uncaught bounce notification Message-ID: Bugs item #746924, was opened at 2003-06-01 10:37 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746924&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Manuel Estrada Sainz (ranty) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught bounce notification Initial Comment: Just that, mailman's documentation suggested sending this to the developers, and this looked like the right way (attached). Thanks for a great tool ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746924&group_id=103 From noreply at sourceforge.net Sun Jun 1 06:25:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 1 08:27:20 2003 Subject: [ mailman-Bugs-746995 ] Error creating mailing list with http://URL/mailman/create Message-ID: Bugs item #746995, was opened at 2003-06-01 12:25 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robin Cook (cuzndragon) Assigned to: Nobody/Anonymous (nobody) Summary: Error creating mailing list with http://URL/mailman/create Initial Comment: I have just install mailman and everything seems to be working until I try to create a mailing list using the web interface. When I click on the create list button I get this error below. I couldn't find in in the FAQ and the archives listed was a bad link. What is set wrong? But if I log in as mailman and run the command line utilities to create the mailing list there aren't any problems. 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/create.py", line 55, in main process_request(doc, cgidata) File "/usr/share/mailman/Mailman/Cgi/create.py", line 217, in process_request sys.modules[modname].create(mlist, cgi=1) File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 232, in create _update_maps() File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /var/spool/mailman/data/aliases (status: 1, Operation not permitted) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 From noreply at sourceforge.net Sun Jun 1 06:28:12 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 1 08:29:45 2003 Subject: [ mailman-Feature Requests-746996 ] e-mail and user name control Message-ID: Feature Requests item #746996, was opened at 2003-06-01 12:28 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=746996&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robin Cook (cuzndragon) Assigned to: Nobody/Anonymous (nobody) Summary: e-mail and user name control Initial Comment: The ability to allow and disallow the changing of the e-mail and name that a subscriber is using. Also notifiction to the list admin /moderators when they are changed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=746996&group_id=103 From noreply at sourceforge.net Sun Jun 1 19:56:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 1 21:56:16 2003 Subject: [ mailman-Bugs-728836 ] invalid HTML in page templates Message-ID: Bugs item #728836, was opened at 2003-04-28 07:01 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=728836&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: invalid HTML in page templates Initial Comment: Some page templates in the 2.1.2 release are defective, i.e. the HTML is invalid A patch file to correct these errors is attached. It corrects problems with languages pl and pt which were newly added with MM 2.1.2: admindetails.html - removed extraneous P tags from inside UL The same errors in other language templates were corrected when patch 716755/661138 was merged into the MM 2.1.2 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=728836&group_id=103 From noreply at sourceforge.net Mon Jun 2 05:22:40 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 2 07:22:44 2003 Subject: [ mailman-Patches-747470 ] crash due to unrecognized mime type Message-ID: Patches item #747470, was opened at 2003-06-02 13:22 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=747470&group_id=103 Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Sjoerd Mullender (sjoerd) Assigned to: Nobody/Anonymous (nobody) Summary: crash due to unrecognized mime type Initial Comment: Cron sent me a message with this stack trace. The problem is due to the fact that I'm using Python 2.3b1 with its version of guess_all_extensions which can return None. The replacement version in Scrubber.py never returns None. A simple patch is attached. 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 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 349, in save_attachment ext = guess_extension(ctype, fnext) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 80, in guess_extension if ext in all: TypeError: iterable argument required ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=747470&group_id=103 From noreply at sourceforge.net Mon Jun 2 17:55:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 2 19:55:11 2003 Subject: [ mailman-Bugs-747830 ] Host name changes not followed Message-ID: Bugs item #747830, was opened at 2003-06-02 23:55 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=747830&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Chris Dudley (dudleyc) Assigned to: Nobody/Anonymous (nobody) Summary: Host name changes not followed Initial Comment: I have a server called foo.x.com but have all the lists running on it running of a CNAME called lists.x.com. The value for both DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in Defaults.py is foo.x.com, however both variables are set to lists.x.com in mm_cfg.py. All lists were originally created with the value in mm_cfg.py set to foo.x.com and so they all have foo.x.com as their preferred hostname and show up in the http://foo.x.com/mailman/listinfo page. However I want them to be listed on http://lists.x.com/mailman/listinfo. If I try to change the hostname each list prefers then it seems to take effect but sometimes on clicking submit I get redirected to the exact same admin page but on foo.x.com not lists.x.com. All the links in the admin interface point to foo.x.com except the link to the lists archives which points to lists.x.com. I really dont want to have to delete lists and recreate them just top get them to show up on the correct domain name as they already have hundreds of subscribers to each list. Have I configured something wrong? (a quick grep of the files in the /var/mailman/lists directory shows that each list info file contains the words foo.x.com AND lists.foo.com) Im using mailman 2.1.2 compiled from source running on RedHat 8.0. Thanks ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=747830&group_id=103 From noreply at sourceforge.net Tue Jun 3 06:05:59 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jun 3 08:10:25 2003 Subject: [ mailman-Bugs-747830 ] Host name changes not followed Message-ID: Bugs item #747830, was opened at 2003-06-02 23:55 Message generated for change (Comment added) made by dudleyc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=747830&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Chris Dudley (dudleyc) Assigned to: Nobody/Anonymous (nobody) Summary: Host name changes not followed Initial Comment: I have a server called foo.x.com but have all the lists running on it running of a CNAME called lists.x.com. The value for both DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in Defaults.py is foo.x.com, however both variables are set to lists.x.com in mm_cfg.py. All lists were originally created with the value in mm_cfg.py set to foo.x.com and so they all have foo.x.com as their preferred hostname and show up in the http://foo.x.com/mailman/listinfo page. However I want them to be listed on http://lists.x.com/mailman/listinfo. If I try to change the hostname each list prefers then it seems to take effect but sometimes on clicking submit I get redirected to the exact same admin page but on foo.x.com not lists.x.com. All the links in the admin interface point to foo.x.com except the link to the lists archives which points to lists.x.com. I really dont want to have to delete lists and recreate them just top get them to show up on the correct domain name as they already have hundreds of subscribers to each list. Have I configured something wrong? (a quick grep of the files in the /var/mailman/lists directory shows that each list info file contains the words foo.x.com AND lists.foo.com) Im using mailman 2.1.2 compiled from source running on RedHat 8.0. Thanks ---------------------------------------------------------------------- >Comment By: Chris Dudley (dudleyc) Date: 2003-06-03 12:05 Message: Logged In: YES user_id=504751 By setting: DEFAULT_URL = 'http://lists.x.com/mailman' and recreating all the lists the problem seems to have been fixed. So I can only conclude that this was either due to something stupid I did during the install or during the setup stage - doesnt appear to be a code problem anyway so this bug can be closed (sorry ;-). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=747830&group_id=103 From noreply at sourceforge.net Tue Jun 3 12:46:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jun 3 14:47:05 2003 Subject: [ mailman-Feature Requests-748370 ] Would like alternate actions for anti-spam filters Message-ID: Feature Requests item #748370, was opened at 2003-06-03 11:46 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=748370&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: John DuBois (jhdiii) Assigned to: Nobody/Anonymous (nobody) Summary: Would like alternate actions for anti-spam filters Initial Comment: Currently, the only option for spam processing is to hold it for approval. Would like the options of reject & discard. It would also be nice if the spam filter could be configured to take place before sender filtering, so that a members-only list could be configured to hold posts by non-members, but only in the case of messages that get past the spam filtering. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=748370&group_id=103 From noreply at sourceforge.net Tue Jun 3 17:58:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jun 3 19:58:40 2003 Subject: [ mailman-Feature Requests-748543 ] wider discard on pending requests Message-ID: Feature Requests item #748543, was opened at 2003-06-03 23:58 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=748543&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: wider discard on pending requests Initial Comment: Like many people, I maintain a number of mailman lists at my site. They all moderate non-member posts, to avoid distributing spam and virus mail. As you know, a given spam/virus mail is sent to many mailing lists at once. Right now it's necessary to discard them all separately. It would be nice if on the pending requests page for a given list, there was an option `discard from all pending lists'. That is, if the same Message-Id or same envelope/Subject was waiting on more than one list, be able to dump them all at once. For authentication perhaps allow explicitly logging in as the mailman site admin, or somehow go through the authentication page on the other lists. Probably not easy to implement, but it sure would make dealing with spam a lot less painful. Thanks, karl@freefriends.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=748543&group_id=103 From noreply at sourceforge.net Tue Jun 3 18:02:47 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jun 3 20:02:50 2003 Subject: [ mailman-Feature Requests-748549 ] recognize bounces from old users Message-ID: Feature Requests item #748549, was opened at 2003-06-04 00:02 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=748549&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: recognize bounces from old users Initial Comment: It would be nice if mailman kept track of ex-users on a mailing list. Then when a bounce comes in for such a person, it could be discarded instead of being `unrecognized'. That is, when an address goes bad, there's typically a delay (of five days, for example) before an actual bounce is received. In the interim, only warning messages will be received. On an active mailing list, there could be a lot of messages in those fives, all of which will (eventually) bounce. After either mailman auto-unsubscribes the user, or the admin manually does it, all those queued bounces become `unrecognized', causing additional (not useful) mail to the admin. (I'm using mailman 2.1.2 under Linux.) Thanks, karl@freefriends.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=748549&group_id=103 From noreply at sourceforge.net Tue Jun 3 18:03:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jun 3 20:03:24 2003 Subject: [ mailman-Feature Requests-748543 ] wider discard on pending requests Message-ID: Feature Requests item #748543, was opened at 2003-06-03 23:58 Message generated for change (Comment added) made by kberry You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=748543&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: wider discard on pending requests Initial Comment: Like many people, I maintain a number of mailman lists at my site. They all moderate non-member posts, to avoid distributing spam and virus mail. As you know, a given spam/virus mail is sent to many mailing lists at once. Right now it's necessary to discard them all separately. It would be nice if on the pending requests page for a given list, there was an option `discard from all pending lists'. That is, if the same Message-Id or same envelope/Subject was waiting on more than one list, be able to dump them all at once. For authentication perhaps allow explicitly logging in as the mailman site admin, or somehow go through the authentication page on the other lists. Probably not easy to implement, but it sure would make dealing with spam a lot less painful. Thanks, karl@freefriends.org ---------------------------------------------------------------------- >Comment By: karl berry (kberry) Date: 2003-06-04 00:03 Message: Logged In: YES user_id=33248 (I'm using mailman 2.1.2 under Linux.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=748543&group_id=103 From noreply at sourceforge.net Wed Jun 4 14:24:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jun 4 16:24:16 2003 Subject: [ mailman-Feature Requests-749135 ] Maildir support Message-ID: Feature Requests item #749135, was opened at 2003-06-04 13:24 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=749135&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nadim Shaikli (shaikli) Assigned to: Nobody/Anonymous (nobody) Summary: Maildir support Initial Comment: It would readlly be nice if Mailman were able to produce Maildir type of formats along side its current mbox. Maybe augment the 'ARCHIVE_TO_MBOX' with a 'ARCHIVE_TO_MAILDIR_FORMAT' :-) Regards & Thanks ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=749135&group_id=103 From noreply at sourceforge.net Wed Jun 4 16:28:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jun 4 18:28:20 2003 Subject: [ mailman-Bugs-736559 ] Subject wrap with tab character Message-ID: Bugs item #736559, was opened at 2003-05-12 10:05 Message generated for change (Comment added) made by disser You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=736559&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Swen Haubold (swen_haubold) Assigned to: Nobody/Anonymous (nobody) Summary: Subject wrap with tab character Initial Comment: Mailman: 2.1.2 The subject line is wrapped by a tab character, if the line contains more than 78 characters. In this case a space is replaced by an tab character. This behaviour gives trouble with some e-mail client and is also not handled by MHonArc correctly. In an e-mail client a long space is shown or a special character. MHonArc simply removes the tab character therefore two words are combined, e.g. the tab is inserted between the two word "and" and "delivery"; in the archive the subject contains the new word "anddelivery" ---------------------------------------------------------------------- Comment By: Dave Disser (disser) Date: 2003-06-04 15:28 Message: Logged In: YES user_id=794167 I notice this also with Mailman 2.1.1. I don't see code in mailman doing it, so it appears to be in email.Header or unicode. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=736559&group_id=103 From noreply at sourceforge.net Thu Jun 5 08:23:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 5 10:23:24 2003 Subject: [ mailman-Bugs-749555 ] nimda.txt file - virus? Message-ID: Bugs item #749555, was opened at 2003-06-05 14: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=749555&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Martin Heelis (heelism) Assigned to: Nobody/Anonymous (nobody) Summary: nimda.txt file - virus? Initial Comment: Hi I just downloaded mainman-2.1.2.tgz and when extracting the files from the archive my virus scanner (McAfee VirusScan(v7)) reported that the file nimda.txt (mailman-2.1.2\tests\msgs\nimda.txt) contains a virus (Exploit-MIME.gen). Has anyone else had this problem? ttfn Martin Heelis ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=749555&group_id=103 From noreply at sourceforge.net Thu Jun 5 08:56:04 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 5 10:57:30 2003 Subject: [ mailman-Bugs-749555 ] nimda.txt file - virus? Message-ID: Bugs item #749555, was opened at 2003-06-05 10:23 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=749555&group_id=103 Category: configuring/installing Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Martin Heelis (heelism) Assigned to: Nobody/Anonymous (nobody) Summary: nimda.txt file - virus? Initial Comment: Hi I just downloaded mainman-2.1.2.tgz and when extracting the files from the archive my virus scanner (McAfee VirusScan(v7)) reported that the file nimda.txt (mailman-2.1.2\tests\msgs\nimda.txt) contains a virus (Exploit-MIME.gen). Has anyone else had this problem? ttfn Martin Heelis ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-05 10:56 Message: Logged In: YES user_id=12800 The test suite contains a neutered virus sample. It is completely harmless and it's unfortunate that your virus scanner is tripping on it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=749555&group_id=103 From noreply at sourceforge.net Fri Jun 6 11:45:04 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jun 6 13:45:28 2003 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 patch -p1 < ---------------------------------------------------------------------- >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 Fri Jun 6 11:47:12 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jun 6 13:47:32 2003 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 patch -p1 < ---------------------------------------------------------------------- >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 Sun Jun 8 17:12:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 8 19:12:27 2003 Subject: [ mailman-Bugs-751083 ] List-Id contains two spaces Message-ID: Bugs item #751083, was opened at 2003-06-09 01:12 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=751083&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Christian Garbs [Master Mitch] (mastermitch) Assigned to: Nobody/Anonymous (nobody) Summary: List-Id contains two spaces Initial Comment: I've recently upgraded to the current Debian mailman package 2.1.2-1. Now the List-Id header line generated by Mailman contains two spaces instead of one: now: List-Id: Mitchs Linux-Mailingliste before: List-Id: Mitchs Linux-Mailingliste This breaks existing filter scripts (procmail etc.) for my list's users. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=751083&group_id=103 From noreply at sourceforge.net Sun Jun 8 21:18:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 8 23:18:30 2003 Subject: [ mailman-Bugs-751083 ] List-Id contains two spaces Message-ID: Bugs item #751083, was opened at 2003-06-08 19:12 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=751083&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Christian Garbs [Master Mitch] (mastermitch) Assigned to: Nobody/Anonymous (nobody) Summary: List-Id contains two spaces Initial Comment: I've recently upgraded to the current Debian mailman package 2.1.2-1. Now the List-Id header line generated by Mailman contains two spaces instead of one: now: List-Id: Mitchs Linux-Mailingliste before: List-Id: Mitchs Linux-Mailingliste This breaks existing filter scripts (procmail etc.) for my list's users. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-08 23:18 Message: Logged In: YES user_id=12800 This is fixed in cvs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=751083&group_id=103 From noreply at sourceforge.net Mon Jun 9 10:01:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 9 12:25:37 2003 Subject: [ mailman-Bugs-747830 ] Host name changes not followed Message-ID: Bugs item #747830, was opened at 2003-06-02 19:55 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=747830&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Chris Dudley (dudleyc) Assigned to: Nobody/Anonymous (nobody) Summary: Host name changes not followed Initial Comment: I have a server called foo.x.com but have all the lists running on it running of a CNAME called lists.x.com. The value for both DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in Defaults.py is foo.x.com, however both variables are set to lists.x.com in mm_cfg.py. All lists were originally created with the value in mm_cfg.py set to foo.x.com and so they all have foo.x.com as their preferred hostname and show up in the http://foo.x.com/mailman/listinfo page. However I want them to be listed on http://lists.x.com/mailman/listinfo. If I try to change the hostname each list prefers then it seems to take effect but sometimes on clicking submit I get redirected to the exact same admin page but on foo.x.com not lists.x.com. All the links in the admin interface point to foo.x.com except the link to the lists archives which points to lists.x.com. I really dont want to have to delete lists and recreate them just top get them to show up on the correct domain name as they already have hundreds of subscribers to each list. Have I configured something wrong? (a quick grep of the files in the /var/mailman/lists directory shows that each list info file contains the words foo.x.com AND lists.foo.com) Im using mailman 2.1.2 compiled from source running on RedHat 8.0. Thanks ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-09 12:01 Message: Logged In: YES user_id=12800 Actually, you didn't do anything wrong. It's just that Defaults.py/mm_cfg.py only take effect when creating the list. After the list is created, you need to use bin/fix_url.py to change the urls. ---------------------------------------------------------------------- Comment By: Chris Dudley (dudleyc) Date: 2003-06-03 08:05 Message: Logged In: YES user_id=504751 By setting: DEFAULT_URL = 'http://lists.x.com/mailman' and recreating all the lists the problem seems to have been fixed. So I can only conclude that this was either due to something stupid I did during the install or during the setup stage - doesnt appear to be a code problem anyway so this bug can be closed (sorry ;-). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=747830&group_id=103 From noreply at sourceforge.net Mon Jun 9 14:40:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 9 16:40:20 2003 Subject: [ mailman-Patches-747470 ] crash due to unrecognized mime type Message-ID: Patches item #747470, was opened at 2003-06-02 07:22 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=747470&group_id=103 Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Sjoerd Mullender (sjoerd) Assigned to: Nobody/Anonymous (nobody) Summary: crash due to unrecognized mime type Initial Comment: Cron sent me a message with this stack trace. The problem is due to the fact that I'm using Python 2.3b1 with its version of guess_all_extensions which can return None. The replacement version in Scrubber.py never returns None. A simple patch is attached. 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 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 349, in save_attachment ext = guess_extension(ctype, fnext) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 80, in guess_extension if ext in all: TypeError: iterable argument required ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-09 16:40 Message: Logged In: YES user_id=12800 I wonder if the interface for guess_all_extensions() isn't broken in Python 2.3? I mean, why not just return an empty list if there are no extensions found? What advantage does returning None buy you? I'd opt for changing (read: fixing :) Python 2.3's guess_all_extensions(). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=747470&group_id=103 From noreply at sourceforge.net Mon Jun 9 15:05:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 9 17:06:04 2003 Subject: [ mailman-Patches-747470 ] crash due to unrecognized mime type Message-ID: Patches item #747470, was opened at 2003-06-02 07:22 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=747470&group_id=103 Category: None Group: Mailman 2.1 >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Sjoerd Mullender (sjoerd) Assigned to: Nobody/Anonymous (nobody) Summary: crash due to unrecognized mime type Initial Comment: Cron sent me a message with this stack trace. The problem is due to the fact that I'm using Python 2.3b1 with its version of guess_all_extensions which can return None. The replacement version in Scrubber.py never returns None. A simple patch is attached. 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 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 349, in save_attachment ext = guess_extension(ctype, fnext) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 80, in guess_extension if ext in all: TypeError: iterable argument required ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-09 17:05 Message: Logged In: YES user_id=12800 See my message on python-dev. I have BDFL agreement that the fix belongs in mimetypes. :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-09 16:40 Message: Logged In: YES user_id=12800 I wonder if the interface for guess_all_extensions() isn't broken in Python 2.3? I mean, why not just return an empty list if there are no extensions found? What advantage does returning None buy you? I'd opt for changing (read: fixing :) Python 2.3's guess_all_extensions(). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=747470&group_id=103 From noreply at sourceforge.net Thu Jun 12 04:06:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 12 06:06:21 2003 Subject: [ mailman-Bugs-753175 ] authorizing to private archives with sitepass fails Message-ID: Bugs item #753175, was opened at 2003-06-12 12:06 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=753175&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Zoran Dzelajlija (followme) Assigned to: Nobody/Anonymous (nobody) Summary: authorizing to private archives with sitepass fails Initial Comment: Mailman 2.1.2: When trying to view private archives using site admin password, I get Authorization Failed. Debugging shows that SecurityManager. Authenticate() raises NotAMemberError which breaks out of that function before all authcontexts are checked. Workaround is to check for valid user (!= None) when ac == mm_cfg. AuthUser. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=753175&group_id=103 From noreply at sourceforge.net Thu Jun 12 09:13:05 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 12 11:13:12 2003 Subject: [ mailman-Bugs-753343 ] Admin interface should follow manager lang preferences Message-ID: Bugs item #753343, was opened at 2003-06-12 12:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=753343&group_id=103 Category: Web/CGI Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Paulo Eduardo Neves (neves) Assigned to: Nobody/Anonymous (nobody) Summary: Admin interface should follow manager lang preferences Initial Comment: This is more a feature request. The maillist admin interface should appear in the list manager user language preference, instead of appearing in the maillist default language. I have my mailling in brazilian portuguese, but the translation text isn't as good as the original english one. It's easier to understand the english text. Sometimes to decide about some preference I have to temporarily change the list to english, select my preference, and then turn it back to portuguese. If the manager interface followed my user lang preference, it wouldn't be necessary. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=753343&group_id=103 From noreply at sourceforge.net Fri Jun 13 23:50:35 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jun 14 01:50:58 2003 Subject: [ mailman-Patches-725369 ] Remove X-Originating-Email: for anonymous lists Message-ID: Patches item #725369, was opened at 2003-04-21 19:15 Message generated for change (Comment added) made by bluecloud You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=725369&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Closed Resolution: Accepted Priority: 5 Submitted By: R Tsang (bluecloud) Assigned to: Nobody/Anonymous (nobody) Summary: Remove X-Originating-Email: for anonymous lists Initial Comment: The email address of the poster is send out to anonymous lists in an X-Originating-Email header. Hotmail adds this header to outgoing messages!!! Patched against Mailman 2.1.1 If you use the source patch, you need to manually recompile your .py to .pyc format and restart Mailman. ---------------------------------------------------------------------- >Comment By: R Tsang (bluecloud) Date: 2003-06-14 00:50 Message: Logged In: YES user_id=383304 Just discovered that Hotmail also uses X-Originating-IP in the header. Remove X-Originating-IP header with the following line in addition to the attached Cleanse.py-2.1.1-1.patch: del msg['X-Originating-Email'] + del msg['X-Originating-IP'] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=725369&group_id=103 From noreply at sourceforge.net Sat Jun 14 15:32:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jun 14 17:32:06 2003 Subject: [ mailman-Patches-754661 ] pending posts navigation Message-ID: Patches item #754661, was opened at 2003-06-14 21:32 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=754661&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: matze (indygena) Assigned to: Nobody/Anonymous (nobody) Summary: pending posts navigation Initial Comment: this patch permits to limit the number of posts shown in the pending admin interface. only mm_cfg.NUM_HELDS_PER_PAGE posts are shown per page, 'prev' and 'next' links are shown on the bottom of the page if needed ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=754661&group_id=103 From noreply at sourceforge.net Sun Jun 15 16:12:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 15 18:12:45 2003 Subject: [ mailman-Patches-754661 ] pending posts navigation Message-ID: Patches item #754661, was opened at 2003-06-14 21:32 Message generated for change (Comment added) made by indygena You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=754661&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: matze (indygena) Assigned to: Nobody/Anonymous (nobody) Summary: pending posts navigation Initial Comment: this patch permits to limit the number of posts shown in the pending admin interface. only mm_cfg.NUM_HELDS_PER_PAGE posts are shown per page, 'prev' and 'next' links are shown on the bottom of the page if needed ---------------------------------------------------------------------- >Comment By: matze (indygena) Date: 2003-06-15 22:12 Message: Logged In: YES user_id=791070 an indymedia pal suggested making configurable on per list base the usage of this feature and number of posts shown. sounds good to me as a future development idea ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=754661&group_id=103 From noreply at sourceforge.net Sun Jun 15 16:22:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 15 18:22:34 2003 Subject: [ mailman-Patches-755045 ] discard all button for pending posts administration Message-ID: Patches item #755045, was opened at 2003-06-15 22:22 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=755045&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: matze (indygena) Assigned to: Nobody/Anonymous (nobody) Summary: discard all button for pending posts administration Initial Comment: adds a 'discard all' button at the bottom of the pending posts page, usefull for lists with high spam rate. not sure if this feature is of general interest, people in the projects where we applied this patch feel confortable with it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=755045&group_id=103 From noreply at sourceforge.net Sun Jun 15 16:27:51 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 15 18:27:57 2003 Subject: [ mailman-Patches-754661 ] pending posts navigation Message-ID: Patches item #754661, was opened at 2003-06-14 21:32 Message generated for change (Comment added) made by indygena You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=754661&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: matze (indygena) Assigned to: Nobody/Anonymous (nobody) Summary: pending posts navigation Initial Comment: this patch permits to limit the number of posts shown in the pending admin interface. only mm_cfg.NUM_HELDS_PER_PAGE posts are shown per page, 'prev' and 'next' links are shown on the bottom of the page if needed ---------------------------------------------------------------------- >Comment By: matze (indygena) Date: 2003-06-15 22:27 Message: Logged In: YES user_id=791070 forgot to check the file upload box when submitting the patch ... ---------------------------------------------------------------------- Comment By: matze (indygena) Date: 2003-06-15 22:12 Message: Logged In: YES user_id=791070 an indymedia pal suggested making configurable on per list base the usage of this feature and number of posts shown. sounds good to me as a future development idea ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=754661&group_id=103 From noreply at sourceforge.net Mon Jun 16 02:25:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 16 04:25:43 2003 Subject: [ mailman-Bugs-746995 ] Error creating mailing list with http://URL/mailman/create Message-ID: Bugs item #746995, was opened at 2003-06-01 14:25 Message generated for change (Comment added) made by pheinlein You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robin Cook (cuzndragon) Assigned to: Nobody/Anonymous (nobody) Summary: Error creating mailing list with http://URL/mailman/create Initial Comment: I have just install mailman and everything seems to be working until I try to create a mailing list using the web interface. When I click on the create list button I get this error below. I couldn't find in in the FAQ and the archives listed was a bad link. What is set wrong? But if I log in as mailman and run the command line utilities to create the mailing list there aren't any problems. 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/create.py", line 55, in main process_request(doc, cgidata) File "/usr/share/mailman/Mailman/Cgi/create.py", line 217, in process_request sys.modules[modname].create(mlist, cgi=1) File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 232, in create _update_maps() File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /var/spool/mailman/data/aliases (status: 1, Operation not permitted) ---------------------------------------------------------------------- >Comment By: Peer Heinlein (pheinlein) Date: 2003-06-16 10:25 Message: Logged In: YES user_id=581680 It doesn`t look like a bug... You just have to set proper permissions to /var/spool/mailman/data/aliases. You have a file-persmission problem, that`s all. Peer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 From noreply at sourceforge.net Mon Jun 16 02:36:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 16 04:36:13 2003 Subject: [ mailman-Bugs-755188 ] subscribing by e-mail crashs lists Message-ID: Bugs item #755188, was opened at 2003-06-16 10:36 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=755188&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None Priority: 7 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: subscribing by e-mail crashs lists Initial Comment: We have a lot of problems with crashed membership-lists. It seems to happen, when a mailinglist owner subscribes users by e-mail. After the crash there`s no access to the membership-list any more! :-(( We need HELP, there`s not just one list crashed! Peer Traceback: Traceback (most recent call last): File "/usr/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 193, in main print doc.Format() File "/usr/lib/mailman/Mailman/htmlformat.py", line 331, in Format output.append(Container.Format(self, indent)) File "/usr/lib/mailman/Mailman/htmlformat.py", line 264, in Format output.append(HTMLFormatObject(item, indent)) File "/usr/lib/mailman/Mailman/htmlformat.py", line 50, in HTMLFormatObject return item.Format(indent) File "/usr/lib/mailman/Mailman/htmlformat.py", line 417, in Format output = output + Container.Format(self, indent+2) File "/usr/lib/mailman/Mailman/htmlformat.py", line 264, in Format output.append(HTMLFormatObject(item, indent)) File "/usr/lib/mailman/Mailman/htmlformat.py", line 50, in HTMLFormatObject return item.Format(indent) File "/usr/lib/mailman/Mailman/htmlformat.py", line 264, in Format output.append(HTMLFormatObject(item, indent)) File "/usr/lib/mailman/Mailman/htmlformat.py", line 50, in HTMLFormatObject return item.Format(indent) File "/usr/lib/mailman/Mailman/htmlformat.py", line 354, in Format output = output + Container.Format(self, indent) File "/usr/lib/mailman/Mailman/htmlformat.py", line 264, in Format output.append(HTMLFormatObject(item, indent)) File "/usr/lib/mailman/Mailman/htmlformat.py", line 50, in HTMLFormatObject return item.Format(indent) File "/usr/lib/mailman/Mailman/htmlformat.py", line 200, in Format output = output + self.FormatRow(i, indent + 2) UnicodeError: ASCII decoding error: ordinal not in range(128) Python information: Variable Value sys.version 2.2.1 (#1, Sep 10 2002, 17:49:17) [GCC 3.2] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_COOKIE $Version="1"; wikoop-intern+admin=280200000069107ded3e732800000061393939353833373738396532623863643737643631386432366530353133356665316435373534; $Path="/mailman/", $Version="1"; wikoop-dev+admin=280200000069fb7ced3e732800000062306237393762336166313633623637363230386339336633633461316161356436363439653038; $Path="/mailman/", $Version="1"; wikoop-admins+admin=280200000069f17ced3e732800000031386234613139326266636436343535346135383536643763373535633639616530343761623965; $Path="/mailman/", $Version="1"; wikoop+admin=280200000069d47ced3e732800000031373430626363343762353838366265613437336230623834636263353265366330376634363331; $Path="/mailman/", $Version="1"; site=280200000069c97ced3e732800000035616531636634333162323234356264363134383566373439363632633635353763393665383164; $Path="/mailman/" SERVER_SOFTWARE Apache/1.3.26 (Linux/SuSE) mod_ssl/2.8.10 OpenSSL/0.9.6g PYTHONPATH /usr/lib/mailman SCRIPT_FILENAME /usr/lib/mailman/cgi-bin/admin SERVER_ADMIN webmaster@jpberlin.de SCRIPT_NAME /mailman/admin SERVER_SIGNATURE Apache/1.3.26 Server at ilpostino.jpberlin.de Port 80 REQUEST_METHOD GET HTTP_HOST listi.jpberlin.de PATH_INFO /rowo-pe-alle/members SERVER_PROTOCOL HTTP/1.1 QUERY_STRING letter=b PATH_TRANSLATED /srv/www/htdocs/rowo-pe-alle/members REQUEST_URI /mailman/admin/rowo-pe-alle/members?letter=b HTTP_ACCEPT text/*, image/jpeg, image/png, image/*, */* HTTP_ACCEPT_CHARSET iso-8859-15, utf-8;q=0.5, *;q=0.5 HTTP_USER_AGENT Mozilla/5.0 (compatible; Konqueror/3.1; Linux) HTTP_CONNECTION Keep-Alive HTTP_REFERER http://listi.jpberlin.de/mailman/admin/rowo-pe-alle/members SERVER_NAME ilpostino.jpberlin.de REMOTE_ADDR 217.224.236.248 REMOTE_PORT 33413 HTTP_ACCEPT_LANGUAGE de, DE, en SERVER_ADDR 62.8.206.157 SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING x-gzip, x-deflate, gzip, deflate, identity UNIQUE_ID Pu2Aiz4Izp0AAAykGBw DOCUMENT_ROOT /srv/www/htdocs ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=755188&group_id=103 From noreply at sourceforge.net Mon Jun 16 02:37:26 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 16 04:37:28 2003 Subject: [ mailman-Bugs-755190 ] ASCII decoding error: mailpasswds Message-ID: Bugs item #755190, was opened at 2003-06-16 10:37 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=755190&group_id=103 Category: None Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: ASCII decoding error: mailpasswds Initial Comment: We still have a *LOT* of those "ASCII decoding errors". Here`s a new one -- it isn`t possible to send out password reminders any more: ilpostino:/etc # /usr/lib/mailman/cron/mailpasswds Traceback (most recent call last): File "/usr/lib/mailman/cron/mailpasswds", line 226, in ? main() File "/usr/lib/mailman/cron/mailpasswds", line 202, in main text += (header + '\n' + NL.join(table)) UnicodeError: ASCII decoding error: ordinal not in range(128) Maybe it depends to # 755 188 Peer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=755190&group_id=103 From noreply at sourceforge.net Mon Jun 16 08:50:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 16 10:50:08 2003 Subject: [ mailman-Bugs-746995 ] Error creating mailing list with http://URL/mailman/create Message-ID: Bugs item #746995, was opened at 2003-06-01 08:25 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Robin Cook (cuzndragon) Assigned to: Nobody/Anonymous (nobody) Summary: Error creating mailing list with http://URL/mailman/create Initial Comment: I have just install mailman and everything seems to be working until I try to create a mailing list using the web interface. When I click on the create list button I get this error below. I couldn't find in in the FAQ and the archives listed was a bad link. What is set wrong? But if I log in as mailman and run the command line utilities to create the mailing list there aren't any problems. 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/create.py", line 55, in main process_request(doc, cgidata) File "/usr/share/mailman/Mailman/Cgi/create.py", line 217, in process_request sys.modules[modname].create(mlist, cgi=1) File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 232, in create _update_maps() File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /var/spool/mailman/data/aliases (status: 1, Operation not permitted) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-16 10:50 Message: Logged In: YES user_id=12800 You either have to make sure the data/aliases and data/aliases.db files have the right permissions (as described in the README and INSTALL files) or your postfix commands aren't in /usr/sbin, in which case you need to edit those variables in your mm_cfg.py file. IOW, this is a configuration problem, not a bug. ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2003-06-16 04:25 Message: Logged In: YES user_id=581680 It doesn`t look like a bug... You just have to set proper permissions to /var/spool/mailman/data/aliases. You have a file-persmission problem, that`s all. Peer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 From noreply at sourceforge.net Mon Jun 16 09:01:36 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 16 11:01:48 2003 Subject: [ mailman-Bugs-746995 ] Error creating mailing list with http://URL/mailman/create Message-ID: Bugs item #746995, was opened at 2003-06-01 12:25 Message generated for change (Comment added) made by cuzndragon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 Category: None Group: None Status: Closed Resolution: Invalid Priority: 5 Submitted By: Robin Cook (cuzndragon) Assigned to: Nobody/Anonymous (nobody) Summary: Error creating mailing list with http://URL/mailman/create Initial Comment: I have just install mailman and everything seems to be working until I try to create a mailing list using the web interface. When I click on the create list button I get this error below. I couldn't find in in the FAQ and the archives listed was a bad link. What is set wrong? But if I log in as mailman and run the command line utilities to create the mailing list there aren't any problems. 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/create.py", line 55, in main process_request(doc, cgidata) File "/usr/share/mailman/Mailman/Cgi/create.py", line 217, in process_request sys.modules[modname].create(mlist, cgi=1) File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 232, in create _update_maps() File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /var/spool/mailman/data/aliases (status: 1, Operation not permitted) ---------------------------------------------------------------------- >Comment By: Robin Cook (cuzndragon) Date: 2003-06-16 15:01 Message: Logged In: YES user_id=5208 Yes. Permissions are correct. -rw-rw---- 1 root mailman 2083 May 30 22:03 aliases -rw-rw---- 1 root mailman 12288 May 30 22:03 aliases.db And yes postalias and postmap are in /usr/sbin So what else would I need to look at for configuration error? It works when I do it manually with the command line scripts. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-16 14:50 Message: Logged In: YES user_id=12800 You either have to make sure the data/aliases and data/aliases.db files have the right permissions (as described in the README and INSTALL files) or your postfix commands aren't in /usr/sbin, in which case you need to edit those variables in your mm_cfg.py file. IOW, this is a configuration problem, not a bug. ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2003-06-16 08:25 Message: Logged In: YES user_id=581680 It doesn`t look like a bug... You just have to set proper permissions to /var/spool/mailman/data/aliases. You have a file-persmission problem, that`s all. Peer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 From noreply at sourceforge.net Mon Jun 16 09:03:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 16 11:03:36 2003 Subject: [ mailman-Bugs-746995 ] Error creating mailing list with http://URL/mailman/create Message-ID: Bugs item #746995, was opened at 2003-06-01 12:25 Message generated for change (Settings changed) made by cuzndragon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 Category: None Group: None >Status: Open Resolution: Invalid Priority: 5 Submitted By: Robin Cook (cuzndragon) Assigned to: Nobody/Anonymous (nobody) Summary: Error creating mailing list with http://URL/mailman/create Initial Comment: I have just install mailman and everything seems to be working until I try to create a mailing list using the web interface. When I click on the create list button I get this error below. I couldn't find in in the FAQ and the archives listed was a bad link. What is set wrong? But if I log in as mailman and run the command line utilities to create the mailing list there aren't any problems. 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/create.py", line 55, in main process_request(doc, cgidata) File "/usr/share/mailman/Mailman/Cgi/create.py", line 217, in process_request sys.modules[modname].create(mlist, cgi=1) File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 232, in create _update_maps() File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /var/spool/mailman/data/aliases (status: 1, Operation not permitted) ---------------------------------------------------------------------- Comment By: Robin Cook (cuzndragon) Date: 2003-06-16 15:01 Message: Logged In: YES user_id=5208 Yes. Permissions are correct. -rw-rw---- 1 root mailman 2083 May 30 22:03 aliases -rw-rw---- 1 root mailman 12288 May 30 22:03 aliases.db And yes postalias and postmap are in /usr/sbin So what else would I need to look at for configuration error? It works when I do it manually with the command line scripts. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-16 14:50 Message: Logged In: YES user_id=12800 You either have to make sure the data/aliases and data/aliases.db files have the right permissions (as described in the README and INSTALL files) or your postfix commands aren't in /usr/sbin, in which case you need to edit those variables in your mm_cfg.py file. IOW, this is a configuration problem, not a bug. ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2003-06-16 08:25 Message: Logged In: YES user_id=581680 It doesn`t look like a bug... You just have to set proper permissions to /var/spool/mailman/data/aliases. You have a file-persmission problem, that`s all. Peer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 From noreply at sourceforge.net Mon Jun 16 09:08:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 16 11:09:00 2003 Subject: [ mailman-Bugs-746995 ] Error creating mailing list with http://URL/mailman/create Message-ID: Bugs item #746995, was opened at 2003-06-01 08:25 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 Category: None Group: None >Status: Closed Resolution: Invalid Priority: 5 Submitted By: Robin Cook (cuzndragon) Assigned to: Nobody/Anonymous (nobody) Summary: Error creating mailing list with http://URL/mailman/create Initial Comment: I have just install mailman and everything seems to be working until I try to create a mailing list using the web interface. When I click on the create list button I get this error below. I couldn't find in in the FAQ and the archives listed was a bad link. What is set wrong? But if I log in as mailman and run the command line utilities to create the mailing list there aren't any problems. 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/create.py", line 55, in main process_request(doc, cgidata) File "/usr/share/mailman/Mailman/Cgi/create.py", line 217, in process_request sys.modules[modname].create(mlist, cgi=1) File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 232, in create _update_maps() File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /var/spool/mailman/data/aliases (status: 1, Operation not permitted) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-16 11:08 Message: Logged In: YES user_id=12800 The files should be owned by mailman. See README.POSTFIX ---------------------------------------------------------------------- Comment By: Robin Cook (cuzndragon) Date: 2003-06-16 11:01 Message: Logged In: YES user_id=5208 Yes. Permissions are correct. -rw-rw---- 1 root mailman 2083 May 30 22:03 aliases -rw-rw---- 1 root mailman 12288 May 30 22:03 aliases.db And yes postalias and postmap are in /usr/sbin So what else would I need to look at for configuration error? It works when I do it manually with the command line scripts. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-16 10:50 Message: Logged In: YES user_id=12800 You either have to make sure the data/aliases and data/aliases.db files have the right permissions (as described in the README and INSTALL files) or your postfix commands aren't in /usr/sbin, in which case you need to edit those variables in your mm_cfg.py file. IOW, this is a configuration problem, not a bug. ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2003-06-16 04:25 Message: Logged In: YES user_id=581680 It doesn`t look like a bug... You just have to set proper permissions to /var/spool/mailman/data/aliases. You have a file-persmission problem, that`s all. Peer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 From noreply at sourceforge.net Mon Jun 16 09:15:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 16 11:15:25 2003 Subject: [ mailman-Bugs-746995 ] Error creating mailing list with http://URL/mailman/create Message-ID: Bugs item #746995, was opened at 2003-06-01 12:25 Message generated for change (Comment added) made by cuzndragon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 Category: None Group: None Status: Closed Resolution: Invalid Priority: 5 Submitted By: Robin Cook (cuzndragon) Assigned to: Nobody/Anonymous (nobody) Summary: Error creating mailing list with http://URL/mailman/create Initial Comment: I have just install mailman and everything seems to be working until I try to create a mailing list using the web interface. When I click on the create list button I get this error below. I couldn't find in in the FAQ and the archives listed was a bad link. What is set wrong? But if I log in as mailman and run the command line utilities to create the mailing list there aren't any problems. 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/create.py", line 55, in main process_request(doc, cgidata) File "/usr/share/mailman/Mailman/Cgi/create.py", line 217, in process_request sys.modules[modname].create(mlist, cgi=1) File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 232, in create _update_maps() File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /var/spool/mailman/data/aliases (status: 1, Operation not permitted) ---------------------------------------------------------------------- >Comment By: Robin Cook (cuzndragon) Date: 2003-06-16 15:15 Message: Logged In: YES user_id=5208 Ok if that is the case then you need to fix your check permission script as it comes back with nothing wrong. Also the group mailman has read/write to the files. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-16 15:08 Message: Logged In: YES user_id=12800 The files should be owned by mailman. See README.POSTFIX ---------------------------------------------------------------------- Comment By: Robin Cook (cuzndragon) Date: 2003-06-16 15:01 Message: Logged In: YES user_id=5208 Yes. Permissions are correct. -rw-rw---- 1 root mailman 2083 May 30 22:03 aliases -rw-rw---- 1 root mailman 12288 May 30 22:03 aliases.db And yes postalias and postmap are in /usr/sbin So what else would I need to look at for configuration error? It works when I do it manually with the command line scripts. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-16 14:50 Message: Logged In: YES user_id=12800 You either have to make sure the data/aliases and data/aliases.db files have the right permissions (as described in the README and INSTALL files) or your postfix commands aren't in /usr/sbin, in which case you need to edit those variables in your mm_cfg.py file. IOW, this is a configuration problem, not a bug. ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2003-06-16 08:25 Message: Logged In: YES user_id=581680 It doesn`t look like a bug... You just have to set proper permissions to /var/spool/mailman/data/aliases. You have a file-persmission problem, that`s all. Peer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 From noreply at sourceforge.net Mon Jun 16 09:22:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 16 11:22:25 2003 Subject: [ mailman-Bugs-746995 ] Error creating mailing list with http://URL/mailman/create Message-ID: Bugs item #746995, was opened at 2003-06-01 08:25 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 Category: None Group: None Status: Closed Resolution: Invalid Priority: 5 Submitted By: Robin Cook (cuzndragon) Assigned to: Nobody/Anonymous (nobody) Summary: Error creating mailing list with http://URL/mailman/create Initial Comment: I have just install mailman and everything seems to be working until I try to create a mailing list using the web interface. When I click on the create list button I get this error below. I couldn't find in in the FAQ and the archives listed was a bad link. What is set wrong? But if I log in as mailman and run the command line utilities to create the mailing list there aren't any problems. 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/create.py", line 55, in main process_request(doc, cgidata) File "/usr/share/mailman/Mailman/Cgi/create.py", line 217, in process_request sys.modules[modname].create(mlist, cgi=1) File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 232, in create _update_maps() File "/usr/share/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /var/spool/mailman/data/aliases (status: 1, Operation not permitted) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-16 11:22 Message: Logged In: YES user_id=12800 Hmm, check_perms fixes data/aliases.db for me in Mailman 2.1.2 (it only really cares about data/aliases.db). ---------------------------------------------------------------------- Comment By: Robin Cook (cuzndragon) Date: 2003-06-16 11:15 Message: Logged In: YES user_id=5208 Ok if that is the case then you need to fix your check permission script as it comes back with nothing wrong. Also the group mailman has read/write to the files. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-16 11:08 Message: Logged In: YES user_id=12800 The files should be owned by mailman. See README.POSTFIX ---------------------------------------------------------------------- Comment By: Robin Cook (cuzndragon) Date: 2003-06-16 11:01 Message: Logged In: YES user_id=5208 Yes. Permissions are correct. -rw-rw---- 1 root mailman 2083 May 30 22:03 aliases -rw-rw---- 1 root mailman 12288 May 30 22:03 aliases.db And yes postalias and postmap are in /usr/sbin So what else would I need to look at for configuration error? It works when I do it manually with the command line scripts. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-16 10:50 Message: Logged In: YES user_id=12800 You either have to make sure the data/aliases and data/aliases.db files have the right permissions (as described in the README and INSTALL files) or your postfix commands aren't in /usr/sbin, in which case you need to edit those variables in your mm_cfg.py file. IOW, this is a configuration problem, not a bug. ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2003-06-16 04:25 Message: Logged In: YES user_id=581680 It doesn`t look like a bug... You just have to set proper permissions to /var/spool/mailman/data/aliases. You have a file-persmission problem, that`s all. Peer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=746995&group_id=103 From noreply at sourceforge.net Tue Jun 17 09:58:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jun 17 11:59:12 2003 Subject: [ mailman-Bugs-755188 ] subscribing by e-mail crashs lists Message-ID: Bugs item #755188, was opened at 2003-06-16 04:36 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=755188&group_id=103 Category: (un)subscribing >Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: subscribing by e-mail crashs lists Initial Comment: We have a lot of problems with crashed membership-lists. It seems to happen, when a mailinglist owner subscribes users by e-mail. After the crash there`s no access to the membership-list any more! :-(( We need HELP, there`s not just one list crashed! Peer Traceback: Traceback (most recent call last): File "/usr/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 193, in main print doc.Format() File "/usr/lib/mailman/Mailman/htmlformat.py", line 331, in Format output.append(Container.Format(self, indent)) File "/usr/lib/mailman/Mailman/htmlformat.py", line 264, in Format output.append(HTMLFormatObject(item, indent)) File "/usr/lib/mailman/Mailman/htmlformat.py", line 50, in HTMLFormatObject return item.Format(indent) File "/usr/lib/mailman/Mailman/htmlformat.py", line 417, in Format output = output + Container.Format(self, indent+2) File "/usr/lib/mailman/Mailman/htmlformat.py", line 264, in Format output.append(HTMLFormatObject(item, indent)) File "/usr/lib/mailman/Mailman/htmlformat.py", line 50, in HTMLFormatObject return item.Format(indent) File "/usr/lib/mailman/Mailman/htmlformat.py", line 264, in Format output.append(HTMLFormatObject(item, indent)) File "/usr/lib/mailman/Mailman/htmlformat.py", line 50, in HTMLFormatObject return item.Format(indent) File "/usr/lib/mailman/Mailman/htmlformat.py", line 354, in Format output = output + Container.Format(self, indent) File "/usr/lib/mailman/Mailman/htmlformat.py", line 264, in Format output.append(HTMLFormatObject(item, indent)) File "/usr/lib/mailman/Mailman/htmlformat.py", line 50, in HTMLFormatObject return item.Format(indent) File "/usr/lib/mailman/Mailman/htmlformat.py", line 200, in Format output = output + self.FormatRow(i, indent + 2) UnicodeError: ASCII decoding error: ordinal not in range(128) Python information: Variable Value sys.version 2.2.1 (#1, Sep 10 2002, 17:49:17) [GCC 3.2] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_COOKIE $Version="1"; wikoop-intern+admin=280200000069107ded3e732800000061393939353833373738396532623863643737643631386432366530353133356665316435373534; $Path="/mailman/", $Version="1"; wikoop-dev+admin=280200000069fb7ced3e732800000062306237393762336166313633623637363230386339336633633461316161356436363439653038; $Path="/mailman/", $Version="1"; wikoop-admins+admin=280200000069f17ced3e732800000031386234613139326266636436343535346135383536643763373535633639616530343761623965; $Path="/mailman/", $Version="1"; wikoop+admin=280200000069d47ced3e732800000031373430626363343762353838366265613437336230623834636263353265366330376634363331; $Path="/mailman/", $Version="1"; site=280200000069c97ced3e732800000035616531636634333162323234356264363134383566373439363632633635353763393665383164; $Path="/mailman/" SERVER_SOFTWARE Apache/1.3.26 (Linux/SuSE) mod_ssl/2.8.10 OpenSSL/0.9.6g PYTHONPATH /usr/lib/mailman SCRIPT_FILENAME /usr/lib/mailman/cgi-bin/admin SERVER_ADMIN webmaster@jpberlin.de SCRIPT_NAME /mailman/admin SERVER_SIGNATURE Apache/1.3.26 Server at ilpostino.jpberlin.de Port 80 REQUEST_METHOD GET HTTP_HOST listi.jpberlin.de PATH_INFO /rowo-pe-alle/members SERVER_PROTOCOL HTTP/1.1 QUERY_STRING letter=b PATH_TRANSLATED /srv/www/htdocs/rowo-pe-alle/members REQUEST_URI /mailman/admin/rowo-pe-alle/members?letter=b HTTP_ACCEPT text/*, image/jpeg, image/png, image/*, */* HTTP_ACCEPT_CHARSET iso-8859-15, utf-8;q=0.5, *;q=0.5 HTTP_USER_AGENT Mozilla/5.0 (compatible; Konqueror/3.1; Linux) HTTP_CONNECTION Keep-Alive HTTP_REFERER http://listi.jpberlin.de/mailman/admin/rowo-pe-alle/members SERVER_NAME ilpostino.jpberlin.de REMOTE_ADDR 217.224.236.248 REMOTE_PORT 33413 HTTP_ACCEPT_LANGUAGE de, DE, en SERVER_ADDR 62.8.206.157 SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING x-gzip, x-deflate, gzip, deflate, identity UNIQUE_ID Pu2Aiz4Izp0AAAykGBw DOCUMENT_ROOT /srv/www/htdocs ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-17 11:58 Message: Logged In: YES user_id=12800 Fixed in admin.py 2.89 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=755188&group_id=103 From noreply at sourceforge.net Tue Jun 17 10:09:47 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jun 17 12:09:54 2003 Subject: [ mailman-Bugs-755190 ] ASCII decoding error: mailpasswds Message-ID: Bugs item #755190, was opened at 2003-06-16 04:37 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=755190&group_id=103 Category: None >Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: ASCII decoding error: mailpasswds Initial Comment: We still have a *LOT* of those "ASCII decoding errors". Here`s a new one -- it isn`t possible to send out password reminders any more: ilpostino:/etc # /usr/lib/mailman/cron/mailpasswds Traceback (most recent call last): File "/usr/lib/mailman/cron/mailpasswds", line 226, in ? main() File "/usr/lib/mailman/cron/mailpasswds", line 202, in main text += (header + '\n' + NL.join(table)) UnicodeError: ASCII decoding error: ordinal not in range(128) Maybe it depends to # 755 188 Peer ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-17 12:09 Message: Logged In: YES user_id=12800 This is related to 755188 but it's a different bug (as that one's been fixed). I believe this one is triggered by having an address in the member database that is a unicode object, not a string object. The address contains only ascii characters though. The fix for 755188 was to addr.encode() before putting it in the admin.py table. The fix for this one might be similar. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=755190&group_id=103 From noreply at sourceforge.net Thu Jun 19 15:49:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 19 17:49:49 2003 Subject: [ mailman-Bugs-755190 ] ASCII decoding error: mailpasswds Message-ID: Bugs item #755190, was opened at 2003-06-16 04:37 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=755190&group_id=103 Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: ASCII decoding error: mailpasswds Initial Comment: We still have a *LOT* of those "ASCII decoding errors". Here`s a new one -- it isn`t possible to send out password reminders any more: ilpostino:/etc # /usr/lib/mailman/cron/mailpasswds Traceback (most recent call last): File "/usr/lib/mailman/cron/mailpasswds", line 226, in ? main() File "/usr/lib/mailman/cron/mailpasswds", line 202, in main text += (header + '\n' + NL.join(table)) UnicodeError: ASCII decoding error: ordinal not in range(128) Maybe it depends to # 755 188 Peer ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-19 17:49 Message: Logged In: YES user_id=12800 Fixed in mailpasswds 2.17 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-06-17 12:09 Message: Logged In: YES user_id=12800 This is related to 755188 but it's a different bug (as that one's been fixed). I believe this one is triggered by having an address in the member database that is a unicode object, not a string object. The address contains only ascii characters though. The fix for 755188 was to addr.encode() before putting it in the admin.py table. The fix for this one might be similar. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=755190&group_id=103 From noreply at sourceforge.net Fri Jun 20 20:23:40 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jun 20 22:23:48 2003 Subject: [ mailman-Patches-646989 ] NAH6 Secure List patch: GPG plugin Message-ID: Patches item #646989, was opened at 2002-12-02 11:07 Message generated for change (Comment added) made by pcarr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646989&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 6 Submitted By: Rop Gonggrijp (rop) Assigned to: Thomas Wouters (twouters) Summary: NAH6 Secure List patch: GPG plugin Initial Comment: "NAH6 Secure List" is a patch for Mailman 2.1b5 that adds GPG functionality. It is built around a key-scheme that allows an admin to create an encrypted list for which even the server operator doesn't have access to the messages. Only the public key for the list is given to the server, so it can perform 'emergency encryption' in case someone forgets, and all users get the public and private key for the list. We think we've done a decent job of describing the new functionality from server-operator, list-admin and list- member points of view. There's also a technical document for those familiar with the Mailman code. Please have a look at: http://www.nah6.com/products/secure-list/ and follow the links from there We feel more people need this, and we'd really like it to be part of the Mailman distribution at some point... Kind Regards, Rop Gonggrijp Joshua Eichen Please forgive mangling the Mailman logo on the site: if y'all don't like it or think it's over the top we'll use something else.... ---------------------------------------------------------------------- Comment By: Pat Carr (pcarr) Date: 2003-06-20 22:23 Message: Logged In: YES user_id=710070 The problem with the NAH approach is that every time a member leaves the list, the administrator needs to generate and distribute a new key, and every remaining member would have to remove the old list key and replace it with the new one. This could become a logistical nightmare, and makes it more difficult to sell this capability to a group that has people who are email savvy, but not necessarily pgp-savvy. I prefer the approach in patch #645297, recognizing that the task there is to maintain strict security of the server and the secret keys of the lists. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 11:16 Message: Logged In: YES user_id=34209 I'm looking at this patch, but I'm a bit confused. Which is the newer patch, v1.0 for Mailman 2.1 (uploaded last) or v1.1 for Mailman 2.1b5 (which is linked to from the NAH6 secure-list page.) Otherwise, the patch looks okay. There are some whitespace issues, and the PGP specific options aren't properly internationalized, but that can all be fixed. The patch edits Defaults.py, but it should be Defaults.py.in (if you want to apply to CVS before installation, anyway.) Oh, and a 'global' statement for DETAILS in the global namespace really isn't necessary... Do you need someone to come over and give a Python tutorial at NAH6 ? :-) Assigning to myself so I don't forget it; if someone else wants it, that's fine by me. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-11 23:01 Message: Logged In: YES user_id=12800 The logo's fine (plus the original is free software). I'm defering this until after MM2.1 because we're about ready for the first release candidate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=646989&group_id=103 From noreply at sourceforge.net Sun Jun 22 05:04:00 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 22 07:04:27 2003 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 19:17 Message generated for change (Comment added) made by danbri You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 22:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 21:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-18 01:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 20:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 19:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 19:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 19:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 From noreply at sourceforge.net Sun Jun 22 05:48:54 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 22 07:49:16 2003 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 19:17 Message generated for change (Comment added) made by danbri You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:48 Message: Logged In: YES user_id=7830 I thought I'd have a look at this myself, though have modest knowledge of both Python and MailMan. In the course of trying to patch the patch, I tried running the archiver over just the last couple of messages, to speed things along: "../../bin/arch -s 4390 rdfweb-dev". Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 310, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1082, in write_TOC rss.write(self.RSS()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 769, in RSS date, msgid = self.database.dateIndex.first() AttributeError: HyperDatabase instance has no attribute 'dateIndex' Not sure what's going on there, but this seemed as good a place of any to keep note of it. Investigating... ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 22:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 21:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-18 01:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 20:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 19:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 19:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 19:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 From noreply at sourceforge.net Sun Jun 22 09:00:51 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 22 11:01:10 2003 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 19:17 Message generated for change (Comment added) made by danbri You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 15:00 Message: Logged In: YES user_id=7830 OK, I've regenerated the patch with some code which works for me. http://rdfweb.org/2003/06/mailman-rss/rsspatch Health warning: * I suspect it may fail in conditions when get_archives() returns a list not a string (does this ever happen?). * See also problems mentioned below, regenerating partial archives seems tricky. Hope this is useful anyways... Dan ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:48 Message: Logged In: YES user_id=7830 I thought I'd have a look at this myself, though have modest knowledge of both Python and MailMan. In the course of trying to patch the patch, I tried running the archiver over just the last couple of messages, to speed things along: "../../bin/arch -s 4390 rdfweb-dev". Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 310, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1082, in write_TOC rss.write(self.RSS()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 769, in RSS date, msgid = self.database.dateIndex.first() AttributeError: HyperDatabase instance has no attribute 'dateIndex' Not sure what's going on there, but this seemed as good a place of any to keep note of it. Investigating... ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 22:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 21:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-18 01:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 20:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 19:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 19:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 19:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 From noreply at sourceforge.net Sun Jun 22 09:57:46 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 22 11:57:54 2003 Subject: [ mailman-Feature Requests-758801 ] MAXIMUM HELD TIME Message-ID: Feature Requests item #758801, was opened at 2003-06-22 17:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=758801&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: MAXIMUM HELD TIME Initial Comment: I`d like to have a MAXIMUM_HELD_TIME in the config and a little script, that deletes those old entries from pending.pck I have some list-admins, which doesn`t care enough about their held-database and which have held messages from more then 10 weeks in it. Sure, they HAVE to care about this, but they don`t and I have to handle this. Sure, I can write a simple script that deletes too old FILES, but I don`t know how to handle pending.pck Peer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=758801&group_id=103 From noreply at sourceforge.net Tue Jun 24 08:22:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jun 24 10:22:22 2003 Subject: [ mailman-Bugs-759841 ] Multipart/mixed issues in archives Message-ID: Bugs item #759841, was opened at 2003-06-24 09:22 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Multipart/mixed issues in archives Initial Comment: We are having problems with mailing lists that are not being properly stripped down to text content in the archives. When there is multipart/mixed, it doesn't pull the multipart/alternative sections into their appropriate text portions. For example, from content such as the following: ============================================================================== >From ... [...] Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=------------InterScan_NT_MIME_Boundary [...] This is a multi-part message in MIME format. --------------InterScan_NT_MIME_Boundary Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C336A1.2C7564BC" Content-Transfer-Encoding: 7bit ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Kevin has a pending checkin that addresses the minss/maxss issue. =20 [...] ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message= [...] ============================================================================== I only get the following: ============================================================================== [64bit-compiler-analysis] RE: vpr analysis Syyyy Kyyyyy syyyk at yyy.com Thu Jun 19 14:27:16 CDT 2003 Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- Skipped content of type multipart/alternative -------------------------------------------------------------------------------- Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- More information about the 64bit-compiler-analysis mailing list ============================================================================== As you can see, the actual content of the multipart/alternative portion [text/plain and text/html] were completely stripped out instead of being shown a plain text. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 From noreply at sourceforge.net Tue Jun 24 08:23:47 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jun 24 10:23:51 2003 Subject: [ mailman-Bugs-759842 ] Formatting archives that don't have newlines Message-ID: Bugs item #759842, was opened at 2003-06-24 09: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=759842&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Formatting archives that don't have newlines Initial Comment: I have a problem (mostly with M$ Outlook users) that when a user sends a message without newlines in it (because their email client auto-displays it "properly" for them), the message gets stored just like this in the archives as expected. The problem is that when the message gets pulled up in the webpages, they will appear as one long line instead of being formatted to the size of the browser width. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759842&group_id=103 From noreply at sourceforge.net Tue Jun 24 11:01:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jun 24 13:01:57 2003 Subject: [ mailman-Bugs-759841 ] Multipart/mixed issues in archives Message-ID: Bugs item #759841, was opened at 2003-06-24 09:22 Message generated for change (Comment added) made by phelim_gervase You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Multipart/mixed issues in archives Initial Comment: We are having problems with mailing lists that are not being properly stripped down to text content in the archives. When there is multipart/mixed, it doesn't pull the multipart/alternative sections into their appropriate text portions. For example, from content such as the following: ============================================================================== >From ... [...] Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=------------InterScan_NT_MIME_Boundary [...] This is a multi-part message in MIME format. --------------InterScan_NT_MIME_Boundary Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C336A1.2C7564BC" Content-Transfer-Encoding: 7bit ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Kevin has a pending checkin that addresses the minss/maxss issue. =20 [...] ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message= [...] ============================================================================== I only get the following: ============================================================================== [64bit-compiler-analysis] RE: vpr analysis Syyyy Kyyyyy syyyk at yyy.com Thu Jun 19 14:27:16 CDT 2003 Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- Skipped content of type multipart/alternative -------------------------------------------------------------------------------- Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- More information about the 64bit-compiler-analysis mailing list ============================================================================== As you can see, the actual content of the multipart/alternative portion [text/plain and text/html] were completely stripped out instead of being shown a plain text. ---------------------------------------------------------------------- >Comment By: Pug Bainter (phelim_gervase) Date: 2003-06-24 12:01 Message: Logged In: YES user_id=484284 This appears to be within: def process(mlist, msg, msgdata=None): at around line 276, but I saw no way of making it recurse for multipart/[mixed|alternative] sub-MIME parts. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 From noreply at sourceforge.net Wed Jun 25 09:25:38 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jun 25 11:25:42 2003 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 (Tracker Item Submitted) made by Item Submitter 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=760567&group_id=103 From noreply at sourceforge.net Wed Jun 25 11:21:48 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jun 25 13:21:58 2003 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: 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 Wed Jun 25 15:14:48 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jun 25 17:14:52 2003 Subject: [ mailman-Bugs-760777 ] add member error Message-ID: Bugs item #760777, was opened at 2003-06-25 21:14 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=760777&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: b0rg qw3r dr0n3 (b0rg) Assigned to: Nobody/Anonymous (nobody) Summary: add member error Initial Comment: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 169, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 1263, in change_options send_admin_notif, invitation) File "/var/lib/mailman/Mailman/MailList.py", line 902, in ApprovedAddMember digest, text) File "/var/lib/mailman/Mailman/Deliverer.py", line 78, in SendSubscribeAck text, pluser) File "/var/lib/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' Python information: Variable Value sys.version 2.2.2 (#1, Mar 21 2003, 23:01:54) [GCC 3.2.3 20030316 (Debian prerelease)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Python 2.2.2 is this information enough? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=760777&group_id=103 From noreply at sourceforge.net Thu Jun 26 14:23:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 26 16:23:55 2003 Subject: [ mailman-Patches-761421 ] var_prefix directory mounted with noatime breaks Mailman. Message-ID: Patches item #761421, was opened at 2003-06-26 13:23 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=761421&group_id=103 Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Max Kalika (mkalika) Assigned to: Nobody/Anonymous (nobody) Summary: var_prefix directory mounted with noatime breaks Mailman. Initial Comment: On a test machine: ike mailman # mount /dev/root on / type reiserfs (rw,noatime,notail) ike mailman # su - mailman -c "bin/newlist list user@domain pass" Traceback (most recent call last): File "bin/newlist", line 219, in ? main() File "bin/newlist", line 180, in main mlist.Unlock() File "/home/mailman/Mailman/MailList.py", line 165, in Unlock self.__lock.unlock(unconditionally=1) File "/home/mailman/Mailman/LockFile.py", line 321, in unlock islocked = self.locked() File "/home/mailman/Mailman/LockFile.py", line 345, in locked self.__touch() File "/home/mailman/Mailman/LockFile.py", line 442, in __touch os.utime(filename or self.__tmpfname, (t, t)) TypeError: utime() arg 2 must be a tuple (atime, mtime) now, if you change the filesystem options... ike mailman # mount /dev/root on / type reiserfs (rw,notail) ike mailman # su - mailman -c "bin/newlist list user@domain pass" To finish creating your mailing list, you must edit your /etc/aliases (or equivalent) file by adding the following lines, and possibly running the `newaliases' program: ## list mailing list list: "|/home/mailman/mail/mailman post list" list-admin: "|/home/mailman/mail/mailman admin list" list-bounces: "|/home/mailman/mail/mailman bounces list" .... The attached patch seems to fix the situation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=761421&group_id=103 From noreply at sourceforge.net Thu Jun 26 15:24:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 26 17:24:20 2003 Subject: [ mailman-Patches-761421 ] var_prefix directory mounted with noatime breaks Mailman. Message-ID: Patches item #761421, was opened at 2003-06-26 13:23 Message generated for change (Comment added) made by mkalika You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=761421&group_id=103 Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Max Kalika (mkalika) Assigned to: Nobody/Anonymous (nobody) Summary: var_prefix directory mounted with noatime breaks Mailman. Initial Comment: On a test machine: ike mailman # mount /dev/root on / type reiserfs (rw,noatime,notail) ike mailman # su - mailman -c "bin/newlist list user@domain pass" Traceback (most recent call last): File "bin/newlist", line 219, in ? main() File "bin/newlist", line 180, in main mlist.Unlock() File "/home/mailman/Mailman/MailList.py", line 165, in Unlock self.__lock.unlock(unconditionally=1) File "/home/mailman/Mailman/LockFile.py", line 321, in unlock islocked = self.locked() File "/home/mailman/Mailman/LockFile.py", line 345, in locked self.__touch() File "/home/mailman/Mailman/LockFile.py", line 442, in __touch os.utime(filename or self.__tmpfname, (t, t)) TypeError: utime() arg 2 must be a tuple (atime, mtime) now, if you change the filesystem options... ike mailman # mount /dev/root on / type reiserfs (rw,notail) ike mailman # su - mailman -c "bin/newlist list user@domain pass" To finish creating your mailing list, you must edit your /etc/aliases (or equivalent) file by adding the following lines, and possibly running the `newaliases' program: ## list mailing list list: "|/home/mailman/mail/mailman post list" list-admin: "|/home/mailman/mail/mailman admin list" list-bounces: "|/home/mailman/mail/mailman bounces list" .... The attached patch seems to fix the situation. ---------------------------------------------------------------------- >Comment By: Max Kalika (mkalika) Date: 2003-06-26 14:24 Message: Logged In: YES user_id=805201 I found another place where this is happening. I reposted the patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=761421&group_id=103 From noreply at sourceforge.net Thu Jun 26 16:00:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 26 18:00:46 2003 Subject: [ mailman-Feature Requests-761484 ] Allow alternate email addresses Message-ID: Feature Requests item #761484, was opened at 2003-06-26 17:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=761484&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Allow alternate email addresses Initial Comment: Allow users to specify alternate email addresses that they may post from. For example: pug.bainter@pug.net would like to allow pug@pug.net as well as pug.bainter@stardock.pug.net to be able to post to the restricted lists that he's subscribed to. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=761484&group_id=103 From noreply at sourceforge.net Thu Jun 26 16:05:19 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 26 18:05:47 2003 Subject: [ mailman-Feature Requests-761484 ] Allow alternate email addresses Message-ID: Feature Requests item #761484, was opened at 2003-06-26 17:00 Message generated for change (Comment added) made by phelim_gervase You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=761484&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Allow alternate email addresses Initial Comment: Allow users to specify alternate email addresses that they may post from. For example: pug.bainter@pug.net would like to allow pug@pug.net as well as pug.bainter@stardock.pug.net to be able to post to the restricted lists that he's subscribed to. ---------------------------------------------------------------------- >Comment By: Pug Bainter (phelim_gervase) Date: 2003-06-26 17:05 Message: Logged In: YES user_id=484284 It would also be beneficial to allow a user or list to recognize subdomains as acceptable email addresses for the user. As above, pug.bainter@stardock.pug.net would be the same as pug.bainter@pug.net. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=761484&group_id=103 From noreply at sourceforge.net Thu Jun 26 17:38:47 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 26 19:38:51 2003 Subject: [ mailman-Patches-761421 ] var_prefix directory mounted with noatime breaks Mailman. Message-ID: Patches item #761421, was opened at 2003-06-26 13:23 Message generated for change (Comment added) made by mkalika You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=761421&group_id=103 Category: None Group: Mailman 2.1 >Status: Deleted >Resolution: Invalid Priority: 5 Submitted By: Max Kalika (mkalika) Assigned to: Nobody/Anonymous (nobody) Summary: var_prefix directory mounted with noatime breaks Mailman. Initial Comment: On a test machine: ike mailman # mount /dev/root on / type reiserfs (rw,noatime,notail) ike mailman # su - mailman -c "bin/newlist list user@domain pass" Traceback (most recent call last): File "bin/newlist", line 219, in ? main() File "bin/newlist", line 180, in main mlist.Unlock() File "/home/mailman/Mailman/MailList.py", line 165, in Unlock self.__lock.unlock(unconditionally=1) File "/home/mailman/Mailman/LockFile.py", line 321, in unlock islocked = self.locked() File "/home/mailman/Mailman/LockFile.py", line 345, in locked self.__touch() File "/home/mailman/Mailman/LockFile.py", line 442, in __touch os.utime(filename or self.__tmpfname, (t, t)) TypeError: utime() arg 2 must be a tuple (atime, mtime) now, if you change the filesystem options... ike mailman # mount /dev/root on / type reiserfs (rw,notail) ike mailman # su - mailman -c "bin/newlist list user@domain pass" To finish creating your mailing list, you must edit your /etc/aliases (or equivalent) file by adding the following lines, and possibly running the `newaliases' program: ## list mailing list list: "|/home/mailman/mail/mailman post list" list-admin: "|/home/mailman/mail/mailman admin list" list-bounces: "|/home/mailman/mail/mailman bounces list" .... The attached patch seems to fix the situation. ---------------------------------------------------------------------- >Comment By: Max Kalika (mkalika) Date: 2003-06-26 16:38 Message: Logged In: YES user_id=805201 bah! please ignore this bug. the errors were caused due to glibc/python/mailman being compiled with -march=pentium4 which breaks some floating point calculations. sorry for the inconvenience, everything is fine now. ---------------------------------------------------------------------- Comment By: Max Kalika (mkalika) Date: 2003-06-26 14:24 Message: Logged In: YES user_id=805201 I found another place where this is happening. I reposted the patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=761421&group_id=103 From noreply at sourceforge.net Fri Jun 27 11:56:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jun 27 13:56:36 2003 Subject: [ mailman-Bugs-761995 ] can't remove moderator password Message-ID: Bugs item #761995, was opened at 2003-06-27 13:56 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=761995&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: can't remove moderator password Initial Comment: Once you provide a moderator password, you cannot remove this via the web interface, although you can via the shell. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=761995&group_id=103 From noreply at sourceforge.net Fri Jun 27 16:05:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jun 27 18:05:14 2003 Subject: [ mailman-Patches-762130 ] web interface for editing archives Message-ID: Patches item #762130, was opened at 2003-06-27 18:05 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=762130&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Adriane Boyd (aaboyd) Assigned to: Nobody/Anonymous (nobody) Summary: web interface for editing archives Initial Comment: This patch makes it possible for list administrators to edit their list archives through a web interface linked into the admin interface. A new cgi script called editarch allows administrators to browse by month and delete messages from the archives. The messages are immediately deleted from the mbox file, but because of the overhead in reprocessing archives, the archives aren't redone on-the-fly. Instead, a file is kept with a running list of recently edited archives and a nightly cron job does the reprocessing. The file location is configurable in mm_cfg. (Note: since it has to read through the mbox file message by message, pages will load slowly for lists with large archives.) In the mailman 2.1.2 source directory: patch -p1 < editarch-2.1.2-0.1.patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=762130&group_id=103