Gnus development mailing list
 help / color / mirror / Atom feed
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 17:18:59 +0200	[thread overview]
Message-ID: <87myzuxna4.fsf@mocca.josefsson.org> (raw)
In-Reply-To: <smufy5mi7b7.fsf@linuxpal.mit.edu> (Greg Troxel's message of "Thu\, 24 May 2007 11\:13\:00 -0400")

Greg Troxel <gdt@work.lexort.com> writes:

> Simon Josefsson <simon@josefsson.org> writes:
>
>>> The word from dovecot is that STATUS on a selected mailbox is SHOULD NOT
>>> to start with, and MUST NOT to check for new mail.  See 6.3.10 of
>>> RFC3501.
>>>
>>> http://dovecot.org/pipermail/dovecot/2007-May/023045.html
>>>
>>> Plus, doing lots of STATUS commands seems to be disfavored but I don't
>>> understand IMAP well enough to understand.
>>
>> nnimap was written when RFC 2060 was current, and we haven't really
>> updated it for RFC 3501.  I suspect the notes in 6.3.10 was added as a
>> result of nnimap and other implementations behaviour, but the problem is
>> that I don't know of a good way to implement this in Gnus without using
>> STATUS (and, alas, I wouldn't have time to implement anything even if I
>> had some ideas).  Note that I cannot see that RFC 3501 allows servers to
>> respond with incorrect data in this situation, which dovecot appears to
>> be doing.
>
> The dovecot people talk about 'synchronizing the mailbox', and
> apparently they are in an implementation bind because they aren't
> allowed to clear recent flags.
>
> I see your point, but the RFC says "MUST NOT" use STATUS on a selected
> mailbox to check for new mail.

RFC 2060 didn't, and nnimap was written for that RFC.  Ideally, someone
could revise nnimap to make it more modern.

> I think one is supposed to use SEARCH RECENT, but I really  just barely
> understand imap.

Alternatively use something like the IDLE extension.  Or issue a NOOP.

>> I don't have a strong opinion on what the default should be.  If others
>> think it is safer to let it be t by default, by all means change it.
>
> Someone else was having trouble with courier imap, so this seems not to
> just be a dovecot issue.   I'd favor safety over efficiency.   for me
> 'g' takes a while and does 100 STATUS checks, so an unselect hardly
> seems like a big deal.

The unselect happens in a few other situations too, though, which could
trigger other kind of bugs.

Still, let's try it for a while.  I have installed it in CVS.

Heads up: if anyone notices that nnimap has become significantly slower
and/or some new IMAP is showing up that can be traced to this change,
let us know!

/Simon



  reply	other threads:[~2007-05-24 15:18 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
2007-05-24 15:00     ` Simon Josefsson
2007-05-24 15:13       ` Greg Troxel
2007-05-24 15:18         ` Simon Josefsson [this message]
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=87myzuxna4.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).