Mailman 3 December 2002 - Mailman-Developers

[ mailman-Patches-647083 ] compress dies w/ MemoryError
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Patches item #647083, was opened at 2002-12-02 10:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=647083&group_i… Category: command line scripts Group: None Status: Open Resolution: None Priority: 5 Submitted By: John-Mark Gurney (jmg) Assigned to: Nobody/Anonymous (nobody) Summary: compress dies w/ MemoryError Initial Comment: If you have a large mailing list, it is very easy to quickly exhast memory in many conditions. nightly_gzip script tries to load the entire file into memory before compressing it, not only is this terribly ineffecient, it also means you are limited to file sizes that can fit in memory. Some machines also further restrict how much memory each process can access at a time. If that limit is 512megs, and you have a 400+meg file, compress will die. Solution: read/write the file in blocks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=647083&group_i…

1 0

[ mailman-Bugs-610570 ] RFC 2369 URL is broken
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #610570, was opened at 2002-09-17 10:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610570&group_i… Category: documentation Group: 2.1 beta >Status: Closed >Resolution: Out of Date Priority: 7 Submitted By: Nick Arnett (narnett) Assigned to: Nobody/Anonymous (nobody) Summary: RFC 2369 URL is broken Initial Comment: Paths to RFCs have changed. The correct one for 2369 is now http://www.faqs.org/rfcs/rfc2369.html ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-02 11:26 Message: Logged In: YES user_id=12800 I think this is out of date, since all references in 2.1b5+ cvs point to this location. Or do you know of a place I'm missing? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610570&group_i…

1 0

[ mailman-Bugs-419992 ] bin/arch messed up existing web archive
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #419992, was opened at 2001-04-29 14:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=419992&group_i… Category: Pipermail Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: bin/arch messed up existing web archive Initial Comment: When running arch and webpages still exists, the web archive is messed up. This is quite confusing. A warning should be printed if arch is started on a list where there is already stuff in the web archive. Optionally it could delete the files is is regenerating first. Details: arch seems to attach each mail again to the .txt monthly archive files here and then build the web archive out of this. No wonder that the mail I deleted is still in after the process.... ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-02 11:25 Message: Logged In: YES user_id=12800 I (finally) fixed this by giving bin/arch a --wipe argument ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=419992&group_i…

1 0

[ mailman-Bugs-612174 ] subscribe_policy + ALLOW_OPEN_SUBSCRIBE
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #612174, was opened at 2002-09-20 11:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612174&group_i… Category: command line scripts Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Jay Luker (lbjay) Assigned to: Nobody/Anonymous (nobody) Summary: subscribe_policy + ALLOW_OPEN_SUBSCRIBE Initial Comment: There is a flaw somewhere in the logic that alters the value of subscribe_policy based on the value of mm_cfg.ALLOW_OPEN_SUBSCRIBE. I have ALLOW_OPEN_SUBSCRIBE = 0. When I attempt to set subscribe_policy = 1 via the config_list script, subscribe_policy is always set to 2. ---------------------------------------------------------------------- Comment By: Jay Luker (lbjay) Date: 2002-09-20 12:02 Message: Logged In: YES user_id=51347 OK, I was just able to track this down further. The problem (I think) lies in Gui/Privacy.py. _setValue states: "For subscribe_policy when ALLOW_OPEN_SUBSCRIBE is true, we need to add one to the value because the page didn't present an open list as an option." ... but then the subsequent code actually adds one to the value if ALLOW_OPEN_SUBSCRIBE is untrue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612174&group_i…

1 0

[ mailman-Bugs-640374 ] 2.1b4 Mailman bug
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #640374, was opened at 2002-11-18 17:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640374&group_i… Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Paul Marshall (paulmarshll) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1b4 Mailman bug Initial Comment: When I try to access some of my lists via the web interface to moderate them I receive this error message: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/admindb.py", line 227, in main show_pending_unsubs(mlist, form) File "/var/mailman/Mailman/Cgi/admindb.py", line 332, in show_pending_unsubs fullname = Utils.uncanonstr(mlist.getMemberName (addr), lang) File "/var/mailman/Mailman/OldStyleMemberships.py", line 128, in getMemberName self.__assertIsMember(member) File "/var/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member NotAMemberError: capeterson28(a)hotmail.com This is only a problem for some of my lists. Some lists I can log into and moderate successfully from the Web. I am running Mailman 2.1b4 on RedHat Linux 7.3. Let me know if you need more information. Thanks for your help. Paul Marshall ---------------------------------------------------------------------- Comment By: Paul Marshall (paulmarshll) Date: 2002-11-19 14:27 Message: Logged In: YES user_id=582441 I recently upgraded to Mailman 2.1b5, however I still receive this error when I try to log into some of the lists. Thanks. Paul. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640374&group_i…

1 0

[ mailman-Bugs-644005 ] sync_members: problems with u umlaut
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #644005, was opened at 2002-11-26 04:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644005&group_i… Category: command line scripts Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Matthias Klose (doko) Assigned to: Nobody/Anonymous (nobody) Summary: sync_members: problems with u umlaut Initial Comment: Running sync_members -n, I get this error, when a member with an umlaut-u in it's real name gets removed. Traceback (most recent call last): File "/usr/sbin/sync_members", line 283, in ? main() File "/usr/sbin/sync_members", line 275, in main print _('Removed: <%(addr)30s> %(name)s') UnicodeError: ASCII encoding error: ordinal not in range(128) Changing the ü in the web-frontend to ue, and then running again sync_members "fixes" the problem. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-02 11:15 Message: Logged In: YES user_id=12800 The same problem affects list_members. I think I've fixed them both by coercing the unicode text to a byte string in the default encoding. That's about the only way to know what encoding is going to be used by stdout, AFAICT. Please check and if this isn't sufficient, we'll have to think of something else. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=644005&group_i…

1 0

[ mailman-Bugs-229568 ] Pipermail won't resolve author names of aol.com addresses
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #229568, was opened at 2001-01-20 22:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=229568&group_i… Category: Pipermail Group: 2.1 beta >Status: Closed >Resolution: Out of Date Priority: 7 Submitted By: Aharon Varady (aharon) Assigned to: Nobody/Anonymous (nobody) Summary: Pipermail won't resolve author names of aol.com addresses Initial Comment: Pipermail does not resolve the "author" of emails sent from aol.com. Instead, Pipermail gives the email address of the listserve. For example: "John" <user(a)aol.com> is resolved by pipermail as: listname(a)foo.com and not as John. This bug only occurs for users of aol.com addresses. ---------------------------------------------------------------------- Comment By: Terri Oda (spot) Date: 2002-07-02 16:00 Message: Logged In: YES user_id=110886 Whoops. Diffed the wrong thing. That's what happens when I try to patch code but haven't slept in a few days. This actually works better: 180c180 < if e is not None: --- > if e is not None and self.email == "": ---------------------------------------------------------------------- Comment By: Terri Oda (spot) Date: 2002-07-01 14:03 Message: Logged In: YES user_id=110886 The problem is that it defaults to using the reply-to address if it's set, and this isn't what we want when the reply-to is always being set by the list. Take a careful look at the rest of your archives and you'll probably note that *everyone's* email address is showing up as listname(a)foo.com. It's a nice anti-spam feature, perhaps, but probably not what you want. Here's a quick fix for pipermail.py: 180c180 < if e is not None: --- > if e is not None and self.email is None: This just changes it so that it defaults to the From: address (when it's set) rather than the Reply-to address. If there's some particular reason to take the Reply-To over the From, I can make something which actually checks to see if the reply-to is being set by the list, but this should solve your problem for the moment. Terri ---------------------------------------------------------------------- Comment By: Ava Jarvis (katanalynx) Date: 2002-06-10 22:14 Message: Logged In: YES user_id=561110 This bug -- for version 2.0.11 at least -- seems to occur when 'from' only contains the email address. There's some code in pipermail.py (version 2.0.11), line 177: <excerpt> # Figure out the e-mail address and poster's name self.author, self.email = message.getaddr('From') e = message.getheader('Reply-To') if e is not None: self.email = e self.email = strip_separators(self.email) self.author = strip_separators(self.author) if self.author == "": self.author = self.email </excerpt> If reply-to is set, then it is always taken as the author's email address. However, some lists set the reply-to field to be, for instance, the list address.... and you can guess what happens next when there is no name comment/author. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-06-06 12:09 Message: Logged In: NO This comment doesn't directly address the case you report, but it might be related so I thought it worthwhile to submit. I see you are using MM2.0.9. I saw a similar problem with MM2.1b1, which was fixed in MM2.1b2. The problem then was that an address with a name "comment" would be displayed in the archive as the list name, whereas an address with a name comment would be displayed (properly) with the name. Example: "John Doe" jdoe(a)whereever.com displayed as "John Doe" whereas jdoe(a)whereever.com displayed as the list name. In your comment, you use an example with a name comment of "John", but in the example you provided there is no name comment field, so perhaps my statements here do apply. ---------------------------------------------------------------------- Comment By: Aharon Varady (aharon) Date: 2002-06-05 21:37 Message: Logged In: YES user_id=139355 Well, this remains (and has always been) a problem for my lists. I have never had a user posting with an aol.com address that this hasn't been the case with. Currently my solution is to replace the wrong address shown (philly_ambient(a)phobos.serve.com) with a generic or balnk mark. Here is the html source of a typical email from our pipermail archive, and below it the source email with headers. ------------------------------------------------------------- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <html> <head> <title> [Philly_ambient] tool! </title> <link REL="Index" HREF="index.html" > <link REL="made" HREF="mailto:philly_ambient%40phobos.serve.com"> <meta NAME="robots" CONTENT="index,nofollow"> <link REL="Previous" href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/002904.html"> <link REL="Next" href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/002911.html"> <style TYPE="text/css"></style></head> <body BGCOLOR="#cccccc"><font face="Arial,Helvetica" size=-1><ul> <h4>[Philly_ambient] tool!</h4>Posted by <b>. . . .. . . .</b> on <i>Mon Jun 3 23:17:02 2002</i> <p></font><table cellpadding=3><tr><td bgcolor=#FFFFFF width="475"><font face="geneva,courier"><tt>  <pre>hey all a friend can get me some free tickets to see TOOL on monday august 12 at sovereign bank arena in trenton. i know mondays suck, but oh well. is anyone here into going? if so, contact me privately. i know it's not ambient, but neither is some of what we discuss here :) let me know asap, please gina </pre>  </tt></font></td></tr></table><font face="Arial,Helvetica" size=-1> <p>  <li> Previous message: <a href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/002904.html">[Philly_ambient] Noise Deafinitions and playlist </a></li> <li> Next message: <a href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/002911.html">[Philly_ambient] Do you hear what I hear? (re: noise deaf) </a></li> <li> <b>Messages sorted by:</b> <a href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/date.html#2907">[ date ]</a> <a href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/thread.html#2907">[ thread ]</a> <a href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/subject.html#2907">[ subject ]</a> <a href="http://phobos.serve.com/pipermail/philly_ambient/2002-June/author.html#2907">[ author ]</a> </li> </body></html> --------------------------------------------------------------------- Here is the original email with headers: --------------------------------------------------------------- >From - Tue Jun 04 01:16:56 2002 X-UIDL: m;n!!9'f!!a2E"!3;D"! X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: <philly_ambient-admin(a)phobos.serve.com> Delivered-To: aharon(a)phobos.serve.com Received: from phobos.serve.com (localhost.localdomain [127.0.0.1]) by phobos.serve.com (Postfix) with ESMTP id 6BC4D52D2B; Mon, 3 Jun 2002 23:17:06 -0400 (EDT) Delivered-To: philly_ambient(a)phobos.serve.com Received: from imo-r06.mx.aol.com (imo-r06.mx.aol.com [152.163.225.102]) by phobos.serve.com (Postfix) with ESMTP id 6F82F52D1D for <philly_ambient(a)phobos.serve.com>; Mon, 3 Jun 2002 23:16:46 -0400 (EDT) Received: from Mistsojorn(a)aol.com by imo-r06.mx.aol.com (mail_out_v32.5.) id p.d4.184e63f9 (17378) for <philly_ambient(a)phobos.serve.com>; Mon, 3 Jun 2002 23:14:35 -0400 (EDT) From: Mistsojorn(a)aol.com Message-ID: <d4.184e63f9.2a2d8a9b(a)aol.com> To: philly_ambient(a)phobos.serve.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 4.0 for Mac - Post-GM sub 66 Subject: [Philly_ambient] tool! Sender: philly_ambient-admin(a)phobos.serve.com Errors-To: philly_ambient-admin(a)phobos.serve.com X-BeenThere: philly_ambient(a)phobos.serve.com X-Mailman-Version: 2.0.9 Precedence: bulk Reply-To: philly_ambient(a)phobos.serve.com List-Help: <mailto:philly_ambient-request@phobos.serve.com?subject=help> List-Post: <mailto:philly_ambient@phobos.serve.com> List-Subscribe: <http://phobos.serve.com/mailman/listinfo/philly_ambient>, <mailto:philly_ambient-request@phobos.serve.com?subject=subscribe> List-Id: a discussion list relevant to Philadelphia Ambient and Experimental Psychedelic Music Enthusiasts <philly_ambient.phobos.serve.com> List-Unsubscribe: <http://phobos.serve.com/mailman/listinfo/philly_ambient>, <mailto:philly_ambient-request@phobos.serve.com?subject=unsubscribe> List-Archive: <http://phobos.serve.com/pipermail/philly_ambient/> X-Original-Date: Mon, 3 Jun 2002 23:14:35 EDT Date: Mon, 3 Jun 2002 23:14:35 EDT X-UIDL: m;n!!9'f!!a2E"!3;D"! hey all a friend can get me some free tickets to see TOOL on monday august 12 at sovereign bank arena in trenton. i know mondays suck, but oh well. is anyone here into going? if so, contact me privately. i know it's not ambient, but neither is some of what we discuss here :) let me know asap, please gina _______________________________________________ Philly_ambient mailing list Philly_ambient(a)phobos.serve.com Subscribe, Unsubscribe, Edit Options at: http://phobos.serve.com/mailman/listinfo/philly_ambient a PAC(MaN) List http://simpletone.com -------------------------------------------------------------------- I don't know why pipermail would treat my aol subscribers different either. But it is. Aharon ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-28 21:11 Message: Logged In: YES user_id=12800 Bizarre. I've never seen this, and I can't see any reason why Pipermail would treat aol.com addresses any different. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=229568&group_i…

1 0

[ mailman-Bugs-642996 ] can't send Plain Digest w/multipart msg.
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #642996, was opened at 2002-11-24 02:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642996&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: Works For Me >Priority: 4 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: can't send Plain Digest w/multipart msg. Initial Comment: cron/senddigests and cgi-bin/admin/digest can't send plain digest when multipart message(s) are contained. Note: Attached file will solve this problem for only cron/senddigests, but not for cgi. Traceback: admin(17454): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(17454): [----- Mailman Version: 2.1b5 -----] admin(17454): [----- Traceback ------] admin(17454): Traceback (most recent call last): admin(17454): File "/usr/local/mail/mailman/scripts/driver", line 87, in run_main admin(17454): main() admin(17454): File "/usr/local/mail/mailman/Mailman/Cgi/admin.py", line 169, in main admin(17454): change_options(mlist, category, subcat, cgidata, doc) admin(17454): File "/usr/local/mail/mailman/Mailman/Cgi/admin.py", line 1229, in change_options admin(17454): gui.handleForm(mlist, category, subcat, cgidata, doc) admin(17454): File "/usr/local/mail/mailman/Mailman/Gui/GUIBase.py", line 169, in handleForm admin(17454): self._setValue(mlist, property, val, doc) admin(17454): File "/usr/local/mail/mailman/Mailman/Gui/Digest.py", line 148, in _setValue admin(17454): status = mlist.send_digest_now() admin(17454): File "/usr/local/mail/mailman/Mailman/Digester.py", line 60, in send_digest_now admin(17454): ToDigest.send_digests(self, mboxfp) admin(17454): File "/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests admin(17454): send_i18n_digests(mlist, mboxfp) admin(17454): File "/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py", line 301, in send_i18n_digests admin(17454): g(msg, unixfrom=0) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 100, in flatten admin(17454): self._write(msg) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 128, in _write admin(17454): self._dispatch(msg) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 154, in _dispatch admin(17454): meth(msg) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 212, in _handle_text admin(17454): raise TypeError, 'string payload expected: %s' % type(payload) admin(17454): TypeError: string payload expected: <type 'list'> ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-02 11:11 Message: Logged In: YES user_id=12800 I tried some examples but couldn't get this to reproduce. Can you send me an example message which, when sent through the plain text digest, causes it to barf like this? IOW, can you upload a reproducible test case? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642996&group_i…

1 0

[ mailman-Bugs-635462 ] Admin pages HTML does not set TEXT color
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #635462, was opened at 2002-11-08 07:13 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_i… Category: Web/CGI Group: 2.1 beta Status: Open >Resolution: Wont Fix >Priority: 4 Submitted By: Marcin Orlowski (carl-os) Assigned to: Nobody/Anonymous (nobody) Summary: Admin pages HTML does not set TEXT color Initial Comment: Mailman admin pages believe that TEXT color is always black and does not set it to, hoping nobody changes the defaults. And this is false assumption ;-) For testing purposes my defaults are black bg color and yellow text. And since admin pages sets bg to white it now exposes yellow fonts on white background here. Kinda unreadable. Solution -> fix template/css/whatever to set up text color to black. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-02 11:12 Message: Logged In: YES user_id=12800 There's no official css support yet. I won't fix this for MM2.1 unless someone can provide a really clean patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=635462&group_i…

1 0

[ mailman-Bugs-642996 ] can't send Plain Digest w/multipart msg.
by noreply＠sourceforge.net 02 Dec '02

02 Dec '02

Bugs item #642996, was opened at 2002-11-24 02:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642996&group_i… Category: mail delivery Group: 2.1 beta Status: Open >Resolution: Works For Me Priority: 7 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: can't send Plain Digest w/multipart msg. Initial Comment: cron/senddigests and cgi-bin/admin/digest can't send plain digest when multipart message(s) are contained. Note: Attached file will solve this problem for only cron/senddigests, but not for cgi. Traceback: admin(17454): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(17454): [----- Mailman Version: 2.1b5 -----] admin(17454): [----- Traceback ------] admin(17454): Traceback (most recent call last): admin(17454): File "/usr/local/mail/mailman/scripts/driver", line 87, in run_main admin(17454): main() admin(17454): File "/usr/local/mail/mailman/Mailman/Cgi/admin.py", line 169, in main admin(17454): change_options(mlist, category, subcat, cgidata, doc) admin(17454): File "/usr/local/mail/mailman/Mailman/Cgi/admin.py", line 1229, in change_options admin(17454): gui.handleForm(mlist, category, subcat, cgidata, doc) admin(17454): File "/usr/local/mail/mailman/Mailman/Gui/GUIBase.py", line 169, in handleForm admin(17454): self._setValue(mlist, property, val, doc) admin(17454): File "/usr/local/mail/mailman/Mailman/Gui/Digest.py", line 148, in _setValue admin(17454): status = mlist.send_digest_now() admin(17454): File "/usr/local/mail/mailman/Mailman/Digester.py", line 60, in send_digest_now admin(17454): ToDigest.send_digests(self, mboxfp) admin(17454): File "/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests admin(17454): send_i18n_digests(mlist, mboxfp) admin(17454): File "/usr/local/mail/mailman/Mailman/Handlers/ToDigest.py", line 301, in send_i18n_digests admin(17454): g(msg, unixfrom=0) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 100, in flatten admin(17454): self._write(msg) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 128, in _write admin(17454): self._dispatch(msg) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 154, in _dispatch admin(17454): meth(msg) admin(17454): File "/usr/local/mail/mailman/pythonlib/email/Generator.py", line 212, in _handle_text admin(17454): raise TypeError, 'string payload expected: %s' % type(payload) admin(17454): TypeError: string payload expected: <type 'list'> ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-02 11:11 Message: Logged In: YES user_id=12800 I tried some examples but couldn't get this to reproduce. Can you send me an example message which, when sent through the plain text digest, causes it to barf like this? IOW, can you upload a reproducible test case? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=642996&group_i…

1 0