Mailman 3 April 2004 - Mailman-coders

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net 19 Aug '22

19 Aug '22

Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i…

2 1

[ mailman-Bugs-945346 ] "Subscription-forwarded" Mail is sent to the wrong address
by SourceForge.net 30 Apr '04

30 Apr '04

Bugs item #945346, was opened at 2004-04-30 16:50 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=945346&group_i… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Bussmann (bus) Assigned to: Nobody/Anonymous (nobody) Summary: "Subscription-forwarded" Mail is sent to the wrong address Initial Comment: Hi there, I'm not sure whether this is a bug, non-standard behaviour or simply the right way, but I noticed the following: Mail address A sends out an subscription-request to a list (subscribe policy: approval) with the command subscribe address=B. The message "Your subscription request has been forwarded to the list admin" is sent to address A instead of B. The confirmation mail (if the admin approves the request) is sent to address B. >From my point of view even the first piece of email should be sent to address B, but if you think the current behaviour is ok, feel free to trash this report. Cheers, Michael ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=945346&group_i…

1 0

[ mailman-Bugs-944927 ] Non-Ascii character in e-mail address causes traceback
by SourceForge.net 29 Apr '04

29 Apr '04

Bugs item #944927, was opened at 2004-04-29 22:18 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=944927&group_i… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Joseph Tate (jtate) Assigned to: Nobody/Anonymous (nobody) Summary: Non-Ascii character in e-mail address causes traceback Initial Comment: I fixed the problem without saving a trackback, but if a non-ascii character (>127) somehow makes it into the subscribers list, the admin/members page will not display, and will show a python error on line 870 of Mailman/Cgi/Admin.py. The error says something like not in range(128). Thus user management must be done via command line utility. No error occurs when using list_members. Either no non-ascii character should be allowed in e-mail addresses, or this error should be worked around. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=944927&group_i…

1 0

[ mailman-Bugs-931861 ] MemoryError when running senddigests
by SourceForge.net 29 Apr '04

29 Apr '04

Bugs item #931861, was opened at 2004-04-08 17:19 Message generated for change (Comment added) made by steffen_mhl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=931861&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Patrick Finnerty (finnertyp) Assigned to: Nobody/Anonymous (nobody) Summary: MemoryError when running senddigests Initial Comment: Using Mailman v2.1.4 & Python v2.3.3. OS = TRU64 5.1a Problem only occurs on one mailing list: /usr/local/bin/python -S /usr/local/mailman/cron/senddigests -l shc.nt Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 304, in process t = part.get_payload(decode=True) File "/usr/local/mailman/pythonlib/email/Message.py", line 197, in get_payload return Utils._qdecode(payload) File "/usr/local/lib/python2.3/quopri.py", line 161, in decodestring return a2b_qp(s, header = header) MemoryError ---------------------------------------------------------------------- Comment By: Steffen Muehlnickel (steffen_mhl) Date: 2004-04-29 14:59 Message: Logged In: YES user_id=1031993 Can confirm. I got the same error message (under Tru64 5.1b, mailman 2.1.2) disabling digest helped. ---------------------------------------------------------------------- Comment By: Michael Newlyn Blake (zakureth) Date: 2004-04-20 21:30 Message: Logged In: YES user_id=111909 I to am having this problem on an up to date Suse 9.0 system with Mailman 2.1.2. Messages I'm getting in the error log are: Apr 20 14:14:51 2004 (7447) uncaught archiver exception at filepos: 0 Apr 20 14:14:51 2004 (7447) Uncaught runner exception: Empty module name Apr 20 14:14:51 2004 (7447) 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 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 206, in ArchiveMail h.processUnixMailbox(f) File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 544, in processUnixMailbox m = mbox.next() File "/usr/lib/python2.3/mailbox.py", line 35, in next return self.factory(_Subfile(self.fp, start, stop)) File "/usr/lib/mailman/Mailman/Mailbox.py", line 89, in scrubber return mailbox.scrub(msg) File "/usr/lib/mailman/Mailman/Mailbox.py", line 109, in scrub return self._scrubber(self._mlist, msg) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.3/encodings/__init__.py", line 84, in search_function globals(), locals(), _import_tail) ValueError: Empty module name Apr 20 14:14:51 2004 (7447) SHUNTING: 1082469143.1593151+1674b479f52223bba07f4eda7f29b743c99ae34f And an occasional: Apr 20 14:07:58 2004 (3191) Uncaught runner exception: unknown encoding: big5 Apr 20 14:07:58 2004 (3191) 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 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 218, in _dispose res = Results(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 75, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/usr/lib/mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/lib/mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) LookupError: unknown encoding: big5 Apr 20 14:07:58 2004 (3191) SHUNTING: 1080098916.48541+a5acb6484d8d579d298079c3ebc3d255953e217c Disabling digest doesn't seem to have any effect. ---------------------------------------------------------------------- Comment By: Patrick Finnerty (finnertyp) Date: 2004-04-15 10:29 Message: Logged In: YES user_id=594846 The list in question is also shunting all posts. Disabling the Digest option allowed posts to come through again and also allowed the posts in te queue to be unshunted. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=931861&group_i…

1 0

[ mailman-Bugs-229568 ] Pipermail won't resolve author names of aol.com addresses
by SourceForge.net 28 Apr '04

28 Apr '04

Bugs item #229568, was opened at 2001-01-21 14:53 Message generated for change (Comment added) made by cajela 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: Cath Lawrence (cajela) Date: 2004-04-29 15:49 Message: Logged In: YES user_id=1031650 Of course, it is NOT only for aol.com. I can confirm the same problem with a firstname.lastname(a)csiro.au address format. ---------------------------------------------------------------------- Comment By: Terri Oda (spot) Date: 2002-07-03 06: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-02 04: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-11 12: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-07 02: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-06 11: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-29 11: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-Patches-943827 ] true virtual hosting patch for 2.1
by SourceForge.net 28 Apr '04

28 Apr '04

Patches item #943827, was opened at 2004-04-28 12:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_i… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: The Anarcat (anarcat) Assigned to: Nobody/Anonymous (nobody) Summary: true virtual hosting patch for 2.1 Initial Comment: [copy of the mail sent to -developpers@] We developped a reliable solution for running lists with the same name on different domains on the same Mailman installation. I implemented that on top of the Mailman 2.1.1-5.1 Debian stable package. All that is needed is to patch 2 files (bin/newlist, Mailman/MailList.py) in the mailman install, and here is the patch: http://bugs.koumbit.net/file_download.php?file_id=3&type=bug There's only one caveat right now: Mailman/Cgi/create.py might need to get patched too, but I haven't got around looking at it yet, and it "just works", for now. I don't know what's the current status of virtual hosting support on Mailman, but this patch is a simple hack that should bring joy in the homes of all Mailman admins around the world. :) I got my inspiration and part of the code from: http://mithrandr.moria.org/blog/139.html All it does is to add the domain to the internal_name() of a list. The real_name is kept as is, and the getListAddress() does the Right Thing. This makes Mailman generate aliases like: list-example.com: "|/var/lib/mailman/mail/mailman post list-example.com" Care will have to be taken on the MTA side to map those list-example.com to list(a)example.com. We are using alternc.org to manage our server, so we are using LDAP, so everything went pretty smoothly. :) But I guess it will require some magic on the Postfix side or something... Cheers, A. PS: for those wanting to see more, you can come to our Wiki: http://koumbit.net/wiki/VirtualMailman You'll probably have a little trouble finding your way if you don't read french though. :) Babelfish might help, haven't tried. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_i…

1 0

[ mailman-Patches-699199 ] French translation of "cancel" has reverse meaning
by SourceForge.net 28 Apr '04

28 Apr '04

Patches item #699199, was opened at 2003-03-06 23:54 Message generated for change (Comment added) made by anarcat You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_i… Category: internationalization Group: Mailman 2.1 >Status: Closed Resolution: Works For Me Priority: 5 Submitted By: The Anarcat (anarcat) Assigned to: Ousmane Wilane (wilane) Summary: French translation of "cancel" has reverse meaning Initial Comment: When confirming a subscribe request via the web, the user is presented with two buttons: - "Cancel my subscription request" - "Subscribe to list %(listname)s" The unfortunate thing is that this is translated as: - "Annuler la requête d'abonnement" - "Abonnement à la liste: %(listname)s" which translates to: - "Confirm my subscription request" - "Subscribtion to list %(listname)s" The correct translation is outlined in the patch. I took the liberty of also removing the extra ":" that was lying there. It is not in the english version, and I don't see how it should be in the french one. ---------------------------------------------------------------------- >Comment By: The Anarcat (anarcat) Date: 2004-04-28 12:51 Message: Logged In: YES user_id=246797 I think this is ok in mailman right now. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 10:23 Message: Logged In: YES user_id=34209 Assigning to wilane, who (at least partially) does the French translations. ---------------------------------------------------------------------- Comment By: The Anarcat (anarcat) Date: 2003-03-10 10:07 Message: Logged In: YES user_id=246797 Man, what a bad patch report. :( This bug report should have read: When confirming a subscribe request via the web, the user is presented with two buttons: - "Cancel my subscription request" - "Subscribe to list %(listname)s" The unfortunate thing is that this is translated as: - "Confirmer la requête d'abonnement" - "Abonnement à la liste: %(listname)s" which translates to: - "Confirm my subscription request" - "Subscribtion to list %(listname)s" If you look closer in the actual .po file, it is indeed written "confirmer" where it should be "annuler". I have attached the patch which should take care of all this. Sorry for the confusion. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 08:35 Message: Logged In: YES user_id=34209 There is no patch attached, and (though my french isn't what it used to be) I don't see how "Annuler la requête d'abonnement" reads as 'confirm my submission request'. Please contact the french translation team directly, if you still think this needs fixing: http://listes.rezo.net/mailman/listinfo/mailman-fr ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_i…

1 0

[ mailman-Bugs-803729 ] LookupError: unknown encoding: X-UNKNOWN
by SourceForge.net 26 Apr '04

26 Apr '04

Bugs item #803729, was opened at 2003-09-10 15:31 Message generated for change (Comment added) made by nemethe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ervin Németh (nemethe) Assigned to: Nobody/Anonymous (nobody) Summary: LookupError: unknown encoding: X-UNKNOWN Initial Comment: Our site encounters the following problem. mailman-2.1.2 installed from OpenBSD ports. Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) LookupError: unknown encoding: X-UNKNOWN ---------------------------------------------------------------------- >Comment By: Ervin Németh (nemethe) Date: 2004-04-26 20:03 Message: Logged In: YES user_id=768522 As far as I recognised mailman copies Message.py from the python libraries so I also reported it for python (id 854102). As a workaround replace the line in question: return unicode(newvalue[2], newvalue[0] or 'us-ascii') with try: return unicode(newvalue[2], newvalue[0] or 'us-ascii') except LookupError: return unicode(newvalue[2], 'us-ascii', 'replace') ---------------------------------------------------------------------- Comment By: Gregor Maier (maiergre) Date: 2004-04-26 18:53 Message: Logged In: YES user_id=38025 Hello, I have the same problem with mailmain-2.1.4 with python-2.3.3 under linux gentoo. Are there any clues where the problem lies or any workarounds? Disableing the digest option works but is not really a solution. Another interesting fact is, that the only some lists show this problem and that the prolbem just "occurs" and then it doesn't go away.. Here's a part of my error log: Apr 26 18:27:05 2004 (17449) Uncaught runner exception: unknown encoding: X-UNKNOWN Apr 26 18:27:05 2004 (17449) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 265, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 361, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 714, in get_filename return unicode(newvalue[2], newvalue[0] or 'us-ascii') LookupError: unknown encoding: X-UNKNOWN Apr 26 18:27:05 2004 (17449) SHUNTING: 1082996756.746207+e85fdb8b141ccd2a8f0757824f62fbff58 da2ce4 ---------------------------------------------------------------------- Comment By: Ervin Németh (nemethe) Date: 2003-10-08 14:23 Message: Logged In: YES user_id=768522 It's quite unpleasant to recieve this mail daily. In addition there was a local mailing list to which no mail was delivered until digests to this list was turned off. Last day I have upgraded to mailman 2.1.3 and the last lines of the traceback changed: File "/usr/local/mailman/pythonlib/email/Message.py", line 714, in get_filename return unicode(newvalue[2], newvalue[0] or 'us-ascii') LookupError: unknown encoding: X-UNKNOWN ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_i…

1 0

[ mailman-Bugs-803729 ] LookupError: unknown encoding: X-UNKNOWN
by SourceForge.net 26 Apr '04

26 Apr '04

Bugs item #803729, was opened at 2003-09-10 13:31 Message generated for change (Comment added) made by maiergre You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ervin Németh (nemethe) Assigned to: Nobody/Anonymous (nobody) Summary: LookupError: unknown encoding: X-UNKNOWN Initial Comment: Our site encounters the following problem. mailman-2.1.2 installed from OpenBSD ports. Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) LookupError: unknown encoding: X-UNKNOWN ---------------------------------------------------------------------- Comment By: Gregor Maier (maiergre) Date: 2004-04-26 16:53 Message: Logged In: YES user_id=38025 Hello, I have the same problem with mailmain-2.1.4 with python-2.3.3 under linux gentoo. Are there any clues where the problem lies or any workarounds? Disableing the digest option works but is not really a solution. Another interesting fact is, that the only some lists show this problem and that the prolbem just "occurs" and then it doesn't go away.. Here's a part of my error log: Apr 26 18:27:05 2004 (17449) Uncaught runner exception: unknown encoding: X-UNKNOWN Apr 26 18:27:05 2004 (17449) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 265, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 361, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 714, in get_filename return unicode(newvalue[2], newvalue[0] or 'us-ascii') LookupError: unknown encoding: X-UNKNOWN Apr 26 18:27:05 2004 (17449) SHUNTING: 1082996756.746207+e85fdb8b141ccd2a8f0757824f62fbff58 da2ce4 ---------------------------------------------------------------------- Comment By: Ervin Németh (nemethe) Date: 2003-10-08 12:23 Message: Logged In: YES user_id=768522 It's quite unpleasant to recieve this mail daily. In addition there was a local mailing list to which no mail was delivered until digests to this list was turned off. Last day I have upgraded to mailman 2.1.3 and the last lines of the traceback changed: File "/usr/local/mailman/pythonlib/email/Message.py", line 714, in get_filename return unicode(newvalue[2], newvalue[0] or 'us-ascii') LookupError: unknown encoding: X-UNKNOWN ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_i…

1 0

[ mailman-Bugs-707610 ] Uncaught runner exception: Empty module name
by SourceForge.net 24 Apr '04

24 Apr '04

Bugs item #707610, was opened at 2003-03-21 11:55 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707610&group_i… Category: None >Group: 2.1 (stable) >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception: Empty module name Initial Comment: mailman is shunting a lot of mails with this message in error-log, my language-version is german. i work with the current cvs-version Mar 21 16:11:21 2003 (12591) Uncaught runner exception: Empty module name Mar 21 16:11:21 2003 (12591) Traceback (most recent call last): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman- 2.1//Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman- 2.1//Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 82, in process send_digests(mlist, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman- 2.1//Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') ValueError: Empty module name Mar 21 16:11:21 2003 (12591) SHUNTING: 1048241610.7517231+289483353c3e3632ab0892d8ceb 8c936f107bc5e ---------------------------------------------------------------------- Comment By: Jochen Witte (zebaoth) Date: 2004-04-18 08:26 Message: Logged In: YES user_id=565663 See Bug 871050 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707610&group_i…

1 0