news.mozilla.org server
.Q.
fixed. Anyone who wants to access this newsgroup should connect to the
server news.mozilla.org. If you continue to use another newsserver,
most folks reading the group won't see your posts, and you won't see
theirs.
The bug was <http://mozillanews.org/bugzilla_warning.php3?id=326759>
--
.Q.
gwtc
Fixed, no, not really. The groups have been showing up on aioe.org and
usenet2.ath.cx, but when posted to them from there, they don't show up
on the news.mozilla.org server, but only on theirs.
for aioe.org:
Path: emma.aioe.org!aioe.org!not-for-mail
From: [snip]
Newsgroups: mozilla.support.firefox
Subject: Re: news.mozilla.org server
Date: Thu, 30 Mar 2006 22:46:22 -0800
Organization: Aioe.org NNTP Server
Lines: 10
Message-ID: <e0iisp$bps$1...@emma.aioe.org>
References: <Xns9796EBA39...@QsFQDN.dyndns.org>
NNTP-Posting-Host: 9ph5qSjw1L9YUSflOfdiHA.user.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: ab...@aioe.org
In-Reply-To:
Xref: emma.aioe.org mozilla.support.firefox:3208
xxxxxxxxxxxxxxxxxxxxxxxx
For usenet2.ath.cx:
Path: usenet2.ath.cx!not-for-mail
From: [snip]
Newsgroups: mozilla.support.firefox
Subject: Re: news.mozilla.org server
Date: Thu, 30 Mar 2006 22:58:24 -0800
Organization:
Lines: 13
Message-ID: <e0ijji$6be$1...@usenet2.ath.cx>
References: <Xns9796EBA39...@QsFQDN.dyndns.org>
<e0iisp$bps$1...@emma.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: ab...@usenet.ath.cx
NNTP-Posting-Date: Fri, 31 Mar 2006 06:52:34 +0000 (UTC)
In-Reply-To: <e0iisp$bps$1...@emma.aioe.org>
Xref: usenet2.ath.cx mozilla.support.firefox:399
--
Time for another change
Me
gwtc
looks like I'm wrong. They *ARE* showing up. Slowly but for surely.
jg
aioe.org is a free news service - might have something to do with it...
»Q«
<news:fr6dne6QZJ6RTrHZ...@mozilla.org>:
> .Q. wrote:
>
>> There was a leak of the mozilla groups onto Usenet, but it has
>> been fixed. Anyone who wants to access this newsgroup should
>> connect to the server news.mozilla.org. If you continue to use
>> another newsserver, most folks reading the group won't see your
>> posts, and you won't see theirs.
>>
>> The bug was
>> <http://mozillanews.org/bugzilla_warning.php3?id=326759>
>>
> Fixed, no, not really.
Yes, fixed; articles from n.m.o don't leak to Usenet, which was
all the bug was about.
And for the most part, articles from Usenet do not make it to n.m.o,
though my OP in this thread somehow /did/ make it. I posted it to
the AIOE Usenet server, not to n.m.o. I didn't expect to see it
here at n.m.o, but here it is, with an NNTP-Posting-Host of
158.64.14.86, which is in Luxembourg. I'm nowhere near Luxembourg;
it looks like some machine there connected to n.m.o as a client and
posted my Usenet post here. Now I wonder if all posts make to
mozilla.* via AIOE will make it to n.m.o, and I'll test some when I
get a chance.
> The groups have been showing up on aioe.org
> and usenet2.ath.cx, but when posted to them from there, they don't
> show up on the news.mozilla.org server, but only on theirs.
And the groups are on a lot of other Usenet servers, as you can see
in the Path headers. Once Usenet groups are created, it's very very
difficult to destroy them. They'd have to be rmgrouped on every
Usenet server which currently carries them.
AFAIAC, we're stuck with the existence of those groups on Usenet,
but traffic to them is very very light now. I only saw a few posts
(since the leak was fixed) to the Usenet version of
mozilla.support.firefox, so I posted the OP[1] in this
thread to let those folks know they should come to n.m.o. All the
other mozilla.* Usenet groups have have been completely dead since
the leak fix.
--
»Q«
»Q«
<news:MrQ9797A7213...@QsFQDN.dyndns.org>:
> And for the most part, articles from Usenet do not make it to
> n.m.o, though my OP in this thread somehow /did/ make it. I
> posted it to the AIOE Usenet server, not to n.m.o. I didn't
> expect to see it here at n.m.o, but here it is, with an
> NNTP-Posting-Host of 158.64.14.86, which is in Luxembourg. I'm
> nowhere near Luxembourg; it looks like some machine there
> connected to n.m.o as a client and posted my Usenet post here.
> Now I wonder if all posts make to mozilla.* via AIOE will make it
> to n.m.o, and I'll test some when I get a chance.
I see that <mho...@netscape.net>'s reply to me, which was also
posted to AIOE, has also made it to n.m.o, and with that same IP
stamp. I'll try to get the evidence together in concise form and
post to m.dev.mozilla-org, probably tomorrow.
--
»Q«
gwtc
> 籕� <box...@gmx.net> wrote in
ME is actually me. One of my many aliases. I was surpised to see that
it made it through.
Chris Ilias
> I see that <mho...@netscape.net>'s reply to me, which was also
> posted to AIOE, has also made it to n.m.o, and with that same IP
> stamp. I'll try to get the evidence together in concise form and
> post to m.dev.mozilla-org, probably tomorrow.
Post it in bug 326759, and I'll reopen it.
--
Chris Ilias
mozilla.test.multimedia moderator
Mozilla links <http://ilias.ca>
(Please do not email me tech support questions)
.Q.
<news:rqgr22hfuq0cparqs...@4ax.com>:
> mozilla.support.firefox is available from my ISP's server, but is
> not on the list for news.mozilla.org.
You need to re-download the active group list for news.mozilla.org to
get the new groups. I'm sorry I can't give specific instructions for
Agent.