From noreply at sourceforge.net Thu May 1 07:24:19 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 1 09:24:25 2003 Subject: [ mailman-Bugs-730769 ] template access hierarchy is broken Message-ID: Bugs item #730769, was opened at 2003-05-01 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=100103&aid=730769&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: template access hierarchy is broken Initial Comment: The quick_maketext()function in HyperArch.py uses a caching scheme for templates extracted from one of the four possible sources of templates, i.e. general, site, domain and list specific templates. The caching scheme is broken because the key to the cache only uses the name of the template file and the language. Thus once a a file for a given langauge has been cached, regardless of which of the sources it was obtained from, it is that template that is used by all lists, regardless of the existence of a template in a preferred source for that particular list. The attached patch fixes this problem. Apply the patch with the MM build directory as current working directory using the command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730769&group_id=103 From noreply at sourceforge.net Thu May 1 08:00:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 1 10:03:46 2003 Subject: [ mailman-Bugs-730769 ] template access hierarchy is broken Message-ID: Bugs item #730769, was opened at 2003-05-01 13:24 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730769&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None >Priority: 8 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: template access hierarchy is broken Initial Comment: The quick_maketext()function in HyperArch.py uses a caching scheme for templates extracted from one of the four possible sources of templates, i.e. general, site, domain and list specific templates. The caching scheme is broken because the key to the cache only uses the name of the template file and the language. Thus once a a file for a given langauge has been cached, regardless of which of the sources it was obtained from, it is that template that is used by all lists, regardless of the existence of a template in a preferred source for that particular list. The attached patch fixes this problem. Apply the patch with the MM build directory as current working directory using the command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-05-01 14:00 Message: Logged In: YES user_id=75166 And do not forget to mailmanctl restart after applying the patch! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730769&group_id=103 From noreply at sourceforge.net Thu May 1 09:18:41 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 1 11:18:46 2003 Subject: [ mailman-Bugs-730814 ] HTML stripped regardless of filters Message-ID: Bugs item #730814, was opened at 2003-05-01 15:18 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730814&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Charles Hall (hallcp) Assigned to: Nobody/Anonymous (nobody) Summary: HTML stripped regardless of filters Initial Comment: If I enable "content-filtering", HTML is a;ways stripped out regardless of my other filter settings. I have tried to track this down and it appears that MimeDel.py is collapsing ALL multi-part emails to a single component. This leaves the plain text but strips off the HTML flavored portion. If I disable content-filtering, MimeDel is neutralized and HTML email works OK. The suspect function is "collapse_multipart_alternatives". FYI: my test emails were sent from Outlook. I posted and emailed to others on the Users mailing list, but no one responded that they have gotten filtering to work either. This looks like a real nice feature. I hope you guys can fix it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730814&group_id=103 From noreply at sourceforge.net Thu May 1 09:09:12 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 1 11:21:51 2003 Subject: [ mailman-Bugs-730769 ] template access hierarchy is broken Message-ID: Bugs item #730769, was opened at 2003-05-01 13:24 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730769&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 8 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: template access hierarchy is broken Initial Comment: The quick_maketext()function in HyperArch.py uses a caching scheme for templates extracted from one of the four possible sources of templates, i.e. general, site, domain and list specific templates. The caching scheme is broken because the key to the cache only uses the name of the template file and the language. Thus once a a file for a given langauge has been cached, regardless of which of the sources it was obtained from, it is that template that is used by all lists, regardless of the existence of a template in a preferred source for that particular list. The attached patch fixes this problem. Apply the patch with the MM build directory as current working directory using the command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-05-01 15:09 Message: Logged In: YES user_id=75166 After doing some furehtr (proper) testing I hope version 2 of the patch will solve the problem ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-01 14:00 Message: Logged In: YES user_id=75166 And do not forget to mailmanctl restart after applying the patch! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730769&group_id=103 From noreply at sourceforge.net Thu May 1 13:00:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 1 15:00:59 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-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 Thu May 1 19:21:40 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 1 21:21:49 2003 Subject: [ mailman-Bugs-726016 ] confirm crash when admin_notify_mchanges is yes Message-ID: Bugs item #726016, was opened at 2003-04-23 15:54 Message generated for change (Comment added) made by tzs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726016&group_id=103 Category: (un)subscribing Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: confirm crash when admin_notify_mchanges is yes Initial Comment: OS is OpenBSD 3.1, same error occurs in Python-2.2 and Python-2.2.2 This happens after getting the confirmation email, following the link in it and clicking on the ''Subscribe to list Listname" button, but only when admin_notify_mchanges is Yes, otherwise it works. This worked in 2.1b3, but is broken in 2.1 and 2.1.1 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [----- Mailman Version: 2.1.1 -----] [----- Traceback ------] Traceback (most recent call last): File "/home/mailman/scripts/driver", line 87, in run_main main() File "/home/mailman/Mailman/Cgi/confirm.py", line 110, in main subscription_confirm(mlist, doc, cookie, cgidata) File "/home/mailman/Mailman/Cgi/confirm.py", line 333, in subscription_confirm op, addr, pw, digest, lang = mlist.ProcessConfirmation( File "/home/mailman/Mailman/MailList.py", line 1071, in ProcessConfirmation self.ApprovedAddMember(userdesc) File "/home/mailman/Mailman/MailList.py", line 899, in ApprovedAddMember }, mlist=self) File "/home/mailman/Mailman/Utils.py", line 481, in maketext return wrap(text) File "/home/mailman/Mailman/Utils.py", line 113, in wrap if honor_leading_ws and line[0] in whitespace: UnicodeError: ASCII decoding error: ordinal not in range(128) [----- Python Information -----] sys.version = 2.2 (#1, Apr 12 2002, 22:56:34) [GCC 2.95.3 20010125 (prerelease)] sys.executable = /usr/local/bin/python sys.prefix = /usr/local sys.exec_prefix = /usr/local sys.path = /usr/local sys.platform = openbsd3 ---------------------------------------------------------------------- >Comment By: Colin Palmer (tzs) Date: 2003-05-02 13:21 Message: Logged In: YES user_id=658762 Seems fixed in 2.1.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726016&group_id=103 From noreply at sourceforge.net Thu May 1 19:22:39 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 1 21:22:43 2003 Subject: [ mailman-Bugs-726019 ] logger crash when generating tracebacks Message-ID: Bugs item #726019, was opened at 2003-04-23 16:08 Message generated for change (Comment added) made by tzs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726019&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: logger crash when generating tracebacks Initial Comment: OpenBSD-3.1, Python-2.2.2, Mailman-2.1.1 When something causes an exception in the CGI scripts, the logger then produces one of its own trying to report it: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [----- Mailman Version: 2.1.1 -----] [----- Traceback ------] Traceback (most recent call last): File "/home/mailman/scripts/driver", line 224, in ? run_main() File "/home/mailman/scripts/driver", line 96, in run_main print_traceback(logger) File "/home/mailman/scripts/driver", line 121, in print_traceback print >> logfp, '@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@' File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: can't resize shared unicode objects [----- Python Information -----] sys.version = 2.2.2 (#1, Apr 22 2003, 22:52:59) [GCC 2.95.3 20010125 (prerelease)] sys.executable = /usr/local/bin/python sys.prefix = /usr/local sys.exec_prefix = /usr/local sys.path = /usr/local sys.platform = openbsd3 ---------------------------------------------------------------------- >Comment By: Colin Palmer (tzs) Date: 2003-05-02 13:22 Message: Logged In: YES user_id=658762 Also seems fixed now in 2.1.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726019&group_id=103 From noreply at sourceforge.net Thu May 1 19:34:39 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 1 21:35:00 2003 Subject: [ mailman-Patches-645513 ] qmail VERP-enabled delivery handler Message-ID: Patches item #645513, was opened at 2002-11-29 15:58 Message generated for change (Comment added) made by tzs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: qmail VERP-enabled delivery handler Initial Comment: This is based on Peter D. Gray's popen-avoiding Sendmail.py module, tweaked so it can use qmail-inject instead of sendmail and ask qmail to do VERP when the message is delivered, which is much faster than getting Mailman to do it at message injection time. You'll need the following in mm_cfg.py: DELIVERY_MODULE = 'Qmail' SENDMAIL_CMD = '/var/qmail/bin/qmail-inject' DO_QMAIL_VERP = 1 ---------------------------------------------------------------------- >Comment By: Colin Palmer (tzs) Date: 2003-05-02 13:34 Message: Logged In: YES user_id=658762 Latest version, with some logging fixes... has been running on a couple of production servers and seems mostly stable now. ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2003-01-15 16:26 Message: Logged In: YES user_id=675094 Everything works as documented for me right now. Might also need to include a step to make ~alias/.qmail--bounce-default. ---------------------------------------------------------------------- Comment By: Colin Palmer (tzs) Date: 2003-01-09 09:09 Message: Logged In: YES user_id=658762 Yes, python throws an exception if they (or any other config options) are undefined. Set them to 'None' if you don't want logging to happen. ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2003-01-08 22:49 Message: Logged In: YES user_id=675094 using the version released 2003-01-07 17:27, with DO_QMAIL_VERP = 0, any post to a list gets posted to all members properly, but also gets shunted. This happened because I didn't have QMAIL_LOG_EVERY_MESSAGE, QMAIL_LOG_SUCCESS, or QMAIL_LOG_FAILURE defined. Is the Email shunted, yet posted event supposed to happen? I'll be testing out VERP later on ---------------------------------------------------------------------- Comment By: Colin Palmer (tzs) Date: 2003-01-08 09:46 Message: Logged In: YES user_id=658762 Oops, should have been comparing it's function with 'SMTPDirect' as well as 'Sendmail'... this version should work a lot better. It doesn't support personalisation or mailman-generated VERP headers, but should do everything else now. Read the the comments at the top of the module for things that need to be in mm_cfg.py for it to work. ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2002-12-25 13:32 Message: Logged In: YES user_id=675094 Running as listed except DO_QMAIL_VERP = 0, messages don't appear to have the footer tacked on at the bottom. Everything else (header-wise) seems there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 From noreply at sourceforge.net Thu May 1 19:44:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 1 21:45:57 2003 Subject: [ mailman-Patches-731100 ] Postfix XVERP support for SMTPDirect.py Message-ID: Patches item #731100, was opened at 2003-05-02 13:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=731100&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix XVERP support for SMTPDirect.py Initial Comment: This patch adds support for Postfix's XVERP ESMTP extension for doing VERP on delivery instead of requiring Mailman to inject the message once per recipient when VERPing. This patch is against Mailman 2.1.2 To make it work, add: VERP_STYLE = 'Postfix' POSTFIX_XVERP_OPTS = '+=' to mm_cfg.py And to go back to Mailman's way of doing VERP, you can set VERP_STYLE = 'Mailman' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=731100&group_id=103 From noreply at sourceforge.net Sun May 4 15:58:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun May 4 17:59:01 2003 Subject: [ mailman-Bugs-732366 ] posting date on archive pages is wrong Message-ID: Bugs item #732366, was opened at 2003-05-04 21:58 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=732366&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: posting date on archive pages is wrong Initial Comment: The posting date/time shown near the top of archived messages is wrong and does not reflect the timezone in the Date; header of the posting. Only posting from within the same timezone as the MM server are rendered correctly. In the archives of lists where there are posts from users in multiple timezones this means that the archive order and juxtapostioning of postings is wrong. The problem is cause by a defect in the pipermail.Archive._set_date() function in $build/Mailman/Archive/pipermail.py The attached patch file, tz-2.1.2-0.1.patch, corrects the problem. It will be necessary to use $prefix/mailman/arch --wipe to fully correct existing archives. Apply the patch from within the MM build directory with following command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=732366&group_id=103 From noreply at sourceforge.net Sun May 4 16:57:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun May 4 18:57:29 2003 Subject: [ mailman-Bugs-732366 ] posting date on archive pages is wrong Message-ID: Bugs item #732366, was opened at 2003-05-04 21:58 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=732366&group_id=103 Category: Pipermail Group: 2.1 (stable) >Status: Deleted >Resolution: Invalid Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: posting date on archive pages is wrong Initial Comment: The posting date/time shown near the top of archived messages is wrong and does not reflect the timezone in the Date; header of the posting. Only posting from within the same timezone as the MM server are rendered correctly. In the archives of lists where there are posts from users in multiple timezones this means that the archive order and juxtapostioning of postings is wrong. The problem is cause by a defect in the pipermail.Archive._set_date() function in $build/Mailman/Archive/pipermail.py The attached patch file, tz-2.1.2-0.1.patch, corrects the problem. It will be necessary to use $prefix/mailman/arch --wipe to fully correct existing archives. Apply the patch from within the MM build directory with following command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-05-04 22:57 Message: Logged In: YES user_id=75166 This bug report is pure rubbish ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=732366&group_id=103 From noreply at sourceforge.net Sun May 4 17:38:02 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun May 4 19:38:07 2003 Subject: [ mailman-Bugs-732366 ] posting date on archive pages is wrong Message-ID: Bugs item #732366, was opened at 2003-05-04 21:58 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=732366&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Deleted Resolution: Invalid Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: posting date on archive pages is wrong Initial Comment: The posting date/time shown near the top of archived messages is wrong and does not reflect the timezone in the Date; header of the posting. Only posting from within the same timezone as the MM server are rendered correctly. In the archives of lists where there are posts from users in multiple timezones this means that the archive order and juxtapostioning of postings is wrong. The problem is cause by a defect in the pipermail.Archive._set_date() function in $build/Mailman/Archive/pipermail.py The attached patch file, tz-2.1.2-0.1.patch, corrects the problem. It will be necessary to use $prefix/mailman/arch --wipe to fully correct existing archives. Apply the patch from within the MM build directory with following command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-05-04 23:38 Message: Logged In: YES user_id=75166 No. It is no rubbish, just the orgianl patch to fix it. Hopefully, tz-2.1.2-0.2.patch does this biz. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-04 22:57 Message: Logged In: YES user_id=75166 This bug report is pure rubbish ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=732366&group_id=103 From noreply at sourceforge.net Sun May 4 17:38:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun May 4 19:38:58 2003 Subject: [ mailman-Bugs-732366 ] posting date on archive pages is wrong Message-ID: Bugs item #732366, was opened at 2003-05-04 21:58 Message generated for change (Settings changed) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=732366&group_id=103 Category: Pipermail Group: 2.1 (stable) >Status: Open Resolution: Invalid Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: posting date on archive pages is wrong Initial Comment: The posting date/time shown near the top of archived messages is wrong and does not reflect the timezone in the Date; header of the posting. Only posting from within the same timezone as the MM server are rendered correctly. In the archives of lists where there are posts from users in multiple timezones this means that the archive order and juxtapostioning of postings is wrong. The problem is cause by a defect in the pipermail.Archive._set_date() function in $build/Mailman/Archive/pipermail.py The attached patch file, tz-2.1.2-0.1.patch, corrects the problem. It will be necessary to use $prefix/mailman/arch --wipe to fully correct existing archives. Apply the patch from within the MM build directory with following command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-04 23:38 Message: Logged In: YES user_id=75166 No. It is no rubbish, just the orgianl patch to fix it. Hopefully, tz-2.1.2-0.2.patch does this biz. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-04 22:57 Message: Logged In: YES user_id=75166 This bug report is pure rubbish ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=732366&group_id=103 From noreply at sourceforge.net Mon May 5 10:55:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 5 12:56:04 2003 Subject: [ mailman-Patches-534577 ] Add SpamAssassin filter to mail pipeline Message-ID: Patches item #534577, was opened at 2002-03-25 02:17 Message generated for change (Comment added) made by phelim_gervase You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 1 Submitted By: James Henstridge (jhenstridge) Assigned to: Nobody/Anonymous (nobody) Summary: Add SpamAssassin filter to mail pipeline Initial Comment: This filter adds support for discarding or holding spam sent to the mailing list. It contacts a spamd daemon (from SpamAssassin -- http://spamassassin.taint.org) to score the message. If the score is above a certain threshold (default 10), the message is discarded and an entry is written to the vette log. If the score is above another lower threshold (default 5), the message is held for moderation. The SpamAssassin.py file should be installed in Mailman/Handlers/. The LIST_PIPELINE variable in Mailman/Handlers/HandlerAPI.py should be modified to include a 'SpamAssassin' item (I put it just after the existing 'SpamDetect' item). To change the defaults, the following can be added to the mm_cfg.py file: SPAMASSASSIN_HOST = 'host:port' # how to contact SA SPAMASSASSIN_DISCARD_SCORE = 10 SPAMASSASSIN_HOLD_SCORE = 5 If you don't want to discard messages, then DISCARD_SCORE can be set to something very high (1000 should do it). It looks the MM2.1 filter APIs have changed a bit, so this filter will need some modifications to work with that version. When I get round to upgrading, I might look into updating it. ---------------------------------------------------------------------- Comment By: Pug Bainter (phelim_gervase) Date: 2003-05-05 11:55 Message: Logged In: YES user_id=484284 After installing patch 668685 for the HTDig integration into Mailman 2.1.1, I started getting the following: May 02 16:50:34 2003 (23484) Uncaught runner exception: global name 'False' is not defined May 02 16:50:34 2003 (23484) Traceback (most recent call last): File "/var/mailman2/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/var/mailman2/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman2/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman2/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/mailman2/Mailman/Handlers/SpamAssassin.py", line 75, in process score, symbols = check_message(mlist, str(msg)) File "/var/mailman2/Mailman/Handlers/SpamAssassin.py", line 57, in check_message connection = spamd.SpamdConnection(SPAMD_HOST) File "/var/mailman2/Mailman/Handlers/spamd.py", line 79, in __init__ self.request_headers = mimetools.Message(StringIO.StringIO(), seekable=False) NameError: global name 'False' is not defined I corrected this by defining "False = 0" in spamd.py. I don't know what the "real" solution should be though. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2003-03-16 23:46 Message: Logged In: YES user_id=146903 Attached is an updated version of the filter for adding SpamAssassin support to mailman. This version is targetted at Mailman 2.1.x. The code for talking to spamd has been split out into a separate file, so that it can be updated independently of the Mailman specific code. It has also been updated to work with SpamAssassin 2.50 (and should be a lot more robust to future additions to the spamd protocol). The filter has also been changed to use the list name as the username passed to spamd, which means that separate auto-whitelists and bayes databases can be maintained for each list. Installation is trivial. Simply copy spamd.py and SpamAssassin.py to the Mailman/Handlers directory and add the following line to Mailman/mm_cfg.py: GLOBAL_PIPELINE.insert(1, 'SpamAssassin') ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 01:32 Message: Logged In: YES user_id=81797 That last one had a missing quote. Try this patch: *** SpamAssassin.py.orig Fri Aug 23 00:28:59 2002 --- SpamAssassin.py Fri Aug 23 00:31:00 2002 *************** *** 30,45 **** from Mailman.Logging.Syslog import syslog from Hold import hold_for_approval ! SPAMD_PORT = 0 ! try: ! SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST ! i = string.find(SPAMD_HOST, ':') ! if i >= 0: ! SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], host[i+1:] ! try: SPAMD_PORT = int(SPAMD_PORT) ! except: SPAMD_PORT = None ! except: ! SPAMD_HOST = 'localhost' if not SPAMD_PORT: SPAMD_PORT = 783 try: DISCARD_SCORE = mm_cfg.SPAMASSASSIN_DISCARD_SCORE --- 30,44 ---- from Mailman.Logging.Syslog import syslog from Hold import hold_for_approval ! SPAMD_HOST = 'localhost' ! SPAMD_PORT = None ! if hasattr(mm_cfg, 'SPAMASSASSIN_HOST'): ! SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST ! try: ! SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) ! SPAMD_PORT = int(SPAMD_PORT) ! except ValueError: ! SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 try: DISCARD_SCORE = mm_cfg.SPAMASSASSIN_DISCARD_SCORE Sean ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 01:19 Message: Logged In: YES user_id=81797 How about changing that chunk of code to: SPAMD_HOST = 'localhost' SPAMD_PORT = None if hasattr(mm_cfg, 'SPAMASSASSIN_HOST): SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST try: SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) SPAMD_PORT = int(SPAMD_PORT) except ValueError: SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 This gets rid of the "bare except"s, and I think it's a little clearer than the previous code. The ValueError will be tripped if the string doesn't have a : in it, or if the int coercion fails. Though perhaps in that instance you'd want to log an error or something... Sean ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 01:18 Message: Logged In: YES user_id=81797 How about changing that chunk of code to: SPAMD_HOST = 'localhost' SPAMD_PORT = None if hasattr(mm_cfg, 'SPAMASSASSIN_HOST): SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST try: SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) SPAMD_PORT = int(SPAMD_PORT) except ValueError: SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 This gets rid of the "bare except"s, and I think it's a little clearer than the previous code. The ValueError will be tripped if the string doesn't have a : in it, or if the int coercion fails. Though perhaps in that instance you'd want to log an error or something... Sean ---------------------------------------------------------------------- Comment By: dann frazier (dannf) Date: 2002-08-17 13:11 Message: Logged In: YES user_id=146718 hey James, found a typo. also wanted to point out: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=139942&repeatmerged=yes --- SpamAssassin.py.orig Sat Aug 17 12:05:41 2002 +++ SpamAssassin.py Sat Aug 17 12:06:13 2002 @@ -35,7 +35,7 @@ SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST i = string.find(SPAMD_HOST, ':') if i >= 0: - SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], host[i+1:] + SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], SPAMD_HOST[i+1:] try: SPAMD_PORT = int(SPAMD_PORT) except: SPAMD_PORT = None except: ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-25 04:00 Message: Logged In: YES user_id=146903 remembering to check the "upload file" checkbox this time ... ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-25 03:59 Message: Logged In: YES user_id=146903 Yet another new version that fixes a small typo. With previous messages, you couldn't approve messages that had been identified as spam once (they would get identified again when the queue got processed, instead of passing the message through). ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-09 19:19 Message: Logged In: YES user_id=146903 The Mailman installation on mail.gnome.org also uses this filter. I don't think there are any stability problems with the filter. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-07-09 16:16 Message: Logged In: YES user_id=81797 FYI, I ran the previous version since installation and it seemed to work fine. I didn't run into any problems, with probably 500 messages handled. I've updated to the new version and it seems ok so far, but I've only sent about 10 messages through. Sean ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-02 23:02 Message: Logged In: YES user_id=146903 Yet another version. There were some bugs in handling of certain error conditions when talking to spamd. These would result in exceptions and the messages staying in the delivery queue :( With the new version, the message will be passed through unchecked under these conditions, and a message will be added to the error log. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-06-12 16:48 Message: Logged In: YES user_id=81797 FYI: I've been running the 2002-05-14 version of this patch with spamassassin 2.20 for the last day on our main mailman box and it seems to be working great. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-05-14 01:04 Message: Logged In: YES user_id=146903 This version is essentially the same as the previous version, but adds compatibility with python > 1.5.2, which doesn't like you passing two arguments to socket.connect(). ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-04-27 01:17 Message: Logged In: YES user_id=146903 Just attached my updated version of the patch. This version requires SpamAssassin 2.20 (for the extra commands that the spamd daemon understands). It now displays a list of which rules were triggered for held messages, and can give messages from list members a bonus (defaults to 2), so that they are less likely to get held as spam. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-03-25 19:21 Message: Logged In: YES user_id=146903 There is a fairly easy optimisation for this filter that I missed when writing it. It calls str() on the message object twice. It would be quicker to call str() on the message once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 From noreply at sourceforge.net Mon May 5 21:31:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 5 23:31:27 2003 Subject: [ mailman-Patches-534577 ] Add SpamAssassin filter to mail pipeline Message-ID: Patches item #534577, was opened at 2002-03-25 16:17 Message generated for change (Comment added) made by jhenstridge You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 1 Submitted By: James Henstridge (jhenstridge) Assigned to: Nobody/Anonymous (nobody) Summary: Add SpamAssassin filter to mail pipeline Initial Comment: This filter adds support for discarding or holding spam sent to the mailing list. It contacts a spamd daemon (from SpamAssassin -- http://spamassassin.taint.org) to score the message. If the score is above a certain threshold (default 10), the message is discarded and an entry is written to the vette log. If the score is above another lower threshold (default 5), the message is held for moderation. The SpamAssassin.py file should be installed in Mailman/Handlers/. The LIST_PIPELINE variable in Mailman/Handlers/HandlerAPI.py should be modified to include a 'SpamAssassin' item (I put it just after the existing 'SpamDetect' item). To change the defaults, the following can be added to the mm_cfg.py file: SPAMASSASSIN_HOST = 'host:port' # how to contact SA SPAMASSASSIN_DISCARD_SCORE = 10 SPAMASSASSIN_HOLD_SCORE = 5 If you don't want to discard messages, then DISCARD_SCORE can be set to something very high (1000 should do it). It looks the MM2.1 filter APIs have changed a bit, so this filter will need some modifications to work with that version. When I get round to upgrading, I might look into updating it. ---------------------------------------------------------------------- >Comment By: James Henstridge (jhenstridge) Date: 2003-05-06 11:31 Message: Logged In: YES user_id=146903 I have just attached updated versions of the patches (dated 06/05/2003). These versions include a number of bug fixes that I have been testing locally for a while. I also added a similar workaround for the True/False usage (the True and False constants were only added in Python 2.2.1 and 2.3a). This version also puts the SpamAssassin score in the "reason" for held messages, which means you can easily see the scores of messages in the new Mailman 2.1 moderation overview page. I have also put together some documentation on the Mailman setup I use: http://www.daa.com.au/~james/articles/mailman-spamassassin/ This includes information on how to set up an unprivileged spamd that maintains separate Bayes databases for each mailing list. ---------------------------------------------------------------------- Comment By: Pug Bainter (phelim_gervase) Date: 2003-05-06 00:55 Message: Logged In: YES user_id=484284 After installing patch 668685 for the HTDig integration into Mailman 2.1.1, I started getting the following: May 02 16:50:34 2003 (23484) Uncaught runner exception: global name 'False' is not defined May 02 16:50:34 2003 (23484) Traceback (most recent call last): File "/var/mailman2/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/var/mailman2/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman2/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman2/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/mailman2/Mailman/Handlers/SpamAssassin.py", line 75, in process score, symbols = check_message(mlist, str(msg)) File "/var/mailman2/Mailman/Handlers/SpamAssassin.py", line 57, in check_message connection = spamd.SpamdConnection(SPAMD_HOST) File "/var/mailman2/Mailman/Handlers/spamd.py", line 79, in __init__ self.request_headers = mimetools.Message(StringIO.StringIO(), seekable=False) NameError: global name 'False' is not defined I corrected this by defining "False = 0" in spamd.py. I don't know what the "real" solution should be though. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2003-03-17 13:46 Message: Logged In: YES user_id=146903 Attached is an updated version of the filter for adding SpamAssassin support to mailman. This version is targetted at Mailman 2.1.x. The code for talking to spamd has been split out into a separate file, so that it can be updated independently of the Mailman specific code. It has also been updated to work with SpamAssassin 2.50 (and should be a lot more robust to future additions to the spamd protocol). The filter has also been changed to use the list name as the username passed to spamd, which means that separate auto-whitelists and bayes databases can be maintained for each list. Installation is trivial. Simply copy spamd.py and SpamAssassin.py to the Mailman/Handlers directory and add the following line to Mailman/mm_cfg.py: GLOBAL_PIPELINE.insert(1, 'SpamAssassin') ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 14:32 Message: Logged In: YES user_id=81797 That last one had a missing quote. Try this patch: *** SpamAssassin.py.orig Fri Aug 23 00:28:59 2002 --- SpamAssassin.py Fri Aug 23 00:31:00 2002 *************** *** 30,45 **** from Mailman.Logging.Syslog import syslog from Hold import hold_for_approval ! SPAMD_PORT = 0 ! try: ! SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST ! i = string.find(SPAMD_HOST, ':') ! if i >= 0: ! SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], host[i+1:] ! try: SPAMD_PORT = int(SPAMD_PORT) ! except: SPAMD_PORT = None ! except: ! SPAMD_HOST = 'localhost' if not SPAMD_PORT: SPAMD_PORT = 783 try: DISCARD_SCORE = mm_cfg.SPAMASSASSIN_DISCARD_SCORE --- 30,44 ---- from Mailman.Logging.Syslog import syslog from Hold import hold_for_approval ! SPAMD_HOST = 'localhost' ! SPAMD_PORT = None ! if hasattr(mm_cfg, 'SPAMASSASSIN_HOST'): ! SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST ! try: ! SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) ! SPAMD_PORT = int(SPAMD_PORT) ! except ValueError: ! SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 try: DISCARD_SCORE = mm_cfg.SPAMASSASSIN_DISCARD_SCORE Sean ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 14:19 Message: Logged In: YES user_id=81797 How about changing that chunk of code to: SPAMD_HOST = 'localhost' SPAMD_PORT = None if hasattr(mm_cfg, 'SPAMASSASSIN_HOST): SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST try: SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) SPAMD_PORT = int(SPAMD_PORT) except ValueError: SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 This gets rid of the "bare except"s, and I think it's a little clearer than the previous code. The ValueError will be tripped if the string doesn't have a : in it, or if the int coercion fails. Though perhaps in that instance you'd want to log an error or something... Sean ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-08-23 14:18 Message: Logged In: YES user_id=81797 How about changing that chunk of code to: SPAMD_HOST = 'localhost' SPAMD_PORT = None if hasattr(mm_cfg, 'SPAMASSASSIN_HOST): SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST try: SPAMD_HOST, SPAMD_PORT = string.split(SPAMD_HOST, ':', 1) SPAMD_PORT = int(SPAMD_PORT) except ValueError: SPAMD_PORT = None if not SPAMD_PORT: SPAMD_PORT = 783 This gets rid of the "bare except"s, and I think it's a little clearer than the previous code. The ValueError will be tripped if the string doesn't have a : in it, or if the int coercion fails. Though perhaps in that instance you'd want to log an error or something... Sean ---------------------------------------------------------------------- Comment By: dann frazier (dannf) Date: 2002-08-18 02:11 Message: Logged In: YES user_id=146718 hey James, found a typo. also wanted to point out: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=139942&repeatmerged=yes --- SpamAssassin.py.orig Sat Aug 17 12:05:41 2002 +++ SpamAssassin.py Sat Aug 17 12:06:13 2002 @@ -35,7 +35,7 @@ SPAMD_HOST = mm_cfg.SPAMASSASSIN_HOST i = string.find(SPAMD_HOST, ':') if i >= 0: - SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], host[i+1:] + SPAMD_HOST, SPAMD_PORT = SPAMD_HOST[:i], SPAMD_HOST[i+1:] try: SPAMD_PORT = int(SPAMD_PORT) except: SPAMD_PORT = None except: ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-25 17:00 Message: Logged In: YES user_id=146903 remembering to check the "upload file" checkbox this time ... ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-25 16:59 Message: Logged In: YES user_id=146903 Yet another new version that fixes a small typo. With previous messages, you couldn't approve messages that had been identified as spam once (they would get identified again when the queue got processed, instead of passing the message through). ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-10 08:19 Message: Logged In: YES user_id=146903 The Mailman installation on mail.gnome.org also uses this filter. I don't think there are any stability problems with the filter. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-07-10 05:16 Message: Logged In: YES user_id=81797 FYI, I ran the previous version since installation and it seemed to work fine. I didn't run into any problems, with probably 500 messages handled. I've updated to the new version and it seems ok so far, but I've only sent about 10 messages through. Sean ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-07-03 12:02 Message: Logged In: YES user_id=146903 Yet another version. There were some bugs in handling of certain error conditions when talking to spamd. These would result in exceptions and the messages staying in the delivery queue :( With the new version, the message will be passed through unchecked under these conditions, and a message will be added to the error log. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-06-13 05:48 Message: Logged In: YES user_id=81797 FYI: I've been running the 2002-05-14 version of this patch with spamassassin 2.20 for the last day on our main mailman box and it seems to be working great. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-05-14 14:04 Message: Logged In: YES user_id=146903 This version is essentially the same as the previous version, but adds compatibility with python > 1.5.2, which doesn't like you passing two arguments to socket.connect(). ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-04-27 14:17 Message: Logged In: YES user_id=146903 Just attached my updated version of the patch. This version requires SpamAssassin 2.20 (for the extra commands that the spamd daemon understands). It now displays a list of which rules were triggered for held messages, and can give messages from list members a bonus (defaults to 2), so that they are less likely to get held as spam. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-03-26 09:21 Message: Logged In: YES user_id=146903 There is a fairly easy optimisation for this filter that I missed when writing it. It calls str() on the message object twice. It would be quicker to call str() on the message once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 From noreply at sourceforge.net Tue May 6 06:49:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue May 6 08:49:56 2003 Subject: [ mailman-Bugs-733243 ] Subject and attachement corrupt if longer than 72 characters Message-ID: Bugs item #733243, was opened at 2003-05-06 12:49 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=733243&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 and attachement corrupt if longer than 72 characters Initial Comment: If the mailing list message contains a subject longer than 72 charactes, the subject is splitted into two lines with a tab characters. This behaviour looks strange on some e-mail clients. If an attachement has spaces in its name and the name of the attachment is longer than 72 characters, the attachment type (e.g. PDF) is lost and the e-mail contains only an unnamed attachement. Attached is a (sample) message containing such a problem. The correct name of the first attachment is: "CTL Germany Info 0118 - COSMOS v2.3 - Planned functions and delivery date.pdf". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=733243&group_id=103 From noreply at sourceforge.net Fri May 9 08:47:01 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri May 9 10:47:09 2003 Subject: [ mailman-Bugs-572822 ] real_name attribute not changed Message-ID: Bugs item #572822, was opened at 2002-06-23 18:02 Message generated for change (Comment added) made by mike_laborde You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=572822&group_id=103 Category: configuring/installing Group: 2.0.x Status: Closed Resolution: Works For Me Priority: 5 Submitted By: Christine Charity (ccharity) Assigned to: Nobody/Anonymous (nobody) Summary: real_name attribute not changed Initial Comment: When trying to change the name of a mailing list from MAILINGLISTNAME to mailinglistname (lowercase) the following error is returned: real_name attribute not changed! It must differ from the list's name by case only. ---------------------------------------------------------------------- Comment By: Mike Laborde (mike_laborde) Date: 2003-05-09 14:47 Message: Logged In: YES user_id=775299 Well, it does not work for MANY people. We just want ot change the case of the list name like we are supposed to be able to do. Please help... ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-26 03:51 Message: Logged In: YES user_id=12800 Works okay for me in MM 2.0.12 and 2.1cvs. Are you sure you didn't accidently add a space to the end of the new name? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=572822&group_id=103 From noreply at sourceforge.net Sun May 11 18:10:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun May 11 20:10:53 2003 Subject: [ mailman-Patches-664209 ] best effort to keep text/plain Message-ID: Patches item #664209, was opened at 2003-01-08 06:14 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None >Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: best effort to keep text/plain Initial Comment: When a message come in different charset than list specific one, Decorate.py adds the header and footer in mime attatchments. This patch tries to keep the good-old plain text format by making these texts into unicode and encode in list preferred charset. If it fails, the messages will get mime-multiparted as was the case without this patch. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-05-12 00:10 Message: Logged In: YES user_id=67709 If you personalize delivery, i18n user name cause error because the name is stored in unicode. I merge this fix into this Decorate.py.patch.txt ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-20 11:42 Message: Logged In: YES user_id=67709 Sorry, there was a error in the previous patch. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-20 01:24 Message: Logged In: YES user_id=67709 Refine the code and increment priority. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-08 07:34 Message: Logged In: YES user_id=67709 Expand this patch to base64 encoded plain text. apply the second patch Decorate.py.diff2 to the original Decorate.py ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 From noreply at sourceforge.net Sun May 11 22:08:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 12 00:08:56 2003 Subject: [ mailman-Bugs-730769 ] template access hierarchy is broken Message-ID: Bugs item #730769, was opened at 2003-05-01 09:24 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730769&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 8 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: template access hierarchy is broken Initial Comment: The quick_maketext()function in HyperArch.py uses a caching scheme for templates extracted from one of the four possible sources of templates, i.e. general, site, domain and list specific templates. The caching scheme is broken because the key to the cache only uses the name of the template file and the language. Thus once a a file for a given langauge has been cached, regardless of which of the sources it was obtained from, it is that template that is used by all lists, regardless of the existence of a template in a preferred source for that particular list. The attached patch fixes this problem. Apply the patch with the MM build directory as current working directory using the command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-05-12 00:08 Message: Logged In: YES user_id=12800 Do we need two caches? Isn't the important point here that the listname be included in the cache key? If so, maybe we just need one cache that maps (templatefile, lang, listname) to the template text. If you agree, please rework the patch accordingly. Also, rename Utils.real_maketext() to Utils.findtext() and change call sites accordingly. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-01 11:09 Message: Logged In: YES user_id=75166 After doing some furehtr (proper) testing I hope version 2 of the patch will solve the problem ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-01 10:00 Message: Logged In: YES user_id=75166 And do not forget to mailmanctl restart after applying the patch! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730769&group_id=103 From noreply at sourceforge.net Sun May 11 22:11:04 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 12 00:11:16 2003 Subject: [ mailman-Bugs-723123 ] Runs out of memory on larger (5M) messages. Message-ID: Bugs item #723123, was opened at 2003-04-17 09:20 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=723123&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 9 Submitted By: Steve Mertz (xerouz) Assigned to: Nobody/Anonymous (nobody) Summary: Runs out of memory on larger (5M) messages. Initial Comment: When trying to send an email with a 5M attachment, Mailman seems to run out of memory. On the console I get: marcos:mailman {106} Traceback (most recent call last): File "/usr/local/mailman/bin/qrunner", line 270, in ? main() File "/usr/local/mailman/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman/Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._shunt.enqueue(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 91, in enqueue msgsave = cPickle.dumps(_msg, 1) MemoryError: out of memory The system is: OpenBSD 3.1, with 512M ram. Mailman version 2.1.1 It would be nice to be able to have large attachments as I want to use this for my company's support email which quite often has larger than 10M files attached. Thanks, -- Steve ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-05-12 00:11 Message: Logged In: YES user_id=12800 This is going to be a difficult one Steve. The problem is that too much of Mailman wants to keep the message in memory, starting from the email package. I'm not sure what the best approach is, but it's probably going to include stripping out large attachements and not carrying them around during processing. ---------------------------------------------------------------------- Comment By: Steve Mertz (xerouz) Date: 2003-04-24 11:08 Message: Logged In: YES user_id=61424 Now, I'm getting errors in of a different kind: Apr 24 10:03:18 2003 (22458) Uncaught runner exception: out of memory Apr 24 10:03:18 2003 (22458) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 71, in process g.flatten(msg, unixfrom=1) File "/usr/local/mailman/pythonlib/email/Generator.py", line 100, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 128, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 154, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 267, in _handle_multipart print >> self._fp, '\n--' + boundary + '--', MemoryError: out of memory Apr 24 10:03:18 2003 (22458) SHUNTING: 1051196594.0123+3c7e0d1a0cd1e29359dea6cc2bb51307e06ad0df ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=723123&group_id=103 From noreply at sourceforge.net Sun May 11 22:12:16 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 12 00:12:20 2003 Subject: [ mailman-Bugs-733243 ] Subject and attachement corrupt if longer than 72 characters Message-ID: Bugs item #733243, was opened at 2003-05-06 08:49 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=733243&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Swen Haubold (swen_haubold) Assigned to: Nobody/Anonymous (nobody) Summary: Subject and attachement corrupt if longer than 72 characters Initial Comment: If the mailing list message contains a subject longer than 72 charactes, the subject is splitted into two lines with a tab characters. This behaviour looks strange on some e-mail clients. If an attachement has spaces in its name and the name of the attachment is longer than 72 characters, the attachment type (e.g. PDF) is lost and the e-mail contains only an unnamed attachement. Attached is a (sample) message containing such a problem. The correct name of the first attachment is: "CTL Germany Info 0118 - COSMOS v2.3 - Planned functions and delivery date.pdf". ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-05-12 00:12 Message: Logged In: YES user_id=12800 I believe this bug is fixed in Mailman 2.1.2. Please upgrade and re-open if your bug is not fixed (remember to restart mailmanctl after the upgrade). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=733243&group_id=103 From noreply at sourceforge.net Sun May 11 22:25:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 12 00:25:58 2003 Subject: [ mailman-Bugs-732366 ] posting date on archive pages is wrong Message-ID: Bugs item #732366, was opened at 2003-05-04 17:58 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=732366&group_id=103 Category: Pipermail Group: 2.1 (stable) >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: posting date on archive pages is wrong Initial Comment: The posting date/time shown near the top of archived messages is wrong and does not reflect the timezone in the Date; header of the posting. Only posting from within the same timezone as the MM server are rendered correctly. In the archives of lists where there are posts from users in multiple timezones this means that the archive order and juxtapostioning of postings is wrong. The problem is cause by a defect in the pipermail.Archive._set_date() function in $build/Mailman/Archive/pipermail.py The attached patch file, tz-2.1.2-0.1.patch, corrects the problem. It will be necessary to use $prefix/mailman/arch --wipe to fully correct existing archives. Apply the patch from within the MM build directory with following command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-04 19:38 Message: Logged In: YES user_id=75166 No. It is no rubbish, just the orgianl patch to fix it. Hopefully, tz-2.1.2-0.2.patch does this biz. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-04 18:57 Message: Logged In: YES user_id=75166 This bug report is pure rubbish ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=732366&group_id=103 From noreply at sourceforge.net Sun May 11 22:32:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 12 00:32:48 2003 Subject: [ mailman-Bugs-730814 ] HTML stripped regardless of filters Message-ID: Bugs item #730814, was opened at 2003-05-01 11:18 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730814&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Charles Hall (hallcp) Assigned to: Nobody/Anonymous (nobody) Summary: HTML stripped regardless of filters Initial Comment: If I enable "content-filtering", HTML is a;ways stripped out regardless of my other filter settings. I have tried to track this down and it appears that MimeDel.py is collapsing ALL multi-part emails to a single component. This leaves the plain text but strips off the HTML flavored portion. If I disable content-filtering, MimeDel is neutralized and HTML email works OK. The suspect function is "collapse_multipart_alternatives". FYI: my test emails were sent from Outlook. I posted and emailed to others on the Users mailing list, but no one responded that they have gotten filtering to work either. This looks like a real nice feature. I hope you guys can fix it. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-05-12 00:32 Message: Logged In: YES user_id=12800 When you say "collapsing ALLmulti-part emails to a single component", I think you mean all multipart/alternatives. If so, this is documented behavior. Now, it may not be /desired/ behavior, but that's a different issue. I would move this to feature requests to allow you to configure whether multipart/alternatives are collapsed or not. Please follow up here and let me know if I'm correct or not. If there are other problems with content filtering from mailman-users, please submit bug reports on each indivdiually. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730814&group_id=103 From noreply at sourceforge.net Sun May 11 23:38:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 12 01:40:43 2003 Subject: [ mailman-Bugs-730405 ] NNTP -> Mail ignores filter_mime_types Message-ID: Bugs item #730405, was opened at 2003-04-30 16:06 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730405&group_id=103 Category: nntp/news Group: 2.1 (stable) >Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: Matthias Andree (m-a) Assigned to: Nobody/Anonymous (nobody) Summary: NNTP -> Mail ignores filter_mime_types Initial Comment: I have configured filter_mime_types to include text/html, otherwise, I left the 2.1.2 defaults unchanged. When I send a mail with HTML and plain text (multipart/alternative) as mail to the list, the HTML part gets stripped out properly, leaving a text/plain mail behind. If I post a mixed HTML/plain mail to the newsgroup, the text/html part remains in the mail that gets forwarded into the list. I would like to have the text/html part removed also when the mail is pulled in via NNTP (seems I'll have to make the mail <-> news gateway one-way and only allow mail -> news, but not the other way around). I cannot provide a patch (unacquainted with both Python and Mailman code), but I will test patches sent my way or attached to this tracker item, time permitting (allow me some days for testing). Thanks in advance. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-05-12 01:38 Message: Logged In: YES user_id=12800 Works for me in 2.1.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730405&group_id=103 From noreply at sourceforge.net Mon May 12 08:11:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 12 10:11:44 2003 Subject: [ mailman-Bugs-730814 ] HTML stripped regardless of filters Message-ID: Bugs item #730814, was opened at 2003-05-01 15:18 Message generated for change (Comment added) made by hallcp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730814&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Charles Hall (hallcp) Assigned to: Nobody/Anonymous (nobody) Summary: HTML stripped regardless of filters Initial Comment: If I enable "content-filtering", HTML is a;ways stripped out regardless of my other filter settings. I have tried to track this down and it appears that MimeDel.py is collapsing ALL multi-part emails to a single component. This leaves the plain text but strips off the HTML flavored portion. If I disable content-filtering, MimeDel is neutralized and HTML email works OK. The suspect function is "collapse_multipart_alternatives". FYI: my test emails were sent from Outlook. I posted and emailed to others on the Users mailing list, but no one responded that they have gotten filtering to work either. This looks like a real nice feature. I hope you guys can fix it. ---------------------------------------------------------------------- >Comment By: Charles Hall (hallcp) Date: 2003-05-12 14:11 Message: Logged In: YES user_id=747417 Barry, thanks for the comment. You may be correct. I was sending email with a plain/text and text/html component. If I understand you, this feature was designed to selectively filter "EXE" or "ZIP" attachments, not HTML vs plaintext. Can you point me to the docs on this? And how do I convert this bug to a feature request? Or do I just delete? (Can I?). Thanks again for the info. Charles. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-05-12 04:32 Message: Logged In: YES user_id=12800 When you say "collapsing ALLmulti-part emails to a single component", I think you mean all multipart/alternatives. If so, this is documented behavior. Now, it may not be /desired/ behavior, but that's a different issue. I would move this to feature requests to allow you to configure whether multipart/alternatives are collapsed or not. Please follow up here and let me know if I'm correct or not. If there are other problems with content filtering from mailman-users, please submit bug reports on each indivdiually. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730814&group_id=103 From noreply at sourceforge.net Mon May 12 08:11:10 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 12 10:21:21 2003 Subject: [ mailman-Bugs-730769 ] template access hierarchy is broken Message-ID: Bugs item #730769, was opened at 2003-05-01 13:24 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730769&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 8 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: template access hierarchy is broken Initial Comment: The quick_maketext()function in HyperArch.py uses a caching scheme for templates extracted from one of the four possible sources of templates, i.e. general, site, domain and list specific templates. The caching scheme is broken because the key to the cache only uses the name of the template file and the language. Thus once a a file for a given langauge has been cached, regardless of which of the sources it was obtained from, it is that template that is used by all lists, regardless of the existence of a template in a preferred source for that particular list. The attached patch fixes this problem. Apply the patch with the MM build directory as current working directory using the command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-05-12 14:11 Message: Logged In: YES user_id=75166 My first reaction to fixing the problem was as bwarsaw suggests, just add the list name to the cache key. On consideration I decided the use of a two level cache is a justified and trivial complication. The top level cache maps (filename, lang, listname) -> filepath, potentially a many -> one mapping. The second level cache maps filepath -> filecontent, always a one -> one mapping. A single level cache would map (filename, lang, listname) -> filecontent, always a one -> one mapping, which would lead to multiple copies of the same template file content data being held in memory when multiple lists use the same template; arguably the norm on Mailman installations. Take my case of 460 lists using the same default English language templates. This waste of storage is trivially avoidable with the second cache dictionary. I have updated the patch to tcache-2.1.2-0.3.patch, which introduces the change in function name from Utils.real_maketext to Utils.findtext and propagates that change as necessary. Footnotes: The approach adopted is safe as HyperArch.quick_maketext () always calls Utils.findtext() with dict=None so that Utils.findtext() does no characterisation of the template content; this being deferred until HyperArch.quick_maketext() acts on the cache content. When multiple lists use the same template file, its contents will be re-acquired the first time each list first seeks to use it. This latter is a relatively minor inefficency which I thought preferable to more radical changes in the original Utils.maketext function to separate the path determination and file content acquisition aspects of its behaviour into different functions. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-05-12 04:08 Message: Logged In: YES user_id=12800 Do we need two caches? Isn't the important point here that the listname be included in the cache key? If so, maybe we just need one cache that maps (templatefile, lang, listname) to the template text. If you agree, please rework the patch accordingly. Also, rename Utils.real_maketext() to Utils.findtext() and change call sites accordingly. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-01 15:09 Message: Logged In: YES user_id=75166 After doing some furehtr (proper) testing I hope version 2 of the patch will solve the problem ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-01 14:00 Message: Logged In: YES user_id=75166 And do not forget to mailmanctl restart after applying the patch! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730769&group_id=103 From noreply at sourceforge.net Mon May 12 08:35:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 12 10:35:48 2003 Subject: [ mailman-Feature Requests-730814 ] HTML stripped regardless of filters Message-ID: Feature Requests item #730814, was opened at 2003-05-01 11:18 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=730814&group_id=103 >Category: None >Group: None Status: Open Resolution: None Priority: 5 Submitted By: Charles Hall (hallcp) Assigned to: Nobody/Anonymous (nobody) Summary: HTML stripped regardless of filters Initial Comment: If I enable "content-filtering", HTML is a;ways stripped out regardless of my other filter settings. I have tried to track this down and it appears that MimeDel.py is collapsing ALL multi-part emails to a single component. This leaves the plain text but strips off the HTML flavored portion. If I disable content-filtering, MimeDel is neutralized and HTML email works OK. The suspect function is "collapse_multipart_alternatives". FYI: my test emails were sent from Outlook. I posted and emailed to others on the Users mailing list, but no one responded that they have gotten filtering to work either. This looks like a real nice feature. I hope you guys can fix it. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-05-12 10:35 Message: Logged In: YES user_id=12800 If you go to the content filtering page in the admin u/i and read the category's descriptive paragraph, you'll see where the m/a collapsing behavior is defined. I'm not sure if you can convert this bug to a feature request, so I'll do it for you! ---------------------------------------------------------------------- Comment By: Charles Hall (hallcp) Date: 2003-05-12 10:11 Message: Logged In: YES user_id=747417 Barry, thanks for the comment. You may be correct. I was sending email with a plain/text and text/html component. If I understand you, this feature was designed to selectively filter "EXE" or "ZIP" attachments, not HTML vs plaintext. Can you point me to the docs on this? And how do I convert this bug to a feature request? Or do I just delete? (Can I?). Thanks again for the info. Charles. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-05-12 00:32 Message: Logged In: YES user_id=12800 When you say "collapsing ALLmulti-part emails to a single component", I think you mean all multipart/alternatives. If so, this is documented behavior. Now, it may not be /desired/ behavior, but that's a different issue. I would move this to feature requests to allow you to configure whether multipart/alternatives are collapsed or not. Please follow up here and let me know if I'm correct or not. If there are other problems with content filtering from mailman-users, please submit bug reports on each indivdiually. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=730814&group_id=103 From noreply at sourceforge.net Mon May 12 09:20:35 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 12 11:20:42 2003 Subject: [ mailman-Bugs-730769 ] template access hierarchy is broken Message-ID: Bugs item #730769, was opened at 2003-05-01 09:24 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730769&group_id=103 Category: Pipermail Group: 2.1 (stable) >Status: Closed >Resolution: Accepted Priority: 8 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: template access hierarchy is broken Initial Comment: The quick_maketext()function in HyperArch.py uses a caching scheme for templates extracted from one of the four possible sources of templates, i.e. general, site, domain and list specific templates. The caching scheme is broken because the key to the cache only uses the name of the template file and the language. Thus once a a file for a given langauge has been cached, regardless of which of the sources it was obtained from, it is that template that is used by all lists, regardless of the existence of a template in a preferred source for that particular list. The attached patch fixes this problem. Apply the patch with the MM build directory as current working directory using the command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-05-12 11:20 Message: Logged In: YES user_id=12800 Accepted, with minor stylistic modifications. Thanks! ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-12 10:11 Message: Logged In: YES user_id=75166 My first reaction to fixing the problem was as bwarsaw suggests, just add the list name to the cache key. On consideration I decided the use of a two level cache is a justified and trivial complication. The top level cache maps (filename, lang, listname) -> filepath, potentially a many -> one mapping. The second level cache maps filepath -> filecontent, always a one -> one mapping. A single level cache would map (filename, lang, listname) -> filecontent, always a one -> one mapping, which would lead to multiple copies of the same template file content data being held in memory when multiple lists use the same template; arguably the norm on Mailman installations. Take my case of 460 lists using the same default English language templates. This waste of storage is trivially avoidable with the second cache dictionary. I have updated the patch to tcache-2.1.2-0.3.patch, which introduces the change in function name from Utils.real_maketext to Utils.findtext and propagates that change as necessary. Footnotes: The approach adopted is safe as HyperArch.quick_maketext () always calls Utils.findtext() with dict=None so that Utils.findtext() does no characterisation of the template content; this being deferred until HyperArch.quick_maketext() acts on the cache content. When multiple lists use the same template file, its contents will be re-acquired the first time each list first seeks to use it. This latter is a relatively minor inefficency which I thought preferable to more radical changes in the original Utils.maketext function to separate the path determination and file content acquisition aspects of its behaviour into different functions. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-05-12 00:08 Message: Logged In: YES user_id=12800 Do we need two caches? Isn't the important point here that the listname be included in the cache key? If so, maybe we just need one cache that maps (templatefile, lang, listname) to the template text. If you agree, please rework the patch accordingly. Also, rename Utils.real_maketext() to Utils.findtext() and change call sites accordingly. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-01 11:09 Message: Logged In: YES user_id=75166 After doing some furehtr (proper) testing I hope version 2 of the patch will solve the problem ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-01 10:00 Message: Logged In: YES user_id=75166 And do not forget to mailmanctl restart after applying the patch! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730769&group_id=103 From noreply at sourceforge.net Mon May 12 11:05:41 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon May 12 13:05:44 2003 Subject: [ mailman-Bugs-736559 ] Subject wrap with tab character Message-ID: Bugs item #736559, was opened at 2003-05-12 17:05 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=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" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=736559&group_id=103 From noreply at sourceforge.net Tue May 13 02:04:05 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue May 13 04:04:11 2003 Subject: [ mailman-Feature Requests-736895 ] temporary members, delivery disable on cc Message-ID: Feature Requests item #736895, was opened at 2003-05-13 16:04 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=736895&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Pabs (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: temporary members, delivery disable on cc Initial Comment: when lists are open to non-members - either through admin approval, orfully open it would be nice if mailman could then deliver the rest of the thread initiated by that non-member to that non-member. this would need some kind of password for the non-member to turn off delivery, and a way for admins to also do this. related to this would be the ability to turn off delivery to email addresses that are listed as bcc/cc/to on arrival, this would prevent people from recieving duplicate posts, especially usefull for people who are used to the old behaviour of mailman (no temp members), who cc by habit ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=736895&group_id=103 From noreply at sourceforge.net Tue May 13 19:36:59 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue May 13 21:37:09 2003 Subject: [ mailman-Patches-688410 ] better phrasing for listinfo page Message-ID: Patches item #688410, was opened at 2003-02-18 14:11 Message generated for change (Comment added) made by mbp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=688410&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: better phrasing for listinfo page Initial Comment: The default listinfo page says "please send questions or comments to foo-owner@bar.org". The problem with this is that people repeatedly think "oh, I'll send my Samba question to the mail administrator, rather than to the mailing list." This patch attempts to make it more clear that the administrator address is for problems with the lists themselves. It has dropped the number of misdirected mails on our high-traffic site from a couple per week to almost zero. ---------------------------------------------------------------------- >Comment By: Martin Pool (mbp) Date: 2003-05-14 11:36 Message: Logged In: YES user_id=521 Please apply this. We continue to get people who misunderstand this text and send random questions to the postmaster. Yes, those people are pretty dumb (or more charitably, not good with English.) But it would be nice to make a simple change that avoided the problem. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2003-03-11 12:14 Message: Logged In: YES user_id=521 Here's the patch. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2003-03-11 11:38 Message: Logged In: YES user_id=521 Oops, I'll post it. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 00:57 Message: Logged In: YES user_id=34209 There's no attached patch. Are you sure you clicked the 'Check to Ipload and Attach File' box ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=688410&group_id=103 From noreply at sourceforge.net Wed May 14 21:04:30 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed May 14 23:04:38 2003 Subject: [ mailman-Patches-688410 ] better phrasing for listinfo page Message-ID: Patches item #688410, was opened at 2003-02-17 22:11 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=688410&group_id=103 Category: Web UI Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: better phrasing for listinfo page Initial Comment: The default listinfo page says "please send questions or comments to foo-owner@bar.org". The problem with this is that people repeatedly think "oh, I'll send my Samba question to the mail administrator, rather than to the mailing list." This patch attempts to make it more clear that the administrator address is for problems with the lists themselves. It has dropped the number of misdirected mails on our high-traffic site from a couple per week to almost zero. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2003-05-13 21:36 Message: Logged In: YES user_id=521 Please apply this. We continue to get people who misunderstand this text and send random questions to the postmaster. Yes, those people are pretty dumb (or more charitably, not good with English.) But it would be nice to make a simple change that avoided the problem. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2003-03-10 20:14 Message: Logged In: YES user_id=521 Here's the patch. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2003-03-10 19:38 Message: Logged In: YES user_id=521 Oops, I'll post it. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 08:57 Message: Logged In: YES user_id=34209 There's no attached patch. Are you sure you clicked the 'Check to Ipload and Attach File' box ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=688410&group_id=103 From noreply at sourceforge.net Fri May 16 15:59:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri May 16 17:59:29 2003 Subject: [ mailman-Bugs-728847 ] 2.1.2 Messages.Py Message-ID: Bugs item #728847, was opened at 2003-04-28 07:25 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=728847&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: David English (engush) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.2 Messages.Py Initial Comment: Fix: Edit line 205 of Messages.py add ) and remove line 206 "errors='replace')" otherwise the following error occurs when creating a new list: lostris:/usr/local/mailman/bin# ./newlist test Enter the email of the person running the list: blah@blah.org Initial test password: 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: ## test mailing list test: "|/usr/local/mailman/mail/mailman post test" test-admin: "|/usr/local/mailman/mail/mailman admin test" test-bounces: "|/usr/local/mailman/mail/mailman bounces test" test-confirm: "|/usr/local/mailman/mail/mailman confirm test" test-join: "|/usr/local/mailman/mail/mailman join test" test-leave: "|/usr/local/mailman/mail/mailman leave test" test-owner: "|/usr/local/mailman/mail/mailman owner test" test-request: "|/usr/local/mailman/mail/mailman request test" test-subscribe: "|/usr/local/mailman/mail/mailman subscribe test" test-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe test" Hit enter to notify test owner... Traceback (most recent call last): File "./newlist", line 219, in ? main() File "./newlist", line 211, in main text, mlist.preferred_language) File "/usr/local/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' lostris:/usr/local/mailman/bin# ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-05-16 17:59 Message: Logged In: YES user_id=12800 Something's wrong with your installation -- perhaps you only partially updated? Mailman 2.1.2 should come with email 2.5.2 and its Header class __init__() does indeed take an errors argument. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=728847&group_id=103 From noreply at sourceforge.net Sat May 17 11:42:04 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat May 17 13:42:15 2003 Subject: [ mailman-Patches-601117 ] add sequencial number in subject prefix Message-ID: Patches item #601117, was opened at 2002-08-28 00:07 Message generated for change (Comment added) made by jojoba2 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add sequencial number in subject prefix Initial Comment: This patch for 'CookHeaders.py' add an ability to add a sequencial number in the subject prefix. You can define a subject prefix like: [listname %d] Then, the subject line of delivered mail becomes: Subject: [listname 123] Hoge hoge When someone replied this mail, mailman receives a messages with: Subject: Re: [listname 123] Hoge hoge Then, this patch removes [listname \d+] part and deliver it with: Subject: [listname 124] Re: Hoge hoge And next, another person replies with Subject: Re: [listname 124] Re: Hoge hoge Then, (magically!) you get: Subject: [listname 125] Re: Hoge hoge Not with Re: Re: Hoge hoge. Looks like complicated but this patch has been working well with Japanese-enhanced Mailman for more than a year. Without %d, this patch works like current version, I believe. ---------------------------------------------------------------------- Comment By: Mitchell Marks (jojoba2) Date: 2003-05-17 12:42 Message: Logged In: YES user_id=718482 Is there a version vor MM 2.1.2? I'm trying the older one but doesn't seem to work. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-26 23:33 Message: Logged In: YES user_id=67709 sorry for daily update but there was an error in i18n handling of '(no subject)' ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-25 19:25 Message: Logged In: YES user_id=67709 update of patch for 2.1.1 if the subject is all ascii, then cat the prefix and subject before it is instantiated. Hope to solve prefix only subject 1st line. Note: with this patch without $d, Re: [prefix] is now mungled to [prefix] Re:. This is useful if someone post new issue as follow up to old subject like; New subject bah bah was Re: [prefix] foo ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-14 05:33 Message: Logged In: YES user_id=67709 Hi, I am pleased you like this patch. Here is my current version attached. ---------------------------------------------------------------------- Comment By: Fabio Rossetti (fabiorossetti) Date: 2003-02-14 04:02 Message: Logged In: YES user_id=693899 If you need a quick fix to make the patch work with 2.1.1 here's my take (it's the diff file adapted to work with 2.1.1 CookHeaders.py) 17a18 > (sequence version) 221c222,223 < prefix = mlist.subject_prefix --- > prefix = mlist.subject_prefix.strip(); > if not prefix: return 237,243c239,250 < if prefix and subject: < pattern = re.escape(prefix.strip()) < for decodedsubj, charset in headerbits: < if re.search(pattern, decodedsubj, re.IGNORECASE): < # The subject's already got the prefix, so don't change it < return < del msg['subject'] --- > headerstring = '' > fws = '' > cset = None > for (s, c) in headerbits: > headerstring += fws + s > if c == None or c == 'us-ascii': > fws = ' ' > cset = Utils.GetCharSet(mlist.preferred_language) > else: > fws = '' > cset = c > # Note: searching prefix in subject is REMOVED. (seq version) 245a253,275 > else: > subject = headerstring > # If the subject_prefix contains '%d', it is replaced with the > # mailing list sequential number. Also, if the prefix is closed with > # [],(), or {}, the prefix in the responding post subject will be cared. > # sequential number format allows '%05d' like pattern. > p = re.compile('%\d*d') > if p.search(prefix,1): > # prefix have number, so we should search prefix w/number > # in subject. > prefix_pattern = p.sub(r'\s*\d+\s*', prefix) > else: > prefix_pattern = prefix > prefix_pattern = re.sub('([\[\(\{])', '\\\g<1>', prefix_pattern) > subject = re.sub(prefix_pattern, '', subject) > subject = re.compile('(RE:\s*)+', re.I).sub('Re: ', subject, 1) > # and substitute %d in prefix with post_id > try: > prefix = prefix % mlist.post_id > except: > pass > # Note that trailing space was stripped in seq version (TK) > prefix += ' ' 248,262c278,288 < for s, c in headerbits: < # Once again, convert the string to unicode. < if c is None: < c = Charset('iso-8859-1') < if not isinstance(c, Charset): < c = Charset(c) < if not _isunicode(s): < codec = c.input_codec or 'ascii' < try: < s = unicode(s, codec, 'replace') < except LookupError: < # Unknown codec, is this default reasonable? < s = unicode(s, Utils.GetCharSet (mlist.preferred_language), < 'replace') < h.append(s, c) --- > # in seq version, subject header is already concatnated > if not _isunicode(subject): > try: > subject = unicode(subject, cset, 'replace') > except LookupError: > # unknown codec > cset = Utils.GetCharSet(mlist.preferred_language) > subject = unicode(subject, cset, 'replace') > subject = subject.encode(cset) > h.append(subject, cset) > del msg['subject'] ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-12-19 22:31 Message: Logged In: YES user_id=67709 update for 2.1b6+ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-30 23:59 Message: Logged In: YES user_id=67709 I have uploaded the patch with the same name as the old one. Please download the upper one because it's newer. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-30 23:53 Message: Logged In: YES user_id=67709 Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 From noreply at sourceforge.net Sat May 17 20:01:02 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat May 17 22:01:06 2003 Subject: [ mailman-Patches-601117 ] add sequencial number in subject prefix Message-ID: Patches item #601117, was opened at 2002-08-28 05:07 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add sequencial number in subject prefix Initial Comment: This patch for 'CookHeaders.py' add an ability to add a sequencial number in the subject prefix. You can define a subject prefix like: [listname %d] Then, the subject line of delivered mail becomes: Subject: [listname 123] Hoge hoge When someone replied this mail, mailman receives a messages with: Subject: Re: [listname 123] Hoge hoge Then, this patch removes [listname \d+] part and deliver it with: Subject: [listname 124] Re: Hoge hoge And next, another person replies with Subject: Re: [listname 124] Re: Hoge hoge Then, (magically!) you get: Subject: [listname 125] Re: Hoge hoge Not with Re: Re: Hoge hoge. Looks like complicated but this patch has been working well with Japanese-enhanced Mailman for more than a year. Without %d, this patch works like current version, I believe. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-05-18 02:01 Message: Logged In: YES user_id=67709 Here is update of my patch for 2.1.2 ---------------------------------------------------------------------- Comment By: Mitchell Marks (jojoba2) Date: 2003-05-17 17:42 Message: Logged In: YES user_id=718482 Is there a version vor MM 2.1.2? I'm trying the older one but doesn't seem to work. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-27 05:33 Message: Logged In: YES user_id=67709 sorry for daily update but there was an error in i18n handling of '(no subject)' ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-26 01:25 Message: Logged In: YES user_id=67709 update of patch for 2.1.1 if the subject is all ascii, then cat the prefix and subject before it is instantiated. Hope to solve prefix only subject 1st line. Note: with this patch without $d, Re: [prefix] is now mungled to [prefix] Re:. This is useful if someone post new issue as follow up to old subject like; New subject bah bah was Re: [prefix] foo ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-14 11:33 Message: Logged In: YES user_id=67709 Hi, I am pleased you like this patch. Here is my current version attached. ---------------------------------------------------------------------- Comment By: Fabio Rossetti (fabiorossetti) Date: 2003-02-14 10:02 Message: Logged In: YES user_id=693899 If you need a quick fix to make the patch work with 2.1.1 here's my take (it's the diff file adapted to work with 2.1.1 CookHeaders.py) 17a18 > (sequence version) 221c222,223 < prefix = mlist.subject_prefix --- > prefix = mlist.subject_prefix.strip(); > if not prefix: return 237,243c239,250 < if prefix and subject: < pattern = re.escape(prefix.strip()) < for decodedsubj, charset in headerbits: < if re.search(pattern, decodedsubj, re.IGNORECASE): < # The subject's already got the prefix, so don't change it < return < del msg['subject'] --- > headerstring = '' > fws = '' > cset = None > for (s, c) in headerbits: > headerstring += fws + s > if c == None or c == 'us-ascii': > fws = ' ' > cset = Utils.GetCharSet(mlist.preferred_language) > else: > fws = '' > cset = c > # Note: searching prefix in subject is REMOVED. (seq version) 245a253,275 > else: > subject = headerstring > # If the subject_prefix contains '%d', it is replaced with the > # mailing list sequential number. Also, if the prefix is closed with > # [],(), or {}, the prefix in the responding post subject will be cared. > # sequential number format allows '%05d' like pattern. > p = re.compile('%\d*d') > if p.search(prefix,1): > # prefix have number, so we should search prefix w/number > # in subject. > prefix_pattern = p.sub(r'\s*\d+\s*', prefix) > else: > prefix_pattern = prefix > prefix_pattern = re.sub('([\[\(\{])', '\\\g<1>', prefix_pattern) > subject = re.sub(prefix_pattern, '', subject) > subject = re.compile('(RE:\s*)+', re.I).sub('Re: ', subject, 1) > # and substitute %d in prefix with post_id > try: > prefix = prefix % mlist.post_id > except: > pass > # Note that trailing space was stripped in seq version (TK) > prefix += ' ' 248,262c278,288 < for s, c in headerbits: < # Once again, convert the string to unicode. < if c is None: < c = Charset('iso-8859-1') < if not isinstance(c, Charset): < c = Charset(c) < if not _isunicode(s): < codec = c.input_codec or 'ascii' < try: < s = unicode(s, codec, 'replace') < except LookupError: < # Unknown codec, is this default reasonable? < s = unicode(s, Utils.GetCharSet (mlist.preferred_language), < 'replace') < h.append(s, c) --- > # in seq version, subject header is already concatnated > if not _isunicode(subject): > try: > subject = unicode(subject, cset, 'replace') > except LookupError: > # unknown codec > cset = Utils.GetCharSet(mlist.preferred_language) > subject = unicode(subject, cset, 'replace') > subject = subject.encode(cset) > h.append(subject, cset) > del msg['subject'] ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-12-20 04:31 Message: Logged In: YES user_id=67709 update for 2.1b6+ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:59 Message: Logged In: YES user_id=67709 I have uploaded the patch with the same name as the old one. Please download the upper one because it's newer. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:53 Message: Logged In: YES user_id=67709 Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 From noreply at sourceforge.net Tue May 20 07:33:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue May 20 09:33:08 2003 Subject: [ mailman-Bugs-740453 ] encoding problems (1/3) Message-ID: Bugs item #740453, was opened at 2003-05-20 15:32 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=740453&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Fil (filfil) Assigned to: Nobody/Anonymous (nobody) Summary: encoding problems (1/3) Initial Comment: May 20 11:47:10 2003 (8944) Uncaught runner exception: ASCII decoding error: or May 20 11:47:10 2003 (8944) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 218, in _dispo res = Results(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 75, in __init_ subj = make_header(decode_header(subj)).__unicode__() File "/usr/local/mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/local/mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) UnicodeError: ASCII decoding error: ordinal not in range(128) May 20 11:47:10 2003 (8944) SHUNTING: 1052919608.508467+145b45eb26201772a1a52c3 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=740453&group_id=103 From noreply at sourceforge.net Tue May 20 07:35:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue May 20 09:35:14 2003 Subject: [ mailman-Bugs-740457 ] mktime problem (2/3) Message-ID: Bugs item #740457, was opened at 2003-05-20 15:35 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=740457&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Fil (filfil) Assigned to: Nobody/Anonymous (nobody) Summary: mktime problem (2/3) Initial Comment: May 20 11:47:12 2003 (8942) Uncaught runner exception: mktime argument out of r May 20 11:47:12 2003 (8942) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/ArchRunner.py", line 49, in _dispose elif abs(now - mktime_tz(tup)) > \ File "/usr/local/mailman/pythonlib/email/_parseaddr.py", line 145, in mktime_ t = time.mktime(data[:8] + (0,)) OverflowError: mktime argument out of range May 20 11:47:12 2003 (8942) SHUNTING: 1051480510.323101+bfeaf3c7cb30777ce3f7a67 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=740457&group_id=103 From noreply at sourceforge.net Tue May 20 07:36:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue May 20 09:36:45 2003 Subject: [ mailman-Bugs-740459 ] unicode problem (3/3) Message-ID: Bugs item #740459, was opened at 2003-05-20 15: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=740459&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Fil (filfil) Assigned to: Nobody/Anonymous (nobody) Summary: unicode problem (3/3) Initial Comment: May 20 11:47:10 2003 (8944) Uncaught runner exception: unknown encoding May 20 11:47:10 2003 (8944) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 218, in _dispo res = Results(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 75, in __init_ subj = make_header(decode_header(subj)).__unicode__() File "/usr/local/mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/local/mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) LookupError: unknown encoding May 20 11:47:10 2003 (8944) SHUNTING: 1053383696.5418921+6121da3902700d6a7906d8 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=740459&group_id=103 From noreply at sourceforge.net Wed May 21 17:32:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed May 21 19:33:07 2003 Subject: [ mailman-Feature Requests-741426 ] Per list customisation of system messages Message-ID: Feature Requests item #741426, was opened at 2003-05-22 09:32 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=741426&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Steve McInerney (stevemci) Assigned to: Nobody/Anonymous (nobody) Summary: Per list customisation of system messages Initial Comment: Currently to modify various mailman generated system messages requires modifying python. Not difficult, but annoying if you want different responses for different lists. An example is the message generated if a subscriber tries to re-subscribe via the web interface. Our list owners, _really_ didn't like the default wording, and wanted it changed to better reflect our user base. Unf this modifies for all lists on that server. 2ndly I noticed that the %(description)s string didn't work in the above notification??? Thanks - Steve ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=741426&group_id=103 From noreply at sourceforge.net Tue May 27 13:41:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue May 27 15:41:12 2003 Subject: [ mailman-Bugs-744466 ] error message Message-ID: Bugs item #744466, was opened at 2003-05-27 14:41 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=744466&group_id=103 Category: nntp/news Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Robert Hinson (oppie) Assigned to: Nobody/Anonymous (nobody) Summary: error message Initial Comment: I get this error message. From: Cron Daemon To: mailman@oppie.oppie.net Subject: Cron /usr/bin/python - S /var/mailman/cron/gate_news Traceback (innermost last): File "/var/mailman/cron/gate_news", line 222, in ? main() File "/var/mailman/cron/gate_news", line 203, in main process_lists(lock) File "/var/mailman/cron/gate_news", line 148, in process_lists conn, first, last = open_newsgroup(mlist) File "/var/mailman/cron/gate_news", line 75, in open_newsgroup password=mm_cfg.NNTP_PASSWORD) File "/var/mailman/Mailman/pythonlib/nntplib.py", line 114, in __init__ self.welcome = self.getresp() File "/var/mailman/Mailman/pythonlib/nntplib.py", line 184, in getresp raise NNTPTemporaryError(resp) Mailman.pythonlib.nntplib.NNTPTemporaryError: 400 File exists writing SMstore file -- throttling I am running INN Version inn-2.3.2-5 Python version python-1.5.2-43.72 mailman version mailman-2.0.13-1 RedHat 7.2 Linux oppie 2.4.18-27.7.x #1 Fri Mar 14 05:51:48 EST 2003 i586 unknown Can someone please help me figure this out? Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=744466&group_id=103 From noreply at sourceforge.net Wed May 28 10:42:46 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed May 28 12:42:50 2003 Subject: [ mailman-Bugs-745006 ] "/" is a valid e-mail address character Message-ID: Bugs item #745006, was opened at 2003-05-28 10:42 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=745006&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pete Deffendol (deffendol) Assigned to: Nobody/Anonymous (nobody) Summary: "/" is a valid e-mail address character Initial Comment: I believe that a forward slash (/) is a valid character in the mailbox name for an e-mail address. Some U.S. Forest Service addresses have them. Around line 200 in Utils.py, the forward slash is included in the _badchars regex. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=745006&group_id=103 From noreply at sourceforge.net Thu May 29 14:48:27 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu May 29 16:48:31 2003 Subject: [ mailman-Feature Requests-415137 ] CSS for webpage design. Message-ID: Feature Requests item #415137, was opened at 2001-04-10 13:00 Message generated for change (Comment added) made by nxtek You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=415137&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: CSS for webpage design. Initial Comment: It would be very nice to be able to change the looks of the web pages by using CSS. Ie, include a Feature Requests item #745753, was opened at 2003-05-29 20:51 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=745753&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Phil Iovino (nxtek) Assigned to: Nobody/Anonymous (nobody) Summary: List all subscribers Initial Comment: I'd like to give the mailing list owners the ability to list all subscribers instead of having to click each letter. I know I can do it from the command line, but list owners can't through the admin interface. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=745753&group_id=103 From noreply at sourceforge.net Fri May 30 11:23:36 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri May 30 13:23:47 2003 Subject: [ mailman-Patches-670167 ] fix i18n attachment description in archive Message-ID: Patches item #670167, was opened at 2003-01-18 05:58 Message generated for change (Comment added) made by hcaley You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670167&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: Accepted Priority: 8 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: fix i18n attachment description in archive Initial Comment: Bug-ID 669081 (Major attachment handling bug!) is caused inaccurate handling of charset in Scrubber.py. This is caused by misuse of email functions (or by bug in email package). In Scrubber.py, attempt is made to get message charset by part.get_charset() but it returns only None, as far as I experimented. In this patch, message charset is extracted from regular expression pattern in content-type header. This also set the charset of internally crafted message part. ---------------------------------------------------------------------- Comment By: Hugh Caley (hcaley) Date: 2003-05-30 17:23 Message: Logged In: YES user_id=17460 I patched version 2.1.2 of Mail man with patch Scrubber.py.patch.030224.txt, using "patch -p0 Patches item #746728, was opened at 2003-05-31 20:27 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=746728&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: ssl support for list administration Initial Comment: adds ssl support for the administration interface. via the boolean configuration parameter DEFAULT_ADMIN_USE_SSL can be defined that the list administration interface is accessed oven a ssl encrypted connection ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=746728&group_id=103