From 790994 at bugs.launchpad.net Wed Jun 1 03:06:14 2011
From: 790994 at bugs.launchpad.net (Richard Wackerbarth)
Date: Wed, 01 Jun 2011 01:06:14 -0000
Subject: [Bug 790994] [NEW] GPL License
References: <20110601010614.2891.32732.malonedeb@wampee.canonical.com>
Message-ID: <20110601010614.2891.32732.malonedeb@wampee.canonical.com>
Public bug reported:
The gnu-COPYING-GPL file in "trunk" is GPL2. Although I would prefer
that all of mailman be under no more-restrictive license, there are
references to GPL v3. Therefore, should that not be the license
distributed with the source code>
** Affects: mailman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/790994
Title:
GPL License
From 790994 at bugs.launchpad.net Wed Jun 1 19:11:27 2011
From: 790994 at bugs.launchpad.net (Barry Warsaw)
Date: Wed, 01 Jun 2011 17:11:27 -0000
Subject: [Bug 790994] Re: GPL License
References: <20110601010614.2891.32732.malonedeb@wampee.canonical.com>
Message-ID: <20110601171127.13810.51049.launchpad@wampee.canonical.com>
** Tags added: mailman3
** Changed in: mailman
Status: New => Triaged
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/790994
Title:
GPL License
From 787790 at bugs.launchpad.net Thu Jun 2 13:10:48 2011
From: 787790 at bugs.launchpad.net (Steve Foster)
Date: Thu, 02 Jun 2011 11:10:48 -0000
Subject: [Bug 787790] Re: Scrubber can return raw message body for multipart
message
References: <20110524204102.22289.35363.malonedeb@wampee.canonical.com>
Message-ID: <20110602111048.10756.97134.malone@soybean.canonical.com>
Patch applied... appears to fix digest messages but not messages going
into archive
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/787790
Title:
Scrubber can return raw message body for multipart message
From mark at msapiro.net Thu Jun 2 17:34:55 2011
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 02 Jun 2011 15:34:55 -0000
Subject: [Bug 787790] Re: Scrubber can return raw message body for multipart
message
References: <20110524204102.22289.35363.malonedeb@wampee.canonical.com>
Message-ID: <20110602153455.14990.39627.malone@wampee.canonical.com>
Did you restart Mailman after applying the patch? If you didn't, only
periodic digests would be fixed because they are produced by a new cron
process each time, but the archives and any digests triggered on size
would continue to use the unpatched scrubber until the qrunners are
restarted.
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/787790
Title:
Scrubber can return raw message body for multipart message
From 787790 at bugs.launchpad.net Thu Jun 2 17:55:43 2011
From: 787790 at bugs.launchpad.net (Steve Foster)
Date: Thu, 02 Jun 2011 15:55:43 -0000
Subject: [Bug 787790] Re: Scrubber can return raw message body for multipart
message
References: <20110524204102.22289.35363.malonedeb@wampee.canonical.com>
Message-ID: <20110602155543.16793.17950.malone@gac.canonical.com>
OK thats cracked it... Many thanks
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/787790
Title:
Scrubber can return raw message body for multipart message
From mark at msapiro.net Thu Jun 2 20:16:14 2011
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 02 Jun 2011 18:16:14 -0000
Subject: [Bug 787790] Re: Scrubber can return raw message body for multipart
message
References: <20110524204102.22289.35363.malonedeb@wampee.canonical.com>
Message-ID: <20110602181614.14909.5694.launchpad@wampee.canonical.com>
** Changed in: mailman
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/787790
Title:
Scrubber can return raw message body for multipart message
From 793669 at bugs.launchpad.net Mon Jun 6 20:00:51 2011
From: 793669 at bugs.launchpad.net (Laura Creighton)
Date: Mon, 06 Jun 2011 18:00:51 -0000
Subject: [Bug 793669] [NEW] feature request. change the 'list my other
subscriptions' to also report if the other subscriptions are
enabled or disabled
References: <20110606180051.24892.99900.malonedeb@wampee.canonical.com>
Message-ID: <20110606180051.24892.99900.malonedeb@wampee.canonical.com>
Public bug reported:
I have a large number of subscriptions to mailing lists on python.org.
Delivery is disabled on most of them. This is exactly how I want it --
I don't want to keep up with the day to day matters of the list, but I
do want to be able to re-anable delivery and discuss things there should
the need arise without having to create a new account.
However, when I go on vacation, what I want to do is also disable a few high volume lists that I normally want
to read every day. Thus what I would really like to see is which lists are currently enabled, so I can decide
which one(s) if any I want to disable for the vacation. I don't want to disable the low-volume ones. Given
that I am going to have to re-enable the lists I want to read when I get back one by one, I want the number of lists that get temporarily disabled to be as small as possible. And I want to be able to email me the short list of what they were so I can remember which ones to turn on again.
Interestingly, the text of the message indicates a usability
misunderstanding, and a grammatical error. The text reads:
You can view a list of all the other mailing lists at python.org for which you are a member.
Use this if you want to make the same membership option changes to this other subscriptions.
It should be 'these other subscriptions'.
And the people who want to make the same membership option changes to all the lists they are subscribed to on a site are precisely the users who don't need the feature. They can blindly go off and change things
globally. If the number of lists they are subscribed to on that site is 1 -- i.e. they do not have any other subscriptions -- then saying to do things globally will do no harm.
The reason you might want to look is to check because you might _not_ want to do things globally. And once you are dealing with that case, things you do not want to do globally, then of course you want to see the
current settings that you have. But for my use case, all I care about is changing delivery status. All the
other options I either never change, or want to change globally. I suspect that most people use mailing
lists in this way, where the only thing they need to worry about is changes due to vacation, but I haven't
conducted any polls to test this theory.
This request sent to the tracker because the automated mail I recevied when some moderator refused
to accept my mail to mailman-dev with this feature request, with the message 'why don't you just disable delivery globally and then reset them globally when you return' said that this was the place for feature requests and not the mailing list. Hope this request is clearer and explains why globally disabling is not
what I want to do.
Thank you
** Affects: mailman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/793669
Title:
feature request. change the 'list my other subscriptions' to also
report if the other subscriptions are enabled or disabled
From mark at msapiro.net Tue Jun 7 01:28:15 2011
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 06 Jun 2011 23:28:15 -0000
Subject: [Bug 793669] Re: feature request. change the 'list my other
subscriptions' to also report if the other subscriptions are
enabled or disabled
References: <20110606180051.24892.99900.malonedeb@wampee.canonical.com>
Message-ID: <20110606232815.24892.83010.malone@wampee.canonical.com>
Thank you for the request and the detailed explanation of the
requirement. It would be fairly simple to implement this in Mailman 2.1,
but I hesitate to do so because it opens a can of worms which is not so
easy to deal with. If this were implemented, I see more requests with
equal justification for displaying digest mode, and possibly other
settings.
I am attaching a patch which will italicize those list names for which
delivery is disabled, but as I said, I hesitate to actually implement
it. I understand the patch does you no good because you want it on
python.org, but even if I released it, there's no telling when it would
be installed (python.org is currently two releases behind).
At this point, I suggest you do post something to mailman-
developers at python.org or possibly better, mailman-users at python.org
referring to this request and asking if others have interest in this
feature. Note that both this lists are 'officially' closed to non-member
posts. See the respective listinfo pages. Had you joined mailman-
developers before sending your original post, I wouldn't have rejected
it, but any reply from me would have been the same.
Also, I completely agree that the text "Use this if you want to make the
same membership option changes to this other subscriptions." is
misleading and should probably say something like "Use this if you want
to make membership option changes to these other subscriptions.", but
changing that has serious i18n implications, and I'm not sure it's worth
it.
I'm also tagging this report for MM 3.
** Changed in: mailman
Importance: Undecided => Wishlist
** Tags added: mailman3
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/793669
Title:
feature request. change the 'list my other subscriptions' to also
report if the other subscriptions are enabled or disabled
From mark at msapiro.net Tue Jun 7 01:30:31 2011
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 06 Jun 2011 23:30:31 -0000
Subject: [Bug 793669] Re: feature request. change the 'list my other
subscriptions' to also report if the other subscriptions are
enabled or disabled
References: <20110606180051.24892.99900.malonedeb@wampee.canonical.com>
Message-ID: <20110606233031.19230.31413.malone@gac.canonical.com>
** Attachment added: "Patch to italicize 'other lists' with disabled delivery."
https://bugs.launchpad.net/mailman/+bug/793669/+attachment/2157931/+files/options.patch.txt
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/793669
Title:
feature request. change the 'list my other subscriptions' to also
report if the other subscriptions are enabled or disabled
From mark at msapiro.net Tue Jun 7 19:21:02 2011
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 07 Jun 2011 17:21:02 -0000
Subject: [Bug 793669] Re: feature request. change the 'list my other
subscriptions' to also report if the other subscriptions are
enabled or disabled
References: <20110606180051.24892.99900.malonedeb@wampee.canonical.com>
Message-ID: <20110607172102.25004.31673.malone@wampee.canonical.com>
I have rethought this and come up with a more extensible patch with
fewer i18n implications. I'm inclined to include it in 2.1.15.
** Attachment added: "patch to add ', nomail' and/or ', digest' to lists"
https://bugs.launchpad.net/mailman/+bug/793669/+attachment/2159532/+files/options.patch.txt
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/793669
Title:
feature request. change the 'list my other subscriptions' to also
report if the other subscriptions are enabled or disabled
From mark at msapiro.net Wed Jun 8 00:46:56 2011
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 07 Jun 2011 22:46:56 -0000
Subject: [Bug 793669] Re: feature request. change the 'list my other
subscriptions' to also report if the other subscriptions are
enabled or disabled
References: <20110606180051.24892.99900.malonedeb@wampee.canonical.com>
Message-ID: <20110607224657.16786.92286.launchpad@soybean.canonical.com>
** Changed in: mailman
Status: New => Fix Committed
** Changed in: mailman
Milestone: None => 2.1.15
** Changed in: mailman
Assignee: (unassigned) => Mark Sapiro (msapiro)
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/793669
Title:
feature request. change the 'list my other subscriptions' to also
report if the other subscriptions are enabled or disabled
From tkikuchi at is.kochi-u.ac.jp Fri Jun 10 02:47:37 2011
From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi)
Date: Fri, 10 Jun 2011 00:47:37 -0000
Subject: [Bug 266771] Re: Web interface to sync_members
References: <20080905194242.1806.17962.launchpad@forster.canonical.com>
Message-ID: <20110610004737.18983.18414.malone@wampee.canonical.com>
I know this is an old request and many of the users don't look like in need of this. But, I recently get a request from a list administrator for syncing members and wanted to implement the sync_members function in the web interface.
The idea is to add a 'synchronize' flag in admin/members/add form and synchronize the member list with this file rather than simply adding the member. There is no radio buttons for unsubscribe notifications and they are taken from 'send welcome message' and 'admin notification' buttons. The sync operation is done with uploaded file only. If there is no file, then the synchronize flag is ignored.
** Attachment added: "Add synchronize function in mass subscription web ui"
https://bugs.launchpad.net/mailman/+bug/266771/+attachment/2163103/+files/synchronize.patch.txt
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/266771
Title:
Web interface to sync_members
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/266771/+subscriptions
From 790994 at bugs.launchpad.net Sat Jun 11 20:16:20 2011
From: 790994 at bugs.launchpad.net (Barry Warsaw)
Date: Sat, 11 Jun 2011 18:16:20 -0000
Subject: [Bug 790994] Re: GPL License
References: <20110601010614.2891.32732.malonedeb@wampee.canonical.com>
Message-ID: <20110611181620.27618.30977.launchpad@soybean.canonical.com>
** Changed in: mailman
Milestone: None => 3.0.0a8
** Changed in: mailman
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: mailman
Importance: Undecided => Low
** Changed in: mailman
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/790994
Title:
GPL License
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/790994/+subscriptions
From 778687 at bugs.launchpad.net Sat Jun 11 20:45:27 2011
From: 778687 at bugs.launchpad.net (Barry Warsaw)
Date: Sat, 11 Jun 2011 18:45:27 -0000
Subject: [Bug 778687] Re: Invalid roster upon initial list creation
References: <20110506185152.19505.36492.malonedeb@wampee.canonical.com>
Message-ID: <20110611184527.554.68780.launchpad@chaenomeles.canonical.com>
** Changed in: mailman
Status: New => In Progress
** Changed in: mailman
Importance: Undecided => Low
** Changed in: mailman
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: mailman
Milestone: None => 3.0.0a8
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/778687
Title:
Invalid roster upon initial list creation
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/778687/+subscriptions
From 778687 at bugs.launchpad.net Sat Jun 11 21:02:44 2011
From: 778687 at bugs.launchpad.net (Barry Warsaw)
Date: Sat, 11 Jun 2011 19:02:44 -0000
Subject: [Bug 778687] Re: Invalid roster upon initial list creation
References: <20110506185152.19505.36492.malonedeb@wampee.canonical.com>
Message-ID: <20110611190244.18718.34610.malone@wampee.canonical.com>
r7020
** Changed in: mailman
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/778687
Title:
Invalid roster upon initial list creation
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/778687/+subscriptions
From 667252 at bugs.launchpad.net Sun Jun 12 21:23:04 2011
From: 667252 at bugs.launchpad.net (Barry Warsaw)
Date: Sun, 12 Jun 2011 19:23:04 -0000
Subject: [Bug 667252] Re: Mailman 3 Branch,
install fails with --prefix specified
References: <20101027122355.7038.41189.malonedeb@gandwana.canonical.com>
Message-ID: <20110612192304.3979.51771.malone@wampee.canonical.com>
Try --root instead of --prefix
** Changed in: mailman
Status: New => Invalid
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/667252
Title:
Mailman 3 Branch, install fails with --prefix specified
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/667252/+subscriptions
From 667252 at bugs.launchpad.net Mon Jun 13 16:24:24 2011
From: 667252 at bugs.launchpad.net (Simon Fraser)
Date: Mon, 13 Jun 2011 14:24:24 -0000
Subject: [Bug 667252] Re: Mailman 3 Branch,
install fails with --prefix specified
References: <20101027122355.7038.41189.malonedeb@gandwana.canonical.com>
Message-ID: <20110613142424.554.44371.malone@chaenomeles.canonical.com>
Am currently unable to 'bzr branch' mailman again, to re-establish the
environment needed to test this. Will keep trying and update later.
Thanks.
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/667252
Title:
Mailman 3 Branch, install fails with --prefix specified
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/667252/+subscriptions
From nikodemus at random-state.net Mon Jun 13 19:32:34 2011
From: nikodemus at random-state.net (Nikodemus Siivola)
Date: Mon, 13 Jun 2011 17:32:34 -0000
Subject: [Bug 283751] Re: feature request: fetch archived emails
References: <20081015124912.15623.8318.malonedeb@palladium.canonical.com>
Message-ID: <20110613173234.1549.73645.malone@gac.canonical.com>
I miss this semi-regularly -- maybe a few times a year.
For some reason an email goes astray or doesn't arrive (doesn't matter
if I binned it by accident or if my mailhost was down or whatever), or I
want to reply to a message from before my subscription.
Then I always pine for the bad old days of majordomo when I could send a
request for /specific/ old mails, and lo! there they would be -- and
everything archives nicely and conversations remain threaded.
Getting the list archives isn't always possible -- not every list makes
the mbox available (eg. SourceForge uses mailman and doesn't give mbox
files to hoi polloi) -- and reply munging is tedious, and possible with
all clients.
Please, please, please consider this. This is my only major beef with
mailman.
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/283751
Title:
feature request: fetch archived emails
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/283751/+subscriptions
From nikodemus at random-state.net Mon Jun 13 19:44:15 2011
From: nikodemus at random-state.net (Nikodemus Siivola)
Date: Mon, 13 Jun 2011 17:44:15 -0000
Subject: [Bug 283751] Re: feature request: fetch archived emails
References: <20081015124912.15623.8318.malonedeb@palladium.canonical.com>
Message-ID: <20110613174415.29851.13875.malone@soybean.canonical.com>
s/possible with all clients/not possible with all clients/ obviously...
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/283751
Title:
feature request: fetch archived emails
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/283751/+subscriptions
From 283751 at bugs.launchpad.net Mon Jun 13 20:11:46 2011
From: 283751 at bugs.launchpad.net (Barry Warsaw)
Date: Mon, 13 Jun 2011 18:11:46 -0000
Subject: [Bug 283751] Re: feature request: fetch archived emails
References: <20081015124912.15623.8318.malonedeb@palladium.canonical.com>
Message-ID: <20110613181146.1682.26107.malone@gac.canonical.com>
I think we'll probably do something like this in Mailman 3, but also,
I'm much more fond of providing a Gmane-like NNTP interface to the
archives. I find myself subscribing to fewer mailing lists these days
and just reading (and replying!) to them via Gmane. Works great.
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/283751
Title:
feature request: fetch archived emails
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/283751/+subscriptions
From mark at msapiro.net Mon Jun 13 23:14:01 2011
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 13 Jun 2011 21:14:01 -0000
Subject: [Bug 796836] [NEW] Valid set commands are never detected as
administrivia.
References: <20110613211401.955.59703.malonedeb@chaenomeles.canonical.com>
Message-ID: <20110613211401.955.59703.malonedeb@chaenomeles.canonical.com>
Public bug reported:
The is_administrivia function in Mailman/Utils.py requires a 'set'
command to have exactly three arguments and further requires that the
second argument be 'on' or 'off' in order to be detected as
administrivia. This means that none of the following valid commands are
detected.
set help
set show [address=
]
set authenticate [address=]
set on
set off
set digest plain
set digest mime
Unless the command is
set authenticate address=
and the password is 'on' or 'off', however a line such as
set that off topic
would be detected as administrivia even though it is not.
Clearly the intent was to require two arguments, not three, but even
this would not detect things like
set help
or
set digest plain
The obvious fix is to require between one and two (or maybe three)
arguments and to not require the second argument to be 'on' or 'off',
but this may wind up giving too many false positives. This bug has
existed since the format of the set command was changed in Mailman 2.1,
and I'm not aware of any complaints about 'set' not being caught as
administrivia, so I'm reluctant to 'rock the boat' too much. Does anyone
have an opinion on this?
** Affects: mailman
Importance: Low
Assignee: Mark Sapiro (msapiro)
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/796836
Title:
Valid set commands are never detected as administrivia.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/796836/+subscriptions
From richard at NFSNet.org Tue Jun 14 02:22:44 2011
From: richard at NFSNet.org (Richard Wackerbarth)
Date: Mon, 13 Jun 2011 19:22:44 -0500
Subject: [Bug 283751] Re: feature request: fetch archived emails
In-Reply-To: <20110613181146.1682.26107.malone@gac.canonical.com>
References: <20081015124912.15623.8318.malonedeb@palladium.canonical.com>
<20110613181146.1682.26107.malone@gac.canonical.com>
Message-ID: <0C620D08-D620-4331-88C8-B4E98A3384AC@NFSNet.org>
This seems "out of place" for MM, per se. Providing this material is something that is intimately tied to the archiver.
As I see it, the only thing that MM can do is to provide a "pass thru" conduit to whatever archiver the installation has chosen.
Wacky
On Jun 13, 2011, at 1:11 PM, Barry Warsaw wrote:
> I think we'll probably do something like this in Mailman 3, but also,
> I'm much more fond of providing a Gmane-like NNTP interface to the
> archives. I find myself subscribing to fewer mailing lists these days
> and just reading (and replying!) to them via Gmane. Works great.
>
> --
> You received this bug notification because you are a member of Mailman
> Coders, which is subscribed to GNU Mailman.
> https://bugs.launchpad.net/bugs/283751
>
> Title:
> feature request: fetch archived emails
From 283751 at bugs.launchpad.net Tue Jun 14 02:22:44 2011
From: 283751 at bugs.launchpad.net (Richard Wackerbarth)
Date: Tue, 14 Jun 2011 00:22:44 -0000
Subject: [Bug 283751] Re: feature request: fetch archived emails
References: <20081015124912.15623.8318.malonedeb@palladium.canonical.com>
<20110613181146.1682.26107.malone@gac.canonical.com>
Message-ID: <0C620D08-D620-4331-88C8-B4E98A3384AC@NFSNet.org>
This seems "out of place" for MM, per se. Providing this material is
something that is intimately tied to the archiver.
As I see it, the only thing that MM can do is to provide a "pass thru"
conduit to whatever archiver the installation has chosen.
Wacky
On Jun 13, 2011, at 1:11 PM, Barry Warsaw wrote:
> I think we'll probably do something like this in Mailman 3, but also,
> I'm much more fond of providing a Gmane-like NNTP interface to the
> archives. I find myself subscribing to fewer mailing lists these days
> and just reading (and replying!) to them via Gmane. Works great.
>
> --
> You received this bug notification because you are a member of Mailman
> Coders, which is subscribed to GNU Mailman.
> https://bugs.launchpad.net/bugs/283751
>
> Title:
> feature request: fetch archived emails
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/283751
Title:
feature request: fetch archived emails
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/283751/+subscriptions
From nikodemus at random-state.net Tue Jun 14 10:52:37 2011
From: nikodemus at random-state.net (Nikodemus Siivola)
Date: Tue, 14 Jun 2011 08:52:37 -0000
Subject: [Bug 283751] Re: feature request: fetch archived emails
References: <20081015124912.15623.8318.malonedeb@palladium.canonical.com>
Message-ID: <20110614085237.28593.68866.malone@chaenomeles.canonical.com>
Out of date architecturally, maybe, but from usage perspective it's a
very clear fit. While I'm not at all knowledgeable on mailman internals,
isn't it mailman that writes the mbox file? I don't see how things like:
resend last 10 mails
resend last 3 days
resend date 2011-06-11
resend dates 2011-06-10 - 2011-06-12
resend id 0C620D08-D620-4331-88C8-B4E98A3384AC at NFSNet.org
resend ids 0C620D08-D620-4331-88C8-B4E98A3384AC at NFSNet.org -
would require more than trivial parsing or secondary indexing of the
mbox. It's also mailman who does sending of mail, not the archiver,
right? :)
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/283751
Title:
feature request: fetch archived emails
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/283751/+subscriptions
From nikodemus at random-state.net Tue Jun 14 10:53:29 2011
From: nikodemus at random-state.net (Nikodemus Siivola)
Date: Tue, 14 Jun 2011 08:53:29 -0000
Subject: [Bug 283751] Re: feature request: fetch archived emails
References: <20081015124912.15623.8318.malonedeb@palladium.canonical.com>
Message-ID: <20110614085329.27320.98504.malone@chaenomeles.canonical.com>
Me type good again. "Out of place", even.
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/283751
Title:
feature request: fetch archived emails
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/283751/+subscriptions
From mark at msapiro.net Tue Jun 14 22:49:45 2011
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 14 Jun 2011 20:49:45 -0000
Subject: [Bug 283751] Re: feature request: fetch archived emails
References: <20081015124912.15623.8318.malonedeb@palladium.canonical.com>
Message-ID: <20110614204945.27070.74794.malone@chaenomeles.canonical.com>
Mailman 2.1 may or may not write a .mbox file. This is a site
configuration. In comment #5 you say "Getting the list archives isn't
always possible -- not every list makes the mbox available (eg.
SourceForge uses mailman and doesn't give mbox files to hoi polloi)".
I'm not actually a member of any SourceForge mailing lists, so I can't
verify the following, but it is clear from the few lists I looked at
that Sourceforge lists are archived using a non-Mailman external
archiver.
However, It appears that one may be able to get a SourceForge list's
listname.mbox file via
https://lists.sourceforge.net/lists/private/listname.mbox/listname.mbox
if one first authenticates as a list member, by going to say
https://lists.sourceforge.net/lists/private/listname and logging in.
Also, that may take you to an index page with links to the periodic text
files - see comment #3.
In any case, regardless of how trivial you think it might be to
implement this, Mailman 2.1 is currently in bug and security fix only
mode and for Mailman 3, comment #8 applies.
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/283751
Title:
feature request: fetch archived emails
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/283751/+subscriptions
From barry at list.org Wed Jun 15 20:42:51 2011
From: barry at list.org (Barry Warsaw)
Date: Wed, 15 Jun 2011 14:42:51 -0400
Subject: [Mailman-Developers] [Bug 283751] Re: feature request: fetch
archived emails
In-Reply-To: <0C620D08-D620-4331-88C8-B4E98A3384AC@NFSNet.org>
References: <20081015124912.15623.8318.malonedeb@palladium.canonical.com>
<20110613181146.1682.26107.malone@gac.canonical.com>
<0C620D08-D620-4331-88C8-B4E98A3384AC@NFSNet.org>
Message-ID: <20110615144251.64c91bab@neurotica.wooz.org>
On Jun 13, 2011, at 07:22 PM, Richard Wackerbarth wrote:
>This seems "out of place" for MM, per se. Providing this material is
>something that is intimately tied to the archiver.
>
>As I see it, the only thing that MM can do is to provide a "pass thru"
>conduit to whatever archiver the installation has chosen.
I think this is exactly right for read-only NNTP, and in fact the current
MM3 NNTP bridge could probably be rewritten as an archiver plugin (that's not
a bad idea for someone looking to do a bite-size branch!). I think there
would need to be tighter integration for the posting side, a la Gmane. Unlike
Gmane though, if you post through NNTP and we "know who you are", we wouldn't
need to do the verification dance.
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL:
From 283751 at bugs.launchpad.net Wed Jun 15 20:42:51 2011
From: 283751 at bugs.launchpad.net (Barry Warsaw)
Date: Wed, 15 Jun 2011 18:42:51 -0000
Subject: [Mailman-Developers] [Bug 283751] Re: feature request: fetch
archived emails
References: <20081015124912.15623.8318.malonedeb@palladium.canonical.com>
<20110613181146.1682.26107.malone@gac.canonical.com>
<0C620D08-D620-4331-88C8-B4E98A3384AC@NFSNet.org>
Message-ID: <20110615144251.64c91bab@neurotica.wooz.org>
On Jun 13, 2011, at 07:22 PM, Richard Wackerbarth wrote:
>This seems "out of place" for MM, per se. Providing this material is
>something that is intimately tied to the archiver.
>
>As I see it, the only thing that MM can do is to provide a "pass thru"
>conduit to whatever archiver the installation has chosen.
I think this is exactly right for read-only NNTP, and in fact the current
MM3 NNTP bridge could probably be rewritten as an archiver plugin (that's not
a bad idea for someone looking to do a bite-size branch!). I think there
would need to be tighter integration for the posting side, a la Gmane. Unlike
Gmane though, if you post through NNTP and we "know who you are", we wouldn't
need to do the verification dance.
-Barry
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/283751
Title:
feature request: fetch archived emails
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/283751/+subscriptions
From 787599 at bugs.launchpad.net Thu Jun 16 22:48:41 2011
From: 787599 at bugs.launchpad.net (Barry Warsaw)
Date: Thu, 16 Jun 2011 20:48:41 -0000
Subject: [Bug 787599] Re: host_name ancient name for mail_host
References: <20110524145425.22626.24657.malonedeb@wampee.canonical.com>
Message-ID: <20110616204842.29281.60550.launchpad@chaenomeles.canonical.com>
** Changed in: mailman
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/787599
Title:
host_name ancient name for mail_host
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/787599/+subscriptions
From 266263 at bugs.launchpad.net Thu Jun 16 22:52:00 2011
From: 266263 at bugs.launchpad.net (Barry Warsaw)
Date: Thu, 16 Jun 2011 20:52:00 -0000
Subject: [Bug 266263] Re: NNTP gatewaying trashes Message-IDs
References: <20080905193013.27052.88735.launchpad@forster.canonical.com>
Message-ID: <20110616205201.28593.25732.launchpad@chaenomeles.canonical.com>
** Also affects: mailman/2.1
Importance: Undecided
Status: New
** Also affects: mailman/3.0
Importance: Medium
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/266263
Title:
NNTP gatewaying trashes Message-IDs
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/266263/+subscriptions
From 799612 at bugs.launchpad.net Mon Jun 20 08:47:52 2011
From: 799612 at bugs.launchpad.net (Florian Fuchs)
Date: Mon, 20 Jun 2011 06:47:52 -0000
Subject: [Bug 799612] [NEW] Expose REST API call to look up member/user id
given an email address
References: <20110620064752.20698.13504.malonedeb@soybean.canonical.com>
Message-ID: <20110620064752.20698.13504.malonedeb@soybean.canonical.com>
Public bug reported:
In order to find out the internal member ID of an email address one
currently has to iterate over the whole member roster. While this works
fine it's certainly not the most efficient way to retrieve the ID. It
would be great to have a REST-exposed mechanism to look up a member (or
user) ID directly.
** Affects: mailman
Importance: Undecided
Status: New
** Tags: mailman3
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/799612
Title:
Expose REST API call to look up member/user id given an email address
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/799612/+subscriptions
From flo.fuchs at gmail.com Mon Jun 20 09:24:36 2011
From: flo.fuchs at gmail.com (Florian Fuchs)
Date: Mon, 20 Jun 2011 07:24:36 -0000
Subject: [Merge] lp:~flo-fuchs/mailman.client/settings into
lp:mailman.client
In-Reply-To: <20110403205827.21436.60592.launchpad@loganberry.canonical.com>
Message-ID: <20110620072327.26197.27607.codereview@gac.canonical.com>
Review: Needs Information
Hi,
after merging the changes locally LP doesn't let me push to lp:mailman.client ("readonly transport"). Maybe that's because the approved revision is 14 while the branch is currently at rev. 16?
Thanks!
Florian
--
https://code.launchpad.net/~flo-fuchs/mailman.client/settings/+merge/56088
Your team Mailman Coders is subscribed to branch lp:mailman.client.
From 799689 at bugs.launchpad.net Mon Jun 20 15:52:33 2011
From: 799689 at bugs.launchpad.net (Barry Warsaw)
Date: Mon, 20 Jun 2011 13:52:33 -0000
Subject: [Bug 799689] Re: Add API call >>>delete_domain("example.net")
References: <20110620112749.26476.62275.malonedeb@gac.canonical.com>
Message-ID: <20110620135234.30066.31229.launchpad@wampee.canonical.com>
** Also affects: mailman
Importance: Undecided
Status: New
** Changed in: mailman
Status: New => Confirmed
** Changed in: mailman
Importance: Undecided => Low
** Changed in: mailman
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: mailman
Milestone: None => 3.0.0a8
** Tags added: mailman3
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/799689
Title:
Add API call >>>delete_domain("example.net")
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/799689/+subscriptions
From barry at canonical.com Mon Jun 20 16:04:30 2011
From: barry at canonical.com (Barry Warsaw)
Date: Mon, 20 Jun 2011 14:04:30 -0000
Subject: [Merge] lp:~flo-fuchs/mailman.client/settings into
lp:mailman.client
In-Reply-To: <20110403205827.21436.60592.launchpad@loganberry.canonical.com>
Message-ID: <20110620140317.25144.82673.codereview@gac.canonical.com>
I think this is Launchpad's way of saying you didn't have push permissions. Have you ever been able to push to this branch? Anyway, I added ~flo-fuchs to ~mailman-coders, which owns the trunk, so please try again. (P.S. I first accidentally added your doppleganger :)
--
https://code.launchpad.net/~flo-fuchs/mailman.client/settings/+merge/56088
Your team Mailman Coders is subscribed to branch lp:mailman.client.
From 799612 at bugs.launchpad.net Mon Jun 20 16:03:45 2011
From: 799612 at bugs.launchpad.net (Barry Warsaw)
Date: Mon, 20 Jun 2011 14:03:45 -0000
Subject: [Bug 799612] Re: Expose REST API call to look up member/user id given
an email address
References: <20110620064752.20698.13504.malonedeb@soybean.canonical.com>
Message-ID: <20110620140345.23545.83426.launchpad@gac.canonical.com>
** Changed in: mailman
Status: New => Confirmed
** Changed in: mailman
Importance: Undecided => Medium
** Changed in: mailman
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: mailman
Milestone: None => 3.0.0a8
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/799612
Title:
Expose REST API call to look up member/user id given an email address
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/799612/+subscriptions
From noreply at launchpad.net Mon Jun 20 16:42:51 2011
From: noreply at launchpad.net (noreply at launchpad.net)
Date: Mon, 20 Jun 2011 14:42:51 -0000
Subject: [Merge] lp:~flo-fuchs/mailman.client/settings into lp:mailman.client
In-Reply-To: <20110403205827.21436.60592.launchpad@loganberry.canonical.com>
Message-ID: <20110620144249.14209.79088.launchpad@loganberry.canonical.com>
The proposal to merge lp:~flo-fuchs/mailman.client/settings into lp:mailman.client has been updated.
Status: Approved => Merged
For more details, see:
https://code.launchpad.net/~flo-fuchs/mailman.client/settings/+merge/56088
--
https://code.launchpad.net/~flo-fuchs/mailman.client/settings/+merge/56088
Your team Mailman Coders is subscribed to branch lp:mailman.client.
From noreply at launchpad.net Mon Jun 20 16:43:20 2011
From: noreply at launchpad.net (noreply at launchpad.net)
Date: Mon, 20 Jun 2011 14:43:20 -0000
Subject: [Branch ~mailman-coders/mailman.client/trunk] Rev 14: Merge settings
branch, adding:
Message-ID: <20110620144320.15323.20998.launchpad@loganberry.canonical.com>
Merge authors:
Florian Fuchs (flo-fuchs)
Related merge proposals:
https://code.launchpad.net/~flo-fuchs/mailman.client/settings/+merge/56088
proposed by: Florian Fuchs (flo-fuchs)
review: Needs Information - Florian Fuchs (flo-fuchs)
review: Approve - Barry Warsaw (barry)
------------------------------------------------------------
revno: 14 [merge]
committer: Florian Fuchs
branch nick: mailman.client
timestamp: Mon 2011-06-20 09:08:14 +0200
message:
Merge settings branch, adding:
- a _Settings class to manipulate mailing list settings
- methods to delete mailing lists
- Some MM3a7 compatibility changes
modified:
mailman/client/_client.py
mailman/client/docs/using.txt
--
lp:mailman.client
https://code.launchpad.net/~mailman-coders/mailman.client/trunk
Your team Mailman Coders is subscribed to branch lp:mailman.client.
To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subscription
-------------- next part --------------
A non-text attachment was scrubbed...
Name: revision-diff.txt
Type: text/x-diff
Size: 7767 bytes
Desc: not available
URL:
From 799689 at bugs.launchpad.net Tue Jun 21 03:30:37 2011
From: 799689 at bugs.launchpad.net (Barry Warsaw)
Date: Tue, 21 Jun 2011 01:30:37 -0000
Subject: [Bug 799689] Re: Add API call >>>delete_domain("example.net")
References: <20110620112749.26476.62275.malonedeb@gac.canonical.com>
Message-ID: <20110621013037.21780.93873.malone@soybean.canonical.com>
Whoops! Mailman's REST interface already supports DELETE on a domain.
:)
** Changed in: mailman
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/799689
Title:
Add API call >>>delete_domain("example.net")
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/799689/+subscriptions
From 799612 at bugs.launchpad.net Tue Jun 21 03:37:32 2011
From: 799612 at bugs.launchpad.net (Barry Warsaw)
Date: Tue, 21 Jun 2011 01:37:32 -0000
Subject: [Bug 799612] Re: Expose REST API call to look up member/user id given
an email address
References: <20110620064752.20698.13504.malonedeb@soybean.canonical.com>
Message-ID: <20110621013732.20973.39905.malone@soybean.canonical.com>
Hi Florian, can you provide some clarification on exactly what you need?
Here's what you can do right now in the REST API:
Given an email address, you can get a list of all that's address's
memberships. You get a sequence of member entries, and from each of
these you can find its mailing list, role, and member id. So while
you'd still have to do a search, it should be of a much smaller set.
Note that to identify a "membership", you need the triplet of address-
or-user[*], mailing list, and role.
[*] You can now provide a user as long as the user has a preferred
address.
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/799612
Title:
Expose REST API call to look up member/user id given an email address
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/799612/+subscriptions
From 802540 at bugs.launchpad.net Mon Jun 27 16:21:50 2011
From: 802540 at bugs.launchpad.net (Barry Warsaw)
Date: Mon, 27 Jun 2011 14:21:50 -0000
Subject: [Bug 802540] Re: Add c.get_domain() by web_host and not only mail_host
References: <20110627133124.21182.5123.malonedeb@chaenomeles.canonical.com>
Message-ID: <20110627142151.971.54498.launchpad@soybean.canonical.com>
** Also affects: mailman
Importance: Undecided
Status: New
** Changed in: mailman
Status: New => Confirmed
** Changed in: mailman
Milestone: None => 3.0.0a8
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/802540
Title:
Add c.get_domain() by web_host and not only mail_host
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/802540/+subscriptions
From 802540 at bugs.launchpad.net Mon Jun 27 16:42:11 2011
From: 802540 at bugs.launchpad.net (benste)
Date: Mon, 27 Jun 2011 14:42:11 -0000
Subject: [Bug 802540] Re: Add c.get_domain() by web_host and not only mail_host
References: <20110627133124.21182.5123.malonedeb@chaenomeles.canonical.com>
Message-ID: <20110627144211.18284.76641.malone@gac.canonical.com>
barry do you prefer to change this in the core ?
Flo told me that SQL querriys might me much faster.
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/802540
Title:
Add c.get_domain() by web_host and not only mail_host
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/802540/+subscriptions
From 802540 at bugs.launchpad.net Mon Jun 27 17:00:45 2011
From: 802540 at bugs.launchpad.net (Barry Warsaw)
Date: Mon, 27 Jun 2011 15:00:45 -0000
Subject: [Bug 802540] Re: Add c.get_domain() by web_host and not only mail_host
References: <20110627133124.21182.5123.malonedeb@chaenomeles.canonical.com>
Message-ID: <20110627150045.29460.74644.malone@soybean.canonical.com>
In general, when there's important functionality missing in the client,
I think it's at least worth considering whether to add it in the core.
For example, if other (i.e. non-Python) REST clients might want the same
functionality, let's push it into the core.
It's fine to add a workaround in mailman.client first, as long as the
API doesn't change once the core adds functionality. In that case,
you'll be able to just change the implementation to the more efficient,
core version, without code using the client library having to change.
When that's the case, it's fine to add a mailman bugtask and a mailman3
tag.
** Tags added: mailman3
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/802540
Title:
Add c.get_domain() by web_host and not only mail_host
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/802540/+subscriptions
From 802971 at bugs.launchpad.net Tue Jun 28 14:55:43 2011
From: 802971 at bugs.launchpad.net (benste)
Date: Tue, 28 Jun 2011 12:55:43 -0000
Subject: [Bug 802971] [NEW] Mailman Client doesn't _DOMAIN doesn't offer a
list of lists
References: <20110628125543.26674.56509.malonedeb@chaenomeles.canonical.com>
Message-ID: <20110628125543.26674.56509.malonedeb@chaenomeles.canonical.com>
Public bug reported:
I'd suggest adding a functionalty which would need a domain as param,
and return a list of mailing lists associated with this domain.
This could be used to display a choice of all available domains on this
web_host and allow simple deletition of all mailinglists on this domains
in case a domain will ever be deleted.
** Affects: mailman
Importance: Undecided
Status: New
** Affects: mailman.client
Importance: Undecided
Status: New
** Affects: mailmanwebgsoc2011
Importance: Wishlist
Assignee: benste (benste)
Status: Triaged
** Tags: mailman3
** Also affects: mailman.client
Importance: Undecided
Status: New
** Also affects: mailman
Importance: Undecided
Status: New
** Tags added: mailman3
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/802971
Title:
Mailman Client doesn't _DOMAIN doesn't offer a list of lists
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/802971/+subscriptions
From 802971 at bugs.launchpad.net Tue Jun 28 14:58:03 2011
From: 802971 at bugs.launchpad.net (benste)
Date: Tue, 28 Jun 2011 12:58:03 -0000
Subject: [Bug 802971] Re: Mailman Client doesn't _DOMAIN doesn't offer a list
of lists
References: <20110628125543.26674.56509.malonedeb@chaenomeles.canonical.com>
Message-ID: <20110628125803.20746.52278.malone@soybean.canonical.com>
If we don't fix it for a8 in the core we could add an additional method
to the Domain class in _client.py to querry all lists and filter those
to only return those which match the web_host
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/802971
Title:
Mailman Client doesn't _DOMAIN doesn't offer a list of lists
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/802971/+subscriptions
From 802971 at bugs.launchpad.net Tue Jun 28 14:58:29 2011
From: 802971 at bugs.launchpad.net (benste)
Date: Tue, 28 Jun 2011 12:58:29 -0000
Subject: [Bug 802971] Re: Mailman Client doesn't _DOMAIN doesn't offer a list
of lists
References: <20110628125543.26674.56509.malonedeb@chaenomeles.canonical.com>
Message-ID: <20110628125829.27178.35336.malone@chaenomeles.canonical.com>
or mail_host :-)
** Changed in: mailmanwebgsoc2011
Status: New => Confirmed
** Changed in: mailmanwebgsoc2011
Status: Confirmed => Triaged
** Changed in: mailmanwebgsoc2011
Importance: Undecided => Wishlist
** Changed in: mailmanwebgsoc2011
Assignee: (unassigned) => benste (benste)
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/802971
Title:
Mailman Client doesn't _DOMAIN doesn't offer a list of lists
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/802971/+subscriptions
From 802971 at bugs.launchpad.net Tue Jun 28 18:25:50 2011
From: 802971 at bugs.launchpad.net (Barry Warsaw)
Date: Tue, 28 Jun 2011 16:25:50 -0000
Subject: [Bug 802971] Re: Mailman Client doesn't _DOMAIN doesn't offer a list
of lists
References: <20110628125543.26674.56509.malonedeb@chaenomeles.canonical.com>
Message-ID: <20110628162551.20233.733.launchpad@soybean.canonical.com>
** Changed in: mailman
Importance: Undecided => Medium
** Changed in: mailman
Status: New => Confirmed
** Changed in: mailman
Milestone: None => 3.0.0a8
** Changed in: mailman
Assignee: (unassigned) => Barry Warsaw (barry)
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/802971
Title:
Mailman Client doesn't _DOMAIN doesn't offer a list of lists
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/802971/+subscriptions