From: Greg Troxel <gdt@work.lexort.com>
To: ding@gnus.org
Subject: Re: sluggish IMAP updating?
Date: Thu, 24 May 2007 08:11:13 -0400 [thread overview]
Message-ID: <smu3b1mto9q.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <87wsyyzb9p.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Thu, 24 May 2007 13:55:30 +0200")
Simon Josefsson <simon@josefsson.org> writes:
> Greg Troxel <gdt@work.lexort.com> writes:
>
>> [gnus/dovecot doesn't notice new messages right away]
>
> Does toggling nnimap-need-unselect-to-notice-new-mail help?
Yes, that seems to fix the problem. From *imap-log*, I can see that
STATUS was returning no new messages, but after UNSELECT, it gives the
right status.
So, is dovecot broken, or gnus? I am not familiar enough with the IMAP
spec to know if dovecot is wrong for failing to report new mail that has
arrived on a selected mailbox since the selection. With ACID hat on it
seems somewhat reasonable of dovecot conceptually, but not really ("SET
IMAP ISOLATION LEVEL READ COMMITTED" :-).
I realize this may be a deoptimization, but it would seem best for gnus
to UNSELECT a mailbox when the user exits from the group and the summary
buffer is destroyed. That may let the imap free resources, and seems
like a good idle state.
next prev parent reply other threads:[~2007-05-24 12:11 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
2007-05-24 12:11 ` Greg Troxel [this message]
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=smu3b1mto9q.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.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).