From noreply at sourceforge.net Mon May 2 16:57:24 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 02 May 2005 07:57:24 -0700 Subject: [ mailman-Patches-1193846 ] pass emailhost to mlist.Create Message-ID: Patches item #1193846, was opened at 2005-05-02 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=300103&aid=1193846&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jorge Jimenez (tribus) Assigned to: Nobody/Anonymous (nobody) Summary: pass emailhost to mlist.Create Initial Comment: As bin/newlist has emailhost option, then make mlist.Create call with lang and host_name parameters to take care of it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1193846&group_id=103 From noreply at sourceforge.net Mon May 2 20:11:16 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 02 May 2005 11:11:16 -0700 Subject: [ mailman-Bugs-1193955 ] SPAM Blacklist Message-ID: Bugs item #1193955, was opened at 2005-05-02 13:11 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=1193955&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: George Kraft IV (gk4) Assigned to: Nobody/Anonymous (nobody) Summary: SPAM Blacklist Initial Comment: It would be nice if the when a mailman admin marks an email address to be discarded and banned, then that email be submitted to spam assassin to be put on the blacklist. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1193955&group_id=103 From noreply at sourceforge.net Mon May 2 20:43:51 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 02 May 2005 11:43:51 -0700 Subject: [ mailman-Bugs-1190404 ] Editing HTML/Text file option sets bad file permissions Message-ID: Bugs item #1190404, was opened at 2005-04-26 08:33 Message generated for change (Comment added) made by ccandreva You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1190404&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Chris Candreva (ccandreva) Assigned to: Nobody/Anonymous (nobody) Summary: Editing HTML/Text file option sets bad file permissions Initial Comment: System is Solaris 8, gcc 3.4.0, python 2.4, Apache 1.3.33 On mailman 2.1.6rc1 and rc2, when I use the "Edit the HTML pages and text files" option, the directories and files created are mode 600 , owned by nobody.mailman . After this, subscriptions fail with a permissions error. Since the listname/en directory is unreadable, there is a permissions error for the e-mail script that tries to send a confirmation message back to the user. ---------------------------------------------------------------------- >Comment By: Chris Candreva (ccandreva) Date: 2005-05-02 10:43 Message: Logged In: YES user_id=116365 This problem still exists in 2.1.6rc3 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1190404&group_id=103 From noreply at sourceforge.net Mon May 2 23:32:20 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 02 May 2005 14:32:20 -0700 Subject: [ mailman-Bugs-1190404 ] Editing HTML/Text file option sets bad file permissions Message-ID: Bugs item #1190404, was opened at 2005-04-26 12:33 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1190404&group_id=103 Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Chris Candreva (ccandreva) Assigned to: Nobody/Anonymous (nobody) Summary: Editing HTML/Text file option sets bad file permissions Initial Comment: System is Solaris 8, gcc 3.4.0, python 2.4, Apache 1.3.33 On mailman 2.1.6rc1 and rc2, when I use the "Edit the HTML pages and text files" option, the directories and files created are mode 600 , owned by nobody.mailman . After this, subscriptions fail with a permissions error. Since the listname/en directory is unreadable, there is a permissions error for the e-mail script that tries to send a confirmation message back to the user. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-05-02 17:32 Message: Logged In: YES user_id=12800 Fixed for 2.1.6 final ---------------------------------------------------------------------- Comment By: Chris Candreva (ccandreva) Date: 2005-05-02 14:43 Message: Logged In: YES user_id=116365 This problem still exists in 2.1.6rc3 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1190404&group_id=103 From noreply at sourceforge.net Tue May 3 14:29:37 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 03 May 2005 05:29:37 -0700 Subject: [ mailman-Bugs-1194419 ] Lose Topics when go directly to topics URL Message-ID: Bugs item #1194419, was opened at 2005-05-03 08:29 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=1194419&group_id=103 Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Jeff Peterson (jeffpeterson) Assigned to: Nobody/Anonymous (nobody) Summary: Lose Topics when go directly to topics URL Initial Comment: If I go directly to my list's Topics URL (http://my.site.com/mailman/admin/scan/topics) the first time I bring up my web browser, I get the List's (Scan) Administrator Authentication page. After signing in, I am redirected to the Admin List's (Scan) Topics page, but all my topics are gone for my list. I looked in the list's directory (mailman/lists/) and the config.pck file has been changed and no longer contains my configurations. Luckily, I had a backup copy of my config.pck file. Is this a known bug? The losing of the configuration/topics information only occurs if I am not currently logged in as administrator and am redirected to the Admin login page. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1194419&group_id=103 From noreply at sourceforge.net Wed May 4 00:05:41 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 03 May 2005 15:05:41 -0700 Subject: [ mailman-Bugs-1194785 ] blank line in headers Message-ID: Bugs item #1194785, was opened at 2005-05-04 00:05 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=1194785&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Enrico Mazzoni (emazzoni) Assigned to: Nobody/Anonymous (nobody) Summary: blank line in headers Initial Comment: Dear developers I run a mailing list service based on mailman 2.1.1 on a SuSE 8.2 server with Postfix 2.0.6 MTA. My problem is the following I recive mail from a domain using the "DomainKey-Signature", such an header arrive to the mailman system as the following: DomainKey-Signature: a=rsa-sha1; c=nofws; s=beta; d=cern.ch; q=dns; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding; b=ap9ypxUfn6e32TCJ/pzBfoTZ5ORy0zIwbdYWApI8LHnxDwswnm5SrK77e5RilnCoD9BPqyUmPOVHgMfcujcobtn1O6+OC2gBAY0EflYTfPB2PcnVcigFhhFDFG/tLshr; when the mailman delivers the message to the list addresses such an header is broken and i got a blank line in it as you can see in the following example: DomainKey-Signature: a=rsa-sha1; c=nofws; s=beta; d=cern.ch; q=dns; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding; b=ap9ypxUfn6e32TCJ/pzBfoTZ5ORy0zIwbdYWApI8LHnxDwswnm5SrK77e5RilnCoD9BPqyUmPOVHgMfcujcobtn1O6+OC2gBAY0EflYTfPB2PcnVcigFhhFDFG/tLshr; Such blank line produce corrupted e-mail for the users who has an account on CERN exchange mail server. Any idea of why mailman produce such a blank line in that kind of header?? Many thanks, Enrico Mazzoni. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1194785&group_id=103 From noreply at sourceforge.net Thu May 5 00:56:11 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 04 May 2005 15:56:11 -0700 Subject: [ mailman-Bugs-1195569 ] HTML email disappears Message-ID: Bugs item #1195569, was opened at 2005-05-04 17:56 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=1195569&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Stan Reeves (sjreeves) Assigned to: Nobody/Anonymous (nobody) Summary: HTML email disappears Initial Comment: In mailman-2.1.6rc2, messages sent in HTML are not posted but simply disappear. If I replace the Messages.py file with the one from 2.1.4, the problem goes away. I found the following in the error log file, which seems to point to this file: May 04 15:16:59 2005 (23119) SHUNTING: 1115245017.9840169+c66ab2072c1f04236dd473ee99eb90 2f7aead680 May 04 15:39:16 2005 (23119) Uncaught runner exception: unicode() argument 2 must be string, not None May 04 15:39:16 2005 (23119) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py ", line 73, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 152, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 285, in verpdeliver Decorate.process(mlist, msgcopy, msgdata) File "/usr/local/mailman/Mailman/Handlers/Decorate.py", line 88, in process mcset = msg.get_content_charset() or 'us-ascii' File "/usr/local/mailman/Mailman/Message.py", line 204, in get_content_charset unicode('x', charset) TypeError: unicode() argument 2 must be string, not None ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1195569&group_id=103 From noreply at sourceforge.net Thu May 5 03:32:28 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 04 May 2005 18:32:28 -0700 Subject: [ mailman-Patches-1160353 ] XHTML Compliant Web UI Message-ID: Patches item #1160353, was opened at 2005-03-09 21:40 Message generated for change (Comment added) made by carbonnb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1160353&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Bryan Carbonnell (carbonnb) Assigned to: Nobody/Anonymous (nobody) Summary: XHTML Compliant Web UI Initial Comment: This is a patch that will make the Web UI XHTML 1.0 Strict compliant. Currently I only have the listinfo pages XHTML compliant, but as time goes by I'm going to make the entire UI compliant. This also allows some small amount of CSS formatting as well. Hopefully this will be of use to somebody. ---------------------------------------------------------------------- >Comment By: Bryan Carbonnell (carbonnb) Date: 2005-05-04 21:32 Message: Logged In: YES user_id=449953 Starting with the patch for MM 2.1.6rc3, the archives are now XHTML1.0 Strict compliant as well as the rest of the UI. To use this patch, unzip it, switch to your source directory and issue the command patch -p1 Bugs item #1196085, was opened at 2005-05-05 17:55 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=1196085&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: dwpoon (dwpoon) Assigned to: Nobody/Anonymous (nobody) Summary: Utils.ScriptURL() doesn't generate relative URLs Initial Comment: In Utils.py, function ScriptURL takes a boolean argument called "absolute". When it's False, the function is supposed to return the target URL relative to the URL of the currently executing CGI. However, a logic bug prevents it from doing that. See the attached patch for the correction. (Patch is against version 2.1.6rc3.) Explanation: fullpath is the URL-path of the current CGI, e.g. '/mailman/create'. baseurl is something like '/mailman/'. Therefore, it makes sense to return a relative URL whenever fullpath STARTSwith baseurl. This fix is important because without the ability to generate relative URLs, the UI will always tend towards using HTTP or HTTPS (whichever happens to be specified in web_page_url). It would be nice if it would continue using whichever protocol was already in use. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1196085&group_id=103 From noreply at sourceforge.net Thu May 5 20:07:17 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 05 May 2005 11:07:17 -0700 Subject: [ mailman-Patches-1196091 ] Really generate relative URLs in Utils.ScriptURL() Message-ID: Patches item #1196091, was opened at 2005-05-05 18:07 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=1196091&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: dwpoon (dwpoon) Assigned to: Nobody/Anonymous (nobody) Summary: Really generate relative URLs in Utils.ScriptURL() Initial Comment: Fix for bug 1196085 https://sourceforge.net/tracker/index.php?func=detail&aid=1196085&group_id=103&atid=100103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1196091&group_id=103 From noreply at sourceforge.net Thu May 5 20:08:32 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 05 May 2005 11:08:32 -0700 Subject: [ mailman-Bugs-1196085 ] Utils.ScriptURL() doesn't generate relative URLs Message-ID: Bugs item #1196085, was opened at 2005-05-05 17:55 Message generated for change (Comment added) made by dwpoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1196085&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: dwpoon (dwpoon) Assigned to: Nobody/Anonymous (nobody) Summary: Utils.ScriptURL() doesn't generate relative URLs Initial Comment: In Utils.py, function ScriptURL takes a boolean argument called "absolute". When it's False, the function is supposed to return the target URL relative to the URL of the currently executing CGI. However, a logic bug prevents it from doing that. See the attached patch for the correction. (Patch is against version 2.1.6rc3.) Explanation: fullpath is the URL-path of the current CGI, e.g. '/mailman/create'. baseurl is something like '/mailman/'. Therefore, it makes sense to return a relative URL whenever fullpath STARTSwith baseurl. This fix is important because without the ability to generate relative URLs, the UI will always tend towards using HTTP or HTTPS (whichever happens to be specified in web_page_url). It would be nice if it would continue using whichever protocol was already in use. ---------------------------------------------------------------------- >Comment By: dwpoon (dwpoon) Date: 2005-05-05 18:08 Message: Logged In: YES user_id=1181585 Patch Tracker 1196091 http://sourceforge.net/tracker/index.php?func=detail&aid=1196091&group_id=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1196085&group_id=103 From noreply at sourceforge.net Sun May 8 09:59:32 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 08 May 2005 00:59:32 -0700 Subject: [ mailman-Patches-1197559 ] Bug in 2.1.5 Finnish translation (format string) Message-ID: Patches item #1197559, was opened at 2005-05-08 07:59 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=1197559&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: dev at bacademy (bacademy) Assigned to: Nobody/Anonymous (nobody) Summary: Bug in 2.1.5 Finnish translation (format string) Initial Comment: Mailman bin/arch bug due to invalid format string in the Finnish translation. raceback (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 313, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1051, in write_TOC toc.write(self.html_TOC()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 740, in html_TOC accum.append(self.html_TOC_entry(a)) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 766, in html_TOC_entry templ = '[ ' + _('Text%(sz)s') + ']' File "/usr/local/mailman/Mailman/i18n.py", line 89, in _ return tns % dict ValueError: unsupported format character '?' (0xffffffe4) at index 11 I've attached a patch that fixes this, on a running system msgfmt -o mailman.mo mailman.po must be run to regenerate the .mo file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1197559&group_id=103 From noreply at sourceforge.net Mon May 9 12:43:54 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 09 May 2005 03:43:54 -0700 Subject: [ mailman-Bugs-958816 ] bug in 2.1.5 - can't unsubscribe (with danish lang selected) Message-ID: Bugs item #958816, was opened at 2004-05-23 09:12 Message generated for change (Comment added) made by regnauld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=958816&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Klavs Klavsen (klavs) Assigned to: Nobody/Anonymous (nobody) Summary: bug in 2.1.5 - can't unsubscribe (with danish lang selected) Initial Comment: When viewing the user page in danish (with 30% or less translated - I'll have a look a that at some point when I get the time) - it fails with this message (it works fine when using english): 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, Jul 28 2003, 11:43:19) [GCC 3.2.2 20030322 (Gentoo Linux 1.4 3.2.2-r2)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value PATH_INFO /lp-nyhedsbrev CONTENT_LENGTH 100 CONTENT_TYPE application/x-www-form-urlencoded HTTP_COOKIE POSTNUKESID=5241e6345df9c0303def0d4b0749ea3a SCRIPT_FILENAME /usr/local/mailman/cgi-bin/options PYTHONPATH /usr/local/mailman SERVER_SOFTWARE Apache SERVER_ADMIN admin at EnableIT.dk SCRIPT_NAME /mailman/options SCRIPT_URI http://www.mysite.dk/mailman/options/lp-nyhedsbrev SERVER_SIGNATURE REQUEST_METHOD POST HTTP_HOST www.mysite.dk SCRIPT_URL /mailman/options/lp-nyhedsbrev SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/options/lp-nyhedsbrev HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040418 Firefox/0.8 HTTP_CONNECTION keep-alive HTTP_REFERER http://www.mysite.dk/mailman/listinfo/lp-nyhedsbrev SERVER_NAME my site REMOTE_ADDR HTTP_KEEP_ALIVE 300 REMOTE_PORT 34514 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 PATH_TRANSLATED /www/websites/mysite/html/lp-nyhedsbrev SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 192.168.1.2 DOCUMENT_ROOT /www/websites ---------------------------------------------------------------------- Comment By: Phil Regnauld (regnauld) Date: 2005-05-09 12:43 Message: Logged In: YES user_id=1275085 This fixed it for me. See related item: https://sourceforge.net/tracker/? func=detail&atid=100103&aid=1166155&group_id=103 --- messages/da/LC_MESSAGES/mailman.po.orig Mon May 9 12:34:51 2005 +++ messages/da/LC_MESSAGES/mailman.po Mon May 9 12:32:27 2005 @@ -2491,7 +2491,7 @@ " " msgstr "" "For at ændre dine personlige indstillinger, skal du logge ind nedenfor " -"ved at indtaste dit %(extra)password.\n" +"ved at indtaste dit %(extra)spassword.\n" "Hvis du ikke kan huske dit password, kan du bede om at få det tilsendt " "i en e-mail ved at klikke på knappen nedenfor.\n" "Hvis du kun ønsker at framelde dig fra listen, klik da på Meld mig " ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=958816&group_id=103 From noreply at sourceforge.net Mon May 9 13:03:29 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 09 May 2005 04:03:29 -0700 Subject: [ mailman-Bugs-958816 ] bug in 2.1.5 - can't unsubscribe (with danish lang selected) Message-ID: Bugs item #958816, was opened at 2004-05-23 09:12 Message generated for change (Comment added) made by klavs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=958816&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Klavs Klavsen (klavs) Assigned to: Nobody/Anonymous (nobody) Summary: bug in 2.1.5 - can't unsubscribe (with danish lang selected) Initial Comment: When viewing the user page in danish (with 30% or less translated - I'll have a look a that at some point when I get the time) - it fails with this message (it works fine when using english): 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, Jul 28 2003, 11:43:19) [GCC 3.2.2 20030322 (Gentoo Linux 1.4 3.2.2-r2)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value PATH_INFO /lp-nyhedsbrev CONTENT_LENGTH 100 CONTENT_TYPE application/x-www-form-urlencoded HTTP_COOKIE POSTNUKESID=5241e6345df9c0303def0d4b0749ea3a SCRIPT_FILENAME /usr/local/mailman/cgi-bin/options PYTHONPATH /usr/local/mailman SERVER_SOFTWARE Apache SERVER_ADMIN admin at EnableIT.dk SCRIPT_NAME /mailman/options SCRIPT_URI http://www.mysite.dk/mailman/options/lp-nyhedsbrev SERVER_SIGNATURE REQUEST_METHOD POST HTTP_HOST www.mysite.dk SCRIPT_URL /mailman/options/lp-nyhedsbrev SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/options/lp-nyhedsbrev HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040418 Firefox/0.8 HTTP_CONNECTION keep-alive HTTP_REFERER http://www.mysite.dk/mailman/listinfo/lp-nyhedsbrev SERVER_NAME my site REMOTE_ADDR HTTP_KEEP_ALIVE 300 REMOTE_PORT 34514 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 PATH_TRANSLATED /www/websites/mysite/html/lp-nyhedsbrev SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 192.168.1.2 DOCUMENT_ROOT /www/websites ---------------------------------------------------------------------- >Comment By: Klavs Klavsen (klavs) Date: 2005-05-09 13:03 Message: Logged In: YES user_id=23531 I actually got this fixed, via the ML I think. Forgot to update the tracker :( (sorry). Thanks Phil for the fix. ---------------------------------------------------------------------- Comment By: Phil Regnauld (regnauld) Date: 2005-05-09 12:43 Message: Logged In: YES user_id=1275085 This fixed it for me. See related item: https://sourceforge.net/tracker/? func=detail&atid=100103&aid=1166155&group_id=103 --- messages/da/LC_MESSAGES/mailman.po.orig Mon May 9 12:34:51 2005 +++ messages/da/LC_MESSAGES/mailman.po Mon May 9 12:32:27 2005 @@ -2491,7 +2491,7 @@ " " msgstr "" "For at ændre dine personlige indstillinger, skal du logge ind nedenfor " -"ved at indtaste dit %(extra)password.\n" +"ved at indtaste dit %(extra)spassword.\n" "Hvis du ikke kan huske dit password, kan du bede om at få det tilsendt " "i en e-mail ved at klikke på knappen nedenfor.\n" "Hvis du kun ønsker at framelde dig fra listen, klik da på Meld mig " ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=958816&group_id=103 From noreply at sourceforge.net Mon May 9 14:23:58 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 09 May 2005 05:23:58 -0700 Subject: [ mailman-Patches-1197559 ] Bug in 2.1.5 Finnish translation (format string) Message-ID: Patches item #1197559, was opened at 2005-05-08 07:59 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1197559&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: dev at bacademy (bacademy) Assigned to: Nobody/Anonymous (nobody) Summary: Bug in 2.1.5 Finnish translation (format string) Initial Comment: Mailman bin/arch bug due to invalid format string in the Finnish translation. raceback (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 313, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1051, in write_TOC toc.write(self.html_TOC()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 740, in html_TOC accum.append(self.html_TOC_entry(a)) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 766, in html_TOC_entry templ = '[ ' + _('Text%(sz)s') + ']' File "/usr/local/mailman/Mailman/i18n.py", line 89, in _ return tns % dict ValueError: unsupported format character '?' (0xffffffe4) at index 11 I've attached a patch that fixes this, on a running system msgfmt -o mailman.mo mailman.po must be run to regenerate the .mo file. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-05-09 12:23 Message: Logged In: YES user_id=67709 This was fixed in 2.1.6(rc). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1197559&group_id=103 From noreply at sourceforge.net Mon May 9 18:01:57 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 09 May 2005 09:01:57 -0700 Subject: [ mailman-Feature Requests-1198375 ] edit moderated messages directly on admindb page Message-ID: Feature Requests item #1198375, was opened at 2005-05-09 09:01 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=1198375&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: rst (r_st) Assigned to: Nobody/Anonymous (nobody) Summary: edit moderated messages directly on admindb page Initial Comment: When viewing held messages on the administrative database page, owners/moderators should be able to edit those messages without having to forward the messages to themselves. This will allow for easy editing as well as maintaining the original headers. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1198375&group_id=103 From noreply at sourceforge.net Tue May 10 11:33:13 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 10 May 2005 02:33:13 -0700 Subject: [ mailman-Patches-818601 ] 'Announcement-only' (read only) list Message-ID: Patches item #818601, was opened at 2003-10-06 22:07 Message generated for change (Settings changed) made by hatukanezumi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_id=103 Category: Web UI Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) >Summary: 'Announcement-only' (read only) list Initial Comment: Documents say that Mailman "supports a wide range of mailing list types, such as general discussion lists and announce-only lists". It's exactly true. But some people wish really "announcement-only" feature. By `Announcement-only' feature: o Posting by e-mail is not allowed at all. All messages to posting address are forwarded to owners and no other users won't receive it. o Web interface is provided so that only specified users ("posters") can post messages to list. For example for `mail magazine' publishers, `announcement-only' list is safer (Oooops! I've approved the SPAM!) and let them be free from moderation tasks. Changes on codes: o New CGI script `post'. o New handler `Posttop' which switches messages bound to list to owners (only on annnouncement-only list). o New `announcement_only' configuration directive. o Some modifications of templates. Notice: By now this is buggie (both in Python and English). Comments and Fixes are welcome. ---------------------------------------------------------------------- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2004-01-06 16:20 Message: Logged In: YES user_id=529503 Update for 2.1.4. ---------------------------------------------------------------------- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-10-29 19:39 Message: Logged In: YES user_id=529503 rel.1.0. o Confusing "announcement-only" has been changed to "read-only". o New admin category. ---------------------------------------------------------------------- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-10-09 23:51 Message: Logged In: YES user_id=529503 rel.0.2. * Posttop handler now placed after Hold handler so that spam discarding and auto-response are capable. * Global pipelone processing are ommitted when: -------------------------------------- SpamDetect : [A] and [W] Approve : [W] ReplyBot : [W] Moderate : [A] Hold : - administrivia : [A] - too many recips : [A] - implicit dest. : [A] - suspicious headers : [A] and not [W] - message size : [A] and not [W] - news moderation : [A] and not [W] Posttop : (if [A], may be switched to owner pipeline.) AvoidDuplicates : [A] ------------------------------ [A]: list is announcement-only. [W]: message is posted from Web (by `poster'). * Additional modification to templates. * Some admin option categories are hidden. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_id=103 From noreply at sourceforge.net Tue May 10 11:36:44 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 10 May 2005 02:36:44 -0700 Subject: [ mailman-Patches-818601 ] 'Announcement-only' (read only) list Message-ID: Patches item #818601, was opened at 2003-10-06 22:07 Message generated for change (Comment added) made by hatukanezumi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_id=103 Category: Web UI Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: 'Announcement-only' (read only) list Initial Comment: Documents say that Mailman "supports a wide range of mailing list types, such as general discussion lists and announce-only lists". It's exactly true. But some people wish really "announcement-only" feature. By `Announcement-only' feature: o Posting by e-mail is not allowed at all. All messages to posting address are forwarded to owners and no other users won't receive it. o Web interface is provided so that only specified users ("posters") can post messages to list. For example for `mail magazine' publishers, `announcement-only' list is safer (Oooops! I've approved the SPAM!) and let them be free from moderation tasks. Changes on codes: o New CGI script `post'. o New handler `Posttop' which switches messages bound to list to owners (only on annnouncement-only list). o New `announcement_only' configuration directive. o Some modifications of templates. Notice: By now this is buggie (both in Python and English). Comments and Fixes are welcome. ---------------------------------------------------------------------- >Comment By: Hatuka*nezumi (hatukanezumi) Date: 2005-05-10 18:36 Message: Logged In: YES user_id=529503 Update for 2.1.6RC3. ---------------------------------------------------------------------- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2004-01-06 16:20 Message: Logged In: YES user_id=529503 Update for 2.1.4. ---------------------------------------------------------------------- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-10-29 19:39 Message: Logged In: YES user_id=529503 rel.1.0. o Confusing "announcement-only" has been changed to "read-only". o New admin category. ---------------------------------------------------------------------- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-10-09 23:51 Message: Logged In: YES user_id=529503 rel.0.2. * Posttop handler now placed after Hold handler so that spam discarding and auto-response are capable. * Global pipelone processing are ommitted when: -------------------------------------- SpamDetect : [A] and [W] Approve : [W] ReplyBot : [W] Moderate : [A] Hold : - administrivia : [A] - too many recips : [A] - implicit dest. : [A] - suspicious headers : [A] and not [W] - message size : [A] and not [W] - news moderation : [A] and not [W] Posttop : (if [A], may be switched to owner pipeline.) AvoidDuplicates : [A] ------------------------------ [A]: list is announcement-only. [W]: message is posted from Web (by `poster'). * Additional modification to templates. * Some admin option categories are hidden. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_id=103 From noreply at sourceforge.net Tue May 10 13:30:33 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 10 May 2005 04:30:33 -0700 Subject: [ mailman-Patches-630339 ] create list with multiple owners Message-ID: Patches item #630339, was opened at 2002-10-29 18:03 Message generated for change (Comment added) made by hatukanezumi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=630339&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: create list with multiple owners Initial Comment: Create list with multiple list owners, by 'create' CGI script and 'newlist' command line script. ---------------------------------------------------------------------- >Comment By: Hatuka*nezumi (hatukanezumi) Date: 2005-05-10 20:30 Message: Logged In: YES user_id=529503 Update for 2.1.6RC3. ---------------------------------------------------------------------- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2004-01-06 16:28 Message: Logged In: YES user_id=529503 Update for 2.1.4. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=630339&group_id=103 From noreply at sourceforge.net Wed May 11 19:53:35 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 11 May 2005 10:53:35 -0700 Subject: [ mailman-Feature Requests-1200044 ] Multiple list subscription Message-ID: Feature Requests item #1200044, was opened at 2005-05-11 10:53 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=1200044&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Trevor Cullingsworth (phh_sysadmin) Assigned to: Nobody/Anonymous (nobody) Summary: Multiple list subscription Initial Comment: Hi, Is there a way to enter an e-mail account and have all of the mailing lists listed on a browser page with radio buttons and then be able to select all of the lists you want that e-mail account to be subscribed to? And the reverse - is there a way that I can enter an e-mail account and have a page display listing all of the mailing lists this user is subscribed to and be able to unsubscribe that user from all of the lists at once instead of having to go into each list? Thank you. Trevor Cullingsworth ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1200044&group_id=103 From noreply at sourceforge.net Wed May 11 20:17:56 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 11 May 2005 11:17:56 -0700 Subject: [ mailman-Feature Requests-1200060 ] Multiple list subscription Message-ID: Feature Requests item #1200060, was opened at 2005-05-11 11:17 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=1200060&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Trevor Cullingsworth (phh_sysadmin) Assigned to: Nobody/Anonymous (nobody) Summary: Multiple list subscription Initial Comment: Hi, Is there a way to enter an e-mail account and have all of the mailing lists listed on a browser page with radio buttons and then be able to select all of the lists you want that e-mail account to be subscribed to? And the reverse - is there a way that I can enter an e-mail account and have a page display listing all of the mailing lists this user is subscribed to and be able to unsubscribe that user from all of the lists at once instead of having to go into each list? Thank you. Trevor Cullingsworth ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1200060&group_id=103 From noreply at sourceforge.net Fri May 13 08:27:48 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 12 May 2005 23:27:48 -0700 Subject: [ mailman-Feature Requests-1201160 ] Sorting list of members by different view Message-ID: Feature Requests item #1201160, was opened at 2005-05-13 08:27 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=1201160&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Dick Kaas (dick_kaas) Assigned to: Nobody/Anonymous (nobody) Summary: Sorting list of members by different view Initial Comment: At the moment I (as a list administrator) can only view the members sorted by the first letter of their e- mailaddress. [also the users can only view them in this order] I also want the opportunity (and I even prefer this as a default) to list the member sorted by the name of the member. As I start with the organisation name followed by a user I would hope this is possible. Is there I way to change this option? I could not find it in the faq or documentation Dick e-mail thuis: dick at kaas.nl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1201160&group_id=103 From noreply at sourceforge.net Sun May 15 08:03:22 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 14 May 2005 23:03:22 -0700 Subject: [ mailman-Patches-1189243 ] Unhandle exception in Message.get_content_charset() Message-ID: Patches item #1189243, was opened at 2005-04-24 21:16 Message generated for change (Comment added) made by jparise You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1189243&group_id=103 Category: None Group: Mailman 2.1 Status: Closed Resolution: Accepted Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: Unhandle exception in Message.get_content_charset() Initial Comment: Message.get_content_charset() can encounter an unhandled exception "(TypeError: unicode() argument 2 must be string, not None") when charset is None. This can can only occur when the call to email.Message.Message.get_content_charset(self, failobj) itself returns None, but, not being acquainted with the email package, I don't understand the circumstances which can cause this situation. Regardless, when charset is None, the call to unicode() will throw the TypeError exception. The attached patch recognizes this as a valid failure case such that failobj will be returned. ---------------------------------------------------------------------- >Comment By: Jon Parise (jparise) Date: 2005-05-14 23:03 Message: Logged In: YES user_id=485579 I haven't been able to catch any more of those evil messages, so I'm going to stop hunting for them. Sorry I wasn't able to provide you with a test case. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-04-29 06:30 Message: Logged In: YES user_id=12800 Tokio, I don't like having duplicate code, so I think it's best to fix the problem in one place and not keep the workaround in Mailman's copy. I've installed email 2.5.6 now and will release Mailman 2.1.6rc3 in a little while. At my own site, all the shunted messages that were broken because of this problem have now been fixed and properly unshunted. I will be updating python.org hopefully this weekend. Let's give rc3 a couple of weeks to shake out. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-04-28 17:02 Message: Logged In: YES user_id=67709 Barry, TypeError is already avoided in email package by this statement: pcharset = charset[0] or 'us-ascii' I want to keep the latter try/except in Mailman/Message.py to assure the charset is known to mailman so that it can serve as security precaution to future mailman code changes, even after the email package is updated to 2.5.6. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-04-25 10:02 Message: Logged In: YES user_id=12800 If it's not too much trouble. I'd love to have a test case in the email package for the TypeError exception. If you can't, no worries. ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2005-04-25 08:46 Message: Logged In: YES user_id=485579 Sorry, I don't. Those messages were unshunted as a result of my fix. I could try to instrument a collection mechanism by trapping that exception and storing a copy of the offensive message, however. Would that still be useful? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-04-25 07:32 Message: Logged In: YES user_id=12800 Is there any possibility that you have a sample message that exhibits this problem? I would /really/ like to add a test case for this to the email package, which is where the patch really belongs. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-04-24 21:50 Message: Logged In: YES user_id=67709 Thank you! I just fixed in CVS. (I'd rather make it bare except ...) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1189243&group_id=103 From noreply at sourceforge.net Sun May 15 16:07:03 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 15 May 2005 07:07:03 -0700 Subject: [ mailman-Patches-1189243 ] Unhandle exception in Message.get_content_charset() Message-ID: Patches item #1189243, was opened at 2005-04-25 00:16 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1189243&group_id=103 Category: None Group: Mailman 2.1 Status: Closed Resolution: Accepted Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: Unhandle exception in Message.get_content_charset() Initial Comment: Message.get_content_charset() can encounter an unhandled exception "(TypeError: unicode() argument 2 must be string, not None") when charset is None. This can can only occur when the call to email.Message.Message.get_content_charset(self, failobj) itself returns None, but, not being acquainted with the email package, I don't understand the circumstances which can cause this situation. Regardless, when charset is None, the call to unicode() will throw the TypeError exception. The attached patch recognizes this as a valid failure case such that failobj will be returned. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-05-15 10:07 Message: Logged In: YES user_id=12800 No problem. I believe we've got this one fixed now. ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2005-05-15 02:03 Message: Logged In: YES user_id=485579 I haven't been able to catch any more of those evil messages, so I'm going to stop hunting for them. Sorry I wasn't able to provide you with a test case. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-04-29 09:30 Message: Logged In: YES user_id=12800 Tokio, I don't like having duplicate code, so I think it's best to fix the problem in one place and not keep the workaround in Mailman's copy. I've installed email 2.5.6 now and will release Mailman 2.1.6rc3 in a little while. At my own site, all the shunted messages that were broken because of this problem have now been fixed and properly unshunted. I will be updating python.org hopefully this weekend. Let's give rc3 a couple of weeks to shake out. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-04-28 20:02 Message: Logged In: YES user_id=67709 Barry, TypeError is already avoided in email package by this statement: pcharset = charset[0] or 'us-ascii' I want to keep the latter try/except in Mailman/Message.py to assure the charset is known to mailman so that it can serve as security precaution to future mailman code changes, even after the email package is updated to 2.5.6. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-04-25 13:02 Message: Logged In: YES user_id=12800 If it's not too much trouble. I'd love to have a test case in the email package for the TypeError exception. If you can't, no worries. ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2005-04-25 11:46 Message: Logged In: YES user_id=485579 Sorry, I don't. Those messages were unshunted as a result of my fix. I could try to instrument a collection mechanism by trapping that exception and storing a copy of the offensive message, however. Would that still be useful? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-04-25 10:32 Message: Logged In: YES user_id=12800 Is there any possibility that you have a sample message that exhibits this problem? I would /really/ like to add a test case for this to the email package, which is where the patch really belongs. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-04-25 00:50 Message: Logged In: YES user_id=67709 Thank you! I just fixed in CVS. (I'd rather make it bare except ...) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1189243&group_id=103 From noreply at sourceforge.net Sun May 15 20:13:24 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 15 May 2005 11:13:24 -0700 Subject: [ mailman-Feature Requests-1192175 ] provide filtered log access via web Message-ID: Feature Requests item #1192175, was opened at 2005-04-28 22:33 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1192175&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Stephen J. Turnbull (yaseppochi) Assigned to: Nobody/Anonymous (nobody) Summary: provide filtered log access via web Initial Comment: ... and queuefile summary data, too! Suggested interface: new toplevel menu item for a TROUBLESHOOTING page. The page would contain query boxes for (a) logfiles and (b) queue summaries. The LOG QUERY would have a checkbox (not radio button) interface listing the available logs. Filters would include (a) timestamp range (b) general Python regexp at least. The QUEUE QUERY would have a checkbox listing the queues. Rather than have filters (at least at first) the QUEUE QUERY might just provide age distributions, say < 1 hour, < 5 hours, < 1 day, > 1 day for each requested queue. I'm of two minds as to whether an interface to access data about individual messages would be useful. The thing is, generally to do anything useful about the queues you need shell and privileged access to the host. It might be useful to have a MiniFAQ on this page that just points to the MFAQs on the FAQWizard. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-05-15 11:13 Message: Logged In: YES user_id=1123998 How would access to the TROUBLESHOOTING page be controlled? I can see many (most?, all?) hosting providers not wanting to allow e.g. a list admin to access even Mailman logs since these logs contain entries for the entire site. Some logs but not all can be filtered by list so possibly just a list password could be used to access list specific entries, but in general, I think we might need a new sitewide TROUBLESHOOTING page password. ---------------------------------------------------------------------- Comment By: Stephen J. Turnbull (yaseppochi) Date: 2005-04-30 00:12 Message: Logged In: YES user_id=88738 As pointed out by Brad Knowles, Mailman can't unilaterally provide access to MTA queues. That will depend on the privileges the host gives to the list admins. It would be useful on the troubleshooting page to point to FAQs that help the list admins provide the MTA admins with the info they need to troubleshoot problems on the MTA side. For newbie list+MTA admins, pointers to the MTA mailing lists. ---------------------------------------------------------------------- Comment By: Stephen J. Turnbull (yaseppochi) Date: 2005-04-30 00:10 Message: Logged In: YES user_id=88738 As pointed out by Brad Knowles, Mailman can't unilaterally provide access to MTA queues. That will depend on the privileges the host gives to the list admins. It would be useful on the troubleshooting page to point to FAQs that help the list admins provide the MTA admins with the info they need to troubleshoot problems on the MTA side. For newbie list+MTA admins, pointers to the MTA mailing lists. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1192175&group_id=103 From noreply at sourceforge.net Tue May 17 01:06:53 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 16 May 2005 16:06:53 -0700 Subject: [ mailman-Feature Requests-1203189 ] sort or filter pending moderator requests Message-ID: Feature Requests item #1203189, was opened at 2005-05-16 23:06 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=1203189&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Lorin Gaertner (lsgaertner) Assigned to: Nobody/Anonymous (nobody) Summary: sort or filter pending moderator requests Initial Comment: Make it possible to sort or filter pending moderator requests. (1) by reason message is pending (e.g. not a member of list, implicit destination, message too large) (2) by sender of message (3) by subject of message #1 is the most useful but once you had the ability to do one I imagine the others would follow quickly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1203189&group_id=103 From noreply at sourceforge.net Tue May 17 14:05:02 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 17 May 2005 05:05:02 -0700 Subject: [ mailman-Bugs-839419 ] feature req: mails should contain URIs of archived msg Message-ID: Bugs item #839419, was opened at 2003-11-10 18:23 Message generated for change (Comment added) made by grahamk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=839419&group_id=103 Category: mail delivery Group: None Status: Open Resolution: None Priority: 5 Submitted By: Justin Mason (jmason) Assigned to: Nobody/Anonymous (nobody) Summary: feature req: mails should contain URIs of archived msg Initial Comment: Hi all, It'd be a great feature for web integration, if outgoing messages were to contain that message's URI in the web archives. This would provide a nice way for each message on a public, archived list, to have a "permanent URI" for that message; if I come across a message I'd like to forward, I have to do one of these: 1. forward the entire message text, traditional style, or 2. go to the archive URI, find current month, and visually look for the message in question in the "by thread" page for that month ---------------------------------------------------------------------- Comment By: Graham Klyne (grahamk) Date: 2005-05-17 13:05 Message: Logged In: YES user_id=168177 Yes please!!! Cf. also http://www.ietf.org/internet-drafts/draft-duerst-archived-at-03.txt Which is modelled on a system operated by W3C ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=839419&group_id=103 From noreply at sourceforge.net Tue May 17 16:23:14 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 17 May 2005 07:23:14 -0700 Subject: [ mailman-Bugs-1203596 ] List-archive link not working Message-ID: Bugs item #1203596, was opened at 2005-05-17 15:23 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=1203596&group_id=103 Category: Pipermail Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Graham Klyne (grahamk) Assigned to: Nobody/Anonymous (nobody) Summary: List-archive link not working Initial Comment: Running mailman version 2.1.6rc1, new installation on Scientific Linux 3.04 with Apache and Postfix as distributed. The list-archive link supplied in messages loses the archive name when clicking through to the view by "thread" link. Example: 1. Message contains: List-Archive: 2. Clicking on this yields a page at the given URI. NOTE browser is running and already logged into view the private archive (see step 6 below) 3. Clicking on view by thread link displays new page at this URI: http://lists.ontonet.org/mailman/private/2005q2/thread.html containing the text: No such list 2005q2 Note that the mailing list name (ontogenesis) has been dropped. 4. If I browse directly to the same URI, same result (no surprise). 5. If I browse directly to this URI http://lists.ontonet.org/mailman/private/ontogenesis/ (note trailing '/') then it works just fine. 6. And here's an extra wrinkle. If the browser is not already logged in to view the private mailing list, then the login page is displayed. After logging in, the requested archive frontpage is displayes *with a trailing '/' in its URI*, and the view-by link works just fine. ... Hypothesis: relative URI calculation is dropping the final path segment of the base URI when there is no trailing '/'. (This would be correct behaviour according to URI spec) Examination of "view page source" shows that the links are relative refererecnes within the TOC page, so this hypothesis appears to be confirmed. Thus, it is vital that the index page is accessed using a URI with a trailing '/', otherwise the list name is dropped when a full URI is formed from the relative reference. One solution is to place a directive in the of the TOC document. I've edited the corresponding Index.html by hand, and this seems to work. I've also identified two simple patches that I think achieve this: (1) In Archive/HyperArch.py: [[ def html_TOC(self): mlist = self.maillist listname = mlist.internal_name() mbox = os.path.join(mlist.archive_dir()+'.mbox', listname+'.mbox') d = {"listname": mlist.real_name, "listinfo": mlist.GetScriptURL('listinfo', absolute=1), "archurl": mlist.GetScriptURL('private', absolute=1)+'/', [[[GK]]] "fullarch": '../%s.mbox/%s.mbox' % (listname, listname), "size": sizeof(mbox, mlist.preferred_language), 'meta': '', } : ]] (added "archurl" entry) (2) In templates/en/archtoc.html, archtocnombx.html [[ The %(listname)s Archives %(meta)s : ]] (added in Similar edits would be needed for other languages. I haven't figured out how to force mailman to regenerate the archive TOC file, so haven't yet been able to test thisyet. ... Not sure if this might be related to: [ 767596 ] mailman list archive links not working with virtual hosts ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1203596&group_id=103 From noreply at sourceforge.net Wed May 18 15:15:24 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 18 May 2005 06:15:24 -0700 Subject: [ mailman-Bugs-1204262 ] Block attachments by default Message-ID: Bugs item #1204262, was opened at 2005-05-18 16:15 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=1204262&group_id=103 Category: mail delivery Group: None Status: Open Resolution: None Priority: 5 Submitted By: Lars Nood?n (larsnooden) Assigned to: Nobody/Anonymous (nobody) Summary: Block attachments by default Initial Comment: Netiquette requires that people refrain from sending attachments to lists. Most mailing lists have have policy anyway to explicity request that user respect eachother's bandwidth. Thus for these groups any mail that arrives with an attachment is probably an mS- virus or mS-worm and not welcome anyway. So Mailman ought to have a function to block messages with attachments - and that function ought to be turned on by default. There are exceptions though, so it should be possible to turn off this blocking for individual lists. There could be several behaviors to do this: 1) send the whole thing to /dev/null 2) send the attachment to /dev/null and let the text-based body through 3) do either of the above and send a warning to the sender explaining what happened etc. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1204262&group_id=103 From noreply at sourceforge.net Wed May 18 18:01:01 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 18 May 2005 09:01:01 -0700 Subject: [ mailman-Bugs-1204386 ] check_perms doesn't ensure aliases.db is group-writeable Message-ID: Bugs item #1204386, was opened at 2005-05-18 17:01 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=1204386&group_id=103 Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Graham Klyne (grahamk) Assigned to: Nobody/Anonymous (nobody) Summary: check_perms doesn't ensure aliases.db is group-writeable Initial Comment: Problem reported for mailman 2.1.6rc4 With postfix 2:2.0.16-14.RHEL3 When installing mailman 2.1.6rc1 using postfix MTA and "Integrating Postfix and Mailman" as described inthe installation document, I encountered a problem that the aliases.db file was created without group write capability. This was not detected by check_perms. (Even on re-reading, it's not obvious to me that g+w permissions are required, though that became pretty obvious when I tracked the error log failure report when attempting to create a new mailing list.) Because I messed around a bit with that installation, I've verified the problem with check_perms on a working 2.1.6rc4 installation, by resetting the groupwrite permission, thus: The following is executed as user mailman in dirtectory /var/mailman/data: [[ bash-2.05b$ ls -al total 60 drwxrwsr-x 2 mailman mailman 4096 May 18 14:31 . drwxrwsr-x 9 mailman mailman 4096 Apr 21 18:36 .. -rw-r----- 1 mailman mailman 41 Apr 29 13:54 adm.pw -rw-rw---- 1 mailman mailman 4922 May 4 16:25 aliases -rw-rw---- 1 mailman mailman 12288 May 4 16:25 aliases.db -rw-r----- 1 mailman mailman 41 Apr 22 15:07 creator.pw -rw-r--r-- 1 mailman mailman 10 May 18 14:32 last_mailman_version -rw-rw---- 1 mailman mailman 6 May 12 09:19 master-qrunner.pid -rw-r--r-- 1 mailman mailman 14110 May 18 14:31 sitelist.cfg bash-2.05b$ bash-2.05b$ /home/mailman/bin/check_perms No problems found (This is a normal working configuration from which I started) bash-2.05b$ chmod g-w aliases* bash-2.05b$ /home/mailman/bin/check_perms /var/mailman/data/aliases permissions must be 066x (got 0100640) Problems found: 1 Re-run as mailman (or root) with -f flag to fix (check_perms notices the problem with aliases, but not with aliases.db) bash-2.05b$ ls -al total 60 drwxrwsr-x 2 mailman mailman 4096 May 18 14:31 . drwxrwsr-x 9 mailman mailman 4096 Apr 21 18:36 .. -rw-r----- 1 mailman mailman 41 Apr 29 13:54 adm.pw -rw-r----- 1 mailman mailman 4922 May 4 16:25 aliases -rw-r----- 1 mailman mailman 12288 May 4 16:25 aliases.db -rw-r----- 1 mailman mailman 41 Apr 22 15:07 creator.pw -rw-r--r-- 1 mailman mailman 10 May 18 14:32 last_mailman_version -rw-rw---- 1 mailman mailman 6 May 12 09:19 master-qrunner.pid -rw-r--r-- 1 mailman mailman 14110 May 18 14:31 sitelist.cfg bash-2.05b$ chmod g+w aliases bash-2.05b$ /home/mailman/bin/check_perms No problems found bash-2.05b$ ls -al total 60 drwxrwsr-x 2 mailman mailman 4096 May 18 14:31 . drwxrwsr-x 9 mailman mailman 4096 Apr 21 18:36 .. -rw-r----- 1 mailman mailman 41 Apr 29 13:54 adm.pw -rw-rw---- 1 mailman mailman 4922 May 4 16:25 aliases -rw-r----- 1 mailman mailman 12288 May 4 16:25 aliases.db -rw-r----- 1 mailman mailman 41 Apr 22 15:07 creator.pw -rw-r--r-- 1 mailman mailman 10 May 18 14:32 last_mailman_version -rw-rw---- 1 mailman mailman 6 May 12 09:19 master-qrunner.pid -rw-r--r-- 1 mailman mailman 14110 May 18 14:31 sitelist.cfg (No report from check_perms despite missing group write permission on aliases.db) ]] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1204386&group_id=103 From noreply at sourceforge.net Sun May 22 22:19:08 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 22 May 2005 13:19:08 -0700 Subject: [ mailman-Bugs-1099138 ] Scrubber.py traceback Message-ID: Bugs item #1099138, was opened at 2005-01-09 17:36 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099138&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Fixed Priority: 5 Submitted By: Owen Taylor (otaylor) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber.py traceback Initial Comment: Outgoing mail on one of our lists on mail.gnome.org was being held up because of a error that was occuring sending out digests. Jan 09 16:07:24 2005 (22410) Uncaught runner exception: len() of unsized object Jan 09 16:07:24 2005 (22410) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 262, in process size = len(payload) TypeError: len() of unsized object Unfortunately, I don't know what mail was triggering this... was trying to get the mailing list going and didn't want to spend a lot of time investigating. It's also not immediately clear to me how payload could end up as None there... from reading the code in email.Message maybe part._payload was None due to an earlier problem. I'll attach a workaround patch... the if: also covers the call to save_attachment() since that also tracebacked when I just fixed the call to len(). Anyways, filing in case it makes sense to someone more familiar with the guts of email.Message. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-05-22 16:19 Message: Logged In: YES user_id=12800 I figured this one out and the patch should be in 2.1.6 final. Under email 2.5, it is possible to get a message with a None payload. len(None) will produce the above error. I believe it is safe to ignore such parts and that is the fix I've checked into CVS. Note that under email 3 (which Mailman can't use until Python 2.3 is a minimum requirement), you won't get those None payloads. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-11 23:11 Message: Logged In: YES user_id=67709 I believe I fixed this bug. it will appear in public CVS soon. ---------------------------------------------------------------------- Comment By: Owen Taylor (otaylor) Date: 2005-01-11 21:59 Message: Logged In: YES user_id=63124 Sorry about that ... that's what happens when you work on multiple computers and call patches things like 'diff'. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-11 21:34 Message: Logged In: YES user_id=67709 Well, the patch looks like for different project?? ---------------------------------------------------------------------- Comment By: Owen Taylor (otaylor) Date: 2005-01-09 18:15 Message: Logged In: YES user_id=63124 Oh, forgot to add say, this is python-2.2.3 and mailman-2.1.5. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1099138&group_id=103 From noreply at sourceforge.net Wed May 25 21:16:47 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 25 May 2005 12:16:47 -0700 Subject: [ mailman-Patches-1208685 ] mailmanctl report status Message-ID: Patches item #1208685, was opened at 2005-05-25 15:16 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=1208685&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: John Dennis (jdennis-redhat) Assigned to: Nobody/Anonymous (nobody) Summary: mailmanctl report status Initial Comment: Mark's point about the presence of the pid and lock files not being a definitive metric of mailman health should not be ignored. You really have to ascertain the status of the process. If mailman is abnormally aborting, which is what started this thread, then there is a high degree of probably the lock files will be left behind and testing them will give false positives. In the Red Hat mailman RPM's we've modified mailmanctl so that it can be asked the status of the mailman process as an unprivledged user and return the result as status to the shell as well as printing a message. Since mailmanctl knows how to locate the process and communicate with the process via signals it makes mailmanctl the optimal reporter of status. It was probably an oversight mailmanctl never had this facility. We have also integrated this with the mailman init.d script so that one can perform the standard "service mailman status" command. The init.d script depends on the exit status of "mailmanctl status". These two changes probably represent a more robust and standard way to determine status. Two files are patched in this patch, mailmanctl and mailman init.d script. Technically the init.d script does not need to be modified to take advantage of the mailmanctl status feature, but the two are really meant to play together. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1208685&group_id=103 From noreply at sourceforge.net Thu May 26 01:49:30 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 25 May 2005 16:49:30 -0700 Subject: [ mailman-Bugs-1208828 ] Message from InterScan Messaging Security Suite Message-ID: Bugs item #1208828, was opened at 2005-05-26 02: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=1208828&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: bounce detection Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sub Zero (subzero5) Assigned to: Nobody/Anonymous (nobody) Summary: Message from InterScan Messaging Security Suite Initial Comment: I get a bounce from InterScan Messaging Security Suite and the body of the returned message is like this (between the quotes) "****** Message from InterScan Messaging Security Suite ****** Sent <<< RCPT TO: Received >>> 550 5.1.1 ... user unknown Unable to deliver message to . ************************ End of message **********************" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1208828&group_id=103 From noreply at sourceforge.net Sat May 28 21:05:45 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 28 May 2005 12:05:45 -0700 Subject: [ mailman-Patches-1210507 ] Option to not respond to successful confirm command Message-ID: Patches item #1210507, was opened at 2005-05-28 12:05 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=1210507&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: Option to not respond to successful confirm command Initial Comment: Some people feel that the e-mail response to a successful e-mail confirm command is unnecessary and confusing. This patch to the 2.1.6rc4 base adds a mm_cfg.py option to control the sending of the e-mail reply to a successful confirm. The patch adds RESPOND_TO_SUCCESSFUL_CONFIRM = Yes to Defaults.py.in, and code to cmd_confirm.py to test this and not send the response in the case when it is a successful confirm and RESPOND_TO_SUCCESSFUL_CONFIRM has been set to No in mm_cfg.py. Note that if you apply the patch to an already configured existing installation, you need to patch Defaults.py instead of Defaults.py.in, but presumably you would only apply the patch if you were going to put RESPOND_TO_SUCCESSFUL_CONFIRM = No in mm_cfg.py anyway, so patching Defaults.py would not be mandatory in this case. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1210507&group_id=103 From noreply at sourceforge.net Sun May 29 00:04:17 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 28 May 2005 15:04:17 -0700 Subject: [ mailman-Patches-1210507 ] Option to not respond to successful confirm command Message-ID: Patches item #1210507, was opened at 2005-05-28 12:05 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1210507&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: Option to not respond to successful confirm command Initial Comment: Some people feel that the e-mail response to a successful e-mail confirm command is unnecessary and confusing. This patch to the 2.1.6rc4 base adds a mm_cfg.py option to control the sending of the e-mail reply to a successful confirm. The patch adds RESPOND_TO_SUCCESSFUL_CONFIRM = Yes to Defaults.py.in, and code to cmd_confirm.py to test this and not send the response in the case when it is a successful confirm and RESPOND_TO_SUCCESSFUL_CONFIRM has been set to No in mm_cfg.py. Note that if you apply the patch to an already configured existing installation, you need to patch Defaults.py instead of Defaults.py.in, but presumably you would only apply the patch if you were going to put RESPOND_TO_SUCCESSFUL_CONFIRM = No in mm_cfg.py anyway, so patching Defaults.py would not be mandatory in this case. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2005-05-28 15:04 Message: Logged In: YES user_id=1123998 Updated patch - structurally different but functionally the same ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1210507&group_id=103 From noreply at sourceforge.net Tue May 31 13:00:41 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 31 May 2005 04:00:41 -0700 Subject: [ mailman-Bugs-1211922 ] Incorrect config load 2.1.5 up to 2.1.6rc4 Message-ID: Bugs item #1211922, was opened at 2005-05-31 11: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=1211922&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Anton R. Ivanov (arivanov) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrect config load 2.1.5 up to 2.1.6rc4 Initial Comment: This is observed in debian 2.1.5 package and in 2.1.6rc4 installed from source: Custom header rules under Privacy Options/Spam filters are lost if the URL http://server/cgi-bin/mailman/admin/listname/privacy/spam is accessed directly without being authenticated in advance. How to reproduce: 1. Enter some rules 2. Logout/Login view them to see if they are still there 3. Logout 3. Try to access http://server/cgi-bin/mailman/admin/listname/privacy/spam directly. Mailman asks for a password and after that the rules are blank. 2.1.5 also loses them on a few more occasions when navigating around the web interface. In either case the custom antispam rules feature is unusable. For more information see debian bug 309870 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=309870 A. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1211922&group_id=103 From noreply at sourceforge.net Tue May 31 17:08:38 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 31 May 2005 08:08:38 -0700 Subject: [ mailman-Bugs-1212066 ] 2.1.6rc4 mailing list creation mail has no Date: header Message-ID: Bugs item #1212066, was opened at 2005-05-31 15:08 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=1212066&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Anton R. Ivanov (arivanov) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.6rc4 mailing list creation mail has no Date: header Initial Comment: This is cosmetic (mostly) The mail with a subject: Mailing list creation request for list LISTNAME is sent without a Date: header which makes Mozilla and other mail clients display it as sent on 1/01/1970 A. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1212066&group_id=103 From noreply at sourceforge.net Tue May 31 20:57:42 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 31 May 2005 11:57:42 -0700 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 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. 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: 2005-05-31 19:57 Message: Logged In: YES user_id=99923 Folks, Well, I've finally gotten around to releasing an update to this thing, after a phone conversation with the client who are using it, and I've incorporated a couple of cosmetic fixes, fairly substantial changes to make the bounce processing work properly (the ability to set people to NOMAIL now exists, and real world testing is commencing soon), and incorporated the flat vs. wide table archivecture types with various bugfixes. Main notes: * It would be a good idea to change all your delivery_status fields from VARCHAR(255) to INT(10) or similar, so that they will work properly, and not bomb out on this new version (they should be okay I think, but I'd advise the change). * The missing-'AND' typo has been rectified. Any suggestions and bugs should be sent to my sourceforge account address, which ends up in the right place. K. ---------------------------------------------------------------------- Comment By: Gergely EGERVARY (egervary) Date: 2005-04-09 11:14 Message: Logged In: YES user_id=1255996 Thank you for your good work. FYI: there's a missing "AND" in MysqlMemberships.py in line 494. ---------------------------------------------------------------------- Comment By: simboforge (simboforge) Date: 2005-03-11 23:22 Message: Logged In: YES user_id=1226150 excellent. can you please give me a list of the files modified from the original distro? grep sees six that grep have msyql in them. thx ---------------------------------------------------------------------- Comment By: Kev Green (kyrian) Date: 2005-03-11 22:56 Message: Logged In: YES user_id=99923 The flat file databases are unused when you put the MySQL adaptor in place, and they are untouched (and indeed not deleted) by it, the MySQL adaptor only queries the MySQL tables for membership information, without trying to force you into using it fulltime by deleting anything, etc. Once you unconfigure the MySQL adaptor, Mailman should revert back to your existing flat file databases. Of course, I could have missed something, etc. so do back up your flat file databases before installing the MySQL adaptor, and then you can just migrate back to them by restoring the backups. Either way, you have come up with a good question for an FAQ on the SQL adaptor :-) K. ---------------------------------------------------------------------- Comment By: simboforge (simboforge) Date: 2005-03-11 22:42 Message: Logged In: YES user_id=1226150 neat. just what i was looking for. i have a couple of live lists running on version version 2.1.5. i am a bit leary about unzipping this distrobution over the top of my working mailman as i am not sure how to backup the existing flat file databases. i would prefer to experiment with dropping the adapter into my existing installation. any pointers as to where to start? thx ---------------------------------------------------------------------- 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