From: Michael Welle <m.welle@gmx.net>
Subject: Re: Messages marked as ancient without apparent reason
Date: Sun, 18 Dec 2005 10:56:09 +0100 [thread overview]
Message-ID: <873bkqloee.fsf@buerbach048.buerbach.wohnheim.uni-siegen.de> (raw)
In-Reply-To: <8764u0aakr.fsf@debian.IGP>
Hi Andreas,
Andreas Goesele <goesele@hfph.mwn.de> writes:
> Hi!
>
> I had asked this question before, I have looked through the google
> archives, I have studied the manual but I don't find an answer to a
> problem I have had right from the time I started to use gnus up to
> 5.10.6:
>
> Every now and then (mostly on weekends?) *part* (the majority) of the
> older but *not* read messages are marked as ancient with an O. This is
> strange for two reasons: 1. I neither read them nor marked them as
> read. 2. If I enter a group without prefix I normally don't see any
> ancient messages, I have to enter C-u before entering to see the
> ancient messages.
have you solved the problem? I am aware of the problem since my
transition from an external news server to a local leafnode. I guess
there is an interdependency. Any hints are greatly appreciated.
Michael
--
We're back to the times when men were men and wrote their own device drivers
Linus Torvalds
prev parent reply other threads:[~2005-12-18 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8764u0aakr.fsf@debian.IGP>
2005-08-20 20:06 ` William F Hammond
2005-12-18 9:56 ` Michael Welle [this message]
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=873bkqloee.fsf@buerbach048.buerbach.wohnheim.uni-siegen.de \
--to=m.welle@gmx.net \
/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).