Mailman 3 July 2002 - Mailman-Developers

[ mailman-Bugs-577617 ] Edit before approve
by noreply＠sourceforge.net 26 Jul '02

26 Jul '02

Bugs item #577617, was opened at 2002-07-04 19:59 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=577617&group_i… Category: Web/CGI Group: 2.0.x >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Jasper van Beusekom (jvbeusek) Assigned to: Nobody/Anonymous (nobody) Summary: Edit before approve Initial Comment: All my list owners have made the mistake of expecting to be able to edit a message in the admindb interface before approving, assuming that the edited message would reach the list... I realize that the form-fields are truncated from the original message, but would there be some way for the owner to edit a message before approving it? ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-25 23:28 Message: Logged In: YES user_id=12800 Unfortunately at this time I've decided not to support direct editing of the message via the web page, even for MM2.1. However in 2.1, the field will be read-only so as not to confuse list administrators. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=577617&group_i…

1 0

[ mailman-Bugs-577919 ] Forwarding to comma separated addresses
by noreply＠sourceforge.net 26 Jul '02

26 Jul '02

Bugs item #577919, was opened at 2002-07-05 16:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=577919&group_i… Category: Web/CGI Group: 2.0.x >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Pavel Roskin (proski) Assigned to: Nobody/Anonymous (nobody) Summary: Forwarding to comma separated addresses Initial Comment: Mailman 2.0.8 gives an option to forward mail held for approval. Entering comma separated addresses as the forwarding address doesn't cause any warnings, but the message is only delivered to the first address. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-25 23:25 Message: Logged In: YES user_id=12800 While this won't be fixed for MM2.0, I just made sure this works for MM2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=577919&group_i…

1 0

[ mailman-Bugs-585229 ] opening holes by changing permissions?
by noreply＠sourceforge.net 26 Jul '02

26 Jul '02

Bugs item #585229, was opened at 2002-07-22 23:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585229&group_i… Category: configuring/installing Group: 2.1 beta >Status: Closed Resolution: None Priority: 5 Submitted By: Paul Marshall (paulmarshll) Assigned to: Nobody/Anonymous (nobody) Summary: opening holes by changing permissions? Initial Comment: I was having problems adding a list in Mailman 2.1beta via the web interface, it was giving me an error regarding permissions to the mailman/data/aliases.db file. This is the error I got: ... File "/var/mailman/Mailman/MTA/Postfix.py", line 46, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /var/mailman/data/aliases (status: 1, Operation not permitted) To fix this I changed the permissions on this file so apache could write to it. chmod a+w aliases.db This did fix the problem of creating and deleting lists via the web interface. Does anyone know if this would open up any security holes? Is there another way to fix the permissions problem that is more logical? Thanks for your help. Paul Marshall ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-25 21:19 Message: Logged In: YES user_id=12800 Cool, thanks, I'm closing this bug report. ---------------------------------------------------------------------- Comment By: Paul Marshall (paulmarshll) Date: 2002-07-24 11:44 Message: Logged In: YES user_id=582441 Thanks for the help bwarsaw, its working now and I don't have a+w on aliases.db Paul ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 11:28 Message: Logged In: YES user_id=12800 You shouldn't need to do this if you've followed the directions in README.POSTFIX. The key issue is that aliases and aliases.db must be group owned by `mailman' and must be group writeable. Since the cgi scripts are setgid mailman Apache should have no problems writing the file. And since Postfix filter prog is also setgid mailman, it should have no problems either. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585229&group_i…

1 0

Re: [Mailman-Developers] Why both a .msg and .db in qfiles?
by J C Lawrence 25 Jul '02

25 Jul '02

On Wed, 24 Jul 2002 16:20:49 -0600 Jason R Mastaler <Jason> wrote: > I'm curious why MM doesn't just store the rfc822 headers and message > body in the .db pickle/marshal as well? Why maintain two files > instead of just one? One advantage of the flat text message file is that it can be edited by external tools (in my case XEmacs and various odd scripts) prior to being processed and released for broadcast by the moderation interface. <<Yeah, I hand edit every post>> > The reason I ask is because I'm contemplating a similar approach for > TMDA. Mailman v2.1 offers a choice between the above approach and a pickle. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

3 8

Re: [Mailman-Developers] Re: Why both a .msg and .db in qfiles?
by J C Lawrence 25 Jul '02

25 Jul '02

On Thu, 25 Jul 2002 10:10:58 -0600 Jason R Mastaler <Jason> wrote: > J C Lawrence <claw(a)kanga.nu> writes: >> Mailman v2.1 offers a choice between the above approach and a pickle. > Where is this configured in MM 2.1? Defaults.py/mm_cfg.py. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

2 1

Why both a .msg and .db in qfiles?
by Jason R. Mastaler 25 Jul '02

25 Jul '02

For every incoming message waiting to be posted, MM writes both a .msg file containing the message text, and a .db file containing meta-information about that message. I'm curious why MM doesn't just store the rfc822 headers and message body in the .db pickle/marshal as well? Why maintain two files instead of just one? The reason I ask is because I'm contemplating a similar approach for TMDA. Thanks. -- (http://tmda.net/)

2 3

[ mailman-Bugs-586526 ] No way to set default FQDN.
by noreply＠sourceforge.net 25 Jul '02

25 Jul '02

Bugs item #586526, was opened at 2002-07-25 11:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=586526&group_i… Category: configuring/installing >Group: 2.1 beta >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Dylan Griffiths (inoshiro) Assigned to: Nobody/Anonymous (nobody) Summary: No way to set default FQDN. Initial Comment: If you configure Mailmain on a machine with multiple IFs, and the first is an internal name (the second being the internet one), Mailman will configure itself for the INTERNAL domain and use this in mailings everywhere (unless overriden by the mailing list admin). There is NO WAY to specify which FQDN to use by default in the configure path, because the --host= is IGNORED and no other option exists which is remotely similar. PLEASE either make your configure script honour the --host= variable (best case), or document a method for setting a system-wide default FQDN which is not the one that configure finds. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-25 12:13 Message: Logged In: YES user_id=12800 See the --with-urlhost and --with-mailhost configure options in MM2.1 cvs, which will be in the next beta release, likely some time this weekend. In the meantime, it's fairly easy to simply edit the mm_cfg.py file for the correct values after doing a make install. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=586526&group_i…

1 0

[ mailman-Patches-585643 ] Mailman 2.0.13 candidate patch
by noreply＠sourceforge.net 25 Jul '02

25 Jul '02

Patches item #585643, was opened at 2002-07-23 15:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=585643&group_i… Category: None Group: Mailman 2.0.x Status: Open Resolution: None Priority: 8 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Mailman 2.0.13 candidate patch Initial Comment: Mailman 2.0.12 had compatibility problems with Python 1.5.2. This patch fixes these AFAICT, and a few other small bugs that have cropped up. Note that this is a candidate patch. The actual MM2.0.13 patch may be different. However I would really appreciate folks using Mailman 2.0.12 (especially if you're using Python 1.5.2) to give this patch a try and see if it fixes your problems. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-07-25 09:00 Message: Logged In: NO This fixed the problems I'd been having on my Solaris 8 box running Mailman 2.0.12 and Python 1.52. Thanks much. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=585643&group_i…

1 0

[ mailman-Bugs-586526 ] No way to set default FQDN.
by noreply＠sourceforge.net 25 Jul '02

25 Jul '02

Bugs item #586526, was opened at 2002-07-25 09:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=586526&group_i… Category: configuring/installing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Dylan Griffiths (inoshiro) Assigned to: Nobody/Anonymous (nobody) Summary: No way to set default FQDN. Initial Comment: If you configure Mailmain on a machine with multiple IFs, and the first is an internal name (the second being the internet one), Mailman will configure itself for the INTERNAL domain and use this in mailings everywhere (unless overriden by the mailing list admin). There is NO WAY to specify which FQDN to use by default in the configure path, because the --host= is IGNORED and no other option exists which is remotely similar. PLEASE either make your configure script honour the --host= variable (best case), or document a method for setting a system-wide default FQDN which is not the one that configure finds. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=586526&group_i…

1 0

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

25 Jul '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: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) 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-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 25 Jul '02

25 Jul '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: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) 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-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

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

25 Jul '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: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) 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-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-Bugs-584989 ] bounced large messages are deleted!
by noreply＠sourceforge.net 25 Jul '02

25 Jul '02

Bugs item #584989, was opened at 2002-07-22 12:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=584989&group_i… Category: mail delivery Group: 2.1 beta >Status: Closed Resolution: Fixed Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: bounced large messages are deleted! Initial Comment: I`m using 2.1b2+ (July, 22th) and if a message is larger than the maximum allowd size (of this list) it is not bounced or hold for approval succesfully. The message disappears and mailman crashes. Maybe it`s just a mistake in the translation in german mailman.po? Jul 22 17:36:55 2002 (28610) Uncaught runner exception: an integer is required Jul 22 17:36:55 2002 (28610) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 129, in _dispose status = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 152, in _dopipel sys.modules[modname].process(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Handlers/Hold.py", line 179, in process MessageTooBig(bodylen, mlist.max_message_size)) File "/usr/lib/mailman/Mailman/Handlers/Hold.py", line 198, in hold_for_approv reason = Utils.wrap(exc.reason_notice()) File "/usr/lib/mailman/Mailman/Handlers/Hold.py", line 103, in reason_notice return _('''Message body is too big: %(size)d bytes with a limit of File "/usr/lib/mailman/Mailman/i18n.py", line 76, in _ return _translation.gettext(s) % dict TypeError: an integer is required ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-25 09:25 Message: Logged In: YES user_id=12800 I just committed a fix to misc/Makefile.in which should stop japanese.pth from being installed in your system site-packages. You'll need to re-run configure (or config.status) to have this take effect, and you'll need to manually remove japanese.pth to fix your system. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-25 01:55 Message: Logged In: YES user_id=12800 There appears to be a bug in the bundled Japanese codec package, such that japanese.pth is still installed in site-packages even though we're trying hard to force it to not do this. I'm reopening this bug and trying to find out if we can either get a working japanese code package, or a workaround for Mailman. In the meantime, you'll need to manually remove /usr/lib/python2.2/site-packages/japanese.pth ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2002-07-24 12:24 Message: Logged In: YES user_id=581680 I really don`t know how python works and how to help myself. Maybe something has changed - I installed the package python-devel and python tk. There`s a traceback when I start "python -v": [...] # /usr/lib/python2.2/stat.pyc matches /usr/lib/python2.2/stat.py import stat # precompiled from /usr/lib/python2.2/stat.pyc # /usr/lib/python2.2/UserDict.pyc matches /usr/lib/python2.2/UserDict.py import UserDict # precompiled from /usr/lib/python2.2/UserDict.pyc 'import site' failed; traceback: Traceback (most recent call last): File "/var/tmp/python-2.2-build//usr/lib/python2.2/site.py", line 177, in ? addsitedir(sitedir) File "/var/tmp/python-2.2-build//usr/lib/python2.2/site.py", line 128, in addsitedir addpackage(sitedir, name) File "/var/tmp/python-2.2-build//usr/lib/python2.2/site.py", line 151, in addpackage exec dir File "<string>", line 1, in ? ImportError: No module named japanese Python 2.2 (#1, Mar 26 2002, 15:46:04) [GCC 2.95.3 20010315 (SuSE)] on linux2 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 09:26 Message: Logged In: YES user_id=12800 Something may have changed in your Python environment? I don't see how that fix could have had anything to do with it! ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2002-07-24 04:14 Message: Logged In: YES user_id=581680 It looks like it works. -Thanks! But now I`m getting the message "`import site` failed; use -v to traceback"?! Peer ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 01:06 Message: Logged In: YES user_id=12800 It does look like it's a bug in the German translation for that message. I'm about to commit a fix to the German catalog; can you try doing a cvs update and see if that fixes your problem? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=584989&group_i…

1 0

[ mailman-Patches-534577 ] Add SpamAssassin filter to mail pipeline
by noreply＠sourceforge.net 25 Jul '02

25 Jul '02

Patches item #534577, was opened at 2002-03-25 16:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_i… Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 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: 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_i…

1 0

[ mailman-Patches-534577 ] Add SpamAssassin filter to mail pipeline
by noreply＠sourceforge.net 25 Jul '02

25 Jul '02

Patches item #534577, was opened at 2002-03-25 16:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_i… Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 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: 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_i…

1 0

[ mailman-Bugs-584989 ] bounced large messages are deleted!
by noreply＠sourceforge.net 25 Jul '02

25 Jul '02

Bugs item #584989, was opened at 2002-07-22 12:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=584989&group_i… Category: mail delivery Group: 2.1 beta >Status: Open Resolution: Fixed Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: bounced large messages are deleted! Initial Comment: I`m using 2.1b2+ (July, 22th) and if a message is larger than the maximum allowd size (of this list) it is not bounced or hold for approval succesfully. The message disappears and mailman crashes. Maybe it`s just a mistake in the translation in german mailman.po? Jul 22 17:36:55 2002 (28610) Uncaught runner exception: an integer is required Jul 22 17:36:55 2002 (28610) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 129, in _dispose status = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 152, in _dopipel sys.modules[modname].process(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Handlers/Hold.py", line 179, in process MessageTooBig(bodylen, mlist.max_message_size)) File "/usr/lib/mailman/Mailman/Handlers/Hold.py", line 198, in hold_for_approv reason = Utils.wrap(exc.reason_notice()) File "/usr/lib/mailman/Mailman/Handlers/Hold.py", line 103, in reason_notice return _('''Message body is too big: %(size)d bytes with a limit of File "/usr/lib/mailman/Mailman/i18n.py", line 76, in _ return _translation.gettext(s) % dict TypeError: an integer is required ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-25 01:55 Message: Logged In: YES user_id=12800 There appears to be a bug in the bundled Japanese codec package, such that japanese.pth is still installed in site-packages even though we're trying hard to force it to not do this. I'm reopening this bug and trying to find out if we can either get a working japanese code package, or a workaround for Mailman. In the meantime, you'll need to manually remove /usr/lib/python2.2/site-packages/japanese.pth ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2002-07-24 12:24 Message: Logged In: YES user_id=581680 I really don`t know how python works and how to help myself. Maybe something has changed - I installed the package python-devel and python tk. There`s a traceback when I start "python -v": [...] # /usr/lib/python2.2/stat.pyc matches /usr/lib/python2.2/stat.py import stat # precompiled from /usr/lib/python2.2/stat.pyc # /usr/lib/python2.2/UserDict.pyc matches /usr/lib/python2.2/UserDict.py import UserDict # precompiled from /usr/lib/python2.2/UserDict.pyc 'import site' failed; traceback: Traceback (most recent call last): File "/var/tmp/python-2.2-build//usr/lib/python2.2/site.py", line 177, in ? addsitedir(sitedir) File "/var/tmp/python-2.2-build//usr/lib/python2.2/site.py", line 128, in addsitedir addpackage(sitedir, name) File "/var/tmp/python-2.2-build//usr/lib/python2.2/site.py", line 151, in addpackage exec dir File "<string>", line 1, in ? ImportError: No module named japanese Python 2.2 (#1, Mar 26 2002, 15:46:04) [GCC 2.95.3 20010315 (SuSE)] on linux2 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 09:26 Message: Logged In: YES user_id=12800 Something may have changed in your Python environment? I don't see how that fix could have had anything to do with it! ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2002-07-24 04:14 Message: Logged In: YES user_id=581680 It looks like it works. -Thanks! But now I`m getting the message "`import site` failed; use -v to traceback"?! Peer ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 01:06 Message: Logged In: YES user_id=12800 It does look like it's a bug in the German translation for that message. I'm about to commit a fix to the German catalog; can you try doing a cvs update and see if that fixes your problem? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=584989&group_i…

1 0

2.1b2-production ready?
by Laurence Berland 25 Jul '02

25 Jul '02

How unready for production use is 2.1b2? I've written a Handler module for mailman, that I wanted to use to filter things coming into the archive, but I can't find where to put the call to the handler in 2.0. I don't want it in the pipeline because it should only act on the archived messages, not the ones sent out. Any hints on where this should go? How far away is a 2.1 release? TIA, Laurence

3 3

[ mailman-Bugs-571634 ] Date: header field handling
by noreply＠sourceforge.net 25 Jul '02

25 Jul '02

Bugs item #571634, was opened at 2002-06-20 09:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=571634&group_i… Category: mail delivery Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Date: header field handling Initial Comment: I got this traceback in my error log (using latest CVS, 2.1b2+): Jun 20 14:58:21 2002 (1991) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/ArchRunner.py", line 54, in _dispose elif abs(now - mktime_tz(tup)) > \ File "/usr/src/build/87651-i386/install/usr/lib/python2.2/rfc822.py", line 955, in mktime_tz t = time.mktime(data[:8] + (0,)) ValueError: year out of range The offending mail was moved to the qfiles/shunt/ directory. A quick dump_db on the .pck file showed this Date: field in the header: Date: Tue, 18 Jun 0102 05:12:09 +0500 The offending mail was a spam mail, so I've deleted the .db and .pck file. But reporting it anyway. :) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-25 01:45 Message: Logged In: YES user_id=12800 Fixed. The occurrance of this exception is a pretty good indication that the date needs to be clobbered. ;) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=571634&group_i…

1 0

[ mailman-Bugs-425121 ] Double moderator approval messages
by noreply＠sourceforge.net 25 Jul '02

25 Jul '02

Bugs item #425121, was opened at 2001-05-18 10:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=425121&group_i… Category: mail delivery Group: 2.0.x Status: Closed Resolution: None Priority: 4 Submitted By: Gert Jan Kruizinga (gjk4all) Assigned to: Thomas Wouters (twouters) Summary: Double moderator approval messages Initial Comment: Dear *, I get the message "Your message to Gein awaits moderator approval" two or three times after posting a message to the mailing list. My moderator also receives his message two or three times, but the two are not related to each other. I already tried to upgrade from mailman-2.0.1 to mailman-2.0.5, but the multiple posting still exists. I have not fount anything regarding this problem in the faq's so i submit it here. Gert Jan Kruizinga. ---------------------------------------------------------------------- Comment By: J. Ros (ros005) Date: 2002-07-25 01:26 Message: Logged In: YES user_id=414801 The problem disapeared after an upgrade of our mail subsystem. This was not a Mailman problem. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-03 20:53 Message: Logged In: YES user_id=12800 Since I haven't heard anything more about this, I'll assume an upgrade fixed your problem. Closing this bug report. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-29 00:07 Message: Logged In: YES user_id=12800 Is this bug still a problem for you? If so, first, I would recommend upgrading to MM2.0.10. Second, I'd like to know what version of Python you're using, and also what MTA (and version) you're using. If this is not a problem any more, please follow up so I can close this bug. ---------------------------------------------------------------------- Comment By: J. Ros (ros005) Date: 2002-01-14 15:35 Message: Logged In: YES user_id=414801 Yes, there are two different list admin accounts, but this is not the issue, as also regular users receive more than once. Most of the time I and all other users receive one copy of the mail, but sometimes this can be two, three or even four copies. It seems that mailman works fine most of the time, but sometimes it sends two (or more)copies of the same message. All types of message are affected, not only administrative messages of Mailman to the moderator or users, but also regular posts to members. I will include both message headers for a double message. Futhermore I will include the errors in the mailman log files for these messages. First message 10:02 Received: from sat-relay1.telecom.ptt.nl (sat- relay1.pc.telecom.ptt.nl [10.1.88.11]) by tmail050s.telecom.ptt.nl with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YJKFRJDJ; Fri, 11 Jan 2002 10:02:17 +0100 Received: from hdiro004.kpn.com (hdiro004.kpn.com [145.7.200.4]) by sat-relay1.telecom.ptt.nl (8.11.6/8.11.6) with SMTP id g0B92Kj21854; Fri, 11 Jan 2002 10:02:20 +0100 Received: from 145.7.200.6 by hdiro004.kpn.com (InterScan E- Mail VirusWall NT); Fri, 11 Jan 2002 10:02:20 +0100 Received: from mail.gjk4all.net (mail.gjk4all.net [213.196.2.118]) by relay1.kpn-telecom.nl (8.11.6/8.11.6) with ESMTP id g0B92JX02559; Fri, 11 Jan 2002 10:02:19 +0100 Received: from mail.gjk4all.net (mail.gjk4all.net [213.196.2.118]) by mail.gjk4all.net (Postfix) with ESMTP id BFE827C90; Fri, 11 Jan 2002 10:02:16 +0100 (CET) Received: by mail.gjk4all.net (Postfix, from userid 1011) id EB3D77C8C; Fri, 11 Jan 2002 10:00:28 +0100 (CET) Content-Type: Multipart/Related; boundary="---------- =_1010739627-91125-0" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.411 (Entity 5.404) To: gein(a)gjk4all.net Message-Id: <20020111090028.EB3D77C8C(a)mail.gjk4all.net> From: gein-admin(a)gjk4all.net Reply-To: gein(a)gjk4all.net Subject: [Gein] Dagelijkse portie fokke en sukke Sender: gein-admin(a)gjk4all.net Errors-To: gein-admin(a)gjk4all.net X-BeenThere: gein(a)mail.gjk4all.net X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: <mailto:gein-request@mail.gjk4all.net? subject=help> List-Post: <mailto:gein@mail.gjk4all.net> List-Subscribe: <https://www.gjk4all.net/mailman/listinfo/gein>, <mailto:gein-request@mail.gjk4all.net? subject=subscribe> List-Id: <gein.mail.gjk4all.net> List-Unsubscribe: <https://www.gjk4all.net/mailman/listinfo/gein>, <mailto:gein-request@mail.gjk4all.net? subject=unsubscribe> List-Archive: <http://www.gjk4all.net/archive/gein/> Date: Fri, 11 Jan 2002 10:00:28 +0100 (CET) This is a multi-part message in MIME format... ------------=_1010739627-91125-0 Content-Type: Text/HTML Content-Disposition: inline Content-Transfer-Encoding: binary Content-Id: Part-1-20020111@ ------------=_1010739627-91125-0 Content-Type: image/gif; name="fokke_sukke_20020111.gif" Content-Disposition: inline; filename="fokke_sukke_20020111.gif" Content-Transfer-Encoding: base64 Content-Id: Part-2-20020111@ ------------=_1010739627-91125-0-- =========================================== Second message 10:03 Received: from sat-relay1.telecom.ptt.nl (sat- relay1.pc.telecom.ptt.nl [10.1.88.11]) by tmail050s.telecom.ptt.nl with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YJKFRJDY; Fri, 11 Jan 2002 10:02:27 +0100 Received: from hdiro004.kpn.com (hdiro004.kpn.com [145.7.200.4]) by sat-relay1.telecom.ptt.nl (8.11.6/8.11.6) with SMTP id g0B92Uj21921; Fri, 11 Jan 2002 10:02:30 +0100 Received: from 145.7.200.7 by hdiro004.kpn.com (InterScan E- Mail VirusWall NT); Fri, 11 Jan 2002 10:02:30 +0100 Received: from mail.gjk4all.net (mail.gjk4all.net [213.196.2.118]) by relay2.kpn-telecom.nl (8.11.6/8.11.6) with ESMTP id g0B92Tv07835; Fri, 11 Jan 2002 10:02:29 +0100 Received: from mail.gjk4all.net (mail.gjk4all.net [213.196.2.118]) by mail.gjk4all.net (Postfix) with ESMTP id 8C63C7F9A; Fri, 11 Jan 2002 10:02:28 +0100 (CET) Received: by mail.gjk4all.net (Postfix, from userid 1011) id D42257C9A; Fri, 11 Jan 2002 10:00:28 +0100 (CET) Content-Type: Multipart/Related; boundary="---------- =_1010739627-91125-0" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.411 (Entity 5.404) To: gein(a)gjk4all.net Message-Id: <20020111090028.D42257C9A(a)mail.gjk4all.net> From: gein-admin(a)gjk4all.net Reply-To: gein(a)gjk4all.net Subject: [Gein] Dagelijkse portie fokke en sukke Sender: gein-admin(a)gjk4all.net Errors-To: gein-admin(a)gjk4all.net X-BeenThere: gein(a)mail.gjk4all.net X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: <mailto:gein-request@mail.gjk4all.net? subject=help> List-Post: <mailto:gein@mail.gjk4all.net> List-Subscribe: <https://www.gjk4all.net/mailman/listinfo/gein>, <mailto:gein-request@mail.gjk4all.net? subject=subscribe> List-Id: <gein.mail.gjk4all.net> List-Unsubscribe: <https://www.gjk4all.net/mailman/listinfo/gein>, <mailto:gein-request@mail.gjk4all.net? subject=unsubscribe> List-Archive: <http://www.gjk4all.net/archive/gein/> Date: Fri, 11 Jan 2002 10:00:28 +0100 (CET) This is a multi-part message in MIME format... ------------=_1010739627-91125-0 Content-Type: Text/HTML Content-Disposition: inline Content-Transfer-Encoding: binary Content-Id: Part-1-20020111@ ------------=_1010739627-91125-0 Content-Type: image/gif; name="fokke_sukke_20020111.gif" Content-Disposition: inline; filename="fokke_sukke_20020111.gif" Content-Transfer-Encoding: base64 Content-Id: Part-2-20020111@ ------------=_1010739627-91125-0-- ==================================== Errors: error:Jan 11 10:02:15 2002 qrunner(91278): Traceback (most recent call last): error:Jan 11 10:02:15 2002 qrunner(91278): File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 213, in ArchiveMail error:Jan 11 10:02:15 2002 qrunner(91278): self.ExternalArchive(mm_cfg.PUBLIC_EXTERNAL_ARCHIVER, txt) error:Jan 11 10:02:15 2002 qrunner(91278): File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 174, in ExternalArchive error:Jan 11 10:02:15 2002 qrunner(91278): syslog ('error', 'external archiver non-zero exit status: %d\n' % error:Jan 11 10:02:15 2002 qrunner(91278): TypeError: bad operand type(s) for >> error:Jan 11 10:02:15 2002 (91278) CORRUPT ARCHIVE FOR LIST: gein error:Jan 11 10:02:27 2002 qrunner(91278): Traceback (most recent call last): error:Jan 11 10:02:27 2002 qrunner(91278): File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 213, in ArchiveMail error:Jan 11 10:02:27 2002 qrunner(91278): self.ExternalArchive(mm_cfg.PUBLIC_EXTERNAL_ARCHIVER, txt) error:Jan 11 10:02:27 2002 qrunner(91278): File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 174, in ExternalArchive error:Jan 11 10:02:27 2002 qrunner(91278): syslog ('error', 'external archiver non-zero exit status: %d\n' % error:Jan 11 10:02:27 2002 qrunner(91278): TypeError: bad operand type(s) for >> error:Jan 11 10:02:27 2002 (91278) CORRUPT ARCHIVE FOR LIST: gein post:Jan 11 10:02:23 2002 (91278) post to gein from gein- admin(a)mail.gjk4all.net, size=12424, success post:Jan 11 10:02:36 2002 (91278) post to gein from gein- admin(a)mail.gjk4all.net, size=12424, success qrunner:Jan 11 10:02:00 2002 (91278) Exception reading qfile: /usr/local/mailman/qfiles/2e3744b0aa565e294e50cc52632 bb41cb439b904 qrunner:Jan 11 10:02:00 2002 (91278) Exception reading qfile: /usr/local/mailman/qfiles/3142c3521506e1863bcab1aaab4 eb9b00b556d90 qrunner:Jan 11 10:02:00 2002 (91278) Exception reading qfile: /usr/local/mailman/qfiles/35bd0398c386c9fa5949935d920 6517d6bff0e35 qrunner:Jan 11 10:02:00 2002 (91278) Exception reading qfile: /usr/local/mailman/qfiles/871f29104cec59a6c8046bc8a9e bf3047fa800b6 qrunner:Jan 11 10:02:00 2002 (91278) Exception reading qfile: /usr/local/mailman/qfiles/c0e97e9812d06e3e9eb47b29f18 1c26da7dbf6cc qrunner:Jan 11 10:02:00 2002 (91278) Exception reading qfile: /usr/local/mailman/qfiles/5f20c0dcd3c3a96ff32df4fe272 52589a93c8cbb qrunner:Jan 11 10:02:00 2002 (91278) Exception reading qfile: /usr/local/mailman/qfiles/e71a75f4429e10b4a8befe6f429 48d0a5f8d4fcd smtp:Jan 11 10:02:20 2002 (91278) smtp for 28 recips, completed in 4.455 seconds smtp:Jan 11 10:02:36 2002 (91278) smtp for 28 recips, completed in 8.968 seconds ---------------------------------------------------------------------- Comment By: J. Ros (ros005) Date: 2001-12-31 19:00 Message: Logged In: YES user_id=414801 Hi, I am the listadmin of gjk4all. We still have the same problem. Messages get sent more than once. This means not only administrative messages of Mailman to the moderator or users, but also regular posts to menmbers. I noticed the same problem on a different mailing list I am subscribed to: http://www.giggleshumor.com The problem seems to be related to the time of day. I hope you can find a solution. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2001-06-04 20:41 Message: Logged In: YES user_id=12800 In order to debug this, I would need a copy of the all duplicates for one of the duplicated messages. Please include /all/ the original headers, as that's the only way to determine what's going on. My suspicion is that there are multiple qrunners running, and that they aren't getting locked out correctly for some reason. Clearly, we have not seen similar bugs for MM2.0.5 on {python,zope}.org, so I expect it to be a configuration problem. ---------------------------------------------------------------------- Comment By: Gert Jan Kruizinga (gjk4all) Date: 2001-05-29 16:14 Message: Logged In: YES user_id=222418 No, all the users of the list also get the `"your message awaits moderator approval" message twice. Btw i'm not the listadmin, only the server admin, my listadmin also complains that he gets the "messages awaiting moderator approval" message sometimes 2, 3 or even 4 times, but he submitted two email addresses of his own, so that can be explaind. Gert Jan Kruizinga. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2001-05-29 15:56 Message: Logged In: YES user_id=34209 Are you sure you aren't listed as the list-admin several times ? Do you get each messages that many times ? What about the message headers: can you see where they get 'duplicated' ? (Compare Received: lines and message-id's between the duplicates to find out.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=425121&group_i…

1 0

[ mailman-Bugs-564587 ] config_list breaks at filter_mime_types
by noreply＠sourceforge.net 25 Jul '02

25 Jul '02

Bugs item #564587, was opened at 2002-06-04 14:06 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=564587&group_i… Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Devin L. Ganger (dlganger) >Assigned to: Barry A. Warsaw (bwarsaw) Summary: config_list breaks at filter_mime_types Initial Comment: When running: config_list -o cpunk.conf cpunk-secpro on my list cpunk-secpro(a)lists.thecabal.org, I get the following error: (bofh:mailman) /home/mailman $ config_list -o cpunk.conf cpunk-secpro Traceback (most recent call last): File "/home/mailman/bin/config_list", line 268, in ? main() File "/home/mailman/bin/config_list", line 261, in main do_output(listname, outfile) File "/home/mailman/bin/config_list", line 113, in do_output do_list_categories(mlist, k, None, outfp) File "/home/mailman/bin/config_list", line 162, in do_list_categories lines = value.replace('\r', '').split('\n') AttributeError: 'list' object has no attribute 'replace' Doing a tail of the cpunk.conf file show the following: (bofh:mailman) /home/mailman $ tail cpunk.conf # matching MIME major type, e.g. image. Blank lines are ignored. # # After stripping message parts, any multipart attachment that is empty # as a result is removed all together. If the outer part's MIME type # matches one of the strip types, or if all of the outer part's subparts # are stripped, then the whole message is discarded. Finally, each # multipart/alternative section will be replaced by just the first # alternative that is non-empty after the specified types have been # removed. filter_mime_types = ---------------------------------------------------------------------- Comment By: Jay Luker (lbjay) Date: 2002-07-24 14:19 Message: Logged In: YES user_id=51347 I'm experiencing the same problem on a debian (woody) install, python -V = 2.2 I worked around it temporarily by adding a varname != filter_mime_types condition to the "if" on L268. ---------------------------------------------------------------------- Comment By: Devin L. Ganger (dlganger) Date: 2002-06-04 14:08 Message: Logged In: YES user_id=478874 This is on Solaris 7, Python 2.2: (bofh:devin) /home/devin $ python -V Python 2.2 (bofh:devin) /home/devin $ uname -a SunOS bofh.thecabal.internal 5.7 Generic_106541-14 sun4m sparc SUNW,SPARCsystem-600 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=564587&group_i…

1 0

[ mailman-Bugs-564587 ] config_list breaks at filter_mime_types
by noreply＠sourceforge.net 24 Jul '02

24 Jul '02

Bugs item #564587, was opened at 2002-06-04 21:06 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=564587&group_i… Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Devin L. Ganger (dlganger) Assigned to: Nobody/Anonymous (nobody) Summary: config_list breaks at filter_mime_types Initial Comment: When running: config_list -o cpunk.conf cpunk-secpro on my list cpunk-secpro(a)lists.thecabal.org, I get the following error: (bofh:mailman) /home/mailman $ config_list -o cpunk.conf cpunk-secpro Traceback (most recent call last): File "/home/mailman/bin/config_list", line 268, in ? main() File "/home/mailman/bin/config_list", line 261, in main do_output(listname, outfile) File "/home/mailman/bin/config_list", line 113, in do_output do_list_categories(mlist, k, None, outfp) File "/home/mailman/bin/config_list", line 162, in do_list_categories lines = value.replace('\r', '').split('\n') AttributeError: 'list' object has no attribute 'replace' Doing a tail of the cpunk.conf file show the following: (bofh:mailman) /home/mailman $ tail cpunk.conf # matching MIME major type, e.g. image. Blank lines are ignored. # # After stripping message parts, any multipart attachment that is empty # as a result is removed all together. If the outer part's MIME type # matches one of the strip types, or if all of the outer part's subparts # are stripped, then the whole message is discarded. Finally, each # multipart/alternative section will be replaced by just the first # alternative that is non-empty after the specified types have been # removed. filter_mime_types = ---------------------------------------------------------------------- Comment By: Jay Luker (lbjay) Date: 2002-07-24 21:19 Message: Logged In: YES user_id=51347 I'm experiencing the same problem on a debian (woody) install, python -V = 2.2 I worked around it temporarily by adding a varname != filter_mime_types condition to the "if" on L268. ---------------------------------------------------------------------- Comment By: Devin L. Ganger (dlganger) Date: 2002-06-04 21:08 Message: Logged In: YES user_id=478874 This is on Solaris 7, Python 2.2: (bofh:devin) /home/devin $ python -V Python 2.2 (bofh:devin) /home/devin $ uname -a SunOS bofh.thecabal.internal 5.7 Generic_106541-14 sun4m sparc SUNW,SPARCsystem-600 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=564587&group_i…

1 0

2.1b2 error after reboot
by Luigi Rosa 24 Jul '02

24 Jul '02

Hello, half an hour ago I suffered an unscheduled power outage, when my Linux (RH 7.3) rebooted, I had to correct an unlinked i-node in /tmp file system (apparently a .pid file). The qrunner deamon did not start and reported this error: Jul 24 16:34:34 2002 mailmanctl(1040): Traceback (most recent call last): Jul 24 16:34:34 2002 mailmanctl(1040): File "/usr/local/mailman/bin/mailmanctl", line 501, in ? Jul 24 16:34:34 2002 mailmanctl(1040): main() Jul 24 16:34:34 2002 mailmanctl(1040): File "/usr/local/mailman/bin/mailmanctl", line 351, in main Jul 24 16:34:34 2002 mailmanctl(1040): lock = acquire_lock(force) Jul 24 16:34:34 2002 mailmanctl(1040): File "/usr/local/mailman/bin/mailmanctl", line 202, in acquire_lock Jul 24 16:34:34 2002 mailmanctl(1040): lock = acquire_lock_1(force) Jul 24 16:34:34 2002 mailmanctl(1040): File "/usr/local/mailman/bin/mailmanctl", line 196, in acquire_lock_1 Jul 24 16:34:34 2002 mailmanctl(1040): os.unlink(tempfile) Jul 24 16:34:34 2002 mailmanctl(1040): OSError : [Errno 2] No such file or directory: 'master-qrunner.mail.hypertrek.info.25776' Then I did a # service mailman stop and mailman logged this Jul 24 16:35:27 2002 mailmanctl(1112): No child with pid: 25776 Jul 24 16:35:27 2002 mailmanctl(1112): [Errno 3] No such process Jul 24 16:35:27 2002 mailmanctl(1112): Stale pid file removed. after that I did a # service mailman start and everything was Ok. This could be a serious issue in case of unattended machines, is there a solution for this error? -- Best regards, Luigi mailto:lrosa@mail.hypertrek.info

3 7

[ mailman-Bugs-565917 ] mailmanctl bombs after unclean shutdown
by noreply＠sourceforge.net 24 Jul '02

24 Jul '02

Bugs item #565917, was opened at 2002-06-07 14:02 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=565917&group_i… Category: command line scripts Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Dale Stimson (dstimson) Assigned to: Nobody/Anonymous (nobody) Summary: mailmanctl bombs after unclean shutdown Initial Comment: Environment: Red Hat 7.3, latest errata, Mailman 2.1b2 I see that this problem still exists in the current CVS as of a day or two ago. When mailman restarts after having been shutdown uncleanly (e.g., when rebooting following a crash), it bombs leaving no qrunners active with the following in the log: Jun 04 18:05:13 2002 mailmanctl(1572): Traceback (most recent call last): Jun 04 18:05:13 2002 mailmanctl(1572): File "/var/mailman/bin/mailmanctl", line 502, in ? Jun 04 18:05:13 2002 mailmanctl(1572): main() Jun 04 18:05:13 2002 mailmanctl(1572): File "/var/mailman/bin/mailmanctl", line 352, in main Jun 04 18:05:13 2002 mailmanctl(1572): lock = acquire_lock(force) Jun 04 18:05:13 2002 mailmanctl(1572): File "/var/mailman/bin/mailmanctl", line 203, in acquire_lock Jun 04 18:05:13 2002 mailmanctl(1572): lock = acquire_lock_1(force) Jun 04 18:05:13 2002 mailmanctl(1572): File "/var/mailman/bin/mailmanctl", line 197, in acquire_lock_1 Jun 04 18:05:13 2002 mailmanctl(1572): os.unlink(tempfile) Jun 04 18:05:13 2002 mailmanctl(1572): OSError : [Errno 2] No such file or directory: 'master-qrunner.cupro.opengvs.com.9014' Diagnosis: In file bin/mailmanctl, function acquire_lock_1 is attempting to delete the lock file left over from the last run. It calls function get_lock_data to find the name of the old lock file that is to be deleted. Function get_lock_data (incorrectly) returns the file name with the directory part of the path stripped, thereby causing the delete to fail and the trap to occur. Function get_lock_data should instead return the entire file path, including directories. The patch given below corrects the behavior of get_lock_data. As an aside, it would be nice if acquire_lock_1 was more forgiving if the os.unlink calls fail due to "no such file". I have not submitted a patch for that as I don't know the appropriate python semantics. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 14:51 Message: Logged In: YES user_id=12800 Thanks! I'm going to fix this in a slightly different way, but your patch definitely paved the way. ---------------------------------------------------------------------- Comment By: E. Viennet (anotong) Date: 2002-07-07 03:26 Message: Logged In: YES user_id=396722 I also observed this behavior. I did patch my mailman (mailmanctl, acquire_lock_1) by putting try/except pairs around each call to unlink(), but I'm not sure it's the correct fix. ---------------------------------------------------------------------- Comment By: Dale Stimson (dstimson) Date: 2002-06-07 14:14 Message: Logged In: YES user_id=559033 Please ignore uploaded file sf1.txt (it won't let me delete it), which has cruft in it (the problem report text), as opposed to just the patch). The file with just the patch is sf.txt. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=565917&group_i…

1 0

A question about mime to links
by Michael Meltzer 24 Jul '02

24 Jul '02

For give me if this has come up before but I could not find much in a archive. I am running a small list with mailman/postfix, I would really like to demine/dehtml it for the digest users and the archive. The problem is I still want to support image attachments(maybe a few other types) to the email(the users like it :-). I had the great idea to convert the attachment to files and replace them in the email with a URL. I looked around and it seems 2.1 will handle the attachment issue but I am not sure about converting to links. SO: 1)changing to sendmail it out, so their goes mimedefang. 2)Any idea how to do this simply 3)it seem version 2.1 beta 2 has most of what I need, Anyone graftied in subport for what I need with the links. 4)Any Guidance how/where and what level in the code to add it myself 5)I will admint I am not an expert on mime, any show stoppers or "I am asking for it issues" MJM

1 0

[ mailman-Bugs-585833 ] Forward posts held for approval
by noreply＠sourceforge.net 24 Jul '02

24 Jul '02

Bugs item #585833, was opened at 2002-07-24 10:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i… Category: mail delivery Group: 2.1 beta Status: Closed Resolution: Fixed Priority: 5 Submitted By: Ousmane Wilane (wilane) Assigned to: Nobody/Anonymous (nobody) Summary: Forward posts held for approval Initial Comment: FWIW I'm using the current cvs. When I forward a mail which was held for approval to my email address (oversized mail in this case) I get the provided traceback in my logs and the mail in shunt q: ---------------------------------------------------------------------- >Comment By: Ousmane Wilane (wilane) Date: 2002-07-24 17:26 Message: Logged In: YES user_id=47556 I swear I did restart it :):) More seriously I stop postfix, apache, mailman before upgrading as outlined in the UPGRADING file ... :) I also did verify that ListAdmin.py 2.39 was checked out This time I'll paste the traceback here (it's thrown in logs/error when I try to unshunt the messages): Jul 24 17:17:25 2002 (30049) 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 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 134, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 307, in bulkdeliver msgtext = msg.as_string() File "/usr/local/mailman/pythonlib/email/Message.py", line 99, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/local/mailman/pythonlib/email/Generator.py", line 81, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 109, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 141, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 283, in _handle_message g.flatten(msg.get_payload(0), unixfrom=0) File "/usr/local/mailman/pythonlib/email/Message.py", line 167, in get_payload raise TypeError, i TypeError: 0 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 15:46 Message: Logged In: YES user_id=12800 Be sure you "mailmanctl restart" :) ---------------------------------------------------------------------- Comment By: Ousmane Wilane (wilane) Date: 2002-07-24 15:26 Message: Logged In: YES user_id=47556 Oops! After cvs -q up -P -d, The bug stood there with the same traceback. Maybe I'm doing something wrong but don't know what ... :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 14:04 Message: Logged In: YES user_id=12800 Fixed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i…

1 0

Mailman-Developers July 2002