recent problem with IMAP counts

recent problem with IMAP counts

[Didier Verna]

  Hello,

I upgraded Gnus recently (sometime last week) and I have a new problem:
when I start Gnus, it seems unable to get IMAP counts. The number of
unread messages displays '*' for all groups in the group buffer, the
total display '0' etc. No error message, everything seems to work fine
apart from that. In the server buffer, all backend show as 'open'.
Closing and re-opening doesn't change anything.

If I hit M-g on every group individually, I get the correct numbers
displayed, I can read the new messages etc. However, as soon as I hit
'g' again, this information is lost.

The other backends seem unaffected: I have a couple of nntp or nnrss
groups that work fine.


Any ideas ?

Note: I'm runnning Gnus in XEmacs 21.5b31

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com

Re: recent problem with IMAP counts

[Steinar Bang]

>>>>> Didier Verna <didier@xemacs.org>:

> I upgraded Gnus recently (sometime last week) and I have a new
> problem: when I start Gnus, it seems unable to get IMAP counts. The
> number of unread messages displays '*' for all groups in the group
> buffer,

If you do `^' to enter the server buffer, do any of your servers show up
as closed or offline?  If so, try to use `O' to open them and then go
back to the Group buffer, and press `g'.

It happens at startup on one of my gnusen that still runs on emacs22.

Re: recent problem with IMAP counts

[Didier Verna]

Steinar Bang <sb@dod.no> wrote:

> If you do `^' to enter the server buffer, do any of your servers show
> up as closed or offline? If so, try to use `O' to open them and then
> go back to the Group buffer, and press `g'.

  Nope, they're all open. I tried closing and re-opening them.

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com

Re: recent problem with IMAP counts

[Eric S Fraga]

Didier Verna <didier@xemacs.org> writes:

>   Hello,
>
> I upgraded Gnus recently (sometime last week) and I have a new problem:
> when I start Gnus, it seems unable to get IMAP counts. The number of
> unread messages displays '*' for all groups in the group buffer, the
> total display '0' etc. No error message, everything seems to work fine
> apart from that. In the server buffer, all backend show as 'open'.
> Closing and re-opening doesn't change anything.
>
> If I hit M-g on every group individually, I get the correct numbers
> displayed, I can read the new messages etc. However, as soon as I hit
> 'g' again, this information is lost.
>
> The other backends seem unaffected: I have a couple of nntp or nnrss
> groups that work fine.
>
>
> Any ideas ?
>
> Note: I'm runnning Gnus in XEmacs 21.5b31

What is the value of gnus-activate-level and the levels of your groups?

-- 
Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D)

Re: recent problem with IMAP counts

[Giuseppe 'ferdy' Miceli]

[looks like this post doesn't show up in list via gmane. try to resend it]

>>>>> "ESF" == Eric S Fraga <e.fraga@ucl.ac.uk> writes:

    ESF> Didier Verna <didier@xemacs.org> writes:
    >> Hello,
    >> 
    >> I upgraded Gnus recently (sometime last week) and I have a new
    >> problem: when I start Gnus, it seems unable to get IMAP
    >> counts. The number of unread messages displays '*' for all groups
    >> in the group buffer, the total display '0' etc. No error message,
    >> everything seems to work fine apart from that. In the server
    >> buffer, all backend show as 'open'.  Closing and re-opening
    >> doesn't change anything.
    >> 
    >> If I hit M-g on every group individually, I get the correct
    >> numbers displayed, I can read the new messages etc. However, as
    >> soon as I hit 'g' again, this information is lost.
    >> 
    >> The other backends seem unaffected: I have a couple of nntp or
    >> nnrss groups that work fine.
    >> 
    >> 
    >> Any ideas ?
    >> 
    >> Note: I'm runnning Gnus in XEmacs 21.5b31

    ESF> What is the value of gnus-activate-level and the levels of your
    ESF> groups?

that's something happening to me as well.

i have seven imap accounts configured within gnus in the same fashion:
the inbox folders are set to level one, all the other folders are set to level three.

gnus displays correctly the nnimap level one groups, whilst showing stars
for level three ones. on server buffer all the backend are correctily open.
M-g fix the issue. other backends don't show such behaviour.

gnus-activate-level is default to six. i currently run no gnus v0.18 in
aquamacs 2.4 (which is based on emacs 23.3.50.1), but i had the issue
with aquamacs 2.3 and emacs up to 24.0.91.1.

--
Giuseppe `ferdy` Miceli
"If you do know that here is one hand, we'll grant you all the rest."

Re: recent problem with IMAP counts

[Didier Verna]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> What is the value of gnus-activate-level and the levels of your
> groups?

  6, and my groups are between 1 and 3. I haven't changed my
configuration in a while, so I suspect a bug was introduced somewhere.
I'll try to bissect when I find the time.

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com

Re: recent problem with IMAP counts

[Didier Verna]

       I found the culprit. The culprit is:

didier(pts/0)% git log -1 -p -r 90c1f88e5357d61a732d6f78d3c9a0278d78f49e
commit 90c1f88e5357d61a732d6f78d3c9a0278d78f49e (refs/bisect/bad)
Author: Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org>
Date:   Thu Jun 30 01:09:38 2011 +0200

    Bail out in nnimap if the server has closed the connection.

diff --git a/lisp/nnimap.el b/lisp/nnimap.el
index 2cfc889..e78c20b 100644
--- a/lisp/nnimap.el
+++ b/lisp/nnimap.el
@@ -1227,6 +1227,10 @@ textual parts.")
 
 (deffoo nnimap-finish-retrieve-group-infos (server infos sequences)
   (when (and sequences
+            ;; Check that the process is still alive.
+            (get-buffer-process (nnimap-buffer))
+            (memq (process-status (get-buffer-process (nnimap-buffer)))
+                  '(open run))
             (nnimap-possibly-change-group nil server))
     (with-current-buffer (nnimap-buffer)
       ;; Wait for the final data to trickle in.


But in fact, the problem is more complicated than I thought. I
eventually figured out that it's one of my nnimap servers that causes
the problem, and the problem exhibits different symptoms before and
after this revision of Gnus. I have two nnimap servers in Gnus (one on
gmail, the other somewhere else; I think it uses Zimbra).

Before this revision of Gnus, it sync'ed with gmail all right at
startup, and then it hung on the other server. The minibuffer displayed
"Retrieving ... [0%]" flashing and blinking all over the place. I had to
C-g on it and only then got my Group buffer. The gmail account had the
correct info, but not the other one.

Now, with the current HEAD, Gnus startup doesn't hang anymore, but none
of the servers get the correct information. If I remove the problematic
server from my secondary select methods, everything's fine again.

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com

Re: recent problem with IMAP counts

[Steinar Bang]

>>>>> Didier Verna <didier@xemacs.org>:

> But in fact, the problem is more complicated than I thought. I
> eventually figured out that it's one of my nnimap servers that causes
> the problem, and the problem exhibits different symptoms before and
> after this revision of Gnus. I have two nnimap servers in Gnus (one on
> gmail, the other somewhere else; I think it uses Zimbra).

Zimbra has been a problem with the new nnimap.  I don't remember exactly
what the problem was, but it was related to QRESYNC, and I think one
version of zimbra requiring two spaces in a place where a newer version
of zimbra requires a single space (but not tolerating two spaces), and
nothing in the zimbra responses saying what version of zimbra you're
talking to (or something like that...).

Re: recent problem with IMAP counts

[Lars Magne Ingebrigtsen]

Didier Verna <didier@xemacs.org> writes:

>    (when (and sequences
> +            ;; Check that the process is still alive.
> +            (get-buffer-process (nnimap-buffer))
> +            (memq (process-status (get-buffer-process (nnimap-buffer)))
> +                  '(open run))
>              (nnimap-possibly-change-group nil server))

Ah, yeah.  That's not correct.  It checks the process status of the
previous server.

I've pushed out a fix for this now.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/