Last modified: 2014-10-07 16:23:13 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T23928, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 21928 - oversight-l subscriber list: "Visit Subscriber List" results in "You must supply a valid email address."
oversight-l subscriber list: "Visit Subscriber List" results in "You must sup...
Status: REOPENED
Product: Wikimedia
Classification: Unclassified
Mailing lists (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-12-23 05:40 UTC by Dominic
Modified: 2014-10-07 16:23 UTC (History)
9 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Dominic 2009-12-23 05:40:58 UTC
Currently, and for a little while now, the subscriber list for oversight-l has been unreachable, at least for non-listadmins. Putting in the correct email address and password at https://lists.wikimedia.org/mailman/listinfo/oversight-l and hitting "Visit Subscriber List" results in a page with the following error: "You must supply a valid email address." Multiple people report this problem, and the email addresses being supplied are identical to the ones subscribed, not actually invalid.
Comment 1 Fred Vassard 2009-12-29 21:26:44 UTC
Looking into this. 
More to come.
Comment 2 Fred Vassard 2010-03-10 17:30:56 UTC
Could you tell me what happens if once you get the error message (after trying to login) you go to https://lists.wikimedia.org/mailman/roster/oversight-l 
It seems to be working for me, albeit it is very weird. 
Let me know!
Comment 3 Dominic 2010-04-04 06:25:02 UTC
(In reply to comment #2)
> Could you tell me what happens if once you get the error message (after trying
> to login) you go to https://lists.wikimedia.org/mailman/roster/oversight-l 
> It seems to be working for me, albeit it is very weird. 
> Let me know!

That does work, yes. So at least we have some way to see it from the non-administrator interface, thanks. Although, it lists one "private member not shown," whatever that means.
Comment 4 Casey Brown 2011-06-20 02:19:30 UTC
Does this still happen or can we close the bug?
Comment 5 Casey Brown 2011-06-23 15:30:41 UTC
I'm assuming the issue has fixed itself. Please re-open the bug if that's not true, and then we should try to look at whether or not anyone broke the HTML files.
Comment 6 Dominic 2011-07-09 02:56:47 UTC
This isn't resolved. I was told it was a simple error that would take a few minutes to fix... a year and a half ago. Nothing has changed.
Comment 7 Casey Brown 2011-07-11 16:46:07 UTC
Do anyone tell you what the error was?

If you recently tested it and it still doesn't work, I think it might be related to the HTML files. Can you send me whatever the text in <https://lists.wikimedia.org/mailman/edithtml/oversight-l/listinfo.html> is?
Comment 8 Casey Brown 2011-07-11 20:31:29 UTC
Philippe sent it to me and I can't find anything wrong in there. Well, there goes my idea. ;-)
Comment 9 Thehelpfulone 2012-05-02 00:19:57 UTC
Just confirmed with an oversighter that the same error is occuring - http://www.wlug.org.nz/MailManNotes suggests a potential fix. http://mail.python.org/pipermail/mailman-users/2008-January/060018.html and http://mail.python.org/pipermail/mailman-users/2008-January/060026.html are a couple of posts on a thread back in 2008 describing the same problem. I'll send Daniel to this to have a look I think, as he's got a bit of experience with the apache config on mailman.
Comment 10 Daniel Zahn 2012-06-12 07:19:40 UTC
subscribed myself to be able to reproduce this, and i could.

i looked at this a bit and dumped the list config on shell, looking at the variables web_page_url and host_name as mentioned in http://www.debian-administration.org/articles/567 to fix with "withlist", host_name is lists.wikimedia.org.

ran withlist like this:


/withlist -l -r fix_url oversight-l -u lists.wikimedia.org
Importing fix_url...
Running fix_url.fix_url()...
Loading list oversight-l (locked)
Saving list
Finalizing

but it did not appear to fix/change it and i don't see a difference with "web_page_url" compared to all other lists.

hrmm.. Since there is a work-around which gave you the list you wanted (see above), the issue with an "unlisted private member" has disappeared meanwhile and the list is closed (note: it says it is closed and will not accept any mail), is it really needed? or how about just unsubscribing people from it if it really won't receive any new mails anymore?
Comment 11 Thehelpfulone 2012-06-12 07:46:36 UTC
Hi Daniel - the list is actively used by oversighters themselves as far as I am aware for discussion. The list was previously used to handle actual overnighting requests, but this has now moved to OTRS, but it's possible that the email address or list info page is linked somewhere - that could be why the main page says that the list is no longer used, so people don't send OS requests to it.
Comment 12 Daniel Zahn 2012-06-12 10:29:22 UTC
ok. hmm. but existing links don't have to be broken, it can just sit there but does not need subscribers if it does not receive anything. It wouldn't even matter but it would be an easy way to resolve this ticket, since no subscribers = no need to keep trying to pull subscriber lists from it. (which even has the work around)
Comment 13 Snowolf 2012-06-12 12:40:32 UTC
If it is still used, the mailing list should be renamed to something like oversight-en-wp-l or something that makes it clear that it's not a global list, or said discussion should take place in other avenues, such as functionaries-en
Comment 14 Daniel Zahn 2012-06-12 13:22:32 UTC
removed myself from list again as it indeed appears to be still in use.
Comment 15 John F. Lewis 2014-10-07 16:23:13 UTC
Assuming there has been no updates and the list is no longer used anymore; does this issue occur on any other lists?

If not; could we close this? :)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links