Re: the Exchange 2007 fix

[Simon Josefsson <simon@josefsson.org>]

Jake Colman <colman@ppllc.com> writes:

>    SJ> So maybe this patch would work better?  However, it doesn't take care of
>    SJ> the imap.el problems you mentioned in that thread.  Perhaps the
>    SJ> bug-workaround variable should be a imap.el variable rather than a
>    SJ> nnimap.el variable?  Hm.
>
>    SJ> --- nnimap.el   01 Apr 2008 16:27:27 +0200      7.45
>    SJ> +++ nnimap.el   02 Apr 2008 00:38:11 +0200
>    SJ> @@ -568,7 +568,7 @@
>    SJ>               (imap-mailbox-select group examine))
>    SJ>        (let (minuid maxuid)
>    SJ>         (when (> (imap-mailbox-get 'exists) 0)
>    SJ> -         (imap-fetch (if nnimap-enable-minmax-bug-workaround "1:*" "1,*")
>    SJ> +         (imap-fetch (if nnimap-enable-minmax-bug-workaround "1,*:*" "1,*")
>    SJ>                       "UID" nil 'nouidfetch)
>    SJ>           (imap-message-map (lambda (uid Uid)
>    SJ>                               (setq minuid (if minuid (min minuid uid) uid)
>
> I've applied this patch and it works - but I don't think I see any
> performance improvement.
>
> For example, when I enter a group with a very large number of read
> messages and only 2 or 3 unread messages, I see the following message
> for an extended period of time:
>
> nnimap: Updating info for nnimap+exchange-d01:INBOX/Principia...
>
> For the record, I am not using nnimap.el from cvs.  Instead I patched my
> own copy of nnimap.el from two weeks ago to use "1,*:*".  I don't think
> there is any other substantive change that I missed.

What's in *imap-log* if you enable imap-log after this has happened?

For the 1,*:* command do you get a two-line response or a many-line
response?

/Simon