From: Harry Putnam <reader@newsguy.com>
Subject: Re: New mail appears to be old?!
Date: Wed, 26 Sep 2001 08:28:06 -0700 [thread overview]
Message-ID: <m1g09ahszd.fsf@reader.newsguy.com> (raw)
In-Reply-To: <m3vgi6oy7v.fsf@reason.gnu-hamburg> ("Georg C. F. Greve"'s message of "Wed, 26 Sep 2001 15:53:08 +0200")
"Georg C. F. Greve" <greve@gnu.org> writes:
> Hi all,
>
> in the CVS version of GNUS I suddenly experience a rather unwanted and
> annoying phenomenon: after getting new mail, only some part of the new
> mail is marked as new/unread and makes the groups show up in the group
> buffer as groups with new mail.
>
> This means I need to go through all buffers in order to find out
> whether there is something new by looking for unfamiliar mail. This is
> not good as it significantly increases the risk to miss new mail.
>
> Does anyone else experience something similar? Although it may not be
> correlated, I believe this behaviour may have begun when I started
> using nndiary.
>
> If there is anything I can supply to help you guys find the bug,
> please let me know.
I did see such behaviour at one point. But in my case all new mail
was marked as read. It turned out to be a rogue entry in
~/News/cache/active for the nnml group I use to preview new mail. I
removed that entry from ~/News/cache/active and the behavior stopped.
Later on (days) it reappeared in ~/News/cache/active and I removed
it again. Never did see what caused that particular group to show up
in that active file.
Several cvs updates later I haven't seen the behavior now for a couple
weeks.
PS- I don't use nndiary and never did.
PPS- As a timely test for your current problem, you can view
the new mail files that gnus creates for you in ~/Mail/Incoming* with
G f (nndoc) to see what was actually collected in a retrieval by
`G f Mail/MOST_RECENT_Incoming*'. Unless you've turned it off with:
(setq mail-source-delete-incoming t)
next prev parent reply other threads:[~2001-09-26 15:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 13:53 Georg C. F. Greve
2001-09-26 14:41 ` Simon Josefsson
2001-09-27 11:34 ` Georg C. F. Greve
2001-09-27 14:14 ` Harry Putnam
2001-09-28 11:28 ` Georg C. F. Greve
2001-09-29 20:29 ` Georg C. F. Greve
2001-10-01 8:07 ` Didier Verna
2001-09-26 15:28 ` Harry Putnam [this message]
2001-09-27 1:28 ` Dan Christensen
2001-09-27 3:46 ` Harry Putnam
2001-09-27 8:28 ` Simon Josefsson
2001-09-27 11:13 ` Andreas Büsching
2001-09-29 19:17 ` Dan Christensen
2001-09-30 4:37 ` Karl Eichwalder
2001-09-30 11:22 ` Simon Josefsson
2001-09-30 12:31 ` Karl Eichwalder
2001-09-30 13:22 ` Kai Großjohann
2001-09-30 12:53 ` Karl Eichwalder
2001-10-01 10:31 ` Georg C. F. Greve
2001-10-01 11:54 ` Kai Großjohann
2001-10-01 16:36 ` Georg C. F. Greve
2001-09-30 12:02 ` Georg C. F. Greve
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=m1g09ahszd.fsf@reader.newsguy.com \
--to=reader@newsguy.com \
/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).