Gnus development mailing list
 help / color / mirror / Atom feed
From: gdt@work.lexort.com
Subject: 'g' not checking nnimap groups
Date: Thu, 23 Mar 2006 10:06:44 -0500	[thread overview]
Message-ID: <smu7j6l2oaj.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <x7fylbruq1.fsf@davestoy.homelinux.org> (Dave Goldberg's message of "Tue, 21 Mar 2006 23:04:06 -0500")

I'm running Gnus from cvs head this morning with emacs 21.3 (on
NetBSD/i386).

I am mostly reading mail, and have an nnimap secondary select method,
but also one newsgroup at news.mit.edu.

I have turned off the agent on my nnimap select method; I found (with
an earlier release) that articles deleted from the imap folders still
appeared locally, and I consider this bad behavior, or at least not
what I want.

The 'g' command in the *Group* buffer behaves inconsistently.
Sometimes it checks all of my nnimap groups, but often it just checks
nnimap+work.lexort.com:lists.ding   This is the most recently added,
but not the last in the *Group* buffer.

In *imap-log*, I get this on hitting g:

539 UID SEARCH UNSEEN UNDELETED
* SEARCH
539 OK Search completed.
540 UID SEARCH SEEN
* SEARCH 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84
540 OK Search completed.
541 UID SEARCH FLAGGED
* SEARCH 1 2 41
541 OK Search completed.
542 UID SEARCH ANSWERED
* SEARCH 4
542 OK Search completed.
543 UID SEARCH RECENT
* SEARCH
543 OK Search completed.
544 FETCH 1,* UID
* 1 FETCH (UID 1)
* 84 FETCH (UID 84)
544 OK Fetch completed.
545 STATUS "lists.ding" (UNSEEN)
* STATUS "lists.ding" (UNSEEN 0)
545 OK Status completed.
546 EXPUNGE
546 OK Expunge completed.

This indicates to me that the imap connection was already selected,
and that only that one group was checked.

If I do ^U 1 g, I get the following:

555 STATUS "Inbox" (uidvalidity uidnext unseen)
* STATUS "Inbox" (UIDNEXT 351 UIDVALIDITY 1141579755 UNSEEN 0)
555 OK Status completed.

and ^U 2 g gets me:

556 STATUS "misc.gdt-cvs" (uidvalidity uidnext unseen)
557 STATUS "family.foobar" (uidvalidity uidnext unseen)
558 STATUS "Inbox" (uidvalidity uidnext unseen)
* STATUS "misc.gdt-cvs" (UIDNEXT 5 UIDVALIDITY 1142461155 UNSEEN 0)
556 OK Status completed.
* STATUS "family.foobar" (UIDNEXT 2 UIDVALIDITY 1141827703 UNSEEN 0)
557 OK Status completed.
* STATUS "Inbox" (UIDNEXT 351 UIDVALIDITY 1141579755 UNSEEN 0)
558 OK Status completed.


Sometimes, g checks all my nnimap groups, but usually it doesn't.

Questions arising:

  Am I correct in thinking g should query all groups?

  Is there some hairy IMAP register-for-notifications scheme in use,
  and gone wrong?


-- 
	Greg Troxel <gdt@work.lexort.com>



  parent reply	other threads:[~2006-03-23 15:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22  4:04 Problems with attachments in S/MIME encrypted messages from Outlook Dave Goldberg
2006-03-22  9:53 ` Simon Josefsson
2006-03-22 12:13   ` Dave Goldberg
2006-03-23 15:06 ` gdt [this message]
2006-03-25 12:54   ` 'g' not checking nnimap groups Simon Josefsson
2006-04-04  0:25     ` gdt
2006-04-04 12:36       ` Simon Josefsson
2006-04-04 13:46         ` gdt
2006-04-04 13:50           ` Simon Josefsson
2006-04-04 14:54             ` gdt
2006-04-04 16:37               ` Simon Josefsson

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=smu7j6l2oaj.fsf@linuxpal.mit.edu \
    --to=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).