Recovering from broken connection

Recovering from broken connection

[Giorgos Keramidas]

While I was fetching articles with the agent, my dialup connection died,
and left many articles in a `strange' state.  They are listed as:

    00-00-00 [   0: Gnus Agent          ] [Undownloaded article 58998]

in the summary buffer, but hitting SPC or RET on them properly displays
both the headers and the article are available, even in offline mode.

I tried setting `gnus-agent-consider-all-articles' and refetching, but
this doesn't seem to have regenerated the summary buffers which are
`broken'.  Is there any way to force Gnus to query the agent again,
since these articles *are* available when I am offline?

For example, here's how my current summary buffer for news:comp.std.c
looks:

 . 00-00-00 [   0: Gnus Agent          ] [Undownloaded article 58998]
 . 00-00-00 [   0: Gnus Agent          ] [Undownloaded article 58999]
 . 00-00-00 [   0: Gnus Agent          ] [Undownloaded article 59000]
 . 2007-10-28 [  46: cr88192             ] Re: Floating point question
 .+2007-10-29 [  54: Keith Thompson      ] Does a constraint violation cause undefined behavior?
 . 2007-10-29     [  68: James Kuyper        ] Re: Does a constraint violation cause undefined behavior?
 . 2007-10-29     [  11: Wojtek Lerch        ] Re: Does a constraint violation cause undefined behavior?

In larger groups, i.e. in news:comp.lang.c the undownloaded articles are
many dozens, and it is a pain reading them without any sort of threading
or sorting :/

- Giorgos