Mailman 3 December 2004 - Mailman-coders

[ mailman-Bugs-1080508 ] 2.1.6a + python 2.4 crashes
by SourceForge.net Dec. 7, 2004

Dec. 7, 2004

Bugs item #1080508, was opened at 2004-12-07 12:12 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=1080508&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: 2.1.6a + python 2.4 crashes Initial Comment: I upgraded first to 2.1.6a from 2.1.5 -> chinese (gb2312) lists stopped working. Then I upgraded python from 2.3.4 to 2.4 and that problem disappeared. But now I'll get crashes like this: Dec 07 11:24:52 2004 (16871) 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/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/p/appl/mailman/Mailman/Archiver/Archiver.py", line 217, in ArchiveMail h.close() File "/p/appl/mailman/Mailman/Archiver/pipermail.py", line 314, in close self.write_TOC() File "/p/appl/mailman/Mailman/Archiver/HyperArch.py", line 1067, in write_TOC toc.write(self.html_TOC()) File "/p/appl/mailman/Mailman/Archiver/HyperArch.py", line 752, in html_TOC accum.append(self.html_TOC_entry(a)) File "/p/appl/mailman/Mailman/Archiver/HyperArch.py", line 773, in html_TOC_en try templ = '<td><A href="%(url)s">[ ' + _('Gzip\'d Text%(sz)s') \ File "/p/appl/mailman/Mailman/i18n.py", line 89, in _ return tns % dict ValueError: unsupported format character 'ä' (0xffffffe4) at index 16 Dec 07 11:24:53 2004 (16871) SHUNTING: 1102411483.73262+a65edf245b1a5299df373b8f a4871f229f16e83a ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080508&group_…

1 0

[ mailman-Patches-1080477 ] discard all marked as defer
by SourceForge.net Dec. 7, 2004

Dec. 7, 2004

Patches item #1080477, was opened at 2004-12-07 18:28 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=1080477&group_… Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jim Tittsler (jtittsler) Assigned to: Nobody/Anonymous (nobody) Summary: discard all marked as defer Initial Comment: When a list moderator processes held messages, if they view all messages from a specific sender and then use the "Discard all messages marked as Defer" checkbox, the messages are not discarded. (The "discard all messages marked as defer" works on the main admindb page, but not on the sender-specific page.) Also reported in bug 1047532. <http://sourceforge.net/tracker/index.php?func=detail&aid=1047532&group_id=1…> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1080477&group_…

1 0

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net Dec. 6, 2004

Dec. 6, 2004

Patches item #657951, was opened at 2002-12-23 19:17 Message generated for change (Comment added) made by ppsys 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: 9 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: Richard Barrett (ppsys) Date: 2004-12-06 18:01 Message: Logged In: YES user_id=75166 The following is based on the July 2003 version of the patch file posted on sourceforge. The RSS patch adds the RSS() function as member function of the HyperArchive class defined in HyperArch.py. It has been reported that the following statement in RSS(): date, msgid = self.database.dateIndex.first() may generate an AttributeError exception: AttributeError: HyperDatabase instance has no attribute 'dateIndex' The RSS patch appears to make the assumption that whenever the RSS() function is called from the write_TOC() member function of the HyperArchive class the __openIndices() function has already been called on the latest period archive associated with the list, whose TOC page is being generated by write_TOC(), and that no intervening call to __closeIndices() has been made. If the assumption were correct then whenever the RSS() function was called on a HyperArchive instance, the xxxxxIndices attributes of the HyperDatabase instance "owned" by the HyperArchive instance would be pointing to valid instance of DumbBTree. Unfortunately, this assumption is not correct. In order to do its work, write_TOC() does not itself need to perform any call to the __openIndices() function for the list/archive/database whose TOC page is to be recreated. It just happens that in some circumstances, some of the code which might call write_TOC may have called the __openIndices() function at some prior point and left the HyperDatabase instance with a valid set of xxxxxIndices attributes in place when write_TOC() is called. For the RSS patch to be work reliably the code in the RSS() function has to be changed so that it ensures that the conditions it wants prevail when it executes the statement giving the problem. The following is an untested code change but if part of the RSS() function's code definition in HyperArch.py is modified from: <quote> # Get the most recent messages. The only index operation # we can count on is traversal by increasing date, so # we end up traversing all of the entries and remembering the last # N of them. Sigh. items = [] try: date, msgid = self.database.dateIndex.first() items.append(msgid) except KeyError: pass while 1: try: </quote> to read: <quote> # Get the most recent messages. The only index operation # we can count on is traversal by increasing date, so # we end up traversing all of the entries and remembering the last # N of them. Sigh. items = [] got_first = 0 try: msgid = self.database.first(self.archives[0], 'date') if msgid: items.append(msgid) got_first = 1 except KeyError: pass while got_first and 1: try: </quote> this should fix the exception problem. ---------------------------------------------------------------------- Comment By: Roy M. Silvernail (codewhacker) Date: 2003-12-23 19:35 Message: Logged In: YES user_id=670974 I'm trying to enrich the RSS output by adding a proper [description] and a [content:encoded] module, but I am having the devil's own time locating the raw message text. Be happy to contribute a patch if you can point me to the raw content (without the italics markup for quoting). Thanks! ---------------------------------------------------------------------- Comment By: Michael Weber (wookiew) Date: 2003-09-10 16:29 Message: Logged In: YES user_id=863445 So far the patch is included (by the way: i hope that Defaults.py.in in the patch *means* Defaults.py ) and mailman get a restart. Hopefully i add the two lines in listinfo.html ( /de/ because we have german speaking lists) and take a look for the xml file). After search the whole device (only to be sure) i can say: There is no file like this. Is another patch need before? Another setup to make? I cant find any hint here... so i have to ask. But the idea is great... if it work on my lists its genious... regards, Michael running version 2.1.1 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-09-02 04:15 Message: Logged In: YES user_id=12800 Bumping priority. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-15 18:55 Message: Logged In: YES user_id=11375 OK, done! This patch is now ready to go in: some people have looked at the RSS and haven't spotted any problems. Barry, can I please get CVS write access to check this in? ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-11 01:00 Message: Logged In: YES user_id=11375 Attaching correct version of the patch. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-11 00:52 Message: Logged In: YES user_id=11375 Here at last is an updated version of the patch that's crawling closer to being complete. There's now a RSS_NUM_ARTICLES setting in Defaults.py, the generated URLs are correct, and I modified the English template to link to the RSS file. Remaining things: check the generated RSS for correctness; edit all of the other language templates to include the RSS file (I may ask for CVS write access to do that). It would be really nice if the Mailman upgrade script could update existing general list information pages to include the LINK element; any suggestion about how to go about that? ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 15:00 Message: Logged In: YES user_id=7830 OK, I've regenerated the patch with some code which works for me. http://rdfweb.org/2003/06/mailman-rss/rsspatch Health warning: * I suspect it may fail in conditions when get_archives() returns a list not a string (does this ever happen?). * See also problems mentioned below, regenerating partial archives seems tricky. Hope this is useful anyways... Dan <danbri(a)w3.org> ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:48 Message: Logged In: YES user_id=7830 I thought I'd have a look at this myself, though have modest knowledge of both Python and MailMan. In the course of trying to patch the patch, I tried running the archiver over just the last couple of messages, to speed things along: "../../bin/arch -s 4390 rdfweb-dev". Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 310, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1082, in write_TOC rss.write(self.RSS()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 769, in RSS date, msgid = self.database.dateIndex.first() AttributeError: HyperDatabase instance has no attribute 'dateIndex' Not sure what's going on there, but this seemed as good a place of any to keep note of it. Investigating... ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 22: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 21: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-18 01: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 20: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 19: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 19:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 19: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…

1 0

[ mailman-Feature Requests-1079885 ] listinfo page incorrectly states that I can post to a list
by SourceForge.net Dec. 6, 2004

Dec. 6, 2004

Feature Requests item #1079885, was opened at 2004-12-06 10:14 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1079885&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ian Eiloart (ianeiloart) Assigned to: Nobody/Anonymous (nobody) Summary: listinfo page incorrectly states that I can post to a list Initial Comment: It would be useful if the listinfo page could check whether non- members can post (generic_nonmember_action), and check for additional restrictions on postings (like default_member_moderation). I had a complaint from a user yesterday that a listinfo page was misleading. It says something like "To post a message to all the list members, send email to foo(a)example.com", when the list in question is actually an announcement only list - so not even list members can do that. Not such a problem, except that right above is the notice "To see the collection of prior postings to the list, visit the FOO Archives. (The current archive is only available to the list members.)". Now, this implies that the listinfo page is being smart about what people can and cannot do. Indeed it is smart about warning that subscriptions, archives, and membership lists are restricted - but not about posting. It would be useful if the listinfo page could check whether non- members can post (generic_nonmember_action), and check for additional restrictions on postings (like default_member_moderation), and say something like: "To post a message to all the list members, send email to foo(a)example.com (posts from non-members may|will be accepted|moderated|rejected|discarded)", where accepted|moderated|rejected|discarded is the setting from generic_non_member_action and may|will is "will" iff accept_these_nonmembers etc, are not set. I guess that inspecting the list of *_these_nonmembers settings will give a list of possible responses to a non-member posting. "To post a message to all the list members, send email to foo(a)example.com (permitted posters only)", as appropriate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1079885&group_…

1 0

[ mailman-Bugs-1079760 ] 2.1.5 munges CC in AvoidDuplicates -- DON'T DO THAT
by SourceForge.net Dec. 6, 2004

Dec. 6, 2004

Bugs item #1079760, was opened at 2004-12-06 14:57 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=1079760&group_… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stephen J. Turnbull (yaseppochi) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.5 munges CC in AvoidDuplicates -- DON'T DO THAT Initial Comment: The AvoidDuplicates handler in 2.1.5 munges the CC header. This is obvious from the code. I suspect that what is happening is that a user has his "Avoid Duplicates" flag set and his (and maybe other) addresses are being removed. For some reason, this handler also occasionally creates an empty CC header out of thin air. Why This Sucks[tm]: The user in question wishes to be CCed in order to bump the priority of mail where he is personally addressed in his queue, but does not wish to receive duplicates. However, the current AvoidDuplicates behavior ensures that his CC is removed, and therefore later contributors to the thread do not know that someone decided to flag him in this way. Suggested action: get rid of all special processing of CC in AvoidDuplicates. The generic code handles the msgdata. CookHeaders takes care of coalescing several CC headers into one. I searched for similar bugs with the string "cc header delete remove" and didn't see anything reasonably similar in the first four pages returned. Stephen Turnbull stephen(a)xemacs.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1079760&group_…

1 0

[ mailman-Feature Requests-1078589 ] Site wide forced confirmed opt-in setting
by SourceForge.net Dec. 3, 2004

Dec. 3, 2004

Feature Requests item #1078589, was opened at 2004-12-03 12:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1078589&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Kevan Benson (kentrak) Assigned to: Nobody/Anonymous (nobody) Summary: Site wide forced confirmed opt-in setting Initial Comment: A site wide setting to be set in mm_cfg.py that will change some of the GUI options and behavior to enforce lists to be confirmed opt-in. This includes list subscription behavior as well as moderator approval settings in the moderator pending requests page (letting moderators forge requests to a list and then add the address automatically negates the benefits of forcing confirmed opt-in lists). Optionally, disallowing moderator approval for unsubscribes in this mode might be useful as well, but that's a more debatable position (an extra option maybe?). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1078589&group_…

1 0

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

Dec. 3, 2004

Bugs item #1078482, was opened at 2004-12-03 12:43 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=1078482&group_… Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1078482&group_…

1 0

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

Dec. 2, 2004

Bugs item #1077842, was opened at 2004-12-02 19:37 Message generated for change (Settings changed) made by mdickins You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077842&group_… Category: Web/CGI >Group: 2.1 (stable) Status: Open Resolution: None 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077842&group_…

1 0

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

Dec. 2, 2004

Bugs item #1077842, was opened at 2004-12-02 19:37 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=1077842&group_… Category: Web/CGI Group: None Status: Open Resolution: None 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077842&group_…

1 0

[ mailman-Bugs-1077587 ] Memory Leak in Bounce Runner
by SourceForge.net Dec. 2, 2004

Dec. 2, 2004

Bugs item #1077587, was opened at 2004-12-02 09:02 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=1077587&group_… Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Paul Rubin (prubin) Assigned to: Nobody/Anonymous (nobody) Summary: Memory Leak in Bounce Runner Initial Comment: Something is going bady wrong with the BouceRunner It is leaking memory. After it runs for a short time it has consumed hundreds of megabytes of memory. I kill it with -9 and it restarts and is fine for another couple of hours. Sometimes it does not restart and I have to stop and restart the mailman service. This is running on a Linux box with Redhat 9 and postfix 2.1.1 and mailman 2.1.5 and python 2.2.2 Below you will se a PS from right before I killed the process and below that one from a few seconds later. If you will tell me what you need I would really like to get to the bottom of this, I am killing the process like 10 times per day. If it eats too much memory before I catch it then the entire system fails. [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.0 08:05 00:00:00 7068 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.1 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12951 18.9 70.8 08:05 00:08:40 931312 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.1 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 2.5 0.6 08:05 00:01:11 14172 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 0.8 0.2 08:05 00:00:24 10628 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.2 08:05 00:00:04 13272 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.1 08:05 00:00:00 7072 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.0 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.2 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 3.0 0.9 08:05 00:01:43 13584 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 1.2 0.6 08:05 00:00:41 10848 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.6 08:05 00:00:06 13284 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s 14900 29.8 1.1 08:51 00:02:47 13764 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_…

1 0