So:
http://groups.yahoo.com/group/wireline/
which redirects to:
https://groups.yahoo.com/neo/groups/wireline/info (*)
doesn't get you to the same page as:
http://tech.groups.yahoo.com/group/wireline/
used to take you?
(*) The "neo" path isn't to some group owned by Neo and you're not in
the Matrix, either. Even
http://groups.yahoo.com/ redirects to the
"neo" path plus the protocol changes from HTTP to HTTPS so you end up at
https://groups.yahoo.com/neo. NEO is some new format at Yahoo Groups;
http://yahoogroups.tumblr.com/post/59703544200/new-changes-on-yahoo-groups.
A year ago when they made the announcement, it sounded like it would
apply to all groups but that was misleading. It was a proposed change
that would creep through to get employed eventually on their groups'
page design.
"Mail not accessible because not logged in."
I didn't realize the Yahoo Groups mailing lists were ever available to
non-logged users. That is, I thought you had to be logged in to
participate in their discussions and to receive any e-mails, like
newsletters, from or to the group. Allowing anyone to use their mailing
lists without logging in seems such an easy way for a scammer, spammer,
or malcontent to abuse their mailing lists.
The "page not found" is a generic message. Some web browsers provide
more info than others, or you have to dig it out. Indeed, when I use
something that shows me the headers and responses then the error is
"Description: Could not process this "GET" request." Actually that is
not an error message per se but a web page that they present to you.
The complete session looks like:
09/10/14 23:23:09 Browsing
http://tech.groups.yahoo.com/group/wireline/
Fetching
http://tech.groups.yahoo.com/group/wireline/ ...
GET /group/wireline/ HTTP/1.1
Host:
tech.groups.yahoo.com
Connection: close
User-Agent: Sam Spade 1.14
HTTP/1.1 301 Moved Permanently
Date: Thu, 11 Sep 2014 04:23:11 GMT
Connection: close
Via: http/1.1
proxy8.grp.bf1.yahoo.com (ApacheTrafficServer [c s f ])
Server: ATS
Cache-Control: no-store
Content-Type: text/html; charset=utf-8
Content-Language: en
Content-Length: 213
<HTML>
<HEAD>
<TITLE>Error</TITLE>
</HEAD>
<BODY BGCOLOR="white" FGCOLOR="black">
<H1>Error</H1>
<HR>
<FONT FACE="Helvetica,Arial"><B>
Description: Could not process this "GET" request.
</B></FONT>
<HR>
</BODY>
The "Could not process this GET request" is *not* an error message.
That is the web page there server decided to deliver to you. The real
error looks to be:
301 Moved Permanently
but the web server doesn't redirect your connection to wherever the page
got moved. Normally a mapping in the web server should take you to
where the page got moved. The "could not process GET" message is like a
programmer adding a "should not see this" output to stdout. If he sees
that message then something is wrong with his code. You're seeing a web
page that should NOT be visible if the remap at the web server was
working.
Could be whomever is the web server admin screwed up an update and
forgot to add all the redirections for old URLs to the new nav path for
where the pages got moved. Could be they no longer support those old
redirections (i.e., all those "tech" subhosts used to categorize a group
within the URL to it). Whatever the reason, the web pages got moved or
the URLs (that have to get redirected) weren't updated (or they were
deliberately deleted as redundant).
We can't do anything about Yahoo's configuration of their web server and
whether the redirections were screwed up or deleted. That's something
you'll have to take up with Yahoo or find a group there that discusses
problems with their own groups (aka forums).