Hi,
First you need to confirm that the articles are on the upstream servers, and
accessible, not just cached locally by OE (Which by default cleans out
messages after a few days).
Telnet in to the remote server -
telnet servername 119
authinfo user {username}
authinfo pass {pass}
group group.name
Take note of the four numbers returned by the server. The second number
(after 2xx) is an estimate of the number of articles on the server for that
group. This number is not always correct.
Then, try requesting the oldest article (The third number) -
head 12345 (Change 12345 to the thrid number on the line)
If that shows you a header, you should be able to find the article (by
Message ID is the easiest) on your server if it has been sucked correctly.
That is the oldest article on the remote system.
- Roydon L.
<[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>...
> Hi,
>
> Didn't work... i have even less old articles i think
>
> I did exacly like you said, changed the too_old value to 100. But isen't
> this strange i mean even if it is 20 that should be enough to get things
> from the last couple of days.
>
> I rebuild the index... I'm wondering should i have stopped the feeds
during
> the rebuild? And does the index also rebuild the history?
>
> I've also added suck_requeue true.....to dnews.conf. I did not notice
> anything.
>
> After this i have shutdown and restarted the server agian. It's getting
> articles but not from more then 12 hrs ago... even less. It can't be the
> feed. I have 2 feeds configured to fill this binary newsgroup. They both
> have lots of retention.
>
> What are we missing here?
>
> Marcel
>
>
>
>
>
> "Netwin Support" <[EMAIL PROTECTED]> schreef in bericht
> news:[EMAIL PROTECTED]
> > Hi,
> >
> > Set too_old (in days) to allow these older messages on to the system. I
> > believe the default is 20 days.
> >
> > too_old 100
> >
> > DNews will remember the old items it rejected so it can tell other feeds
> it
> > doesn't want the items should they offer them via an ihave feed. In
order
> to
> > be able to suck the items again, you will need to do a rebuild_index to
> make
> > DNews forget about them.
> >
> > tellnews rebuild_index
> >
> > Then wait patiently until that finishes (progress can be monitored from
> > 'tellnews status'), and do as you did previously.
> >
> > I would also recommend -
> >
> > suck_requeue true
> >
> > This will cause DNews to bring the groups up to date every time it is
> > sucked, changing to the next group when the limits are reached, and
> > requeuing the incomplete group.
> >
> > - Roydon L.
> >
> > <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>...
> > >
> > > I've set up Dnews to fetch me a binary group
alt.binaries.sounds.mp3.xxx
> > in suck mode (not dynamic) Updates are scheduled every 10 minutes.
> > >
> > > It retrieved all items from 9h this morning. But what about the items
> > before 9h. The newsserver from which i suck has about 5 day retention in
> > that group. I would like those files as well.
> > >
> > > I've tried:
> > >
> > > tellnews getold "*" 300
> > > tellnews update 2 (2 = nntp2 suckfeed)
> > >
> > > What am i doing wrong here?
> > >
> >
> >
>
>
>
