[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What to do when Article numbers are unreliable?
From: |
David Kastrup |
Subject: |
Re: What to do when Article numbers are unreliable? |
Date: |
Fri, 18 Aug 2006 10:20:13 +0200 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
David Kastrup <dak@gnu.org> writes:
> Ivan Boldyrev <boldyrev+nospam@cgitftp.uiggm.nsc.ru> writes:
>
>> On 9568 day of my life David Kastrup wrote:
>>> with my current news provider, it appears like I get one of a bunch of
>>> news servers on each connection, and the relation between article
>>> numbers and articles is not kept.
>>
>> Use leafnode as proxy server or (better) change provider because
>> provider's admins are idiots, and new problems are just waiting...
>
> Probably my analysis was backwards: updating news seems to work pretty
> ok (which articles are read or not), but it is pretty impossible to
> get a message using its article Id (like with ^ ) unless it has
> already been fetched in this session.
>
> So maybe access by article Id is what is borked.
No, can't be quite that. When I press ^, the appropriate summary line
with subject, author, number of lines actually appears, but it flashes
yellow, gets marked with "G" and I get an "article was canceled or
expired" message.
Can anybody put a finger on what combination of circumstances would
trigger such a behavior? I am somewhat at a loss of where to look for
the problem, and what exactly to report the provider of news.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum