From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: new emails are marked as read before reading!
Date: Tue, 20 Apr 2004 10:37:36 +0900 [thread overview]
Message-ID: <b9yfzazjuov.fsf@jpl.org> (raw)
In-Reply-To: <20040419235940.5cc21ce4.shigeki@mediawars.ne.jp>
>>>>> In <20040419235940.5cc21ce4.shigeki@mediawars.ne.jp>
>>>>> Shigeki UNO <shigeki@mediawars.ne.jp> wrote:
> Why Gnus sometimes or suddenly treats incoming new emails as read
> before I read them. Does anyone have same problem ?
> This is always annoying me. SIGH.
I think that should not occur if all mails are fetched by Gnus'
back end and being controlled by the Gnus' active file. If you
are using the nnml back end, you probably need to keep track of
how the ~/Mail/active file changes, comparing with article
numbers.
Furthermore, if there is an old active[1] file for persistent
articles in a group which you deleted and revived, it may
happen.
[1] It is ~/News/cache/active by default.
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2004-04-20 1:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 14:59 Shigeki UNO
2004-04-20 1:37 ` Katsumi Yamaoka [this message]
2004-04-20 6:26 ` Shigeki UNO
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=b9yfzazjuov.fsf@jpl.org \
--to=yamaoka@jpl.org \
/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).