Mailman 3 November 2002 - Mailman-Developers

Slightly lame logging: web subscription request
by Greg Ward 27 Nov '02

27 Nov '02

It appears that MM 2.1b4's logging of web subscription requests is a bit lame -- it doesn't actually log the email address involved, just the real name. Is this deliberate? Greg -- Greg Ward - software developer gward(a)mems-exchange.org MEMS Exchange http://www.mems-exchange.org

3 3

[ mailman-Patches-444884 ] Integration of Mailman & htdig for archi
by noreply＠sourceforge.net 27 Nov '02

27 Nov '02

Patches item #444884, was opened at 2001-07-26 18:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Integration of Mailman & htdig for archi Initial Comment: This patch is applicable to Mailman 2.0.6 release that has had search enhancement patch 444879 patch installed - if your Defaults.py has the ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in it then you've got that patch. It replaces earlier patches 401670 and 402423 and is mainly to correct some problems arising from fixes introduced into Mailman by bug fix releases since the 402423 patch. This patch integrates htdig with Mailman and provides: 1. per list search facility with a search form on the list's TOC page. 2. maintenance of privacy of private archives which requires the user to establish their credentials via the normal private archive access before any access via htdig is allowed. 3. a common base URL for both public and private archive access via htsearch results so that htdig indices are unaffected by changingan archive from private to public and vice versa. All access to archives via htdig is controlled by a new wrapped cgi- bin script called htdig.py. 4. a new cron activated script and extra crontab entry which runs htdig regularly to maintain the per list search indices. 5. automatic creation, deletion and maintenance of htdig configuration files and such. Beyond installing htdig and telling Mailman where it is via mm_cfg you do not have to do any other setup. Well not quite you do have to set up a single per installation symlink to allow htdig to find the automatically generated per list htdig configuration files. You probably want to run this patch as follows: cd <mailman 2.0.6 untarred and unzipped directory> patch -p1 < <this patch file> ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 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_i…

1 0

[ mailman-Patches-444879 ] Archive indexer control to improve index
by noreply＠sourceforge.net 27 Nov '02

27 Nov '02

Patches item #444879, was opened at 2001-07-26 18:01 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Archive indexer control to improve index Initial Comment: This patch is applicable to Mailman 2.0.6 release and supercedes ealier patches 401669 and 402422. This patch should improve the quality of search results returned by search engines such as htdig (http://www.htdig.org) where the seach engine's index builder responds to strings embedded in the html pages that are the subject of the indexing. The changes in this patch: 1. allow strings for enabling and disabling indexing to be defined in mm_cfg.py. 2. embeds those strings in the pages generated as the html version of a list's archive. By default nothing in the html changes. To get the desired effect, you must define ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in mm_cfg.py You probably want to run this patch as follows: cd <mailman 2.0.6 untarred and unzipped directory> patch -p1 < <this patch file> See also the associated patch for integrating the htdig search software with mailman's internal archiver ouput. ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2002-11-27 10:22 Message: Logged In: YES user_id=75166 indexing-2.1b5-0.1.patch is a revised version of the patch that is compatible with MM 2.1b5 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:40 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:39 Message: Logged In: YES user_id=75166 indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:46 Message: Logged In: YES user_id=75166 indexing-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:32 Message: Logged In: YES user_id=75166 An additional file, README.NOINDEXtags is added to indexing-2.0.13-0.3.patch version that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:19 Message: Logged In: YES user_id=75166 An error when building the indexing-2.1b2-0.1.patch meant that copies of the originals of two of the files modified by this version of the patch were added when the patch was run. indexing-2.1b2-0.1.patch removes this error. However, the original error is benign and can be corrected by deleting the extra files HyperArch.py.orig and Defaults.py.in.orig. An additional file, README.NOINDEXtags is added that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:19 Message: Logged In: YES user_id=12800 Another question: is there no standard (de-facto or otherwise) for generic markup that tells indexers not to index a particular section? IOW, for ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is there some generic value that would instruct most (all?) indexers to ignore that section? Or does it necessarily have to be indexer specific? I'm thinking of the situation where you might have ht://Dig installed locally, but your archives are still being spidered by external indexers. It would be good if something more generic could be added to Defaults.py.in ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:14 Message: Logged In: YES user_id=12800 Looking at the 2.1b2 patch, why does it try to create HyperArch.py.orig and Defaults.py.in.orig? Are those included in the patch by mistake? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:08 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:33 Message: Logged In: YES user_id=75166 indexing-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:23 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:11 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch should apply without problems to MM 2.0.12 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:50 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:53 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch should apply without problems to MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:43 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:14 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002. Corrects problem noted or 5 Mar 2002 by nobody ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-05 21:41 Message: Logged In: NO When applying this patch I get an error with Hunk 1 and Defaults.py is not updated. This happens with the a clean download of the latest cvs installation (5 Mar 2002). Any ideas what the problem is? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:53 Message: Logged In: YES user_id=75166 indexing-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:48 Message: Logged In: YES user_id=75166 indexing-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:07 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:03 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.7 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_i…

1 0

One last bug before I leave for Tday
by Dale Newfield 27 Nov '02

27 Nov '02

Current CVS. When approving a message with the "Preserve" box checked, I got the following error. It worked fine w/o checking that box. BTW, this is working really well, and the VERP-like bounce processing is excellent! It's possible I caused this--I had this list created before 2.1 that got upgraded while SAVE_AS_PICKLES was 1, and I since changed it in mm_cfg.py to 0. I thought I saw that a qrunner restart was all that was required--is there something hidden inside the MailList object that stores this bit and needs to be reset to prevent this breakage? -Dale

1 0

[ mailman-Bugs-644294 ] Uncaught runner exception
by noreply＠sourceforge.net 27 Nov '02

27 Nov '02

Bugs item #644294, was opened at 2002-11-26 10:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644294&group_i… Category: Pipermail Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception Initial Comment: Getting these repeatedly: Nov 26 14:17:11 2002 (327) Uncaught runner exception: Article instance has no attribute '_mlist' Nov 26 14:17:11 2002 (327) Traceback (most recent call last): File "/opt/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/opt/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/opt/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail h.close() File "/opt/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/opt/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/opt/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/opt/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' ---------------------------------------------------------------------- >Comment By: Terry Grace (tgrace) Date: 2002-11-26 16:40 Message: Logged In: YES user_id=87771 Archives broken too. After restarting the deamons, only the first article posted gets archived. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644294&group_i…

1 0

[PATCH] Do not use hardcoded $prefix in contrib/qmail-to-mailman.py
by Matthias Juchem 27 Nov '02

27 Nov '02

Hi. The intention of this patch should be clear. Diff against CVS head. Tested, works for me. Regards, Matthias diff -urN mailman/contrib/qmail-to-mailman.py mailman-matthias/contrib/qmail-to-mailman.py --- mailman/contrib/qmail-to-mailman.py Sat Apr 6 00:49:32 2002 +++ mailman-matthias/contrib/qmail-to-mailman.py Wed Nov 27 01:34:35 2002 @@ -1,7 +1,7 @@ #! @PYTHON@ # Configuration variables - Change these for your site if necessary. -MailmanHome = "/usr/local/mailman"; # Mailman home directory. +MailmanHome = "@prefix@"; # Mailman home directory. MailmanOwner = "postmaster@localhost"; # Postmaster and abuse mail recepient. # End of configuration variables. @@ -32,7 +32,7 @@ # To configure a virtual domain to connect to mailman, create these files: # # ~mailman/.qmail-default -# |preline /usr/bin/python /usr/local/mailman/mail-in.py +# |preline /usr/bin/python @prefix@/mail-in.py # # /var/qmail/control/virtualdomains: # DOMAIN.COM:mailman

1 0

[PATCH] Clean all Makefiles on make distclean
by Matthias Juchem 27 Nov '02

27 Nov '02

Hi. Here is a patch for Mailman CVS head. mailman/messages/Makefile and mailman/tests/*/Makefile do not get cleaned up when doing a 'make distclean'. This should patch fix it. Tested like this: 'configure --some-options; make distclean'; seems to work Regards, Matthias diff -urN mailman/messages/Makefile.in mailman-matthias/messages/Makefile.in --- mailman/messages/Makefile.in Mon Nov 4 23:47:30 2002 +++ mailman-matthias/messages/Makefile.in Wed Nov 27 01:38:29 2002 @@ -115,6 +115,7 @@ -rm -f marked.files docstring.files distclean: clean + -rm -f Makefile catclean: -rm -f Makefile */LC_MESSAGES/mailman.mo */LC_MESSAGES/mailman.po.old $(POTFILE) diff -urN mailman/tests/Makefile.in mailman-matthias/tests/Makefile.in --- mailman/tests/Makefile.in Mon Oct 1 18:39:12 2001 +++ mailman-matthias/tests/Makefile.in Wed Nov 27 01:40:37 2002 @@ -71,5 +71,9 @@ clean: distclean: + @for d in $(SUBDIRS); \ + do \ + (cd $$d; $(MAKE) distclean); \ + done -rm *.pyc -rm Makefile

1 0

error reading SMTP packet; response to dot-stuffed message expected
by Sony Z Thekkumthara 26 Nov '02

26 Nov '02

Hi All, I am using mailman since 5 months and very impressed with its efficiency. Lately I was told by some users that they are not getting few messages or they are getting a delivery delay error from their internet service provider saying somthing like "error reading SMTP packet; response to dot-stuffed message expected" This is happens sometimes when the user trys to post a message from outside. Could anyone please shed some light on this ... Thank You So Much... Zach

1 0

[ mailman-Bugs-644294 ] Uncaught runner exception
by noreply＠sourceforge.net 26 Nov '02

26 Nov '02

Bugs item #644294, was opened at 2002-11-26 10:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644294&group_i… Category: Pipermail Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Terry Grace (tgrace) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception Initial Comment: Getting these repeatedly: Nov 26 14:17:11 2002 (327) Uncaught runner exception: Article instance has no attribute '_mlist' Nov 26 14:17:11 2002 (327) Traceback (most recent call last): File "/opt/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/opt/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/opt/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail h.close() File "/opt/mailman/Mailman/Archiver/pipermail.py", line 303, in close self.update_dirty_archives() File "/opt/mailman/Mailman/Archiver/pipermail.py", line 517, in update_dirty_archives self.update_archive(i) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 1058, in update_archive self.__super_update_archive(archive) File "/opt/mailman/Mailman/Archiver/pipermail.py", line 425, in update_archive self._update_thread_index(archive, arcdir) File "/opt/mailman/Mailman/Archiver/pipermail.py", line 485, in _update_thread_index self.update_article(arcdir, a1, L[0], L[2]) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 1223, in update_article f.write(article.as_html()) File "/opt/mailman/Mailman/Archiver/HyperArch.py", line 407, in as_html d['listurl'] = self._mlist.GetScriptURL('listinfo', absolute=1) AttributeError: Article instance has no attribute '_mlist' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644294&group_i…

1 0

2.1b5: Decoration doesn't work that well for German lists
by Jost Krieger 26 Nov '02

26 Nov '02

The current MIME decoration logic is as follows: If the list language charset is ASCII or the same as the message charset, just put on header and footer, else put on extra parts in some way. Unfortunately, for "almost ASCII" languages like German, this leads to quite a few messages arriving with 2 or 3 text/plain; charset="us-ascii" parts. This always happens when header and footer are just in ASCII, although the list language is not. Someone along the way detects this and follows the RFC in making the parts ASCII, but Decorate.py doen't know about it. I can think of two solutions: 1. Have Decorate.py analyse header and footer for 8bit characters. 2. If the message charset is "below" the list charset, i.e., ASCII, upgrade the message charset and concatenate the parts. If this works as I think it works, it will be corrected back to US-ASCII later on if there were no 8bit characters after all. Jost -- | Jost.Krieger+sig(a)ruhr-uni-bochum.de Please help stamp out spam! | | Postmaster, JAPH, resident answer machine am RZ der RUB | | Pluralitas non est ponenda sine necessitate | | William of Ockham (1285-1347/49) |

1 0

Mailman-Developers November 2002