Patches item #1842412, was opened at 2007-12-01 10:49
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1842412&group_…
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: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Thijs Kinkhorst (kink)
Assigned to: Nobody/Anonymous (nobody)
Summary: Inconsistent case sensitivity w.r.t. listname
Initial Comment:
Hi!
Mailman's command line tools are not consistent in how they handle the case of list names, as shown in this Debian bug:
http://bugs.debian.org/446257
This is a bit problematic as list_lists does report them in mixed case.
The attached patch should make all command line tools do a case-normalisation before processing.
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-12-04 11:41
Message:
Logged In: YES
user_id=1123998
Originator: NO
The attached patch - lower.patch.txt - fixes this issue and will be
included in Mailman 2.1.10. It is somewhat different from the original
patch but accomplishes the same result.
File Added: lower.patch.txt
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1842412&group_…
Patches item #1843966, was opened at 2007-12-04 02:17
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1843966&group_…
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: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: Thijs Kinkhorst (kink)
Assigned to: Nobody/Anonymous (nobody)
Summary: newlist does not pass emailhost upon creation
Initial Comment:
Hi!
newlist does not pass emailhost to Create(), while that does support passing it, and actually uses it when passed too. In mlist.Create(), if emailhost==None, then it's
set to mm_cfg.DEFAULT_EMAIL_HOST which was probably not the intention of the list creator.
Attached patch fixes this issue. Please apply it, thanks!
Thijs
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-12-04 10:59
Message:
Logged In: YES
user_id=1123998
Originator: NO
It is true that newlist does not pass the email host name (actually
host_name, not emailhost at this point in the code) to Create(), but
immediately following a successful mlist.Create(), it does:
# Assign domain-specific attributes
mlist.host_name = host_name
mlist.web_page_url = web_page_url
To set the list's host_name attribute.
The only thing Create() uses emailhost for is to append it to the listname
to make 'listname@emailhost' in order to determine that this is a valid
email address, but the intent of this is to validate the listname, not the
emailhost. Create() does not set any list attribute from emailhost.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1843966&group_…
Patches item #1843966, was opened at 2007-12-04 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=300103&aid=1843966&group_…
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
Private: No
Submitted By: Thijs Kinkhorst (kink)
Assigned to: Nobody/Anonymous (nobody)
Summary: newlist does not pass emailhost upon creation
Initial Comment:
Hi!
newlist does not pass emailhost to Create(), while that does support passing it, and actually uses it when passed too. In mlist.Create(), if emailhost==None, then it's
set to mm_cfg.DEFAULT_EMAIL_HOST which was probably not the intention of the list creator.
Attached patch fixes this issue. Please apply it, thanks!
Thijs
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1843966&group_…
Bugs item #1072002, was opened at 2004-11-23 10:38
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072002&group_…
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: Web/CGI
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Mark Sapiro (msapiro)
Assigned to: Nobody/Anonymous (nobody)
Summary: admin_member_chunksize not available in GUI or config_list
Initial Comment:
admin_member_chunksize is set from
DEFAULT_ADMIN_MEMBER_CHUNKSIZE when a list is created,
but it is not visible in the admin GUI or bin/config_list.
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-12-03 16:43
Message:
Logged In: YES
user_id=1123998
Originator: YES
Fixed in Mailman 2.1.10.
----------------------------------------------------------------------
Comment By: Jon Howell (jonhowell)
Date: 2005-03-21 13:37
Message:
Logged In: YES
user_id=70921
"Me too."
Please add this line after the 'max_message_size' entry in
Gui/General.py:
('admin_member_chunksize', mm_cfg.Number, 7, 0,
_('''Number of members to display at a time.''')),
I was going nuts being forced to look at my membership list
in 26 steps, one bucket at a time. I finally bothered today
to find the problem, and fixing this bug would fix the
problem. Although it would be nice if the membership list
page also had a "show entire list" button, so the next guy
doesn't have to scrape the source to find this option. :v)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072002&group_…
Feature Requests item #782436, was opened at 2003-08-03 12:32
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782436&group_i…
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: Open
Resolution: None
Priority: 5
Private: No
Submitted By: JC Dill (jcdill)
Assigned to: Nobody/Anonymous (nobody)
Summary: members per page on admin page
Initial Comment:
Put a radio button option on the membership page to
allow list owners to change the number of members
returned on each page. I suggest that the options include:
25 per page
50 per page
100 per page
200 per page
500 per page
all subscribers on one page (use with caution if you
have a big list!)
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-12-03 16:41
Message:
Logged In: YES
user_id=1123998
Originator: NO
This has been partially addressed for Mailman 2.1.10 by adding
admin_member_chunksize to the General Options Gui page.
----------------------------------------------------------------------
Comment By: oemardarmaji (umardarmaji)
Date: 2007-04-18 00:19
Message:
Logged In: YES
user_id=1772313
Originator: NO
Test
----------------------------------------------------------------------
Comment By: John W. Baxter (jwbaxter)
Date: 2006-06-11 10:55
Message:
Logged In: YES
user_id=664644
This seems like a quite reasonable proposal.
Is the intent to return to the old method, where the pages (except last)
were all
full and there was on each page an index of links giving the first (first
and last)
address on each other page?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782436&group_i…
Bugs item #1834281, was opened at 2007-11-19 00:19
Message generated for change (Settings changed) made by tkikuchi
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834281&group_…
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: Pipermail
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong mailto subject/in-reply-to link in the article page
Initial Comment:
The Archived article page give an oppotunity to reply or to send comments with the mailto link on the poster (or the list address) with the subject and in-reply-to attributes set. But, the subject should have the 'Re:' prefix like the other messages from the user's MUA, and 'In-Reply-To' should be the message-id of the article not the in-reply-to header value of it.
The patch is attached.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834281&group_…
Bugs item #1842567, was opened at 2007-12-02 07:20
Message generated for change (Comment added) made by tkikuchi
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1842567&group_…
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: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Brad Knowles (shub)
Assigned to: Nobody/Anonymous (nobody)
Summary: LookupError: unknown encoding: iso-2022-jp
Initial Comment:
We're not sending out the monthly password notices, because the cron/Python job to do that keeps dying with the following error (sensitive information omitted):
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/usr/local/mailman>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=mailman>
Date: Sat, 1 Dec 2007 05:01:06 +0100 (CET)
Traceback (most recent call last):
File "/usr/local/mailman/cron/mailpasswds", line 241, in <module>
main()
File "/usr/local/mailman/cron/mailpasswds", line 223, in main
text.encode(enc, 'replace'), poplang)
File "/usr/local/mailman/Mailman/Message.py", line 213, in __init__
self.set_payload(text, charset)
File "/usr/local/mailman/pythonlib/email/Message.py", line 246, in set_payload
self.set_charset(charset)
File "/usr/local/mailman/pythonlib/email/Message.py", line 282, in set_charset
self._payload = charset.body_encode(self._payload)
File "/usr/local/mailman/pythonlib/email/Charset.py", line 399, in body_encode
s = self.convert(s)
File "/usr/local/mailman/pythonlib/email/Charset.py", line 282, in convert
return unicode(s, self.input_codec).encode(self.output_codec)
LookupError: unknown encoding: iso-2022-jp
----------------------------------------------------------------------
>Comment By: Tokio Kikuchi (tkikuchi)
Date: 2007-12-02 07:48
Message:
Logged In: YES
user_id=67709
Originator: NO
What is the python version. The JapaneseCodecs package which is included
in mailman 2.1.9 is incompatible with python2.5. Python 2.4 and later
includes CJK codecs and can be used instead. Mailman 2.1.10 fixes this in
misc/paths.py.in.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1842567&group_…
Bugs item #1842567, was opened at 2007-12-02 07:20
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1842567&group_…
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: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Brad Knowles (shub)
Assigned to: Nobody/Anonymous (nobody)
Summary: LookupError: unknown encoding: iso-2022-jp
Initial Comment:
We're not sending out the monthly password notices, because the cron/Python job to do that keeps dying with the following error (sensitive information omitted):
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/usr/local/mailman>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=mailman>
Date: Sat, 1 Dec 2007 05:01:06 +0100 (CET)
Traceback (most recent call last):
File "/usr/local/mailman/cron/mailpasswds", line 241, in <module>
main()
File "/usr/local/mailman/cron/mailpasswds", line 223, in main
text.encode(enc, 'replace'), poplang)
File "/usr/local/mailman/Mailman/Message.py", line 213, in __init__
self.set_payload(text, charset)
File "/usr/local/mailman/pythonlib/email/Message.py", line 246, in set_payload
self.set_charset(charset)
File "/usr/local/mailman/pythonlib/email/Message.py", line 282, in set_charset
self._payload = charset.body_encode(self._payload)
File "/usr/local/mailman/pythonlib/email/Charset.py", line 399, in body_encode
s = self.convert(s)
File "/usr/local/mailman/pythonlib/email/Charset.py", line 282, in convert
return unicode(s, self.input_codec).encode(self.output_codec)
LookupError: unknown encoding: iso-2022-jp
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1842567&group_…
Patches item #1842412, was opened at 2007-12-01 19:49
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=1842412&group_…
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
Private: No
Submitted By: Thijs Kinkhorst (kink)
Assigned to: Nobody/Anonymous (nobody)
Summary: Inconsistent case sensitivity w.r.t. listname
Initial Comment:
Hi!
Mailman's command line tools are not consistent in how they handle the case of list names, as shown in this Debian bug:
http://bugs.debian.org/446257
This is a bit problematic as list_lists does report them in mixed case.
The attached patch should make all command line tools do a case-normalisation before processing.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1842412&group_…