Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bogus expired messages

24 views
Skip to first unread message

MikeR

unread,
Nov 17, 2012, 10:17:22 AM11/17/12
to
Using TB 16.0.2 on a MacBook Pro.  I've started getting the following message intermittantly when reading newsgroups, this one included. Thus it seems to be a TB problem, not the news server.

I start to read a post and the message pops. If I click on another post (In or out of the thread) then click on the misbehaving post again,  I can read it.

Open to ideas.

Error!

newsgroup server responded:no such article found

Perhaps the article has expired

<someg...@someserver.com> (13911)

Click here to remove all expired articles

Thanks, Mike


Ron Hunter

unread,
Nov 17, 2012, 8:43:28 PM11/17/12
to
On 11/17/2012 9:17 AM, MikeR wrote:
> Using TB 16.0.2 on a MacBook Pro. I've started getting the following
> message intermittantly when reading newsgroups, this one included. Thus
> it seems to be a TB problem, not the news server.
>
> I start to read a post and the message pops. If I click on another post
> (In or out of the thread) then click on the misbehaving post again, I
> can read it.
>
> Open to ideas.
>
>
> Error!
>
> newsgroup server responded:*no such article found*
>
> *Perhaps the article has expired*
>
> <someg...@someserver.com> (13911)
>
> Click here to remove all expired articles
> <news://forums.embarcadero.com/embarcadero.public.delphi.language.delphi.win32?list-ids>
>
> Thanks, Mike
>
>
It may be that you have a corrupt file in the profile for that
newsgroup. Or the news server has a problem.

Russ Eggen

unread,
Nov 18, 2012, 7:30:33 AM11/18/12
to
Happens almost every time I start up.

Chris Luck

unread,
Nov 19, 2012, 4:43:33 AM11/19/12
to
On 17/11/12 15:17, MikeR wrote:
> Using TB 16.0.2 on a MacBook Pro. I've started getting the
> following message intermittantly when reading newsgroups, this one
> included. Thus it seems to be a TB problem, not the news server.
>
> I start to read a post and the message pops. If I click on another
> post (In or out of the thread) then click on the misbehaving post
> again, I can read it.
>
> Open to ideas.
>
> Error! newsgroup server responded:*no such article found*
>
> *Perhaps the article has expired*
>
> <someg...@someserver.com> (13911)
>
> Click here to remove all expired articles
> <news://forums.embarcadero.com/embarcadero.public.delphi.language.delphi.win32?list-ids>


Viewing embarcadero.public.delphi.language.delphi.win32, as I
occasionally do, I see that articles 13907/13910/13911 are absent.
The number sequence suggests they were in the thread -

Subject: Invalid float point operation on Move??
Date: 06/07/12

If I had downloaded the message bodies prior to their removal from the
server how would I know they had been removed? How would TB handle the
situation? I think you've just discovered how TB handles the case but
whether this is new, or intended, behaviour I can't say. It would be
more useful to be notified of a discrepancy and given a choice of how to
handle it.

There's a deal of surmise in the foregoing but at least you can confirm
the absence of messages on the embarcadero web forum.

--
Regards,
Chris Luck
0 new messages