From: Zack Weinberg <zack@codesourcery.com>
Cc: Zack Weinberg <zack@codesourcery.com>, ding@gnus.org
Subject: Re: Gnus does not reliably notice new mail deposited in IMAP groups by nnimap-split-rule
Date: Fri, 6 Dec 2002 08:39:37 -0800 [thread overview]
Message-ID: <20021206163937.GA27966@egil.codesourcery.com> (raw)
In-Reply-To: <uwumntvnu.fsf@axis.com>
On Fri, Dec 06, 2002 at 09:10:29AM +0100, Niklas Morberg wrote:
> Zack Weinberg <zack@codesourcery.com> writes:
>
> > Recently Gnus has stopped reliably noticing mail dropped
> > into various IMAP groups by the nnimap-split-rule.
>
> I've seen this a lot, but just pressing `g' one more time in
> the Group buffer helps me. The problem (I don't consider it
> a major one) has been there for at least a month, probably
> longer.
For me, pressing 'g' again has no effect.
I should add that this isn't a problem with splitting. I commented
that out of .gnus, so that everything should wind up in INBOX, and
Gnus still doesn't see any new mail come in.
zw
next prev parent reply other threads:[~2002-12-06 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 0:26 Zack Weinberg
2002-12-06 8:10 ` Niklas Morberg
2002-12-06 16:39 ` Zack Weinberg [this message]
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=20021206163937.GA27966@egil.codesourcery.com \
--to=zack@codesourcery.com \
--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).