Gnus development mailing list
 help / color / mirror / Atom feed
From: "Georg C. F. Greve" <greve@gnu.org>
Cc: <ding@gnus.org>
Subject: Re: New mail appears to be old?!
Date: Thu, 27 Sep 2001 13:34:17 +0200	[thread overview]
Message-ID: <m3u1xouauz.fsf@reason.gnu-hamburg> (raw)
In-Reply-To: <Pine.LNX.4.33.0109261635280.23895-100000@lie.extundo.com> (Simon Josefsson's message of "Wed, 26 Sep 2001 16:41:02 +0200 (CEST)")


[-- Attachment #1.1: Type: text/plain, Size: 1362 bytes --]

 || On Wed, 26 Sep 2001 16:41:02 +0200 (CEST)
 || Simon Josefsson <jas@extundo.com> wrote: 

 >> 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.

 sj> Does the group show up as having unread articles, but when you
 sj> enter it, only some of those new articles are displayed?  

No, sometimes groups (no recognizable pattern) do not show up having
new articles, although they clearly have messages I didn't see yet.

 sj> Or doesn't even the group buffer reflect that you have new mail?

Yes, sometimes, some groups do not reflect that they contain new mail.

 sj> In the first case, either you may have corrupt active or nov
 sj> files, or there may be a bug in the new marks stuff.

I'v tried regenerating the nov databases to no avail.

 sj> In the latter case, I have no idea.  It seems very weird.  Maybe
 sj> mail gets corrupted somehow, and end up being concatenated to
 sj> each other instead of being filed as individual articles, or
 sj> something like that.

Unlikely, I'm using nnml.

 sj> What is your setup, nnml, nnfolder, mail-sources etc?

Here is my cleaned .gnus file (got rid of the personal stuff):

[-- Attachment #1.2: gnus.el --]
[-- Type: application/emacs-lisp, Size: 24368 bytes --]

[-- Attachment #1.3: Type: text/plain, Size: 335 bytes --]


If there is anything else I can do to help tracking down the bug,
please let me know.

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve@gnu.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)

[-- Attachment #2: Type: application/pgp-signature, Size: 268 bytes --]

  reply	other threads:[~2001-09-27 11:34 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 [this message]
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
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=m3u1xouauz.fsf@reason.gnu-hamburg \
    --to=greve@gnu.org \
    --cc=ding@gnus.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).