Mailman 3 December 2004 - Mailman-coders

[ mailman-Bugs-1085874 ] unsubscribe moderator notify not show subscriber's email/nam
by SourceForge.net Dec. 16, 2004

Dec. 16, 2004

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_… 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_…

1 0

[ mailman-Patches-1086319 ] bin/show_qfiles is terminated by exception
by SourceForge.net Dec. 16, 2004

Dec. 16, 2004

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_… 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_…

1 0

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

Dec. 15, 2004

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_… 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_…

1 0

[ mailman-Bugs-1085874 ] unsubscribe moderator notify not show subscriber's email/nam
by SourceForge.net Dec. 15, 2004

Dec. 15, 2004

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_… 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_…

1 0

[ mailman-Bugs-1085651 ] Broken PGP/MIME signature of messages with attachments
by SourceForge.net Dec. 15, 2004

Dec. 15, 2004

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_… 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_…

1 0

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

Dec. 14, 2004

Feature Requests item #923122, was opened at 2004-03-25 14:01 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_i… Category: None Group: None Status: Closed Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: reply_goes_to_list allow poster+list option Initial Comment: Right now, the reply_goes_to_list option allows (a) poster, (b), list, and (c) explicit. How about (d) poster AND list? That is, insert/override a reply-to: header containing both the list name, and the original reply-to (if present, else From: address). For extra credit, omit the original poster if they are a list member. This would be very useful for a number of lists I maintain, where 90% of the traffic is among the list members (hence having a simple reply go to the list), yet a few messages come in from the outside world (hence including the original poster's address). I'm using mailman 2.1.4 on GNU/Linux. Thanks, karl(a)freefriends.org ---------------------------------------------------------------------- Comment By: 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 <Jones(a)Host.Net> | Sender: Jones@Host | Reply-To: The Committee: Jones(a)Host.Net, | Smith(a)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 <http://www.python.org/cgi-bin/ faqw-mm.py?req=show&file=faq03.048.htp> for details. ---------------------------------------------------------------------- Comment By: URA Hiroshi (ura) Date: 2004-05-10 10:44 Message: Logged In: YES user_id=1007264 I uploaded the patch by different method. see following URL: http://sourceforge.net/tracker/index.php?func=detail&aid=951167&group_id=10… ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_i…

1 0

[ mailman-Patches-1085501 ] Welcome Message
by SourceForge.net Dec. 14, 2004

Dec. 14, 2004

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_… 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 <Freedom_Lover at pobox.com> 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_…

1 0

[ mailman-Bugs-1062663 ] empty charset in header crashes admindb.py
by SourceForge.net Dec. 14, 2004

Dec. 14, 2004

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_… 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: <address>Apache/2.0.52 (Unix) Server at lists.dogan.ch Port 443</address> 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(a)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: <address>Apache/2.0.52 (Unix) Server at lists.dogan.ch Port 443</address> 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(a)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_…

1 0

[ mailman-Bugs-1075686 ] footer added to quoted-printable mail isn't encoded
by SourceForge.net Dec. 14, 2004

Dec. 14, 2004

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_… 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_…

1 0

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

Dec. 14, 2004

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_… 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_…

1 0