Mailman 3 January 2003 - Mailman-coders

[ mailman-Feature Requests-673265 ] Post confirmation + moderation
by SourceForge.net 24 Jan '03

24 Jan '03

Feature Requests item #673265, was opened at 2003-01-23 19:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=673265&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Samuel Tardieu (samtardieu) Assigned to: Nobody/Anonymous (nobody) Summary: Post confirmation + moderation Initial Comment: The following scheme (implemented by me for Sympa as a scenario some time ago) leads to a spam-free mailing-list with almost no work from the moderator. When a mail arrive and should be held for any reason (sender not in subscriber list, list not in to: or cc:, too many recipients), ask the alleged sender to confirm its post then hold it for moderation when the sender confirms its intention to post. This way, spam (whose confirmation request will almost never be answered) is not presented to the moderators, while mail sent by humans will. It would be great to have this feature in mailman. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=673265&group_i…

1 0

[ mailman-Patches-672389 ] admindb.py and admin/user notice i18n subject
by SourceForge.net 23 Jan '03

23 Jan '03

Patches item #672389, was opened at 2003-01-22 12:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=672389&group_i… Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: admindb.py and admin/user notice i18n subject Initial Comment: When a message is hold for approval, notices are sent to the user and administrator. The administrator can later process the message with admindb cgi interface. When an i18n message was held, the subject is shown as mime encoded string and not easily readable. This patch decode the header and show the subject in the list preferred charset. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-23 00:38 Message: Logged In: YES user_id=67709 I have to change cron/checkdbs also. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=672389&group_i…

1 0

[ mailman-Bugs-670535 ] qrunner stops for no apparent reason
by SourceForge.net 23 Jan '03

23 Jan '03

Bugs item #670535, was opened at 2003-01-18 21:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=670535&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 8 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner stops for no apparent reason Initial Comment: About once every day or so, qrunner will stop for no apparent reason. The qrunner log file has the following ... Jan 18 14:29:09 2003 (3443) IncomingRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3443) IncomingRunner qrunner exiting. Jan 18 14:29:09 2003 (3441) BounceRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3441) BounceRunner qrunner exiting. Jan 18 14:29:09 2003 (3445) OutgoingRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3445) OutgoingRunner qrunner exiting. Jan 18 14:29:09 2003 (3442) CommandRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3442) CommandRunner qrunner exiting. Jan 18 14:29:09 2003 (3446) VirginRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3446) VirginRunner qrunner exiting. Jan 18 14:29:09 2003 (3440) ArchRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3440) ArchRunner qrunner exiting. Jan 18 14:29:10 2003 (3444) NewsRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:12 2003 (3444) NewsRunner qrunner exiting. No other log has any indication of what might be happening. Is there a way to increase the logging somewhere so the cause can be identified? ---------------------------------------------------------------------- >Comment By: David Gibbs (midrangeman) Date: 2003-01-22 15:31 Message: Logged In: YES user_id=86339 After some further research, QRUNNER seems to stop after exactly 24 hours of operation. That is, 24 hours after qrunner starts, it ends as if someone killed it with SIGTERM. I know for a fact that nobody is actually doing this ... and no process on my system should be aware of the fact that qrunner is actually running. I will not discount the possiblity that this is an environmental factor, but it seems to me that a daemon process should not be affected by environmental factors. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-19 16:46 Message: Logged In: YES user_id=12800 I'm not sure what kind of logging would help. Some process somewhere is SIGTERMing the mailmanctl controller process. There's no way to know where a signal is coming from, so I'm not sure what more you could do in mailmanctl. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=670535&group_i…

1 0

[ mailman-Patches-672714 ] cope with garbage Date
by SourceForge.net 23 Jan '03

23 Jan '03

Patches item #672714, was opened at 2003-01-22 20:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=672714&group_i… Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: cope with garbage Date Initial Comment: rfc822.parsedate(garbage) -> None This patch allows archive generation to survive a garbage Date value. It recognizes the None return and does what it would have done if Date had been missing. *** Mailman/Archiver/pipermail.py.dist Sat Dec 7 18:21:58 2002 --- Mailman/Archiver/pipermail.py Wed Jan 15 15:58:31 2003 *************** *** 223,228 **** --- 223,230 ---- if datestr is missing: return None date = parsedate_tz(datestr) + if date is None: + return None try: return time.mktime(date[:9]) except (ValueError, OverflowError): *** Mailman/Handlers/Scrubber.py.dist Fri Dec 20 11:55:43 2002 --- Mailman/Handlers/Scrubber.py Wed Jan 15 16:00:31 2003 *************** *** 73,78 **** --- 73,80 ---- def safe_strftime(fmt, floatsecs): + if floatsecs is None: + return None try: return time.strftime(fmt, floatsecs) except ValueError: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=672714&group_i…

1 0

[ mailman-Bugs-672649 ] canonstr -> unicode usernames
by SourceForge.net 23 Jan '03

23 Jan '03

Bugs item #672649, was opened at 2003-01-22 19:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=672649&group_i… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: canonstr -> unicode usernames Initial Comment: Cgi.subscribe.process_form gets a unicode value for fullname, from Utils.canonstr() (return unicode(newstr, charset, 'replace') This came to my attention because it broke OwnerNotification when the email Message couldn't "flatten" itself with the unicode payload. Suspect that's only the beginning of the trouble that will be caused, so I'm hoping we really don't want unicode usernames values as a rule. I fixed it in subscribe.py with fullname = fullname.encode('iso8859-1'), but note that canonstr is used elsewhere like this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=672649&group_i…

1 0

[ mailman-Patches-444884 ] Integration of Mailman & htdig for archi
by SourceForge.net 22 Jan '03

22 Jan '03

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: 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_i…

1 0

[ mailman-Patches-672389 ] admindb.py and admin/user notice i18n subject
by SourceForge.net 22 Jan '03

22 Jan '03

Patches item #672389, was opened at 2003-01-22 12:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=672389&group_i… >Category: internationalization >Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: admindb.py and admin/user notice i18n subject Initial Comment: When a message is hold for approval, notices are sent to the user and administrator. The administrator can later process the message with admindb cgi interface. When an i18n message was held, the subject is shown as mime encoded string and not easily readable. This patch decode the header and show the subject in the list preferred charset. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=672389&group_i…

1 0

[ mailman-Patches-672389 ] admindb.py and admin/user notice i18n subject
by SourceForge.net 22 Jan '03

22 Jan '03

Patches item #672389, was opened at 2003-01-22 12:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=672389&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: admindb.py and admin/user notice i18n subject Initial Comment: When a message is hold for approval, notices are sent to the user and administrator. The administrator can later process the message with admindb cgi interface. When an i18n message was held, the subject is shown as mime encoded string and not easily readable. This patch decode the header and show the subject in the list preferred charset. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=672389&group_i…

1 0

[ mailman-Bugs-621689 ] Subscribe requests dropped from admin db
by SourceForge.net 22 Jan '03

22 Jan '03

Bugs item #621689, was opened at 2002-10-10 20:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621689&group_i… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Mark Dadgar (mdadgar) Assigned to: Nobody/Anonymous (nobody) Summary: Subscribe requests dropped from admin db Initial Comment: Occasionally, subscribe requests (via the web page) to a list that requires moderator approval for subscriptions never make it to the admin db for that list. They are listed in the subscribe log file, but never show up on the admin db page. Log file entries look like this: Oct 10 18:43:43 2002 (31168) eventmasters: pending XXXXXX.swfla.rr.com But the admin db page for the list shows no outstanding issues. I have verified that there was an actual subscription request behind this log entry. ---------------------------------------------------------------------- >Comment By: Mark Dadgar (mdadgar) Date: 2003-01-21 23:57 Message: Logged In: YES user_id=598228 I have a pending.pck file as well as a subscribe log that show subscription attempts that require approval for which I have not gotten admin requests, nor have they shown up in the web interface. I am loath to attach them here as they contain live email addresses. Shoot me an email at md(a)pdc-racing.net and I can get them to you. Then I'll kill this address. :) ---------------------------------------------------------------------- Comment By: Mark Dadgar (mdadgar) Date: 2003-01-20 23:32 Message: Logged In: YES user_id=598228 I suppose it's possible that those two patches are causing it, but it seems unlikely. What information can I provide that will help you track this down? It's kind of a bummer. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 21:06 Message: Logged In: YES user_id=12800 I definitely need more information. I've neve been able to reproduce the problem. Do you think it could be related to the unofficial patches you've applied? ---------------------------------------------------------------------- Comment By: Mark Dadgar (mdadgar) Date: 2002-12-05 23:29 Message: Logged In: YES user_id=598228 Ok, I verified that it's still a problem under 2.1b5 with the htdig and indexing patches. It's a real drag, too. :( Please let me know if you need more debug info. ---------------------------------------------------------------------- Comment By: Mark Dadgar (mdadgar) Date: 2002-11-21 22:08 Message: Logged In: YES user_id=598228 Unfortunately, it's still occurring under 2.1b4. I'll check it under 2.1b5 as soon as the patches for htdig integration are released, as I need those to implement. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-10-22 07:11 Message: Logged In: YES user_id=12800 I'm going to defer this one until 2.1b4 goes out. I've fixed some related bugs in cvs, so hopefully this will be fixed in the new version. ---------------------------------------------------------------------- Comment By: Mark Dadgar (mdadgar) Date: 2002-10-20 10:14 Message: Logged In: YES user_id=598228 Sorry - I'm running 2.1b3. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-10-20 08:48 Message: Logged In: YES user_id=12800 What version of Mailman are you using. It's import to know the exact version, i.e. 2.1beta3, or if you're running from cvs. A lot of these problems have been fixed in cvs, which will soon be released as 2.1 beta 4. ---------------------------------------------------------------------- Comment By: Mark Dadgar (mdadgar) Date: 2002-10-10 21:29 Message: Logged In: YES user_id=598228 I just verified, by cat'ing pending.pck, that the appropriate changes seem to be in there. But the web interface never picks them up. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621689&group_i…

1 0

[ mailman-Bugs-671984 ] move_list script - Syntax Errors
by SourceForge.net 22 Jan '03

22 Jan '03

Bugs item #671984, was opened at 2003-01-21 19:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=671984&group_i… Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Mark (backquack) Assigned to: Nobody/Anonymous (nobody) Summary: move_list script - Syntax Errors Initial Comment: Initial execution of the move_list script resulted in serveral regarding korean encodings... Traceback (innermost last): File "./move_list", line 42, in ? import paths File "./paths.py", line 60, in ? import korean.aliases File "/home/mailman/pythonlib/korean/aliases.py", line 23, in ? import encodings.aliases After editing paths.py and commenting out korean.aliases and executing move_list -h I get the following..... ./move_list -h Traceback (innermost last): File "./move_list", line 44, in ? from Mailman import MailList File "/home/mailman/Mailman/MailList.py", line 686 text += Utils.maketext( ^ SyntaxError: invalid syntax ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=671984&group_i…

1 0