From noreply at sourceforge.net Wed Dec 1 22:38:39 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 1 22:38:43 2004 Subject: [ mailman-Bugs-1077104 ] Uncatched bounces (unknown MTA) Message-ID: Bugs item #1077104, was opened at 2004-12-01 22:38 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=1077104&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077104&group_id=103 From noreply at sourceforge.net Thu Dec 2 04:21:02 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 2 04:21:05 2004 Subject: [ mailman-Feature Requests-1077283 ] add an extra level of authentication - nonbots Message-ID: Feature Requests item #1077283, was opened at 2004-12-02 11:21 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=1077283&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Pabs (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: add an extra level of authentication - nonbots Initial Comment: I think it would be useful to have an extra level of authentication where to authenticate, you write a short password from an image in order to prove you are not a robot/spam harvester. I think the cookies produced should be valid for the whole of a mailman install by default, and that by default, the members list should use this authentication level. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1077283&group_id=103 From noreply at sourceforge.net Thu Dec 2 15:02:21 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 2 15:02:24 2004 Subject: [ mailman-Bugs-1077587 ] Memory Leak in Bounce Runner Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Thu Dec 2 20:37:38 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 2 20:37:42 2004 Subject: [ mailman-Bugs-1077842 ] bug report (problem with Danish support?) Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Thu Dec 2 20:38:00 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 2 20:38:06 2004 Subject: [ mailman-Bugs-1077842 ] bug report (problem with Danish support?) Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Fri Dec 3 18:43:45 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 3 18:43:48 2004 Subject: [ mailman-Bugs-1078482 ] Some bounces cause traceback after upgrading to Python 2.4 Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Fri Dec 3 21:29:16 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 3 21:29:19 2004 Subject: [ mailman-Feature Requests-1078589 ] Site wide forced confirmed opt-in setting Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Mon Dec 6 06:57:15 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 6 06:57:20 2004 Subject: [ mailman-Bugs-1079760 ] 2.1.5 munges CC in AvoidDuplicates -- DON'T DO THAT Message-ID: 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_id=103 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@xemacs.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1079760&group_id=103 From noreply at sourceforge.net Mon Dec 6 11:14:08 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 6 11:14:11 2004 Subject: [ mailman-Feature Requests-1079885 ] listinfo page incorrectly states that I can post to a list Message-ID: 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_id=103 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@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@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@example.com (permitted posters only)", as appropriate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1079885&group_id=103 From noreply at sourceforge.net Mon Dec 6 19:01:43 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 6 19:01:58 2004 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: 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_id=103 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: # 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: to read: # 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: 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@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_id=103 From noreply at sourceforge.net Tue Dec 7 10:28:12 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 7 10:28:16 2004 Subject: [ mailman-Patches-1080477 ] discard all marked as defer Message-ID: 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_id=103 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1080477&group_id=103 From noreply at sourceforge.net Tue Dec 7 11:12:13 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 7 11:12:15 2004 Subject: [ mailman-Bugs-1080508 ] 2.1.6a + python 2.4 crashes Message-ID: 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_id=103 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 = '[ ' + _('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_id=103 From noreply at sourceforge.net Tue Dec 7 12:47:56 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 7 12:48:00 2004 Subject: [ mailman-Bugs-1047532 ] problem with "discard all ..." Message-ID: Bugs item #1047532, was opened at 2004-10-15 12:44 Message generated for change (Comment added) made by jtittsler You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1047532&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: David Relson (relson) Assigned to: Nobody/Anonymous (nobody) Summary: problem with "discard all ..." Initial Comment: Mailman 2.1.5: >From admin page http://www.mydomain.com/mailman/admindb/mylist, checking "Discard all messages marked Defer" and clicking on SUBMIT works fine -- removes the message(s). If I click on the "you can view all messages from address@example.com" link, and then click on "Discard all messages marked Defer", the message(s) aren't discarded. ---------------------------------------------------------------------- Comment By: Jim Tittsler (jtittsler) Date: 2004-12-07 20:47 Message: Logged In: YES user_id=1488 Please try patch 1080477. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1047532&group_id=103 From noreply at sourceforge.net Tue Dec 7 12:51:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 7 12:51:25 2004 Subject: [ mailman-Bugs-1077842 ] bug report (problem with Danish support?) Message-ID: Bugs item #1077842, was opened at 2004-12-03 04:37 Message generated for change (Comment added) made by jtittsler You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077842&group_id=103 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 ---------------------------------------------------------------------- Comment By: Jim Tittsler (jtittsler) Date: 2004-12-07 20: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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077842&group_id=103 From noreply at sourceforge.net Tue Dec 7 14:18:08 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 7 14:18:13 2004 Subject: [ mailman-Bugs-1047532 ] problem with "discard all ..." Message-ID: Bugs item #1047532, was opened at 2004-10-15 03:44 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1047532&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: David Relson (relson) Assigned to: Nobody/Anonymous (nobody) Summary: problem with "discard all ..." Initial Comment: Mailman 2.1.5: >From admin page http://www.mydomain.com/mailman/admindb/mylist, checking "Discard all messages marked Defer" and clicking on SUBMIT works fine -- removes the message(s). If I click on the "you can view all messages from address@example.com" link, and then click on "Discard all messages marked Defer", the message(s) aren't discarded. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-07 13:18 Message: Logged In: YES user_id=67709 Fixed by removing the 'discard all' check box from msgid/sender message lists because the term 'all' may be confusing in these cases. ---------------------------------------------------------------------- Comment By: Jim Tittsler (jtittsler) Date: 2004-12-07 11:47 Message: Logged In: YES user_id=1488 Please try patch 1080477. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1047532&group_id=103 From noreply at sourceforge.net Tue Dec 7 14:19:59 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 7 14:20:06 2004 Subject: [ mailman-Patches-1080477 ] discard all marked as defer Message-ID: Patches item #1080477, was opened at 2004-12-07 09:28 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1080477&group_id=103 Category: Web UI Group: Mailman 2.1 >Status: Closed 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. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-07 13:19 Message: Logged In: YES user_id=67709 Fixed by removing the 'discard all' check box from msgid/sender message lists because the term 'all' may be confusing in these cases. Thanks Jim for raising my attention anyway. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1080477&group_id=103 From noreply at sourceforge.net Tue Dec 7 14:20:50 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 7 14:20:54 2004 Subject: [ mailman-Patches-1071669 ] Danish message catalog update Message-ID: Patches item #1071669, was opened at 2004-11-23 12:44 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1071669&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 5 Submitted By: Tom G. Christensen (tgc99) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Danish message catalog update Initial Comment: Bring the Danish message catalog in line with Release_2.1-maint. - All fuzzy translations have been fixed - All missing translations have been added - Misc updates to existing translations ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-07 13:20 Message: Logged In: YES user_id=67709 merged in CVS, thanks! ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2004-11-29 09:01 Message: Logged In: YES user_id=1159458 Patch updated to apply cleanly on top of CVS as of 2004-11-29 08:49+100. It also fixes two new fuzzies. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1071669&group_id=103 From noreply at sourceforge.net Tue Dec 7 14:42:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 7 14:42:06 2004 Subject: [ mailman-Bugs-1080508 ] 2.1.6a + python 2.4 crashes Message-ID: Bugs item #1080508, was opened at 2004-12-07 10:12 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080508&group_id=103 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 = '[ ' + _('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 ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-07 13:42 Message: Logged In: YES user_id=67709 Currently, Chinese (both China and Taiwan) are not supported. I am curious how you manage gb2312 list. And also, what language message caused this error? There may be incomplete translations and may cause such error. Particularly, big5 (zh_TW) may contain '%' in the second byte of a 16bit character and may cause trouble. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080508&group_id=103 From noreply at sourceforge.net Tue Dec 7 16:20:46 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 7 16:20:50 2004 Subject: [ mailman-Bugs-1080679 ] .txt archive chunks missing NL before From_ lines Message-ID: Bugs item #1080679, was opened at 2004-12-07 16:20 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=1080679&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Zoran Dzelajlija (followme) Assigned to: Nobody/Anonymous (nobody) Summary: .txt archive chunks missing NL before From_ lines Initial Comment: hi, Mailman 2.1.5 txt archives are not mbox compliant. An empty line before the From_ "header" of next message is missing, and mailers cannot parse the *.txt files as mailboxes. See the attached sample. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080679&group_id=103 From noreply at sourceforge.net Tue Dec 7 23:49:48 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 7 23:49:52 2004 Subject: [ mailman-Bugs-1080943 ] Private archive specific message URL lost in authorization Message-ID: Bugs item #1080943, was opened at 2004-12-07 14:49 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=1080943&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: Private archive specific message URL lost in authorization Initial Comment: If a user without an authorization cookie goes to a URL such as http://www.example.com/mailman/private/list-name/yyyy-Month/nnnnnn.html the user will get the private archives authorization page and after filling in e-mail address and password and clicking Let me in... will be taken to the main index for the list at http://www.example.com/mailman/private/list-name/ instead of to the original URL. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080943&group_id=103 From noreply at sourceforge.net Wed Dec 8 03:18:25 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 8 03:18:31 2004 Subject: [ mailman-Bugs-1080679 ] .txt archive chunks missing NL before From_ lines Message-ID: Bugs item #1080679, was opened at 2004-12-07 15:20 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080679&group_id=103 Category: Pipermail Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Zoran Dzelajlija (followme) Assigned to: Nobody/Anonymous (nobody) Summary: .txt archive chunks missing NL before From_ lines Initial Comment: hi, Mailman 2.1.5 txt archives are not mbox compliant. An empty line before the From_ "header" of next message is missing, and mailers cannot parse the *.txt files as mailboxes. See the attached sample. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-08 02:18 Message: Logged In: YES user_id=67709 Fixed in CVS. Please try 2.1.6a (in CVS with -r Release_2_1-maint) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080679&group_id=103 From noreply at sourceforge.net Wed Dec 8 09:37:34 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 8 09:37:36 2004 Subject: [ mailman-Patches-1081180 ] Danish message catalog update Message-ID: Patches item #1081180, was opened at 2004-12-08 09:37 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=1081180&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tom G. Christensen (tgc99) Assigned to: Nobody/Anonymous (nobody) Summary: Danish message catalog update Initial Comment: Fix 2 new fuzzies. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1081180&group_id=103 From noreply at sourceforge.net Wed Dec 8 12:41:39 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 8 12:41:43 2004 Subject: [ mailman-Bugs-1080508 ] 2.1.6a + python 2.4 crashes Message-ID: Bugs item #1080508, was opened at 2004-12-07 12:12 Message generated for change (Comment added) made by tomtervo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080508&group_id=103 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 = '[ ' + _('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 ---------------------------------------------------------------------- >Comment By: Tommi Tervo (tomtervo) Date: 2004-12-08 13:41 Message: Logged In: YES user_id=1094436 This type of crash doesn't come from chinese lists. I suspect that Subject line =E4 which is ? ( a umlaut) is cause of this crash. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Subject: [RKK] =?iso-8859-1?q?Taas_meit=E4_raha=24tettiin!?= ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-07 15:42 Message: Logged In: YES user_id=67709 Currently, Chinese (both China and Taiwan) are not supported. I am curious how you manage gb2312 list. And also, what language message caused this error? There may be incomplete translations and may cause such error. Particularly, big5 (zh_TW) may contain '%' in the second byte of a 16bit character and may cause trouble. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080508&group_id=103 From epi at datis.it Wed Dec 8 13:11:52 2004 From: epi at datis.it (epigrottero) Date: Wed Dec 8 13:11:55 2004 Subject: Mailman problem... Message-ID: <001501c4dd1f$1a711600$1e00a8c0@direzione> Hi, excuse me for my english, i have installed a Mandrake 9.2 (in the package there is Mailman 2.1.2 included) but when i try the creation of a new list i receive this message: Bug in Mailman version 2.1.2 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/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/lib/mailman/Mailman/Cgi/create.py", line 176, in process_request mlist.Create(listname, owner, pw, langs) File "/usr/lib/mailman/Mailman/MailList.py", line 450, in Create self.InitVars(name, admin, crypted_password) File "/usr/lib/mailman/Mailman/MailList.py", line 368, in InitVars baseclass.InitVars(self) File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 116, in InitVars }, mlist=self)) File "/usr/lib/mailman/Mailman/Utils.py", line 467, in maketext raise IOError(errno.ENOENT, 'No template file found', templatefile) IOError: [Errno 2] No template file found: 'emptyarchive.html' -------------------------------------------------------------------------------- Python information: Variable Value sys.version 2.3 (#2, Aug 31 2003, 17:27:29) [GCC 3.3.1 (Mandrake Linux 9.2 3.3.1-1mdk)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 -------------------------------------------------------------------------------- Environment variables: Variable Value HTTP_COOKIE POSTNUKESID=c73aea178415ae184c58ed0774c781b4; pnphpbb2mysql_data=a%3A2%3A%7Bs%3A11%3A%22autologinid%22%3Bs%3A0%3A%22%22%3Bs%3A6%3A%22userid%22%3Bs%3A1%3A%222%22%3B%7D SERVER_SOFTWARE Apache-AdvancedExtranetServer/2.0.47 (Mandrake Linux/6mdk) mod_perl/1.99_09 Perl/v5.8.1 auth_mysql/1.11 mod_ssl/2.0.47 OpenSSL/0.9.7b PHP/4.3.2 SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache-AdvancedExtranetServer/2.0.47 (Mandrake Linux/6mdk) mod_perl/1.99_09 Perl/v5.8.1 auth_mysql/1.11 mod_ssl/2.0.47 OpenSSL/0.9.7b PHP/4.3.2 Server at 192.168.1.2 Port 80 REQUEST_METHOD POST SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 142 HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) HTTP_CONNECTION Keep-Alive HTTP_REFERER http://192.168.0.1/mailman/create SERVER_NAME 192.168.1.2 REMOTE_ADDR 192.168.0.2 SERVER_PORT 80 SERVER_ADDR 192.168.0.1 DOCUMENT_ROOT /var/www/html PYTHONPATH /usr/lib/mailman SCRIPT_FILENAME /usr/lib/mailman/cgi-bin/create SERVER_ADMIN root@localhost HTTP_HOST 192.168.0.1 HTTP_CACHE_CONTROL no-cache REQUEST_URI /mailman/create HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/x-shockwave-flash, */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 1751 HTTP_ACCEPT_LANGUAGE it CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip, deflate -------------------------------------------------------------------------------- I am stopped here from more time, Can you help me? Thanks, epigrottero. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/mailman-coders/attachments/20041208/8ef878c0/attachment.html From noreply at sourceforge.net Wed Dec 8 17:45:37 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 8 17:45:40 2004 Subject: [ mailman-Bugs-1080508 ] 2.1.6a + python 2.4 crashes Message-ID: Bugs item #1080508, was opened at 2004-12-07 12:12 Message generated for change (Comment added) made by tomtervo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080508&group_id=103 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 = '[ ' + _('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 ---------------------------------------------------------------------- >Comment By: Tommi Tervo (tomtervo) Date: 2004-12-08 18:45 Message: Logged In: YES user_id=1094436 I can send you privately a bunch of problematic qfiles/shunts if those help more than my poor guesses. ---------------------------------------------------------------------- Comment By: Tommi Tervo (tomtervo) Date: 2004-12-08 13:41 Message: Logged In: YES user_id=1094436 This type of crash doesn't come from chinese lists. I suspect that Subject line =E4 which is ? ( a umlaut) is cause of this crash. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Subject: [RKK] =?iso-8859-1?q?Taas_meit=E4_raha=24tettiin!?= ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-07 15:42 Message: Logged In: YES user_id=67709 Currently, Chinese (both China and Taiwan) are not supported. I am curious how you manage gb2312 list. And also, what language message caused this error? There may be incomplete translations and may cause such error. Particularly, big5 (zh_TW) may contain '%' in the second byte of a 16bit character and may cause trouble. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080508&group_id=103 From noreply at sourceforge.net Thu Dec 9 00:36:13 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 9 00:36:16 2004 Subject: [ mailman-Bugs-1080508 ] 2.1.6a + python 2.4 crashes Message-ID: Bugs item #1080508, was opened at 2004-12-07 10:12 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080508&group_id=103 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 = '[ ' + _('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 ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-08 23:36 Message: Logged In: YES user_id=67709 I found a bug in Finlandic translation catalog. This will be fixed before final release of 2.1.6. ---------------------------------------------------------------------- Comment By: Tommi Tervo (tomtervo) Date: 2004-12-08 16:45 Message: Logged In: YES user_id=1094436 I can send you privately a bunch of problematic qfiles/shunts if those help more than my poor guesses. ---------------------------------------------------------------------- Comment By: Tommi Tervo (tomtervo) Date: 2004-12-08 11:41 Message: Logged In: YES user_id=1094436 This type of crash doesn't come from chinese lists. I suspect that Subject line =E4 which is ? ( a umlaut) is cause of this crash. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Subject: [RKK] =?iso-8859-1?q?Taas_meit=E4_raha=24tettiin!?= ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-07 13:42 Message: Logged In: YES user_id=67709 Currently, Chinese (both China and Taiwan) are not supported. I am curious how you manage gb2312 list. And also, what language message caused this error? There may be incomplete translations and may cause such error. Particularly, big5 (zh_TW) may contain '%' in the second byte of a 16bit character and may cause trouble. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080508&group_id=103 From noreply at sourceforge.net Thu Dec 9 11:17:25 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 9 11:17:28 2004 Subject: [ mailman-Bugs-1080508 ] 2.1.6a + python 2.4 crashes Message-ID: Bugs item #1080508, was opened at 2004-12-07 12:12 Message generated for change (Comment added) made by tomtervo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080508&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open >Resolution: Fixed 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 = '[ ' + _('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 ---------------------------------------------------------------------- >Comment By: Tommi Tervo (tomtervo) Date: 2004-12-09 12:17 Message: Logged In: YES user_id=1094436 Many thanks to you, I updated that .po file and it seems to work! ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-09 01:36 Message: Logged In: YES user_id=67709 I found a bug in Finlandic translation catalog. This will be fixed before final release of 2.1.6. ---------------------------------------------------------------------- Comment By: Tommi Tervo (tomtervo) Date: 2004-12-08 18:45 Message: Logged In: YES user_id=1094436 I can send you privately a bunch of problematic qfiles/shunts if those help more than my poor guesses. ---------------------------------------------------------------------- Comment By: Tommi Tervo (tomtervo) Date: 2004-12-08 13:41 Message: Logged In: YES user_id=1094436 This type of crash doesn't come from chinese lists. I suspect that Subject line =E4 which is ? ( a umlaut) is cause of this crash. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Subject: [RKK] =?iso-8859-1?q?Taas_meit=E4_raha=24tettiin!?= ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-07 15:42 Message: Logged In: YES user_id=67709 Currently, Chinese (both China and Taiwan) are not supported. I am curious how you manage gb2312 list. And also, what language message caused this error? There may be incomplete translations and may cause such error. Particularly, big5 (zh_TW) may contain '%' in the second byte of a 16bit character and may cause trouble. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1080508&group_id=103 From barry at python.org Thu Dec 9 15:09:41 2004 From: barry at python.org (Barry Warsaw) Date: Thu Dec 9 15:09:45 2004 Subject: Mailman problem... In-Reply-To: <001501c4dd1f$1a711600$1e00a8c0@direzione> References: <001501c4dd1f$1a711600$1e00a8c0@direzione> Message-ID: <1102601381.5091.39.camel@geddy.wooz.org> On Wed, 2004-12-08 at 07:11, epigrottero wrote: > Hi, excuse me for my english, i have installed a Mandrake 9.2 (in the > package there is Mailman 2.1.2 included) but when i try the creation > of a new list i receive this message: > > Bug in Mailman version 2.1.2 Mailman 2.1.2 is fairly old. You should try to at least upgrade to 2.1.5 and see if your problem is fixed. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 307 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/mailman-coders/attachments/20041209/fdb91e56/attachment.pgp From noreply at sourceforge.net Fri Dec 10 10:08:02 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 10 10:08:13 2004 Subject: [ mailman-Patches-1081180 ] Danish message catalog update Message-ID: Patches item #1081180, was opened at 2004-12-08 09:37 Message generated for change (Settings changed) made by tgc99 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1081180&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tom G. Christensen (tgc99) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: Danish message catalog update Initial Comment: Fix 2 new fuzzies. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1081180&group_id=103 From noreply at sourceforge.net Fri Dec 10 13:39:38 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 10 13:39:46 2004 Subject: [ mailman-Patches-1081180 ] Danish message catalog update Message-ID: Patches item #1081180, was opened at 2004-12-08 09:37 Message generated for change (Comment added) made by tgc99 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1081180&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None 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: Tom G. Christensen (tgc99) Date: 2004-12-10 13: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_id=103 From noreply at sourceforge.net Fri Dec 10 13:52:44 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 10 13:52:49 2004 Subject: [ mailman-Patches-1081180 ] Danish message catalog update Message-ID: Patches item #1081180, was opened at 2004-12-08 08:37 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1081180&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None 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_id=103 From noreply at sourceforge.net Fri Dec 10 14:47:53 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 10 14:47:55 2004 Subject: [ mailman-Bugs-1082913 ] Digest-lists wont work with 2.1.6a Message-ID: Bugs item #1082913, was opened at 2004-12-10 15:47 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=1082913&group_id=103 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1082913&group_id=103 From noreply at sourceforge.net Fri Dec 10 19:02:41 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 10 19:02:46 2004 Subject: [ mailman-Bugs-1078482 ] Some bounces cause traceback after upgrading to Python 2.4 Message-ID: Bugs item #1078482, was opened at 2004-12-03 12:43 Message generated for change (Comment added) made by fehwalker You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1078482&group_id=103 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 ---------------------------------------------------------------------- >Comment By: Bryan Fullerton (fehwalker) Date: 2004-12-10 13: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_id=103 From noreply at sourceforge.net Sat Dec 11 02:38:28 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Dec 11 02:38:33 2004 Subject: [ mailman-Bugs-1082913 ] Digest-lists wont work with 2.1.6a Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Mon Dec 13 19:33:00 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 13 19:33:40 2004 Subject: [ mailman-Patches-839386 ] MySQL MemberAdaptor for Mailman 2.1 Message-ID: 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_id=103 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 , but I hadn't found time to do it myself... ] * Add bugfix information from Jinhyok Heo * Add in mksqlmailman script from TheSin * 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_id=103 From noreply at sourceforge.net Mon Dec 13 19:34:36 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 13 19:35:00 2004 Subject: [ mailman-Patches-839386 ] MySQL MemberAdaptor for Mailman 2.1 Message-ID: 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_id=103 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 , but I hadn't found time to do it myself... ] * Add bugfix information from Jinhyok Heo * Add in mksqlmailman script from TheSin * 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_id=103 From noreply at sourceforge.net Tue Dec 14 17:27:13 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 14 17:27:18 2004 Subject: [ mailman-Bugs-998609 ] can subscribe with CR+LF in email address Message-ID: 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_id=103 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_id=103 Can you test it ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=998609&group_id=103 From noreply at sourceforge.net Tue Dec 14 17:28:20 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 14 17:28:41 2004 Subject: [ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option Message-ID: 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_id=103 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@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 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=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 From noreply at sourceforge.net Wed Dec 15 00:50:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 15 00:50:14 2004 Subject: [ mailman-Bugs-975768 ] senddigests doesn't handle consecutive unparseable messages Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Wed Dec 15 00:52:35 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 15 00:52:38 2004 Subject: [ mailman-Patches-1081180 ] Danish message catalog update Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Wed Dec 15 00:55:44 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 15 00:55:49 2004 Subject: [ mailman-Bugs-1078482 ] Some bounces cause traceback after upgrading to Python 2.4 Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Wed Dec 15 00:58:45 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 15 00:58:51 2004 Subject: [ mailman-Bugs-1077842 ] bug report (problem with Danish support?) Message-ID: 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_id=103 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077842&group_id=103 From noreply at sourceforge.net Wed Dec 15 01:01:59 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 15 01:02:06 2004 Subject: [ mailman-Bugs-1077104 ] Uncatched bounces (unknown MTA) Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Wed Dec 15 01:19:11 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 15 01:19:18 2004 Subject: [ mailman-Bugs-1077587 ] Memory Leak in Bounce Runner Message-ID: Bugs item #1077587, was opened at 2004-12-02 14:02 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 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 ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-15 00:19 Message: Logged In: YES user_id=67709 My FreeBSD4.7/Solaris8 installations have no such problems. How many bounces you get on this system? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 From noreply at sourceforge.net Wed Dec 15 01:36:07 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 15 01:36:23 2004 Subject: [ mailman-Bugs-1075686 ] footer added to quoted-printable mail isn't encoded Message-ID: Bugs item #1075686, was opened at 2004-11-30 00:45 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1075686&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Felix Palmen (tentakel) Assigned to: Nobody/Anonymous (nobody) Summary: footer added to quoted-printable mail isn't encoded Initial Comment: When Mailman adds a footer to a mail with Content-Transfer-Encoding quoted-printable, it doesn't encode the footer in quoted-printable, so spaces (and other characters?) are messed up. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-15 00:36 Message: Logged In: YES user_id=67709 I think I fixed this in CVS. (Decorate.py Revision 2.21.2.4) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1075686&group_id=103 From noreply at sourceforge.net Wed Dec 15 01:40:23 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 15 01:40:35 2004 Subject: [ mailman-Bugs-1062663 ] empty charset in header crashes admindb.py Message-ID: Bugs item #1062663, was opened at 2004-11-08 20:52 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1062663&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: empty charset in header crashes admindb.py Initial Comment: when a message contains a header like this: Content-Type: text/plain; charset= (note the empty charset) The admindb.py details page page gives an error. Traceback is below. Btw does this mean the charset value in the header is directly mapped to a module name to import? (sounds kinda scary...) I know the real fault is in the message (I'm not sure if the mime stripper caused this or a bad mailer), but maybe mailman shouldn't crash on this. Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 222, in main show_detailed_requests(mlist, form) File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 545, in show_detailed_requests show_post_requests(mlist, id, info, total, count, form) File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 611, in show_post_requests body = unicode(body, mcset).encode(lcset) File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') ValueError: Empty module name ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-15 00:40 Message: Logged In: YES user_id=67709 Fixed in CVS. (admindb.py Revision 2.45.2.8) ---------------------------------------------------------------------- Comment By: idogan (idogan) Date: 2004-11-30 21:09 Message: Logged In: YES user_id=1169233 I have exactly the same problem: Nov 30 21:53:09 2004 admin(21885): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(21885): [----- Mailman Version: 2.1.5 -----] admin(21885): [----- Traceback ------] admin(21885): Traceback (most recent call last): admin(21885): File "/opt/mailman/scripts/driver", line 87, in run_main admin(21885): main() admin(21885): File "/opt/mailman/Mailman/Cgi/admindb.py", line 163, in main admin(21885): process_form(mlist, doc, cgidata) admin(21885): File "/opt/mailman/Mailman/Cgi/admindb.py", line 711, in process_form admin(21885): forward, forwardaddr) admin(21885): File "/opt/mailman/Mailman/ListAdmin.py", line 159, in HandleRequest admin(21885): forward, addr) admin(21885): File "/opt/mailman/Mailman/ListAdmin.py", line 345, in __handlepost admin(21885): syslog('vette', note) admin(21885): File "/opt/mailman/Mailman/Logging/Syslog.py", line 40, in write admin(21885): self.write_ex(kind, msg, args, kws) admin(21885): File "/opt/mailman/Mailman/Logging/Syslog.py", line 58, in write_ex admin(21885): logf.write(msg + '\n') admin(21885): File "/opt/mailman/Mailman/Logging/StampedLogger.py", line 73, in write admin(21885): Logger.write(self, "%s %s" % (prefix, msg)) admin(21885): File "/opt/mailman/Mailman/Logging/Logger.py", line 91, in write admin(21885): f.write(msg) admin(21885): UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 90: ordinal not in range(128) admin(21885): [----- Python Information -----] admin(21885): sys.version = 2.3.4 (#1, Nov 10 2004, 13:08:40) [C] admin(21885): sys.executable = /opt/csw/bin/python admin(21885): sys.prefix = /opt/csw admin(21885): sys.exec_prefix = /opt/csw admin(21885): sys.path = /opt/csw admin(21885): sys.platform = sunos5 admin(21885): [----- Environment Variables -----] admin(21885): HTTP_COOKIE: eth+admin=2802000000694eddac41732800000031336161396238633262356333316431613335633033383739313330326164303462643162393164 admin(21885): SERVER_SOFTWARE: Apache/2.0.52 (Unix) admin(21885): SCRIPT_NAME: /mailman/admindb admin(21885): SERVER_SIGNATURE:
Apache/2.0.52 (Unix) Server at lists.dogan.ch Port 443
admin(21885): admin(21885): REQUEST_METHOD: POST admin(21885): HTTP_KEEP_ALIVE: 300 admin(21885): SERVER_PROTOCOL: HTTP/1.1 admin(21885): QUERY_STRING: admin(21885): CONTENT_LENGTH: 433 admin(21885): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7 admin(21885): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041108 admin(21885): HTTP_CONNECTION: keep-alive admin(21885): HTTP_REFERER: https://lists.dogan.ch/mailman/admindb/eth admin(21885): SERVER_NAME: lists.dogan.ch admin(21885): REMOTE_ADDR: 213.144.141.146 admin(21885): PATH_TRANSLATED: /var/www/lists.dogan.ch/htdocs/eth admin(21885): SERVER_PORT: 443 admin(21885): SERVER_ADDR: 213.144.137.44 admin(21885): DOCUMENT_ROOT: /var/www/lists.dogan.ch/htdocs admin(21885): PYTHONPATH: /opt/mailman admin(21885): SCRIPT_FILENAME: /opt/mailman/cgi-bin/admindb admin(21885): SERVER_ADMIN: ihsan@dogan.ch admin(21885): HTTP_HOST: lists.dogan.ch admin(21885): HTTPS: on admin(21885): REQUEST_URI: /mailman/admindb/eth admin(21885): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 admin(21885): GATEWAY_INTERFACE: CGI/1.1 admin(21885): REMOTE_PORT: 64543 admin(21885): HTTP_ACCEPT_LANGUAGE: de,tr;q=0.7,en;q=0.3 admin(21885): CONTENT_TYPE: application/x-www-form-urlencoded admin(21885): HTTP_ACCEPT_ENCODING: gzip,deflate admin(21885): PATH_INFO: /eth Nov 30 21:53:20 2004 admin(21886): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(21886): [----- Mailman Version: 2.1.5 -----] admin(21886): [----- Traceback ------] admin(21886): Traceback (most recent call last): admin(21886): File "/opt/mailman/scripts/driver", line 87, in run_main admin(21886): main() admin(21886): File "/opt/mailman/Mailman/Cgi/admindb.py", line 163, in main admin(21886): process_form(mlist, doc, cgidata) admin(21886): File "/opt/mailman/Mailman/Cgi/admindb.py", line 711, in process_form admin(21886): forward, forwardaddr) admin(21886): File "/opt/mailman/Mailman/ListAdmin.py", line 159, in HandleRequest admin(21886): forward, addr) admin(21886): File "/opt/mailman/Mailman/ListAdmin.py", line 345, in __handlepost admin(21886): syslog('vette', note) admin(21886): File "/opt/mailman/Mailman/Logging/Syslog.py", line 40, in write admin(21886): self.write_ex(kind, msg, args, kws) admin(21886): File "/opt/mailman/Mailman/Logging/Syslog.py", line 58, in write_ex admin(21886): logf.write(msg + '\n') admin(21886): File "/opt/mailman/Mailman/Logging/StampedLogger.py", line 73, in write admin(21886): Logger.write(self, "%s %s" % (prefix, msg)) admin(21886): File "/opt/mailman/Mailman/Logging/Logger.py", line 91, in write admin(21886): f.write(msg) admin(21886): UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 90: ordinal not in range(128) admin(21886): [----- Python Information -----] admin(21886): sys.version = 2.3.4 (#1, Nov 10 2004, 13:08:40) [C] admin(21886): sys.executable = /opt/csw/bin/python admin(21886): sys.prefix = /opt/csw admin(21886): sys.exec_prefix = /opt/csw admin(21886): sys.path = /opt/csw admin(21886): sys.platform = sunos5 admin(21886): [----- Environment Variables -----] admin(21886): HTTP_COOKIE: eth+admin=2802000000694eddac41732800000031336161396238633262356333316431613335633033383739313330326164303462643162393164 admin(21886): SERVER_SOFTWARE: Apache/2.0.52 (Unix) admin(21886): SCRIPT_NAME: /mailman/admindb admin(21886): SERVER_SIGNATURE:
Apache/2.0.52 (Unix) Server at lists.dogan.ch Port 443
admin(21886): admin(21886): REQUEST_METHOD: POST admin(21886): HTTP_KEEP_ALIVE: 300 admin(21886): SERVER_PROTOCOL: HTTP/1.1 admin(21886): QUERY_STRING: admin(21886): CONTENT_LENGTH: 433 admin(21886): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7 admin(21886): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041108 admin(21886): HTTP_CONNECTION: keep-alive admin(21886): HTTP_REFERER: https://lists.dogan.ch/mailman/admindb/eth admin(21886): SERVER_NAME: lists.dogan.ch admin(21886): REMOTE_ADDR: 213.144.141.146 admin(21886): PATH_TRANSLATED: /var/www/lists.dogan.ch/htdocs/eth admin(21886): SERVER_PORT: 443 admin(21886): SERVER_ADDR: 213.144.137.44 admin(21886): DOCUMENT_ROOT: /var/www/lists.dogan.ch/htdocs admin(21886): HTTP_PRAGMA: no-cache admin(21886): PYTHONPATH: /opt/mailman admin(21886): SCRIPT_FILENAME: /opt/mailman/cgi-bin/admindb admin(21886): SERVER_ADMIN: ihsan@dogan.ch admin(21886): HTTP_HOST: lists.dogan.ch admin(21886): HTTPS: on admin(21886): HTTP_CACHE_CONTROL: no-cache admin(21886): REQUEST_URI: /mailman/admindb/eth admin(21886): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 admin(21886): GATEWAY_INTERFACE: CGI/1.1 admin(21886): REMOTE_PORT: 64543 admin(21886): HTTP_ACCEPT_LANGUAGE: de,tr;q=0.7,en;q=0.3 admin(21886): CONTENT_TYPE: application/x-www-form-urlencoded admin(21886): HTTP_ACCEPT_ENCODING: gzip,deflate admin(21886): PATH_INFO: /eth ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1062663&group_id=103 From noreply at sourceforge.net Wed Dec 15 01:51:46 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 15 01:51:49 2004 Subject: [ mailman-Patches-1085501 ] Welcome Message Message-ID: Patches item #1085501, was opened at 2004-12-14 16:51 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=1085501&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Grant Bowman (grantbow) Assigned to: Nobody/Anonymous (nobody) Summary: Welcome Message Initial Comment: Problem: Currently, welcome message text can only be prepended to a fixed subscribeack.txt. Welcome messages should be fully customizable by list administrators that do not have command line/shell access to their mailman installations, an arrangement that is not unusual for hosted ISPs (like mine). Solution: The following one line patch allows the use of the existing editing capability with the subscribeack.txt file. Result: Mailman list administrators without shell access will have more control and can customize welcome messages to exactly meet the needs of their subscribers. --- Note: If this is the right approach I would be happy to follow up with additional patches to adjust the text of the existing "HTML selection" page and other appropriate places. http://mail.python.org/pipermail/mailman-users/2003-June/029676.html Note: I obtained this idea from this message by Todd to Mailman-users and have created this patch for the CVS version of mailman. --- Mailman/Cgi/edithtml.py.orig 2001-11-30 00:00:18.000000000 -0800 +++ Mailman/Cgi/edithtml.py 2004-12-10 12:09:31.000000000 -0800 @@ -42,6 +42,7 @@ template_data = ( ('listinfo.html', _('General list information page')), ('subscribe.html', _('Subscribe results page')) + ('subscribeack.txt', _('Welcome email text file')), ('options.html', _('User specific options page')), ) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1085501&group_id=103 From noreply at sourceforge.net Wed Dec 15 02:11:17 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 15 02:11:24 2004 Subject: [ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option Message-ID: Feature Requests item #923122, was opened at 2004-03-25 14:01 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 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@freefriends.org ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-12-15 01:11 Message: Logged In: YES user_id=18417 Actually, the problem has very little to do with the RFCs, but everything to do with how the RFCs are typically interpreted. I've been doing Internet mail for over twelve years now, and I've read RFCs 821, 822, 1123, and various other related ones many, many times over, and quoted many of them from memory. While 2822 supercedes 822, and the BNF is algorithmically more clear in terms of what is allowed in the "Reply-to:" header, RFC 822 section A.2.4 actually gives an example that is more clear to us humans: | A.2.4. Committee activity, with one author | | George is a member of a committee. He wishes to have any | replies to his message go to all committee members. | | From: George Jones | Sender: Jones@Host | Reply-To: The Committee: Jones@Host.Net, | Smith@Other.Org, | Doe@Somewhere-Else; | | Note that if George had not included himself in the | enumeration of The Committee, he would not have gotten an | implicit reply; the presence of the "Reply-to" field SUPER- | SEDES the sending of a reply to the person named in the "From" | field. Having read both of these RFCs many times over, I don't recall ever seeing either of these sections in particular, and I think that's the real problem -- client authors are likely to make similar mistakes, and putting multiple recipients in the "Reply-to:" header is likely to cause way more problems than it can possibly solve, especially with clients that are being LAN e-mail gateways and do not themselves natively understand Internet e-mail protocols. I still think this is a really, really bad idea. I would violently oppose the inclusion of this feature in future versions of Mailman. ---------------------------------------------------------------------- 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 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=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 From noreply at sourceforge.net Wed Dec 15 09:54:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 15 09:54:20 2004 Subject: [ mailman-Bugs-1085651 ] Broken PGP/MIME signature of messages with attachments Message-ID: Bugs item #1085651, was opened at 2004-12-15 03:54 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=1085651&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Etienne M. Gagnon (egagnon) Assigned to: Nobody/Anonymous (nobody) Summary: Broken PGP/MIME signature of messages with attachments Initial Comment: Hi, When I send a PGP/MIME signed message *with* attachments (in addition to the PGP signature) to a Mailman-based mailing list, Firefox/Enigmail fails to verify the signature of the message forwarded by mailman. I have uploaded an example message with a broken signature as attachment to this bug. You can also see how Mailman's automatic archives don't even handle such messages correctly by looking at how it archived that message at: http://sablecc.org/lists/sablecc-user/2004-December/000159.html I've looked in the bugs database and found that a somewhat related problem was reported a while ago, but note that the current bug is different. The original bug was about PGP/MIME signed messages without attachments that were handled incorrectly by Enigmail. This one is about messages with attachments, and it is likely that the bug is Mailman's, at least accroding to the reply I got in: http://bugzilla.mozdev.org/show_bug.cgi?id=8466 Thanks for your help (and for the magnificient software)! Etienne ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_id=103 From noreply at sourceforge.net Wed Dec 15 17:00:04 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 15 17:00:12 2004 Subject: [ mailman-Bugs-1085874 ] unsubscribe moderator notify not show subscriber's email/nam Message-ID: Bugs item #1085874, was opened at 2004-12-15 17:00 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=1085874&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David M (petasques) Assigned to: Nobody/Anonymous (nobody) Summary: unsubscribe moderator notify not show subscriber's email/nam Initial Comment: With Catalan language selected, when a user unsubscribes, the notify to moderator/list-owner does not show his name, e.g.: %(member) ha estat donat de baixa amb ?xit de %(listname)s. the two variables are not substituted. Thanks for your attention to this matter. Best regards. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085874&group_id=103 From noreply at sourceforge.net Wed Dec 15 18:29:13 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 15 18:29:24 2004 Subject: [ mailman-Bugs-1077587 ] Memory Leak in Bounce Runner Message-ID: Bugs item #1077587, was opened at 2004-12-02 09:02 Message generated for change (Comment added) made by prubin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 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 ---------------------------------------------------------------------- >Comment By: Paul Rubin (prubin) Date: 2004-12-15 12:29 Message: Logged In: YES user_id=91557 I do not have a specific number of bounces per day. We send around 500,000 message per day with peak days around 1,000,000, we know that we have some bad addresses, but at any given time there should not be more than 5,000 bounce notices per day (full mailboxes are common) As far as I can tell only certain bounce notices cause the leak. We can go hours or days with memory being almost flat, then suddenly 200M vanishes in 2 or 3 minutes. Is there any way I could 'hack' the code to somehow grab the information about what bounce notice is causing the problem. Or to capture all bounce notices in some outof the way space that I could tar up an send to you for testing. If nothing else I could edit the aliases to copy all of the messages to a file and zip it down for you after a few days. Does any of this make any sense? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-14 19:19 Message: Logged In: YES user_id=67709 My FreeBSD4.7/Solaris8 installations have no such problems. How many bounces you get on this system? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 From noreply at sourceforge.net Thu Dec 16 10:10:21 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 16 10:10:24 2004 Subject: [ mailman-Patches-1086319 ] bin/show_qfiles is terminated by exception Message-ID: Patches item #1086319, was opened at 2004-12-16 18:10 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=1086319&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: bin/show_qfiles is terminated by exception Initial Comment: Shunted queue files may cause exceptions while bin/show_qfiles is running. By this patch, show_qfiles will show tracebacks and continue processing files. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1086319&group_id=103 From noreply at sourceforge.net Fri Dec 17 02:12:19 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 17 02:12:25 2004 Subject: [ mailman-Bugs-1085874 ] unsubscribe moderator notify not show subscriber's email/nam Message-ID: Bugs item #1085874, was opened at 2004-12-15 16:00 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085874&group_id=103 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: David M (petasques) Assigned to: Nobody/Anonymous (nobody) Summary: unsubscribe moderator notify not show subscriber's email/nam Initial Comment: With Catalan language selected, when a user unsubscribes, the notify to moderator/list-owner does not show his name, e.g.: %(member) ha estat donat de baixa amb ?xit de %(listname)s. the two variables are not substituted. Thanks for your attention to this matter. Best regards. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-17 01:12 Message: Logged In: YES user_id=67709 %(member) should be %(member)s Fixed in CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085874&group_id=103 From noreply at sourceforge.net Fri Dec 17 02:29:58 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 17 02:30:32 2004 Subject: [ mailman-Bugs-1077587 ] Memory Leak in Bounce Runner Message-ID: Bugs item #1077587, was opened at 2004-12-02 14:02 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 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 ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-17 01:29 Message: Logged In: YES user_id=67709 I suggest stop automatic processing of bounces by setting bounce_processing variable to 'No' at the admin/bounce page. Looks like your server is very busy and unsubscribing process due to the bounce score may interfering. You may also have to unsubscribe the problematic members manually. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2004-12-15 17:29 Message: Logged In: YES user_id=91557 I do not have a specific number of bounces per day. We send around 500,000 message per day with peak days around 1,000,000, we know that we have some bad addresses, but at any given time there should not be more than 5,000 bounce notices per day (full mailboxes are common) As far as I can tell only certain bounce notices cause the leak. We can go hours or days with memory being almost flat, then suddenly 200M vanishes in 2 or 3 minutes. Is there any way I could 'hack' the code to somehow grab the information about what bounce notice is causing the problem. Or to capture all bounce notices in some outof the way space that I could tar up an send to you for testing. If nothing else I could edit the aliases to copy all of the messages to a file and zip it down for you after a few days. Does any of this make any sense? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-15 00:19 Message: Logged In: YES user_id=67709 My FreeBSD4.7/Solaris8 installations have no such problems. How many bounces you get on this system? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 From noreply at sourceforge.net Fri Dec 17 02:36:45 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 17 02:36:50 2004 Subject: [ mailman-Bugs-1063491 ] Put an error message instead of a bug page Message-ID: Bugs item #1063491, was opened at 2004-11-09 23:35 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1063491&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Laurent Rathle (lrathle) Assigned to: Nobody/Anonymous (nobody) Summary: Put an error message instead of a bug page Initial Comment: Hello, When you put a wrong email in Mailman (with accent, for exemple), and you want to list the subscribers on the web, Mailman show a bug message, which is not clear, since you can think it's the software that goes wrong. Is it possible to had a function that would display a web page saying "there is a worng email in the database", for exemple instead of the bug web page. Thank you, ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-17 01:36 Message: Logged In: YES user_id=67709 Will you be more specific about which page and textbox? Mailman 2.1.6a has fixed number of such bugs. So, please try the latest from the CVS (-r Release_2_1-maint). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1063491&group_id=103 From noreply at sourceforge.net Fri Dec 17 04:34:57 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 17 04:35:00 2004 Subject: [ mailman-Feature Requests-1086838 ] show email attachment name in web interface Message-ID: Feature Requests item #1086838, was opened at 2004-12-16 19:34 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=1086838&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: show email attachment name in web interface Initial Comment: On a mailman hosted list we recently had someone submit a post with an attachment, it was over our max message size and was held for the moderator. So far, so good. However, when using the web admin tool, there was no info on what the attached file *was*. Just the mail header of "multipart/alternative", and then the email body followed by the beginning of the binary contents of the attached file. To better make an informed decision about what to do with a held email with an attachment, it sure would help to have the attachment filename. (Of course, the filename can be inaccurate, the file could do something other than what the name says, but if you know/trust the sender, knowing the filename might give you a reason to want to approve the email with the file where you normally reject all emails with attachments.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1086838&group_id=103 From noreply at sourceforge.net Sat Dec 18 23:01:02 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Dec 18 23:04:28 2004 Subject: [ mailman-Bugs-1077104 ] Uncatched bounces (unknown MTA) Message-ID: Bugs item #1077104, was opened at 2004-12-01 22:38 Message generated for change (Comment added) made by alster You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077104&group_id=103 Category: bounce detection Group: 2.1 (stable) >Status: Open 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: Alster (alster) Date: 2004-12-18 23:01 Message: Logged In: YES user_id=1151865 I would think that this header line: X-FC-MachineGenerated: true combined with these in the body: Sorry. Your message could not be delivered to:[newline] [newline] would make matching possible... Of course, this mail server is using a terrible NDN format which doesn't make matching patterns too easy. However, I've seen these lines in all of the NDNs from this mail server software ("FirstClass Mail Server") on multiple sites. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-15 01: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_id=103 From noreply at sourceforge.net Sun Dec 19 05:27:40 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Dec 19 05:27:50 2004 Subject: [ mailman-Bugs-1064494 ] Accessing list web page - bug report Message-ID: Bugs item #1064494, was opened at 2004-11-11 09:00 Message generated for change (Comment added) made by martin789 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1064494&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ralphabf (mudd47) Assigned to: Nobody/Anonymous (nobody) Summary: Accessing list web page - bug report Initial Comment: Bug in Mailman version 2.1.4 Traceback: Traceback (most recent call last): File "/usr/lib/mailman/scripts/driver", line 68, in run_main immediate=1) File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py ", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 49, in __init__ self.__get_f() File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 67, in __get_f 1) File "/usr/lib/python2.3/codecs.py", line 566, in open file = __builtin__.open(filename, mode, buffering) IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' ------------------------------------------------------ -------------------------- Python information: Variable Value sys.version 2.3.3 (#2, Feb 17 2004, 11:45:40) [GCC 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------ -------------------------- Environment variables: Variable Value SERVER_SOFTWARE Apache- AdvancedExtranetServer/2.0.48 (Mandrake Linux/6.7.100mdk) SCRIPT_NAME /mailman/admin SERVER_SIGNATURE Apache- AdvancedExtranetServer/2.0.48 (Mandrake Linux/6.7.100mdk) Server at hyndan.gbg.abf.se Port 80 REQUEST_METHOD GET PATH_INFO /mailman SERVER_PROTOCOL HTTP/1.1 QUERY_STRING HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) HTTP_CONNECTION Keep-Alive SERVER_NAME hyndan.gbg.abf.se REMOTE_ADDR 62.127.120.98 PATH_TRANSLATED /var/www/html/mailman SERVER_PORT 80 SERVER_ADDR 192.168.1.111 DOCUMENT_ROOT /var/www/html PYTHONPATH /usr/lib/mailman SCRIPT_FILENAME /usr/lib/mailman/cgi-bin/admin SERVER_ADMIN root@localhost HTTP_HOST hyndan.gbg.abf.se REQUEST_URI /mailman/admin/mailman HTTP_ACCEPT */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 16872 HTTP_ACCEPT_LANGUAGE sv HTTP_ACCEPT_ENCODING gzip, deflate ---------------------------------------------------------------------- Comment By: Martin K (martin789) Date: 2004-12-18 23:27 Message: Logged In: YES user_id=1122923 This isn't a bug, run check_perms like tkikuchi says. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-25 20:36 Message: Logged In: YES user_id=67709 It says "Permission denied: '/var/lib/mailman/logs/error'" . Check your logs directory permission by bin/check_perms and fix. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1064494&group_id=103 From noreply at sourceforge.net Sun Dec 19 05:31:28 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Dec 19 05:31:31 2004 Subject: [ mailman-Bugs-1087781 ] Bouncer.py "day of year out of range" Message-ID: Bugs item #1087781, was opened at 2004-12-18 23:31 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=1087781&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Martin K (martin789) Assigned to: Nobody/Anonymous (nobody) Summary: Bouncer.py "day of year out of range" Initial Comment: Not sure what to do about this one. Mailman 2.1.5 Python 2.4 qmail Traceback (most recent call last): File "/home/mailman/public_html/bin/qrunner", line 270, in ? main() File "/home/mailman/public_html/bin/qrunner", line 230, in main qrunner.run() File "/home/mailman/public_html/Mailman/Queue/Runner.py", line 87, in run self._cleanup() File "/home/mailman/public_html/Mailman/Queue/BounceRunner.py", line 220, in _cleanup BounceMixin._cleanup(self) File "/home/mailman/public_html/Mailman/Queue/BounceRunner.py", line 132, in _cleanup self._register_bounces() File "/home/mailman/public_html/Mailman/Queue/BounceRunner.py", line 120, in _register_bounces mlist.registerBounce(addr, msg, day=day) File "/home/mailman/public_html/Mailman/Bouncer.py", line 131, in registerBounce time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1087781&group_id=103 From noreply at sourceforge.net Sun Dec 19 07:22:08 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Dec 19 07:22:11 2004 Subject: [ mailman-Bugs-1087781 ] Bouncer.py "day of year out of range" Message-ID: Bugs item #1087781, was opened at 2004-12-19 04:31 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1087781&group_id=103 Category: bounce detection Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Martin K (martin789) Assigned to: Nobody/Anonymous (nobody) Summary: Bouncer.py "day of year out of range" Initial Comment: Not sure what to do about this one. Mailman 2.1.5 Python 2.4 qmail Traceback (most recent call last): File "/home/mailman/public_html/bin/qrunner", line 270, in ? main() File "/home/mailman/public_html/bin/qrunner", line 230, in main qrunner.run() File "/home/mailman/public_html/Mailman/Queue/Runner.py", line 87, in run self._cleanup() File "/home/mailman/public_html/Mailman/Queue/BounceRunner.py", line 220, in _cleanup BounceMixin._cleanup(self) File "/home/mailman/public_html/Mailman/Queue/BounceRunner.py", line 132, in _cleanup self._register_bounces() File "/home/mailman/public_html/Mailman/Queue/BounceRunner.py", line 120, in _register_bounces mlist.registerBounce(addr, msg, day=day) File "/home/mailman/public_html/Mailman/Bouncer.py", line 131, in registerBounce time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-19 06:22 Message: Logged In: YES user_id=67709 This was fixed in CVS. (Also reported in 1078482) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1087781&group_id=103 From noreply at sourceforge.net Mon Dec 20 12:02:48 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 20 12:02:52 2004 Subject: [ mailman-Patches-1088323 ] sync_member flags processing Message-ID: Patches item #1088323, was opened at 2004-12-20 12:02 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=1088323&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Thomas Quinot (quinot) Assigned to: Nobody/Anonymous (nobody) Summary: sync_member flags processing Initial Comment: This patch extends sync_members to support setting member flags and delivery status. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1088323&group_id=103 From noreply at sourceforge.net Mon Dec 20 15:24:10 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 20 15:24:45 2004 Subject: [ mailman-Patches-645297 ] Add PGP support Message-ID: Patches item #645297, was opened at 2002-11-28 14:54 Message generated for change (Comment added) made by arthur_lutz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_id=103 Category: None Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Ben Laurie (benl) Assigned to: Thomas Wouters (twouters) Summary: Add PGP support Initial Comment: Support PGP encrypted lists using GnuPG. ---------------------------------------------------------------------- Comment By: Arthur Lutz (arthur_lutz) Date: 2004-12-20 14:24 Message: Logged In: YES user_id=848508 another +1 for this patch, I've been looking for this functionality too... willing to contribute ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-11-10 18:31 Message: Logged In: YES user_id=935 another +1 for this patch, I've been looking for this functionality too... ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-17 22:17 Message: Logged In: YES user_id=34209 I'll look at incorporating this when I look at the SecureList patch by NAH6 (SF patch #646989, currently.) ---------------------------------------------------------------------- Comment By: Nicolas Marchildon (elecnix) Date: 2003-02-06 05:16 Message: Logged In: YES user_id=106549 My vote goes to a PGP whitelist and blacklist feature. Messages signed with a key present in the whitelist could go skip moderation, messages in the blacklist would be either ignored or rejected, and all other messages could go through moderation. That way, PGP signatures are not required, but those using them would see their messages delivered quickly. Mailman would have two keyrings, and would manage them by specifying --keyring to gpg. PGP keys would be retreived from a PGP key server. When moderating a message that was signed with a key missing from the whitelist, there would be an option named "Add key to whitelist", and an other one for the blacklist. Keys could be added to the white/blacklist through the web interface by specifying at least a key ID, and mailman would ask gpg to fetch the key from mailman's default key server. Initially proposed in French on: http://www.linux-quebec.org/archives/general/msg03787.html Nicolas Marchildon ---------------------------------------------------------------------- Comment By: David Shaw (dmshaw) Date: 2003-01-04 19:59 Message: Logged In: YES user_id=606006 Another vote of support. I actually submitted an enhancement request earlier today for exactly this. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 19:37 Message: Logged In: YES user_id=147905 Adding a vote of support for this patch. Please add it as soon as it's appropriate! I've been waiting a long time for this functionality and I'd hate to see the patch bitrot. :-) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-12 03:56 Message: Logged In: YES user_id=12800 I have to defer this patch until after MM2.1 since we're about ready for the first release candidate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_id=103 From noreply at sourceforge.net Mon Dec 20 23:56:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 20 23:57:00 2004 Subject: [ mailman-Patches-1088712 ] Use correct char set for command-line scripts Message-ID: Patches item #1088712, was opened at 2004-12-20 23:56 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=1088712&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Miloslav Trmac (trmac) Assigned to: Nobody/Anonymous (nobody) Summary: Use correct char set for command-line scripts Initial Comment: The command-line scripts in mailman-2.1.5 share the i18n framework with the rest of mailman, but unlike the rest of mailman, mailman is not in control of the characer set used; it should always use the character set specified by the LC_CTYPE locale category. Currently on a system using e.g. LANG=cs_CZ.UTF-8 the Czech (cs) translation is selected, but the output uses the character set of the translation (ISO 8859-2), not UTF-8. The attached patch (roughly against 2.1.5) adds Mailman.i18n.C_(), which works like _(), except that the output is in the LC_CTYPE-specified encoding, and modifies all command-line utilities to use it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1088712&group_id=103 From noreply at sourceforge.net Thu Dec 23 06:13:35 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 23 06:13:39 2004 Subject: [ mailman-Bugs-1090208 ] Password reminder bug (wrong "From" address, etc) Message-ID: Bugs item #1090208, was opened at 2004-12-22 21:13 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=1090208&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Brett Garrett (dolphyn) Assigned to: Nobody/Anonymous (nobody) Summary: Password reminder bug (wrong "From" address, etc) Initial Comment: Summary of bug: On a system with multiple domains and multiple lists, the password reminder sometimes contains information about a list to which the user is not subscribed, or in some cases, about a list that does not exist. Likewise, the "From" address of the password reminder can be incorrect. Details: The cron script "mailpasswds" contains the following code: siteowner = Utils.get_site_email(host, 'owner') sitereq = Utils.get_site_email(host, 'request') sitebounce = Utils.get_site_email (host, 'bounces') The problem is, this code is oblivious to the user's actual subscriptions. On a CPanel server, for example, it always defaults to mailman-owner@host, etc. This results in confusion among users. Since the "From" address of the reminder is mailman- owner@host and that address is also referenced in the mail, users send their questions to that address -- which may go to the server administrator, or to nobody at all, instead of the appropriate list owner. On my setup (a CPanel system) the following replacement code appears to correct most of the problem (in combination with an "import string" statement near the top of the script): siteowner = string.replace ( listaddr, '@', '- owner@' ) sitereq = string.replace ( listaddr, '@', '- request@' ) sitebounce = string.replace ( listaddr, '@', '- bounces@' ) I have not tested it thoroughly, but I think it corrects the siteowner and sitereq values. (For some reason the corrected sitebounce address does not have any effect. The reminder messages still have a return-path of mailman-bounces@servername instead of the appropriate listname-bounces@host. But, I don't think this matters as much as making sure the siteowner and sitereq addresses are correct.) Thank you! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090208&group_id=103 From noreply at sourceforge.net Thu Dec 23 12:12:13 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 23 12:12:18 2004 Subject: [ mailman-Bugs-1090208 ] Password reminder bug (wrong "From" address, etc) Message-ID: Bugs item #1090208, was opened at 2004-12-23 05:13 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090208&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Brett Garrett (dolphyn) Assigned to: Nobody/Anonymous (nobody) Summary: Password reminder bug (wrong "From" address, etc) Initial Comment: Summary of bug: On a system with multiple domains and multiple lists, the password reminder sometimes contains information about a list to which the user is not subscribed, or in some cases, about a list that does not exist. Likewise, the "From" address of the password reminder can be incorrect. Details: The cron script "mailpasswds" contains the following code: siteowner = Utils.get_site_email(host, 'owner') sitereq = Utils.get_site_email(host, 'request') sitebounce = Utils.get_site_email (host, 'bounces') The problem is, this code is oblivious to the user's actual subscriptions. On a CPanel server, for example, it always defaults to mailman-owner@host, etc. This results in confusion among users. Since the "From" address of the reminder is mailman- owner@host and that address is also referenced in the mail, users send their questions to that address -- which may go to the server administrator, or to nobody at all, instead of the appropriate list owner. On my setup (a CPanel system) the following replacement code appears to correct most of the problem (in combination with an "import string" statement near the top of the script): siteowner = string.replace ( listaddr, '@', '- owner@' ) sitereq = string.replace ( listaddr, '@', '- request@' ) sitebounce = string.replace ( listaddr, '@', '- bounces@' ) I have not tested it thoroughly, but I think it corrects the siteowner and sitereq values. (For some reason the corrected sitebounce address does not have any effect. The reminder messages still have a return-path of mailman-bounces@servername instead of the appropriate listname-bounces@host. But, I don't think this matters as much as making sure the siteowner and sitereq addresses are correct.) Thank you! ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-12-23 11:12 Message: Logged In: YES user_id=75166 CPanel sells a modified version of Mailman as part of its commercial hosting product. They have not made their modifications available to the Open Source developers and users of Mailman. Unless you can identify that this problem is present with unmodified, stable Mailman distribution source from sourceforge you will have to take this matter up with your ISP/or CPanel. This is not least because without the source code of the CPanel modifications it will be problematic diagnosing the cause of the problem you observe. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090208&group_id=103 From noreply at sourceforge.net Thu Dec 23 17:31:21 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 23 17:32:16 2004 Subject: [ mailman-Bugs-1090439 ] password reminder can be shunt when encoding usascii Message-ID: Bugs item #1090439, was opened at 2004-12-23 17:31 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=1090439&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: password reminder can be shunt when encoding usascii Initial Comment: One user here has a password with characters which are not in usascii. The default language of the Mailman installation is English (USA) which gives usascii as encoding. This is a stable Debian with Python 2.1.3. The password reminders to be send to this person are shunted because of: Uncaught runner exception: ASCII encoding error: ordinal not in range(128) File "/home/services/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/home/services/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Queue/OutgoingRunner.py", line 73, in _dispose self._func(mlist, msg, msgdata) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 152, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/home/services/mailman/Mailman/Handlers/SMTPDirect.py", line 356, in bulkdeliver msgtext = msg.as_string() File "/home/services/mailman/Mailman/Message.py", line 208, in as_string g.flatten(self, unixfrom=unixfrom) File "/home/services/mailman/pythonlib/email/Generator.py", line 102, in flatten self._write(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 130, in _write self._dispatch(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 156, in _dispatch meth(msg) File "/home/services/mailman/pythonlib/email/Generator.py", line 202, in _handle_text self._fp.write(payload) UnicodeError: ASCII encoding error: ordinal not in range(128) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1090439&group_id=103 From noreply at sourceforge.net Tue Dec 28 05:06:42 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 28 05:06:53 2004 Subject: [ mailman-Patches-1085501 ] Welcome Message Message-ID: Patches item #1085501, was opened at 2004-12-14 19:51 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1085501&group_id=103 Category: list administration Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Grant Bowman (grantbow) Assigned to: Nobody/Anonymous (nobody) Summary: Welcome Message Initial Comment: Problem: Currently, welcome message text can only be prepended to a fixed subscribeack.txt. Welcome messages should be fully customizable by list administrators that do not have command line/shell access to their mailman installations, an arrangement that is not unusual for hosted ISPs (like mine). Solution: The following one line patch allows the use of the existing editing capability with the subscribeack.txt file. Result: Mailman list administrators without shell access will have more control and can customize welcome messages to exactly meet the needs of their subscribers. --- Note: If this is the right approach I would be happy to follow up with additional patches to adjust the text of the existing "HTML selection" page and other appropriate places. http://mail.python.org/pipermail/mailman-users/2003-June/029676.html Note: I obtained this idea from this message by Todd to Mailman-users and have created this patch for the CVS version of mailman. --- Mailman/Cgi/edithtml.py.orig 2001-11-30 00:00:18.000000000 -0800 +++ Mailman/Cgi/edithtml.py 2004-12-10 12:09:31.000000000 -0800 @@ -42,6 +42,7 @@ template_data = ( ('listinfo.html', _('General list information page')), ('subscribe.html', _('Subscribe results page')) + ('subscribeack.txt', _('Welcome email text file')), ('options.html', _('User specific options page')), ) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-12-27 23:06 Message: Logged In: YES user_id=12800 Accepted for Mailman 2.1.6. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1085501&group_id=103 From noreply at sourceforge.net Wed Dec 29 20:51:50 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 29 20:51:53 2004 Subject: [ mailman-Bugs-1092895 ] typo: delivery instead of deliver Message-ID: Bugs item #1092895, was opened at 2004-12-29 13:51 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=1092895&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Whit (whit_anderson) Assigned to: Nobody/Anonymous (nobody) Summary: typo: delivery instead of deliver Initial Comment: On the mailing list membership configuration page, next to the last option ("Do you want to receive messages that do not match any t opic filter"), last sentence of first paragaph has a typo. "delivery" is used instead of "deliver." See screen shot. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1092895&group_id=103 From noreply at sourceforge.net Thu Dec 30 05:03:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 30 05:03:06 2004 Subject: [ mailman-Bugs-1085651 ] Broken PGP/MIME signature of messages with attachments Message-ID: Bugs item #1085651, was opened at 2004-12-15 03:54 Message generated for change (Comment added) made by egagnon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_id=103 >Category: mail delivery >Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Etienne M. Gagnon (egagnon) Assigned to: Nobody/Anonymous (nobody) Summary: Broken PGP/MIME signature of messages with attachments Initial Comment: Hi, When I send a PGP/MIME signed message *with* attachments (in addition to the PGP signature) to a Mailman-based mailing list, Firefox/Enigmail fails to verify the signature of the message forwarded by mailman. I have uploaded an example message with a broken signature as attachment to this bug. You can also see how Mailman's automatic archives don't even handle such messages correctly by looking at how it archived that message at: http://sablecc.org/lists/sablecc-user/2004-December/000159.html I've looked in the bugs database and found that a somewhat related problem was reported a while ago, but note that the current bug is different. The original bug was about PGP/MIME signed messages without attachments that were handled incorrectly by Enigmail. This one is about messages with attachments, and it is likely that the bug is Mailman's, at least accroding to the reply I got in: http://bugzilla.mozdev.org/show_bug.cgi?id=8466 Thanks for your help (and for the magnificient software)! Etienne ---------------------------------------------------------------------- >Comment By: Etienne M. Gagnon (egagnon) Date: 2004-12-29 23:03 Message: Logged In: YES user_id=15365 Any update? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_id=103 From noreply at sourceforge.net Thu Dec 30 10:46:55 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 30 10:46:59 2004 Subject: [ mailman-Bugs-1093176 ] Bug in Mailman version 2.1.4 Message-ID: Bugs item #1093176, was opened at 2004-12-30 09:46 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=1093176&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: htitus (htitus) Assigned to: Nobody/Anonymous (nobody) Summary: Bug in Mailman version 2.1.4 Initial Comment: Bug in Mailman version 2.1.4 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/lib/mailman/scripts/driver", line 68, in run_main immediate=1) File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 49, in __init__ self.__get_f() File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 67, in __get_f 1) File "/usr/lib/python2.3/codecs.py", line 566, in open file = __builtin__.open(filename, mode, buffering) IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' -------------------------------------------------------------------------------- Python information: Variable Value sys.version 2.3.3 (#2, Feb 17 2004, 11:45:40) [GCC 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 -------------------------------------------------------------------------------- Environment variables: Variable Value SERVER_SOFTWARE Apache-AdvancedExtranetServer/2.0.48 (Mandrake Linux/5mdk) mod_perl/1.99_11 Perl/v5.8.3 mod_ssl/2.0.48 OpenSSL/0.9.7c PHP/4.3.4 SCRIPT_NAME /mailman/options SERVER_SIGNATURE Apache-AdvancedExtranetServer/2.0.48 (Mandrake Linux/5mdk) mod_perl/1.99_11 Perl/v5.8.3 mod_ssl/2.0.48 OpenSSL/0.9.7c PHP/4.3.4 Server at mon.serveur.net Port 80 REQUEST_METHOD GET PATH_INFO /mailman/antoine@serveur.net SERVER_PROTOCOL HTTP/1.1 QUERY_STRING HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) HTTP_CONNECTION Keep-Alive SERVER_NAME mon.serveur.net REMOTE_ADDR 192.168.0.4 PATH_TRANSLATED /usr/lib/mailman/cgi-bin/antoine@serveur.net SERVER_PORT 80 SERVER_ADDR 192.168.0.100 DOCUMENT_ROOT /var/www/html PYTHONPATH /usr/lib/mailman SCRIPT_FILENAME /usr/lib/mailman/cgi-bin/options SERVER_ADMIN root@localhost SCRIPT_URI http://mon.serveur.net/mailman/options/mailman/antoine@serveur.net HTTP_HOST mon.serveur.net SCRIPT_URL /mailman/options/mailman/antoine@serveur.net REQUEST_URI /mailman/options/mailman/antoine@serveur.net HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 1351 HTTP_ACCEPT_LANGUAGE fr HTTP_ACCEPT_ENCODING gzip, deflate ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1093176&group_id=103 From noreply at sourceforge.net Thu Dec 30 16:06:56 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 30 16:07:01 2004 Subject: [ mailman-Bugs-1093176 ] Bug in Mailman version 2.1.4 Message-ID: Bugs item #1093176, was opened at 2004-12-30 04:46 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1093176&group_id=103 Category: configuring/installing Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: htitus (htitus) Assigned to: Nobody/Anonymous (nobody) Summary: Bug in Mailman version 2.1.4 Initial Comment: Bug in Mailman version 2.1.4 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/lib/mailman/scripts/driver", line 68, in run_main immediate=1) File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 49, in __init__ self.__get_f() File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 67, in __get_f 1) File "/usr/lib/python2.3/codecs.py", line 566, in open file = __builtin__.open(filename, mode, buffering) IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' -------------------------------------------------------------------------------- Python information: Variable Value sys.version 2.3.3 (#2, Feb 17 2004, 11:45:40) [GCC 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 -------------------------------------------------------------------------------- Environment variables: Variable Value SERVER_SOFTWARE Apache-AdvancedExtranetServer/2.0.48 (Mandrake Linux/5mdk) mod_perl/1.99_11 Perl/v5.8.3 mod_ssl/2.0.48 OpenSSL/0.9.7c PHP/4.3.4 SCRIPT_NAME /mailman/options SERVER_SIGNATURE Apache-AdvancedExtranetServer/2.0.48 (Mandrake Linux/5mdk) mod_perl/1.99_11 Perl/v5.8.3 mod_ssl/2.0.48 OpenSSL/0.9.7c PHP/4.3.4 Server at mon.serveur.net Port 80 REQUEST_METHOD GET PATH_INFO /mailman/antoine@serveur.net SERVER_PROTOCOL HTTP/1.1 QUERY_STRING HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) HTTP_CONNECTION Keep-Alive SERVER_NAME mon.serveur.net REMOTE_ADDR 192.168.0.4 PATH_TRANSLATED /usr/lib/mailman/cgi-bin/antoine@serveur.net SERVER_PORT 80 SERVER_ADDR 192.168.0.100 DOCUMENT_ROOT /var/www/html PYTHONPATH /usr/lib/mailman SCRIPT_FILENAME /usr/lib/mailman/cgi-bin/options SERVER_ADMIN root@localhost SCRIPT_URI http://mon.serveur.net/mailman/options/mailman/antoine@serveur.net HTTP_HOST mon.serveur.net SCRIPT_URL /mailman/options/mailman/antoine@serveur.net REQUEST_URI /mailman/options/mailman/antoine@serveur.net HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 1351 HTTP_ACCEPT_LANGUAGE fr HTTP_ACCEPT_ENCODING gzip, deflate ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-12-30 10:06 Message: Logged In: YES user_id=12800 run bin/check_perms ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1093176&group_id=103 From noreply at sourceforge.net Thu Dec 30 23:44:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 30 23:44:22 2004 Subject: [ mailman-Bugs-1092895 ] typo: delivery instead of deliver Message-ID: Bugs item #1092895, was opened at 2004-12-29 14:51 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1092895&group_id=103 Category: None >Group: 2.1 (stable) >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Whit (whit_anderson) Assigned to: Nobody/Anonymous (nobody) Summary: typo: delivery instead of deliver Initial Comment: On the mailing list membership configuration page, next to the last option ("Do you want to receive messages that do not match any t opic filter"), last sentence of first paragaph has a typo. "delivery" is used instead of "deliver." See screen shot. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-12-30 17:44 Message: Logged In: YES user_id=12800 Already fixed in CVS for 2.1.6. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1092895&group_id=103