Mailman 3 December 2004 - Mailman-coders

[ mailman-Patches-1088712 ] Use correct char set for command-line scripts
by SourceForge.net Dec. 20, 2004

Dec. 20, 2004

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

1 0

[ mailman-Patches-645297 ] Add PGP support
by SourceForge.net Dec. 20, 2004

Dec. 20, 2004

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

1 0

[ mailman-Patches-1088323 ] sync_member flags processing
by SourceForge.net Dec. 20, 2004

Dec. 20, 2004

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

1 0

[ mailman-Bugs-1087781 ] Bouncer.py "day of year out of range"
by SourceForge.net Dec. 19, 2004

Dec. 19, 2004

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

1 0

[ mailman-Bugs-1087781 ] Bouncer.py "day of year out of range"
by SourceForge.net Dec. 19, 2004

Dec. 19, 2004

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

1 0

[ mailman-Bugs-1064494 ] Accessing list web page - bug report
by SourceForge.net Dec. 19, 2004

Dec. 19, 2004

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

1 0

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

Dec. 18, 2004

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

1 0

[ mailman-Feature Requests-1086838 ] show email attachment name in web interface
by SourceForge.net Dec. 17, 2004

Dec. 17, 2004

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

1 0

[ mailman-Bugs-1063491 ] Put an error message instead of a bug page
by SourceForge.net Dec. 17, 2004

Dec. 17, 2004

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

1 0

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

Dec. 17, 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-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_…

1 0