Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: 'g' not checking nnimap groups
Date: Tue, 04 Apr 2006 15:50:39 +0200	[thread overview]
Message-ID: <87y7ylbgb4.fsf@latte.josefsson.org> (raw)
In-Reply-To: <smuirppmp1q.fsf@linuxpal.mit.edu> (gdt@work.lexort.com's message of "Tue, 04 Apr 2006 09:46:25 -0400")

gdt@work.lexort.com writes:

> I have in .emacs
>
> (setq gnus-secondary-select-methods
>       '((nnimap "my.logical.domain"
> 		(nnimap-address "my.server.edu")
> 		(nnimap-port 993)
> 		(nnimap-stream ssl)
> 		(nnimap-authenticator login)
> 		)))
>
> and G e showed (nnimap "my.logical.domain")

That is the problem then.

> imap-log when doing g gets lots of blocks like
...
> I had a number of groups with bad method, and after hunting them down
> from *imap-log* I now get just STATUS queries.

Yup.

> So I guess there's a bug where (nnimap "foo") does a slow status
> check.  And, it seems that if there is such a group sometimes the
> other groups on the server do not get checked.

Actually, the bug is how (nnimap "foo") ever got into your setup.

The server (nnimap "foo") isn't the same as (nnimap "foo" (nnimap-port
...) ...), and Gnus will treat them as different servers.
Consequently, (nnimap "foo") is treated as an ephemeral server, and
checked using the slow mechanism (I forgot the reason as to why, but
it is probably because it is simpler to optimize the primary/secondary
case).



  reply	other threads:[~2006-04-04 13:50 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 ` 'g' not checking nnimap groups gdt
2006-03-25 12:54   ` 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 [this message]
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=87y7ylbgb4.fsf@latte.josefsson.org \
    --to=jas@extundo.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).