Mailman 3 December 2004 - Mailman-coders

[ mailman-Bugs-1077104 ] Uncatched bounces (unknown MTA)
by SourceForge.net Dec. 15, 2004

Dec. 15, 2004

Bugs item #1077104, was opened at 2004-12-01 21:38 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077104&group_… Category: bounce detection Group: 2.1 (stable) >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Alster (alster) Assigned to: Nobody/Anonymous (nobody) Summary: Uncatched bounces (unknown MTA) Initial Comment: We're currently using Mailman version 2.1.4 at lists.indymedia.org. Lately we have received a couple of non delivery notifications which have not been recognized by mailman. I'm forwarding two of them to you hoping that you will be able to include a recognition mechanism for it in one of the upcoming Mailman releases. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-15 00:01 Message: Logged In: YES user_id=67709 I don't think these bounce messages are parsable in any way. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077104&group_…

1 0

[ mailman-Bugs-1077842 ] bug report (problem with Danish support?)
by SourceForge.net Dec. 14, 2004

Dec. 14, 2004

Bugs item #1077842, was opened at 2004-12-02 19:37 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077842&group_… Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Matt Dickinson (mdickins) Assigned to: Nobody/Anonymous (nobody) Summary: bug report (problem with Danish support?) Initial Comment: Hi, we've been running Mailman quite extensively, and created a new list, and had a bug reported to us. This is the only list we run foreign language support on (in this case Danish) - i guess that might be the cause? Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/options.py", line 239, in main loginpage(mlist, doc, user, language) File "/usr/local/mailman/Mailman/Cgi/options.py", line 813, in loginpage table.AddRow([_("""In order to change your membership option, you must File "/usr/local/mailman/Mailman/i18n.py", line 89, in _ return tns % dict ValueError: unsupported format character 'p' (0x70) at index 105 ------------------------------------------------------------------------ Python information: Variable Value sys.version 2.2.3 (#1, Aug 8 2003, 08:44:02) [GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-13)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------------------------ Environment variables: Variable Value HTTP_UA_OS MacOS CONTENT_LENGTH 93 HTTP_PRAGMA no-cache CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://lists.xxxx/xxxx/mailman/listinfo/dicar SCRIPT_FILENAME /var/www/mailman-cgi-bin/options PYTHONPATH /usr/local/mailman SERVER_SOFTWARE Apache/2.0.46 (Red Hat) SERVER_ADMIN webmaster@xxxx SCRIPT_NAME /mailman/options QUERY_STRING REQUEST_METHOD POST HTTP_HOST lists.xxxx.xxxx PATH_INFO /dicar SERVER_PROTOCOL HTTP/1.1 HTTP_EXTENSION Security/Remote-Passphrase HTTP_UA_CPU PPC REQUEST_URI /mailman/options/dicar HTTP_ACCEPT */* PATH_TRANSLATED /sites/lists.xxxx.xxxx/htdocs/dicar HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 5.23; Mac_PowerPC) HTTP_CONNECTION Keep-Alive SERVER_NAME lists.xxxx.xxxx REMOTE_ADDR 62.xxxx.xxxx.xxxx REMOTE_PORT 26446 HTTP_ACCEPT_LANGUAGE en UNIQUE_ID wbDAC4DOj@QAAEiMn0cAAAAm SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 SERVER_ADDR 128.xxxx.xxxx.xxxx DOCUMENT_ROOT /sites/lists.xxxx.xxxx/htdocs ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-14 23:58 Message: Logged In: YES user_id=67709 fixed in CVS ---------------------------------------------------------------------- Comment By: Jim Tittsler (jtittsler) Date: 2004-12-07 11:51 Message: Logged In: YES user_id=1488 There is a mistake in the Danish translation that shipped with 2.1.5. It is missing an 's' in one of the translated strings. <http://mail.python.org/pipermail/mailman-users/2004-August/038622.html> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077842&group_…

1 0

[ mailman-Bugs-1078482 ] Some bounces cause traceback after upgrading to Python 2.4
by SourceForge.net Dec. 14, 2004

Dec. 14, 2004

Bugs item #1078482, was opened at 2004-12-03 17:43 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1078482&group_… Category: bounce detection Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: Some bounces cause traceback after upgrading to Python 2.4 Initial Comment: Howdy, I'm running Mailman 2.1.5 and upgraded from Python 2.3.4 to Python 2.4 yesterday, and restarted all Mailman processes. Since then I've gotten 9 tracebacks in the error log as below, with ~130 bounces processed successfully during that time. I've never seen this error before with Mailman that I can remember. Dec 03 07:48:21 2004 qrunner(47971): Traceback (most recent call last): Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/ bin/qrunner", line 270, in ? Dec 03 07:48:21 2004 qrunner(47971): main() Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/ bin/qrunner", line 230, in main Dec 03 07:48:21 2004 qrunner(47971): qrunner.run() Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/ Mailman/Queue/Runner.py", line 87, in run Dec 03 07:48:21 2004 qrunner(47971): self._cleanup() Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/ Mailman/Queue/BounceRunner.py", line 220, in _cleanup Dec 03 07:48:21 2004 qrunner(47971): BounceMixin._cleanup(self) Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/ Mailman/Queue/BounceRunner.py", line 132, in _cleanup Dec 03 07:48:21 2004 qrunner(47971): self._register_bounces() Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/ Mailman/Queue/BounceRunner.py", line 120, in _register_bounces Dec 03 07:48:21 2004 qrunner(47971): mlist.registerBounce(addr, msg, day=day) Dec 03 07:48:21 2004 qrunner(47971): File "/home/mailman-2.1/ Mailman/Bouncer.py", line 131, in registerBounce Dec 03 07:48:21 2004 qrunner(47971): time.strftime('%d- %b-%Y', day + (0,)*6)) Dec 03 07:48:21 2004 qrunner(47971): ValueError : day of year out of range Do I need to do something with Mailman after updating to Python 2.4, or is this a bug? Thanks, Bryan ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-14 23:55 Message: Logged In: YES user_id=67709 fixed in CVS. ---------------------------------------------------------------------- Comment By: Bryan Fullerton (fehwalker) Date: 2004-12-10 18:02 Message: Logged In: YES user_id=660772 FWIW, I haven't seen any more of these tracebacks since Dec 3. It's possible there were some bounces in the qfiles directory from Python 2.3, though I thought I'd checked for that. Or perhaps some bounce messages generated by Python 2.3 came back in that made 2.4 unhappy. In any case, this appears to just have been a transient thing. Feel free to keep this bug open, as a Python 2.4 testing datapoint perhaps, or close it as you see fit. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1078482&group_…

1 0

[ mailman-Patches-1081180 ] Danish message catalog update
by SourceForge.net Dec. 14, 2004

Dec. 14, 2004

Patches item #1081180, was opened at 2004-12-08 08:37 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1081180&group_… Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Tom G. Christensen (tgc99) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Danish message catalog update Initial Comment: Fix 2 new fuzzies. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-10 12:52 Message: Logged In: YES user_id=67709 Thank you, Tom. Checked in CVS. ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2004-12-10 12:39 Message: Logged In: YES user_id=1159458 Rediff against CVS after the "chinese" update ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1081180&group_…

1 0

[ mailman-Bugs-975768 ] senddigests doesn't handle consecutive unparseable messages
by SourceForge.net Dec. 14, 2004

Dec. 14, 2004

Bugs item #975768, was opened at 2004-06-19 07:07 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975768&group_i… Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Andreas Voegele (voegelas) Assigned to: Nobody/Anonymous (nobody) Summary: senddigests doesn't handle consecutive unparseable messages Initial Comment: The following code fragment in send_i18n_digests in Mailman/ Handlers/ToDigest.py doesn't take into account that there could be several consecutive messages that are unparseable: msg = mbox.next() while msg is not None: if msg == '': # It was an unparseable message msg = mbox.next() [...] # Get the next message in the digest mailbox msg = mbox.next() I'm not that familiar with Python but I think that the following code should fix the problem: while 1: msg = mbox.next() if msg is None: break if msg == '': # It was an unparseable message continue [...] ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-14 23:50 Message: Logged In: YES user_id=67709 Fixed in CVS. Thank you! ---------------------------------------------------------------------- Comment By: Thomas Arendsen Hein (thomas_ah) Date: 2004-09-13 12:30 Message: Logged In: YES user_id=839582 This bug is still present and hit our mailman installation last friday. The problem occurs if the unparseable message is the last one, too. Here is a patch against current CVS, effectively doing the same as Andreas Voegele suggested, but with cleaner code. Unfortunately this tracker doesn't allow me to attach it, because I didn't submit this bug. diff -u -r2.28 ToDigest.py --- Mailman/Handlers/ToDigest.py 15 Aug 2003 21:06:28 -0000 2.28 +++ Mailman/Handlers/ToDigest.py 13 Sep 2004 12:22:03 -0000 @@ -210,6 +210,7 @@ if msg == '': # It was an unparseable message msg = mbox.next() + continue msgcount += 1 messages.append(msg) # Get the Subject header ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975768&group_i…

1 0

[ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option
by SourceForge.net Dec. 14, 2004

Dec. 14, 2004

Feature Requests item #923122, was opened at 2004-03-25 14:01 Message generated for change (Comment added) made by ura You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_i… Category: None Group: None Status: Closed Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: reply_goes_to_list allow poster+list option Initial Comment: Right now, the reply_goes_to_list option allows (a) poster, (b), list, and (c) explicit. How about (d) poster AND list? That is, insert/override a reply-to: header containing both the list name, and the original reply-to (if present, else From: address). For extra credit, omit the original poster if they are a list member. This would be very useful for a number of lists I maintain, where 90% of the traffic is among the list members (hence having a simple reply go to the list), yet a few messages come in from the outside world (hence including the original poster's address). I'm using mailman 2.1.4 on GNU/Linux. Thanks, karl(a)freefriends.org ---------------------------------------------------------------------- Comment By: URA Hiroshi (ura) Date: 2004-12-14 16:28 Message: Logged In: YES user_id=1007264 Hi shub. pleases read RFC2822 again. By RFC2822 3.6.2, it is defined as the "Relay-To:" header having one or more mail addresses. from RFC2822 3.4 & 3.6.2 | address-list = (address *("," address)) / obs-addr-list | reply-to = "Reply-To:" address-list CRLF However, it cannot have multiple "Reply-To:" headers as you say. from RFC2822 3.5. | Field Min number Max number Notes | reply-to 0 1 Thus, So, I believe that my patch is right. Am I misunderstanding? ---------------------------------------------------------------------- Comment By: karl berry (kberry) Date: 2004-11-25 18:40 Message: Logged In: YES user_id=33248 Whatever. There's obviously no point in debating it, since you think it is so terribly horrible and I don't see the problem with helping users, regardless of what "standards" would like to impose on us. So I'll try to mark this closed, and we can get on with our lives. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 18:32 Message: Logged In: YES user_id=18417 The problem is that this idea is likely to cause a number of programs to break, probably pretty badly. I think this is a very bad idea. We don't want to be doing things to encourage people to break the standards, especially since most people who would use this option would not understand the true scope of the problem. Using two "Reply-to:" headers doesn't resolve this issue, either. If you want to munge the "Reply-to:" header to point back to the list, then Mailman gives you the ability to do that. It's a bad idea, for the reasons laid out in the FAQ, but you do have that capability. ---------------------------------------------------------------------- Comment By: karl berry (kberry) Date: 2004-11-25 18:20 Message: Logged In: YES user_id=33248 I'm trying to help my users avoid a fairly common mistake, not engage in arguments about standards. Fine, Reply-to: list, poster may not work for the population of some lists. So those lists won't enable it. Meanwhile, it will help some people and lists, and there's no other way to accomplish the behavior (that I know of). It's trivial to add and a tiny change in the user interface. I am not asking for per-user control of this, which is what the FAQ entry you cited mostly discusses. Obviously some compromise has already been made with the "reply-to considered harmful" stance. (For which I am very thankful, because it is very useful.) ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 15:26 Message: Logged In: YES user_id=18417 I don't think this is possible. "Reply-to:" goes back to one address, not two. The action of having multiple "Reply-to:" headers is also undefined, and some clients may work the way you want, while others may work in ways you do not. Pretty much everything to do with "Reply-to:" is really a client problem, and needs to be solved there. See <http://www.python.org/cgi-bin/ faqw-mm.py?req=show&file=faq03.048.htp> for details. ---------------------------------------------------------------------- Comment By: URA Hiroshi (ura) Date: 2004-05-10 10:44 Message: Logged In: YES user_id=1007264 I uploaded the patch by different method. see following URL: http://sourceforge.net/tracker/index.php?func=detail&aid=951167&group_id=10… ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_i…

1 0

[ mailman-Bugs-998609 ] can subscribe with CR+LF in email address
by SourceForge.net Dec. 14, 2004

Dec. 14, 2004

Bugs item #998609, was opened at 2004-07-27 12:13 Message generated for change (Comment added) made by thomas_ah You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=998609&group_i… Category: (un)subscribing Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: can subscribe with CR+LF in email address Initial Comment: With Mailman 2.1.3 (didn't test with newer versions) it is possible to subscribe with an email address which ends with CR+LF. A browser bug made it possible to enter this into the single line entry field, but Mailman should check this. A quick test shows that CR+LF is possible in the middle of an email address, too, but of course this only works when confirmation check is disabled. Unsubscribing or changing the email address wasn't possible, because there are checks against this strange address. Only manually removing all dictionary entries with 'withlist' helped. ---------------------------------------------------------------------- >Comment By: Thomas Arendsen Hein (thomas_ah) Date: 2004-12-14 17:27 Message: Logged In: YES user_id=839582 The patch (already in CVS) helps, thanks. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-20 07:27 Message: Logged In: YES user_id=67709 A patch is uploaded in: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1030228&group_… Can you test it ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=998609&group_i…

1 0

[ mailman-Patches-839386 ] MySQL MemberAdaptor for Mailman 2.1
by SourceForge.net Dec. 13, 2004

Dec. 13, 2004

Patches item #839386, was opened at 2003-11-10 18:04 Message generated for change (Comment added) made by kyrian You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&group_i… Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Kev Green (kyrian) Assigned to: Nobody/Anonymous (nobody) Summary: MySQL MemberAdaptor for Mailman 2.1 Initial Comment: A MemberAdaptor "plugin" which should allow Mailman list members to be loaded from a MySQL database, rather than just a Mailman "pickle" file. Provided as-is, and without warranty, this "plugin" may destroy your server, soul, scalp, house, and life. Please use it with caution. Kev Green, oRe Net. http://www.orenet.co.uk/ ---------------------------------------------------------------------- >Comment By: Kev Green (kyrian) Date: 2004-12-13 18:34 Message: Logged In: YES user_id=99923 Oh, btw. v1.57 hasn't been tested yet, so it might kill your server, eat your dog, and stick your wife in the oven. Be careful using it! ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-12-13 18:33 Message: Logged In: YES user_id=99923 Version 1.57: 2004/12/13 * Merge in Daniel Shriver patch/code for a flat table architecture. [ Suggested by Kevin McCann <kmccann(at)bellanet.org>, but I hadn't found time to do it myself... ] * Add bugfix information from Jinhyok Heo <novembre(a)NOSPAM.ournature.org> * Add in mksqlmailman script from TheSin <thesin(a)SPAMNOTHANKS.southofheaven.org> * Follow Barry Warsaw's suggestion on delivery status timestamp. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-01-08 11:38 Message: Logged In: YES user_id=99923 Latest version incorporates automated generation of the necessary tables, cleaner error reporting, and updated documentation. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2003-11-11 11:14 Message: Logged In: YES user_id=99923 Bit of an oops in version 1.49, 1.50 now uploaded, which should fix it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&group_i…

1 0

[ mailman-Patches-839386 ] MySQL MemberAdaptor for Mailman 2.1
by SourceForge.net Dec. 13, 2004

Dec. 13, 2004

Patches item #839386, was opened at 2003-11-10 18:04 Message generated for change (Comment added) made by kyrian You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&group_i… Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Kev Green (kyrian) Assigned to: Nobody/Anonymous (nobody) Summary: MySQL MemberAdaptor for Mailman 2.1 Initial Comment: A MemberAdaptor "plugin" which should allow Mailman list members to be loaded from a MySQL database, rather than just a Mailman "pickle" file. Provided as-is, and without warranty, this "plugin" may destroy your server, soul, scalp, house, and life. Please use it with caution. Kev Green, oRe Net. http://www.orenet.co.uk/ ---------------------------------------------------------------------- >Comment By: Kev Green (kyrian) Date: 2004-12-13 18:33 Message: Logged In: YES user_id=99923 Version 1.57: 2004/12/13 * Merge in Daniel Shriver patch/code for a flat table architecture. [ Suggested by Kevin McCann <kmccann(at)bellanet.org>, but I hadn't found time to do it myself... ] * Add bugfix information from Jinhyok Heo <novembre(a)NOSPAM.ournature.org> * Add in mksqlmailman script from TheSin <thesin(a)SPAMNOTHANKS.southofheaven.org> * Follow Barry Warsaw's suggestion on delivery status timestamp. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2004-01-08 11:38 Message: Logged In: YES user_id=99923 Latest version incorporates automated generation of the necessary tables, cleaner error reporting, and updated documentation. ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2003-11-11 11:14 Message: Logged In: YES user_id=99923 Bit of an oops in version 1.49, 1.50 now uploaded, which should fix it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=839386&group_i…

1 0

[ mailman-Bugs-1082913 ] Digest-lists wont work with 2.1.6a
by SourceForge.net Dec. 11, 2004

Dec. 11, 2004

Bugs item #1082913, was opened at 2004-12-10 13:47 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1082913&group_… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Tommi Tervo (tomtervo) Assigned to: Nobody/Anonymous (nobody) Summary: Digest-lists wont work with 2.1.6a Initial Comment: If some lists uses digests mailman will crash with following backtrace. Headers from mail which caused crash: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.4i Dec 09 14:39:27 2004 (4051) Traceback (most recent call last): File "/p/appl/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/p/appl/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/p/appl/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/p/appl/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/p/appl/mailman/Mailman/Handlers/ToDigest.py", line 92, in process send_digests(mlist, mboxfp) File "/p/appl/mailman/Mailman/Handlers/ToDigest.py", line 133, in send_digests send_i18n_digests(mlist, mboxfp) File "/p/appl/mailman/Mailman/Handlers/ToDigest.py", line 324, in send_i18n_digests payload = unicode(payload, mcset, 'replace' LookupError: unknown encoding: %charset ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-11 01:38 Message: Logged In: YES user_id=67709 Thank you for the report. I believe I fixed this in 2.1.6a2. Please try. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1082913&group_…

1 0