Could you please provide further details? Our operations engineer has 
tested posting via email and via news reader. Both work with no
problems. All the daemons are up and operational, and he is able to
read news. 

Thank you
Kat

Sorry, works fine again...

dead since Jan 18 09:53:23 GMT+1

I'll take a look at this asap.

I've submitted this issue to our operations group for troubleshooting
(PCN7675).

Our operations group reports that they have found hardware problems
with the server.  They are working on it.  I'll update as soon as I
have new news.

Our operations group is moving to a new server, due to hardware
problems with the old one. They have gotten a new server and loaded
the software on it; they just need to add configurations and data.

Ok. The connection to news.openoffice.org is working now. Also the 
NNTP-Protocol on Port 119 (default) is working.

Could you please explain, what the next steps are, I supscribed to 
serval newsgroups under the OOo.-Folder, but can't post anywhere?

Hope this will be available soon ;-)

Marco

Okay, we have the NNTP service running again.  I subscribed myself to
netbeans.nbannounce and successfully got messages.  I also
successfully submitted a post to netbeans.modules.collabnet.test, and
it arrived in the test@collabnet.netbeans.org archive. Please test
away!  Thanks.

Oops, need to look in openoffice.  I can subscribe to newsgroups (say
ooo.test.announce, ooo.test.users, and ooo.allbugs), but they're empty
so far.  I'll update as soon as I have new news.

I can subscribe to all groups, but when I send messages (from:
marco@by-night.ch) they aren't shown up in the appropriate groups and
I did not get any response (error message or whatever). Can you please
check it again? Did you test this internal/external?

We now have the NNTP server up and accepting posts and displaying new
newspostings.  We are still working on getting historical news items
reflected on the server.  Please test.

New internal issue number (PCN7547).

Stefan- have you taken a look at the NNTP server?  We'd love to hear
how it's working for you.

btw: for me, this works fine at the moment. all postings where listed 
here, timon reported, that he received the messages from the group 
ooo.lang.discuss_de

thanks for the support!

Thanks Marco!  That's good to hear.  We're still working on getting
the historical posts up there.  The operations person and the
developer are planning to get together tomorrow.

Service is up and running.
Marco, thanks for testing.

We need to get a different developer to help us with this due to
resource constraints.  I'll have more details tomorrow after I bring
this up with the appropriate engineering managers.

We've got the technical details all ready.  We're just now verifying
the plan with Eric Renaud et al.

We've cleared all the details.  I've turned over all of our requests
to the operations group and requested a time-frame.

To document the details:
We will have initially max. 500 articles per newsgroup.
Expiration will cut down the number to 500 articles on a regular basis.

Our operations person has been (slowly) working on this, with help
from our instantiations engineer.  I am still pinging him for updates,
and he did provide several status updates today.

The last update I got from our operations engineer was last week, in
which he reported that he was still uploading history files.  I pinged
him again today.

Messages injected today (5/8) as historical data have the current 
date - not the original - and are therefor useless.
Not to speak about the annoyance of #4644 for list subscribers.

Hi Stefan-
I have a question for you.  My perception was that the reason for the
historical messages was so that new subscribers to the newsgroup could
peruse recent history, not for archival purposes (as messages older
than 500 messages ago get expired anyway).  Why, then, does the
absence of date information on the messages make them useless?   I do
not believe that there is a way to "convince" a news server that
messages just delivered to it have, in fact, older dates on them.

From my point of view reposting with current date is forgery of
history. I would prefer no old postings over reposting with wrong date.
That's not absence but wrong date info.

I know that there is a way to repost articles with old dates.
Point your favorite news reader to ooo.test.news and have fun :-)
Believe me, I was at home - spending a nice weekend.
The tricky part may be to convince the server to accept very old
articles (> X days). Usually there is an option for that.

How to proceed?
Remove all articles and let the time work for you...
I'm not sure that you would like to invest time in the "correct"
reposting.
But may be you would like to convince me from the opposite...

Thanks for the update, Stefan.  I've submitted this info to our
engineers and will update you when I hear what they think.

This is still under investigation by our engineers, their current
status on this is that this is not supported and that won't be a
painless way to support old dates without getting into NNTP server
internals.

A solution for migrating historical posts has not yet been formulated.

Still awaiting development of a solution for moving historical posts.

A script option for reflecting historical posts on the server is still
being investigated.

A script is still being investigated by our engineers. I will update
the issue further when there is new information to report or at least
once a week. Please let me know if there are any objections.

Progress is being made on the script. Messages are able to be
transferred with dates preserved. Testing to continue next week.

The script remains in testing to assure all requirements are being
met. If things proceed as planned, we hope to be able to transfer the
historical posts in the coming week. I will keep you updated on the
situation.

Further work is required on this issue. There are aspects of behavior
on the production server that have been called into question.

This has been assigned to an engineer to address the questional
aspects of its behavior.

The issues with the scropt have been addresed, and the functionality
is being incorporated into SC to make this process more fluid in the
future.

adding david boswell to cc list

queried the engineer on this today.  I will respond back with an
update when I get one.  It seems as if we are very close and just need
some final confirmations on this prior to getting it resolved.

Brian, can we close this?
louis

This issue is currently scheduled to be looked at by an engineer when
work on our 2.5 release has been completed.  We are aware that it is
not functioning, however we won't have any updates until that work
begins.  If this need to be a higher priority please let us know.

Please ignore the last entry from me, it was meant for another issue.

Yes, we can close this if and only if, we open another issue to
complete the job here.   This ticket has changed from nntp not working
to nntp historical posts needed.  Although they go hand in hand, it
would be better to track them as seperate issues as we do not have a
convenient tool to re-post the old emails to nntp.

So, closing this issue.  Opened issue 8838 to follow the new issue of
accurately posting historical nntp messages.

As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.

As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.