Mailman 3 September 2002 - Mailman-Developers

[ mailman-Bugs-596361 ] rejection-notice not translated
by noreply＠sourceforge.net 13 Sep '02

13 Sep '02

Bugs item #596361, was opened at 2002-08-17 02:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=596361&group_i… Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: rejection-notice not translated Initial Comment: on the admindb screen, detailed description of the held messages include 'rejection-notice' field to be sent to the message sender but the default value in the text form is in english and not translated into the list-preferred language. Following short patch may work: --- admindb.py.orig Fri Aug 16 11:39:53 2002 +++ admindb.py Sat Aug 17 14:57:37 2002 @@ -595,8 +595,8 @@ t.AddRow([ Bold(_('If you reject this post,<br>please explain (optional):')), TextArea('comment-%d' % id, rows=4, cols=80, - text = Utils.wrap(msgdata.get('rejection-notice', - _('[No explanation given]')), + text = Utils.wrap(_(msgdata.get('rejection-notice', + _('[No explanation given]'))), column=80)) ]) row, col = t.GetCurrentRowIndex(), t.GetCurrentCellIndex() ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 15:46 Message: Logged In: YES user_id=12800 Thanks. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-08-23 20:17 Message: Logged In: YES user_id=67709 Sorry for the inconvenience. I uplaod a diff file. There is some clutter in creating mailman.pot, so I revised the patch. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 17:16 Message: Logged In: YES user_id=12800 In general it's better to attach patches instead of pasting them in. SF doesn't preserve whitespace :( Updating this one so SF will send me the whitespace preserved patch in an email notification. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=596361&group_i…

1 0

[ mailman-Bugs-601082 ] personalized recip should be MIMEed
by noreply＠sourceforge.net 13 Sep '02

13 Sep '02

Bugs item #601082, was opened at 2002-08-28 03:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=601082&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: personalized recip should be MIMEed Initial Comment: If the list delivery is personalized, user's name is placed in To: header. When the user choose to register non-ascii character in the name, To: header contain non-ascii and breaks RFC(number?Idontknow). A quick and dirty patch is included. I hope Barry can inspect and revise it. ---------------------------------------------------------------------- >Comment By: Simone Piunno (pioppo) Date: 2002-09-13 21:24 Message: Logged In: YES user_id=227443 If the address is coming from a web browser I believe you should be able to guess the encoding from the HTTP headers (at least for POST). If the address is coming from the command line you could try to check KBCHARSET or you could just add an optional parameter (the list admin shouldn't be so clueless) If the address is coming from an email you could allow non-ASCII only if properly encoded (so that you can deduce the encoding from the email) In any case you should store the encoding valuesomewhere in the list database file, for later use. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 21:08 Message: Logged In: YES user_id=12800 Ouch, this is a tougher problem because you don't really know what character set the name is in. It may not be the charset for the user's preferred language at all. I can see three approaches. First, you should never have funny characters in the real name component (use the encoded name instead). Second, there could be a a second entry box under the name asking for the charset of the name. It would default to us-ascii (or maybe just empty). I fear however that most people will be entirely clueless as to what the proper value would be. Third, if there are non-ascii characters in the name, I think we could just encode with utf-8 and be done with it -- you can't really guess much more about the proper encoding. I'm not sure the latter will work or will even be cross platform. Ideas? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=601082&group_i…

1 0

[ mailman-Bugs-598010 ] Bad Pickle?
by noreply＠sourceforge.net 13 Sep '02

13 Sep '02

Bugs item #598010, was opened at 2002-08-20 19:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=598010&group_i… Category: None Group: 2.1 beta >Status: Pending Resolution: None Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: Bad Pickle? Initial Comment: Some days ago my server startet forgetting some imcoming mails to some special lists. SInce then I receive the followin error-notes on my Server. Could somebody explain me what`s going on very fast? Some of my important mailinglists aren`t usable any more. File "/usr/lib/mailman/bin/qrunner", line 266, in ? main() File "/usr/lib/mailman/bin/qrunner", line 226, in main qrunner.run() File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 154, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 129, in _dispose status = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 152, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Handlers/Moderate.py", line 101, in process Hold.hold_for_approval(mlist, msg, msgdata, Hold.ModeratedPost) File "/usr/lib/mailman/Mailman/Handlers/Hold.py", line 219, in hold_for_approval cookie = Pending.new(Pending.HELD_MESSAGE, id) File "/usr/lib/mailman/Mailman/Pending.py", line 64, in new db = _load() File "/usr/lib/mailman/Mailman/Pending.py", line 121, in _load return cPickle.load(fp) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 15:17 Message: Logged In: YES user_id=12800 Moving status to pending since I haven't heard any followup from the submitter. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-22 15:17 Message: Logged In: YES user_id=12800 It looks like the file containing your pending actions got corrupted. Possibly you had a disk corruption, or out of space problem, or something similar. If you have a data/pending.pck.tmp file, move that to data/pending.pck. Otherwise you'll have to simply remove the data/pending.pck file, but if you do that you'll lose all your pending subscriptions and held messages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=598010&group_i…

1 0

[ mailman-Bugs-601082 ] personalized recip should be MIMEed
by noreply＠sourceforge.net 13 Sep '02

13 Sep '02

Bugs item #601082, was opened at 2002-08-27 21:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=601082&group_i… Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: personalized recip should be MIMEed Initial Comment: If the list delivery is personalized, user's name is placed in To: header. When the user choose to register non-ascii character in the name, To: header contain non-ascii and breaks RFC(number?Idontknow). A quick and dirty patch is included. I hope Barry can inspect and revise it. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 15:08 Message: Logged In: YES user_id=12800 Ouch, this is a tougher problem because you don't really know what character set the name is in. It may not be the charset for the user's preferred language at all. I can see three approaches. First, you should never have funny characters in the real name component (use the encoded name instead). Second, there could be a a second entry box under the name asking for the charset of the name. It would default to us-ascii (or maybe just empty). I fear however that most people will be entirely clueless as to what the proper value would be. Third, if there are non-ascii characters in the name, I think we could just encode with utf-8 and be done with it -- you can't really guess much more about the proper encoding. I'm not sure the latter will work or will even be cross platform. Ideas? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=601082&group_i…

1 0

[ mailman-Bugs-602077 ] make install fails with import error
by noreply＠sourceforge.net 13 Sep '02

13 Sep '02

Bugs item #602077, was opened at 2002-08-29 16:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=602077&group_i… Category: configuring/installing Group: 2.1 beta >Status: Pending Resolution: None Priority: 5 Submitted By: Goeran Zaengerlein (timetrack) Assigned to: Nobody/Anonymous (nobody) Summary: make install fails with import error Initial Comment: I tried to install Mailman 2.1b3 and I followed the installation instruction exactly but make install fails with the following message: --- snip --- Compiling /usr/local/mailman/Mailman/versions.py ... Traceback (most recent call last): File "bin/update", line 44, in ? import paths ImportError: No module named paths make: *** [update] Error 1 --- snap --- SuSE 7.2 Python 2.2.1 gcc 2.95.3 The problem was already described here: http://mail.python.org/pipermail/mailman-users/2002- July/020991.html but no solution has been posted as far as I could see... Any idea what I did wrong? ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 14:41 Message: Logged In: YES user_id=12800 Moving to pending status, since I think this is the problem, but haven't heard an update from the submitter. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-05 02:22 Message: Logged In: YES user_id=12800 Did you install Python via RPM? If so, be sure you have the python-devel package installed. I don't know why this is, but I've seen reports of this problem when folks only have the python package installed. Installing the python-devel or installing Python from source seems to solve this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=602077&group_i…

1 0

[ mailman-Bugs-605263 ] Bad var in ListAdmin._UpdateRecords()
by noreply＠sourceforge.net 13 Sep '02

13 Sep '02

Bugs item #605263, was opened at 2002-09-05 17:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605263&group_i… Category: configuring/installing Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Les Niles (lniles) Assigned to: Nobody/Anonymous (nobody) Summary: Bad var in ListAdmin._UpdateRecords() Initial Comment: ListAdmin._UpdateRecords() (in the CVS head, and as far as I can tell all the way back to its inception) refers to "mlist", which raises a NameError when updating some lists. Syntactically it would seem that this should be "self" instead, and experimentally that solves the problem. Here's the patch: *** ListAdmin.py.~1~ Wed Sep 4 23:25:26 2002 --- ListAdmin.py Thu Sep 5 00:38:24 2002 *************** *** 539,545 **** # pre-2.1a2 compatibility when, addr, passwd, digest = info fullname = '' ! lang = mlist.preferred_language elif len(info) == 5: # pre-2.1a4 compatibility when, addr, passwd, digest, lang = info --- 539,545 ---- # pre-2.1a2 compatibility when, addr, passwd, digest = info fullname = '' ! lang = self.preferred_language elif len(info) == 5: # pre-2.1a4 compatibility when, addr, passwd, digest, lang = info ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 14:40 Message: Logged In: YES user_id=12800 Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605263&group_i…

1 0

[ mailman-Bugs-605557 ] language support
by noreply＠sourceforge.net 13 Sep '02

13 Sep '02

Bugs item #605557, was opened at 2002-09-06 09:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605557&group_i… Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Emilio Delgado (popemiko) Assigned to: Nobody/Anonymous (nobody) Summary: language support Initial Comment: Bug in Mailman version 2.1b3 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 "/var/lib/mailman/scripts/driver", line 82, in run_main main() File "/var/lib/mailman/Mailman/Cgi/create.py", line 60, in main request_creation(doc) File "/var/lib/mailman/Mailman/Cgi/create.py", line 376, in request_creation [_(Utils.GetLanguageDescr(L)) for L in langs], File "/var/lib/mailman/Mailman/Utils.py", line 599, in GetLanguageDescr return mm_cfg.LC_DESCRIPTIONS[lang][0] KeyError: admlogin_files Python information: Variable Value sys.version 2.2 (#1, Feb 24 2002, 16:21:58) [GCC 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux-i386 Environment variables: Variable Value HTTP_REFERER http://192.168.1.15/mailman/admin SERVER_SOFTWARE Apache-AdvancedExtranetServer/1.3.23 (Mandrake Linux/4.1mdk) mod_ssl/2.8.7 OpenSSL/0.9.6c PHP/4.1.2 PYTHONPATH /var/lib/mailman SCRIPT_FILENAME /var/lib/mailman/cgi-bin/create SERVER_ADMIN root@localhost SCRIPT_NAME /mailman/create SCRIPT_URI http://infor.unibertsitatea.net/mailman/create SERVER_SIGNATURE Apache-AdvancedExtranetServer/1.3.23 Server at infor.unibertsitatea.net Port 80 REQUEST_METHOD GET HTTP_HOST 192.168.1.15 SCRIPT_URL /mailman/create SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/create 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,text/css,*/*;q=0.1 HTTP_ACCEPT_CHARSET ISO-8859-1, utf-8;q=0.66, *;q=0.66 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204 HTTP_CONNECTION keep-alive SERVER_NAME infor.unibertsitatea.net REMOTE_ADDR 192.168.1.15 REMOTE_PORT 1281 HTTP_ACCEPT_LANGUAGE en-us SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 DOCUMENT_ROOT /var/www/html HTTP_ACCEPT_ENCODING gzip, deflate, compress;q=0.9 SERVER_ADDR 192.168.1.15 HTTP_KEEP_ALIVE 300 ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 14:38 Message: Logged In: YES user_id=12800 Did you perhaps drop a file called admlogin_files in your $prefix/templates directory? That directory should only contain subdirs for the language templates. I'll check in a change that will make Mailman less vulnerable to these problems. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605557&group_i…

1 0

[ mailman-Bugs-608789 ] Stripped port info from List-Archive URL
by noreply＠sourceforge.net 13 Sep '02

13 Sep '02

Bugs item #608789, was opened at 2002-09-13 07:36 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608789&group_i… Category: mail delivery Group: 2.1 beta Status: Closed Resolution: Works For Me Priority: 5 Submitted By: Eugene Eric Kim (eekim) Assigned to: Nobody/Anonymous (nobody) Summary: Stripped port info from List-Archive URL Initial Comment: I'm running Mailman 2.1b3 on a host with Apache running on port 2000. In mm_cfg.py, I have: DEFAULT_URL_PATTERN = 'http://%s:2000/mailman/' PUBLIC_ARCHIVE_URL = 'http://%(hostname)s:2000/pipermail/%(listname)s' This works fine for HTML pages generated by the CGI scripts, as well as for the URLs sent out in the bodies of confirmation e-mails. However, the URLs contained in List-Archive headers in e-mails sent to lists do not have port 2000 in them. ---------------------------------------------------------------------- >Comment By: Eugene Eric Kim (eekim) Date: 2002-09-13 18:22 Message: Logged In: YES user_id=39362 Thanks! That corrected the problem. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 18:16 Message: Logged In: YES user_id=12800 Whenever you make a change to the mm_cfg.py file, you have to be sure to do a restart or your changes won't get picked up. Make the change, then do "mailmanctl restart". It worked for me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608789&group_i…

1 0

[ mailman-Bugs-608789 ] Stripped port info from List-Archive URL
by noreply＠sourceforge.net 13 Sep '02

13 Sep '02

Bugs item #608789, was opened at 2002-09-13 03:36 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608789&group_i… Category: mail delivery Group: 2.1 beta >Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: Eugene Eric Kim (eekim) Assigned to: Nobody/Anonymous (nobody) Summary: Stripped port info from List-Archive URL Initial Comment: I'm running Mailman 2.1b3 on a host with Apache running on port 2000. In mm_cfg.py, I have: DEFAULT_URL_PATTERN = 'http://%s:2000/mailman/' PUBLIC_ARCHIVE_URL = 'http://%(hostname)s:2000/pipermail/%(listname)s' This works fine for HTML pages generated by the CGI scripts, as well as for the URLs sent out in the bodies of confirmation e-mails. However, the URLs contained in List-Archive headers in e-mails sent to lists do not have port 2000 in them. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 14:16 Message: Logged In: YES user_id=12800 Whenever you make a change to the mm_cfg.py file, you have to be sure to do a restart or your changes won't get picked up. Make the change, then do "mailmanctl restart". It worked for me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608789&group_i…

1 0

[ mailman-Bugs-605933 ] subscribe by invite dies on dup user
by noreply＠sourceforge.net 13 Sep '02

13 Sep '02

Bugs item #605933, was opened at 2002-09-07 03:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605933&group_i… Category: (un)subscribing Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ron Jarrell (jarrell) Assigned to: Nobody/Anonymous (nobody) Summary: subscribe by invite dies on dup user Initial Comment: Playing with the "invite" feature, I invited myself, knowing I was already on the list. If you reply by email, it properly bounces back a "you're already subscribed" error. Click the web link, however, and fill out the form (which, btw mistakenly said that the moderater had to approve it on an open list; I don't remember if that's hardcoded or dynamic, but I *thought* it was dynamic) and when you submit it you get a traceback... the cgi-form really ought to catch this condition gracefully... Traceback (most recent call last): File "/home/mailman/scripts/driver", line 82, in run_main main() File "/home/mailman/Mailman/Cgi/confirm.py", line 110, in main subscription_confirm(mlist, doc, cookie, cgidata) File "/home/mailman/Mailman/Cgi/confirm.py", line 314, in subscription_confirm op, addr, pw, digest, lang = mlist.ProcessConfirmation( File "/home/mailman/Mailman/MailList.py", line 1072, in ProcessConfirmation self.ApprovedAddMember(userdesc) File "/home/mailman/Mailman/MailList.py", line 858, in ApprovedAddMember raise Errors.MMAlreadyAMember, email MMAlreadyAMember: jarrell(a)vt.edu ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-09-13 12:51 Message: Logged In: YES user_id=12800 There's another bug you didn't mention <wink>. The invite page should not allow you to invite a member. I'm fixing all three bugs now, thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=605933&group_i…

1 0