Gnus development mailing list
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
Subject: Gnus does not reliably notice new mail deposited in IMAP groups by  nnimap-split-rule
Date: Thu, 05 Dec 2002 16:26:04 -0800	[thread overview]
Message-ID: <87smxc3sdf.fsf@egil.codesourcery.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]


Recently Gnus has stopped reliably noticing mail dropped into various
IMAP groups by the nnimap-split-rule.  I know that messages have been
put into the groups because I see the "IMAP split moved message ..."
go by in the echo area, but then the group selection buffer comes up
claiming that there is no new mail in these groups.  If I forcibly
select one of these groups (using 'L' to display the full list, for
instance) the mail does not show up either.  The only workaround I
have found is to quit Gnus, restart, and immediately use 'A A' to
reread the "active file".  This apparently has the side effect of
making Gnus actually look at what's on the server, rather than
whereever it's looking; but I then have to poke each group to see
if there are new messages, which is tedious, and it only works right
after Gnus starts. I turned the agent and the cache off, but this did
not help.  Neither does deleting .newsrc.eld.

I say 'recently' because up to about five days ago it was working just
fine.  I have no idea what changed.  Up till today I was using
whichever random CVS snapshot is in the Debian unstable 'gnus' package
right now; today I upgraded to CVS HEAD to see if that would help, but
it didn't.

zw

Oort Gnus v0.08
GNU Emacs 21.2.2 (i386-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2002-10-15 on raven, modified by Debian


[-- Attachment #2: User settings --]
[-- Type: application/emacs-lisp, Size: 2002 bytes --]

             reply	other threads:[~2002-12-06  0:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06  0:26 Zack Weinberg [this message]
2002-12-06  8:10 ` Niklas Morberg
2002-12-06 16:39   ` Zack Weinberg
2002-12-08 18:34     ` Zack Weinberg

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=87smxc3sdf.fsf@egil.codesourcery.com \
    --to=zack@codesourcery.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).