From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: 423 bad article number from local spool but header are there?
Date: Mon, 02 Dec 2002 08:53:23 +0100 [thread overview]
Message-ID: <84el90svpo.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <878yz9uxdg.fsf@nova.revier.com>
Jochem Huhmann <joh@gmx.net> writes:
> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> Jochem Huhmann <joh@gmx.net> writes:
>>
>>> Hmm. Interesting. I upgraded to Oort some time ago and didn't knew that.
>>> I did notice though that ticked articles don't disappear in the summary
>>> even when the article has expired on my local nntp-server and I can't
>>> open them anymore.
>>
>> Are they also marked with `*'? Then they are cached. But they
>> should be readable...
>
> No, they only have a "!" and they're not readable. Hmm, I'll disable the
> agent and enter ticked articles I'd like to keep into the cache.
You don't have to disable the agent.
> Anyway, this looks like a misfeature or at least undesired behaviour to
> me. When the agent is enabled it should either automatically download
> and store ticked articles or toss the mark when the article is expired
> on the server.
That's right. I'm not sure if Kevin is reading this... Want to
report it to the Gnus mailing list?
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-12-02 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3d6ooxxx7.fsf@ccs.covici.com>
2002-11-30 3:05 ` Jesper Harder
2002-11-30 12:13 ` John Covici
[not found] ` <873cpjw7lh.fsf@nova.revier.com>
[not found] ` <84u1hzasf9.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <878yz9uxdg.fsf@nova.revier.com>
2002-12-02 7:53 ` Kai Großjohann [this message]
2002-12-02 17:33 ` Jochem Huhmann
[not found] ` <v9isyccmoe.fsf@marauder.physik.uni-ulm.de>
2002-12-02 18:59 ` Jochem Huhmann
2002-12-02 20:12 ` Kai Großjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84el90svpo.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@uni-duisburg.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).