From noreply at sourceforge.net  Sat Dec  1 19:49:00 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 01 Dec 2007 10:49:00 -0800
Subject: [ mailman-Patches-1842412 ] Inconsistent case sensitivity w.r.t.
	listname
Message-ID: <E1IyXOe-0002W4-US@sc8-sf-web21.sourceforge.net>

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_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
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_id=103

From noreply at sourceforge.net  Sun Dec  2 08:20:36 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 01 Dec 2007 23:20:36 -0800
Subject: [ mailman-Bugs-1842567 ] LookupError: unknown encoding: iso-2022-jp
Message-ID: <E1Iyj80-0000eN-AU@sc8-sf-web21.sourceforge.net>

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_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: 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_id=103

From noreply at sourceforge.net  Sun Dec  2 08:48:15 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 01 Dec 2007 23:48:15 -0800
Subject: [ mailman-Bugs-1842567 ] LookupError: unknown encoding: iso-2022-jp
Message-ID: <E1IyjYl-0003EI-Rv@sc8-sf-web23.sourceforge.net>

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_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: 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_id=103

From noreply at sourceforge.net  Sun Dec  2 11:54:45 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 02 Dec 2007 02:54:45 -0800
Subject: [ mailman-Bugs-1834281 ] Wrong mailto subject/in-reply-to link in the
	article page
Message-ID: <E1IymTF-0002nD-CW@sc8-sf-web21.sourceforge.net>

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_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: 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_id=103

From noreply at sourceforge.net  Tue Dec  4 01:41:51 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 03 Dec 2007 16:41:51 -0800
Subject: [ mailman-Feature Requests-782436 ] members per page on admin page
Message-ID: <E1IzLrD-0004Sg-Em@sc8-sf-web22.sourceforge.net>

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_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: 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_id=103

From noreply at sourceforge.net  Tue Dec  4 01:43:09 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 03 Dec 2007 16:43:09 -0800
Subject: [ mailman-Bugs-1072002 ] admin_member_chunksize not available in GUI
	or config_list
Message-ID: <E1IzLsT-00069L-0S@sc8-sf-web24.sourceforge.net>

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_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: 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_id=103

From noreply at sourceforge.net  Tue Dec  4 11:17:52 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 04 Dec 2007 02:17:52 -0800
Subject: [ mailman-Patches-1843966 ] newlist does not pass emailhost upon
	creation
Message-ID: <E1IzUqe-0000Ze-SH@sc8-sf-web24.sourceforge.net>

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_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
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_id=103

From noreply at sourceforge.net  Tue Dec  4 19:59:30 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 04 Dec 2007 10:59:30 -0800
Subject: [ mailman-Patches-1843966 ] newlist does not pass emailhost upon
	creation
Message-ID: <E1IzczS-0005nN-Sq@sc8-sf-web24.sourceforge.net>

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_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: 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 at 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_id=103

From noreply at sourceforge.net  Tue Dec  4 20:41:00 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 04 Dec 2007 11:41:00 -0800
Subject: [ mailman-Patches-1842412 ] Inconsistent case sensitivity w.r.t.
	listname
Message-ID: <E1Izddc-0003xx-C7@sc8-sf-web23.sourceforge.net>

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_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: 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_id=103

From noreply at sourceforge.net  Tue Dec  4 21:55:41 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 04 Dec 2007 12:55:41 -0800
Subject: [ mailman-Patches-1842412 ] Inconsistent case sensitivity w.r.t.
	listname
Message-ID: <E1Izent-0003pq-5P@sc8-sf-web23.sourceforge.net>

Patches item #1842412, was opened at 2007-12-01 19:49
Message generated for change (Comment added) made by kink
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1842412&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: 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: Thijs Kinkhorst (kink)
Date: 2007-12-04 21:55

Message:
Logged In: YES 
user_id=285765
Originator: YES

Thanks! Any idea on about when to expect such a 2.1.10 release?

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2007-12-04 20: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_id=103

From noreply at sourceforge.net  Tue Dec  4 22:15:23 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 04 Dec 2007 13:15:23 -0800
Subject: [ mailman-Patches-1842412 ] Inconsistent case sensitivity w.r.t.
	listname
Message-ID: <E1Izf6x-0000u1-Vz@sc8-sf-web21.sourceforge.net>

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_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: 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 13:15

Message:
Logged In: YES 
user_id=1123998
Originator: NO

2.1.10b1 will be released as soon as a few packaging glitches related to
our move from Subversion to Bazaar are worked out. Should be later this
week if not today.

----------------------------------------------------------------------

Comment By: Thijs Kinkhorst (kink)
Date: 2007-12-04 12:55

Message:
Logged In: YES 
user_id=285765
Originator: YES

Thanks! Any idea on about when to expect such a 2.1.10 release?

----------------------------------------------------------------------

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_id=103

From noreply at sourceforge.net  Thu Dec  6 13:11:06 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 06 Dec 2007 04:11:06 -0800
Subject: [ mailman-Bugs-1845459 ] cron/checkdbs produces traceback
Message-ID: <E1J0FZK-0008Ez-S3@sc8-sf-web22.sourceforge.net>

Bugs item #1845459, was opened at 2007-12-06 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=1845459&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: Open
Resolution: None
Priority: 5
Private: No
Submitted By: gjmurphy (gjmurphy)
Assigned to: Nobody/Anonymous (nobody)
Summary: cron/checkdbs produces traceback

Initial Comment:
The following is produced when checkdb expires held messages AND the list preferred language is 'fr'. Patch which fixes this is attached.

--start--
Traceback (most recent call last):
  File "/usr/local/mailman/cron/checkdbs", line 203, in ?
    main()
  File "/usr/local/mailman/cron/checkdbs", line 107, in main
    text = _(
  File "/usr/local/mailman/Mailman/i18n.py", line 90, in _
    return tns % dict
ValueError: unsupported format character 'a' (0x61) at index 34
--end--

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1845459&group_id=103

From noreply at sourceforge.net  Wed Dec 19 00:42:32 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 18 Dec 2007 15:42:32 -0800
Subject: [ mailman-Feature Requests-1853576 ] Membership List for Web Interface
Message-ID: <E1J4m52-0002wh-9M@sc8-sf-web21.sourceforge.net>

Feature Requests item #1853576, was opened at 2007-12-19 07:42
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=1853576&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: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Lev Lafayette (lev_lafayette)
Assigned to: Nobody/Anonymous (nobody)
Summary: Membership List for Web Interface

Initial Comment:

The Membership Management page in the web interface could be improved if it offered a text export of members, rather than having to rely on a 'screen scrape' or access to the command line to achieve the same.

I am thinking of a feature similar to the Yahoo! groups option which provides an output on a webpage of list members in plain-text and sorted alphabetically from members-download.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1853576&group_id=103

From noreply at sourceforge.net  Wed Dec 19 04:20:07 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 18 Dec 2007 19:20:07 -0800
Subject: [ mailman-Patches-1843966 ] newlist does not pass emailhost upon
	creation
Message-ID: <E1J4pTb-0003IN-Jd@sc8-sf-glue1.sourceforge.net>

Patches item #1843966, was opened at 2007-12-04 02:17
Message generated for change (Comment added) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1843966&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: Closed
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: SourceForge Robot (sf-robot)
Date: 2007-12-18 19:20

Message:
Logged In: YES 
user_id=1312539
Originator: NO

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

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 at 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_id=103

From noreply at sourceforge.net  Wed Dec 19 20:14:34 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 19 Dec 2007 11:14:34 -0800
Subject: [ mailman-Feature Requests-1853576 ] Membership List for Web Interface
Message-ID: <E1J54NG-0002YC-HO@sc8-sf-web22.sourceforge.net>

Feature Requests item #1853576, was opened at 2007-12-18 15:42
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1853576&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: Open
>Resolution: Duplicate
Priority: 5
Private: No
Submitted By: Lev Lafayette (lev_lafayette)
Assigned to: Nobody/Anonymous (nobody)
Summary: Membership List for Web Interface

Initial Comment:

The Membership Management page in the web interface could be improved if it offered a text export of members, rather than having to rely on a 'screen scrape' or access to the command line to achieve the same.

I am thinking of a feature similar to the Yahoo! groups option which provides an output on a webpage of list members in plain-text and sorted alphabetically from members-download.

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2007-12-19 11:14

Message:
Logged In: YES 
user_id=1123998
Originator: NO

This is a duplicate of 1574060.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1853576&group_id=103

From noreply at sourceforge.net  Thu Dec 27 07:35:52 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Wed, 26 Dec 2007 22:35:52 -0800
Subject: [ mailman-Patches-1858815 ] [PATCH] Focus first textbox at the admin
	login page
Message-ID: <E1J7mLQ-0007sr-Ia@sc8-sf-web23.sourceforge.net>

Patches item #1858815, was opened at 2007-12-27 09:35
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=1858815&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: Web UI
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: --- (konvpalto)
Assigned to: Nobody/Anonymous (nobody)
Summary: [PATCH] Focus first textbox at the admin login page

Initial Comment:
The default administrator login page (when one is not currently logged in) contains only one textfield -- administrator password.  And almost for sure user will want to enter the password there.  So Web UI can provide some help to the user by focusing the textfield, so user will not need to do extra mouse click or to move focus with keyboard.  This makes administrator logins faster and smoother.

The attached patch was tested against Firefox 1.x/2.x, Opera and IE 7.

I had made the patch only for the English template.  If you're happy with it, I can make a patch against all template pages.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1858815&group_id=103

From noreply at sourceforge.net  Sun Dec 30 01:25:08 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 29 Dec 2007 16:25:08 -0800
Subject: [ mailman-Feature Requests-1860714 ] More flexible viewing of message
	excerpts
Message-ID: <E1J8lzI-00035z-T1@sc8-sf-web23.sourceforge.net>

Feature Requests item #1860714, was opened at 2007-12-30 09:25
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=1860714&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: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Stephen J. Turnbull (yaseppochi)
Assigned to: Nobody/Anonymous (nobody)
Summary: More flexible viewing of message excerpts

Initial Comment:
In <200712290555.lBT5t1JL029460 at a.mail.sonic.net> on Mailman-Users, Cindy Norwitz suggested allowing longer excerpts for moderating posts and gave a plausible use case (users who don't understand copyright submitting long and full copies of others' work).  This should be configurable by list, as many lists require only being able to distinguish spam from real posts, which is normally possible within a few lines.

I would also like to have the ability to view message excerpts for subscription requests, as these are sometimes spam.

In both cases the existing hardcoded values should be the default.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1860714&group_id=103

From noreply at sourceforge.net  Sun Dec 30 01:32:51 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 29 Dec 2007 16:32:51 -0800
Subject: [ mailman-Feature Requests-1860714 ] More flexible viewing of message
	excerpts
Message-ID: <E1J8m6l-0000vS-2N@sc8-sf-web24.sourceforge.net>

Feature Requests item #1860714, was opened at 2007-12-29 16:25
Message generated for change (Comment added) made by cyndi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1860714&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: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Stephen J. Turnbull (yaseppochi)
Assigned to: Nobody/Anonymous (nobody)
Summary: More flexible viewing of message excerpts

Initial Comment:
In <200712290555.lBT5t1JL029460 at a.mail.sonic.net> on Mailman-Users, Cindy Norwitz suggested allowing longer excerpts for moderating posts and gave a plausible use case (users who don't understand copyright submitting long and full copies of others' work).  This should be configurable by list, as many lists require only being able to distinguish spam from real posts, which is normally possible within a few lines.

I would also like to have the ability to view message excerpts for subscription requests, as these are sometimes spam.

In both cases the existing hardcoded values should be the default.


----------------------------------------------------------------------

Comment By: Cyndi (cyndi)
Date: 2007-12-29 16:32

Message:
Logged In: YES 
user_id=1925111
Originator: NO

Thanks, Stephen.  As you said, there are often times when you need to see
the entire post attempt before you can make a judgement.  I have
subscribers who like to forward copyrighted material and other long
inappropriate things, including quotes of entire digests.  With the short
excerpt, sometimes I think the post is okay when it's actually not.  -Cyndi

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1860714&group_id=103

From noreply at sourceforge.net  Sun Dec 30 21:48:28 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 30 Dec 2007 12:48:28 -0800
Subject: [ mailman-Feature Requests-1860714 ] More flexible viewing of message
	excerpts
Message-ID: <E1J955A-00087R-JL@sc8-sf-web22.sourceforge.net>

Feature Requests item #1860714, was opened at 2007-12-29 16:25
Message generated for change (Comment added) made by cyndi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1860714&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: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Stephen J. Turnbull (yaseppochi)
Assigned to: Nobody/Anonymous (nobody)
Summary: More flexible viewing of message excerpts

Initial Comment:
In <200712290555.lBT5t1JL029460 at a.mail.sonic.net> on Mailman-Users, Cindy Norwitz suggested allowing longer excerpts for moderating posts and gave a plausible use case (users who don't understand copyright submitting long and full copies of others' work).  This should be configurable by list, as many lists require only being able to distinguish spam from real posts, which is normally possible within a few lines.

I would also like to have the ability to view message excerpts for subscription requests, as these are sometimes spam.

In both cases the existing hardcoded values should be the default.


----------------------------------------------------------------------

Comment By: Cyndi (cyndi)
Date: 2007-12-30 12:48

Message:
Logged In: YES 
user_id=1925111
Originator: NO

Thanks, Stephen.  As you said, there are often times when you need to see
the entire post attempt before you can make a judgement.  I have
subscribers who like to forward copyrighted material and other long
inappropriate things, including quotes of entire digests.  With the short
excerpt, sometimes I think the post is okay when it's actually not.  -Cyndi

----------------------------------------------------------------------

Comment By: Cyndi (cyndi)
Date: 2007-12-29 16:32

Message:
Logged In: YES 
user_id=1925111
Originator: NO

Thanks, Stephen.  As you said, there are often times when you need to see
the entire post attempt before you can make a judgement.  I have
subscribers who like to forward copyrighted material and other long
inappropriate things, including quotes of entire digests.  With the short
excerpt, sometimes I think the post is okay when it's actually not.  -Cyndi

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1860714&group_id=103