Closed Bug 17649 Opened 25 years ago Closed 25 years ago

snews://news.mozilla.org outdated

Categories

(mozilla.org Graveyard :: Server Operations, task, P1)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: BenB, Assigned: mbaur)

Details

Since maybe a week, the SSL port of the news server seems to be outdated. Last postings I see are from Wed 27 Oct 1999.
Same thing is probably also occuring to snews://secnews.netscape.com
Severity: normal → major
Priority: P3 → P1
Any progress? Somebody on the newsgroups said, it were a sync problem, dunno, if that's true.
According to mbaur@netscape.com (contact for this news server) all should be up and running. There has been some networking issue connecting to this host though.
I don't understand, what you mean with "some networking issue connecting to this host". I can access snews.mozilla.org via SSL, but no new posts.
There have been no new messages to snews://secnews.netscape.com for sometime. Connecting to snews://secnews.netscape.com is fine.
Status: NEW → ASSIGNED
Ok, I can see it now. What I meant is that there seems to be time to time networking problems and news.mozilla.org has been unreachable from some sites - but yours is different case. Btw, regular NNTP site news.mozilla.org is fine.
Assignee: rko → mbaur
Status: ASSIGNED → NEW
> Btw, regular NNTP site news.mozilla.org is fine. Unfortunately, this doesn't help me, because I have no access to it through my firewall.
Status: NEW → ASSIGNED
The communication between both server instances is still broken. This is a CERT issue I haven't been able to resolve yet. I only get a numeric error code I can't interpret.
a workaround for this is to read news via http://www.deja.com/
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Works at least for n.p.m.mail-news. I posted to snews://news.mozilla.org and the msg was forwarded to the mailing list and my local ISP news server.
Thanks
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.