From: Simon Josefsson <simon@josefsson.org>
To: Greg Troxel <gdt@work.lexort.com>
Cc: ding@gnus.org
Subject: Re: sluggish IMAP updating?
Date: Thu, 24 May 2007 13:55:30 +0200 [thread overview]
Message-ID: <87wsyyzb9p.fsf@mocca.josefsson.org> (raw)
In-Reply-To: <smuzm3vjvfp.fsf@linuxpal.mit.edu> (Greg Troxel's message of "Wed\, 23 May 2007 13\:34\:18 -0400")
Greg Troxel <gdt@work.lexort.com> writes:
> I use gnus (head of cvs) in emacs 21.4 on NetBSD 3.1ish and 4.0ish, with
> my mail in IMAP via dovecot (1.0.0). I use gnome's mail-notification
> and sometimes run thunderbird as well. Generally this works well.
>
> Typically when new mail arrives I'll notice because of mail-notification
> (which is using IMAP's idle extension and thus notices new mail
> promptly). I keep a gnus instance running all day, usually sitting in
> the *Group* buffer, and I'll type 'g'. Usually INBOX will show new
> messages, and selecting it will let me reaad them as you'd expect.
> Fairly often (perhaps 1 in 4?), typing g will result in INBOX showing 0
> messages still. In these cases, entering the group, exiting it, and
> then retyping 'g' will show non-zero messages and I can then enter and
> read them. In these cases thunderbird shows new mail just fine.
>
> I know gnus doesn't push read marks back to the server until the group
> is exited, and I wonder if there's some other kind of synchroniziation
> issue. I'll enable imap logging and look at this, but I wanted to ask
> if anyone else is seeing this, with dovecot, or with any other IMAP
> server.
Does toggling nnimap-need-unselect-to-notice-new-mail help?
/Simon
next prev parent reply other threads:[~2007-05-24 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 17:34 Greg Troxel
2007-05-24 7:13 ` Gabor Z. Papp
2007-05-24 11:55 ` Simon Josefsson [this message]
2007-05-24 12:11 ` Greg Troxel
2007-05-24 15:00 ` Simon Josefsson
2007-05-24 15:13 ` Greg Troxel
2007-05-24 15:18 ` Simon Josefsson
2007-05-24 15:43 ` Greg Troxel
2007-05-24 13:50 ` Greg Troxel
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=87wsyyzb9p.fsf@mocca.josefsson.org \
--to=simon@josefsson.org \
--cc=ding@gnus.org \
--cc=gdt@work.lexort.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).