Accessing sub-letter search lists
[Using Mailman 2.1.14 on a hosted service]
I have a large list (7600 addresses), and when I search for a list of users of a popular domain (e.g. yahoo.com), I of course get a large result set back - sometimes more than 50 beginning with a particular letter. On those addresses with more than 50 starting with a common letter, they are of course split up, but when I click on another of the sub-letter lists, the “Find” string disappears in the search results and I’m back to a subset of the whole list, not the searched list. Is there any way around this? Thanks much.
-Conrad
-- SILENCE Don’t tweet our secrets
On 04/13/2014 10:48 PM, Conrad G T Yoder wrote:
I have a large list (7600 addresses), and when I search for a list of users of a popular domain (e.g. yahoo.com), I of course get a large result set back - sometimes more than 50 beginning with a particular letter. On those addresses with more than 50 starting with a common letter, they are of course split up, but when I click on another of the sub-letter lists, the “Find” string disappears in the search results and I’m back to a subset of the whole list, not the searched list. Is there any way around this? Thanks much.
This is a bug. Thanks for the report. I'll fix it. See https://bugs.launchpad.net/mailman/+bug/1307454.
In the mean time, the only work around is to set admin_member_chunksize on the General Options page large enough to include all members of the largest sublist so it isn't chunked.
On 04/14/2014 04:39 AM, Mark Sapiro wrote:
On 04/13/2014 10:48 PM, Conrad G T Yoder wrote:
I have a large list (7600 addresses), and when I search for a list of users of a popular domain (e.g. yahoo.com), I of course get a large result set back - sometimes more than 50 beginning with a particular letter. On those addresses with more than 50 starting with a common letter, they are of course split up, but when I click on another of the sub-letter lists, the “Find” string disappears in the search results and I’m back to a subset of the whole list, not the searched list. Is there any way around this? Thanks much.
This is a bug. Thanks for the report. I'll fix it. See https://bugs.launchpad.net/mailman/+bug/1307454.
In the mean time, the only work around is to set admin_member_chunksize on the General Options page large enough to include all members of the largest sublist so it isn't chunked.
The fix has been committed for 2.1.18. In the mean time, another work around is when you click the link for another chunk and get the unfiltered chunk back with a URL like http://www.example.com/mailman/admin/listname/members?letter=m&chunk=1 in the browsers address bar, add the filter to the URL and get that. E.g. with yahoo.com as the search, the above becomes http://www.grizz.org/mailman/admin/gpc-talk/members?letter=m&chunk=1&findmember=yahoo.com.
On 04/16/2014 08:06 AM, Mark Sapiro wrote:
In the mean time, another work around is when you click the link for another chunk and get the unfiltered chunk back with a URL like http://www.example.com/mailman/admin/listname/members?letter=m&chunk=1 in the browsers address bar, add the filter to the URL and get that. E.g. with yahoo.com as the search, the above becomes http://www.grizz.org/mailman/admin/gpc-talk/members?letter=m&chunk=1&findmember=yahoo.com.
Just to avoid any possible confusion, the second URL above should have been http://www.example.com/mailman/admin/listname/members?letter=m&chunk=1&findmember=yahoo.com.
Just to confirm my suspicions, the "chunk" capability requires Mailman newer than version 2.1.9? Another question: is there a way to negate the findmember search, so that all members not in the example.com domain could be shown?
Thanks!
Kirke Johnson Internet: kjohnson@pcc.edu Email Administrator, TSS , Sylvania Campus Portland Community College, Portland, OR, USA (971) 722-4368
On Wed, Apr 16, 2014 at 8:14 AM, Mark Sapiro mark@msapiro.net wrote:
On 04/16/2014 08:06 AM, Mark Sapiro wrote:
In the mean time, another work around is when you click the link for another chunk and get the unfiltered chunk back with a URL like http://www.example.com/mailman/admin/listname/members?letter=m&chunk=1 in the browsers address bar, add the filter to the URL and get that. E.g. with yahoo.com as the search, the above becomes http://www.grizz.org/mailman/admin/gpc-talk/members?letter=m&chunk=1&findmember=yahoo.com.
Just to avoid any possible confusion, the second URL above should have been http://www.example.com/mailman/admin/listname/members?letter=m&chunk=1&findmember=yahoo.com.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/kjohnson%40pcc.edu
On 04/16/2014 08:35 AM, Kirke Johnson wrote:
Just to confirm my suspicions, the "chunk" capability requires Mailman newer than version 2.1.9?
If you mean the ability to set admin_member_chunksize from the admin General Options page, then yes, that was added in 2.1.10. Everything else to do with chunking the admin Membership List has always been in Mailman 2.1
Another question: is there a way to negate the findmember search, so that all members not in the example.com domain could be shown?
The search is a python regular expression. There is syntax for negative lookahead/lookbehind assertions, so that for example the search pattern
$(?<!example.com)
will match any string that doesn't have 'example.com' immediately preceding the end of the string.
The problem is this won't work because the search is done against both the email address and the real name so while that search won't find user@example.com, that user's real name (say John Doe) doesn't end with example.com so the search result will still include that entry because it finds the real name.
On Apr 16, 2014, at 11:06 AM, Mark Sapiro mark@msapiro.net wrote:
On 04/14/2014 04:39 AM, Mark Sapiro wrote:
On 04/13/2014 10:48 PM, Conrad G T Yoder wrote:
I have a large list (7600 addresses), and when I search for a list of users of a popular domain (e.g. yahoo.com), I of course get a large result set back - sometimes more than 50 beginning with a particular letter. On those addresses with more than 50 starting with a common letter, they are of course split up, but when I click on another of the sub-letter lists, the “Find” string disappears in the search results and I’m back to a subset of the whole list, not the searched list. Is there any way around this? Thanks much.
This is a bug. Thanks for the report. I'll fix it. See https://bugs.launchpad.net/mailman/+bug/1307454.
In the mean time, the only work around is to set admin_member_chunksize on the General Options page large enough to include all members of the largest sublist so it isn't chunked.
The fix has been committed for 2.1.18. In the mean time, another work around is when you click the link for another chunk and get the unfiltered chunk back with a URL like http://www.example.com/mailman/admin/listname/members?letter=m&chunk=1 in the browsers address bar, add the filter to the URL and get that. E.g. with yahoo.com as the search, the above becomes http://www.grizz.org/mailman/admin/gpc-talk/members?letter=m&chunk=1&findmember=yahoo.com.
What great service - 2-day turnaround on bug fixes! (Not that I will be seeing it any time in the near future with my hosting service :^)
Since we’re on the topic of items residing at bugs.launchpad.net, what are the odds of Bug #1067953 (https://bugs.launchpad.net/mailman/+bug/1067953) getting a little love? Not quite as easy a change as this one, but would benefit many I’m sure. Everyone subscribe!
-Conrad
-- Truth is information.
On 04/16/2014 12:20 PM, Conrad G T Yoder wrote:
What great service - 2-day turnaround on bug fixes! (Not that I will be seeing it any time in the near future with my hosting service :^)
We try. Thanks for the appreciation.
Since we’re on the topic of items residing at bugs.launchpad.net, what are the odds of Bug #1067953 (https://bugs.launchpad.net/mailman/+bug/1067953) getting a little love? Not quite as easy a change as this one, but would benefit many I’m sure. Everyone subscribe!
I updated the bug report and marked it Wishlist. I commented
This won't happen in MM 2.1. The best you can do is set admin_immed_notify On and view the HTML rendering of the message attached to the moderation notice in your mail client. Something may be done in MM 3, but rendering untrusted HTML on your web site via a privileged CGI is not a very good idea.
Conrad G T Yoder writes:
Since we’re on the topic of items residing at bugs.launchpad.net, what are the odds of Bug #1067953 (https://bugs.launchpad.net/mailman/+bug/1067953) getting a little love? Not quite as easy a change as this one, but would benefit many I’m sure. Everyone subscribe!
Pretty good, now that you've posted this -- the Mailman developers are sprinting at Pycon as I write this, I believe, or maybe still at dinner since none of them are on IRC.
A few words to the wise, in the interest of DAO[1]. At least for me personally I would be slightly more likely to look, and very likely to look sooner, if you posted the title as well as the bug number.
In general, Mailman developers are mail-oriented (including Barry who last I heard was a Launchpad developer). I don't know if anybody who can do something about bugs actually pays attention to subscription counts. Can't hurt, but posting here (or on -developers if you actually want to participate in fixing by contributing code or code reviews) is likely the best way to be a "squeaky wheel". Please avoid "me too posts" unless nobody responds in a few days. At least Mark and I read *every post* to mailman-users.
Once discussion on a fix starts, it will typically move to -developers for the requirements and design discussion, then to the issue itself (this is formalized for developing Python itself, we're less informal but take our cue from Python).
Footnotes: [1] Developer Attention Optimization. :-)
participants (4)
-
Conrad G T Yoder -
Kirke Johnson -
Mark Sapiro -
Stephen J. Turnbull