Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: <ding@gnus.org>
Subject: Re: IMAP to Exchange hangs: NO Connect filed: server may be down or too busy to respond
Date: Wed, 01 Feb 2006 13:49:00 +0100	[thread overview]
Message-ID: <iluhd7jz1kz.fsf@latte.josefsson.org> (raw)
In-Reply-To: <86wtggdsix.fsf@PECTOPAH.shenton.org> (Chris Shenton's message of "Tue, 31 Jan 2006 15:57:58 -0500")

Chris Shenton <chris@shenton.org> writes:

> I've tried to make it avoid anything but the INBOX tree using
> nnimap-list-pattern as below:
>
>   (setq gnus-select-method
>       '(nnimap "hemi"                ; use ~/.authinfo for user/passwd
>              (nnimap-address "mail01.ndc.nasa.gov")
>              (nnimap-stream ssl)
>              (nnimap-list-pattern ("INBOX"))
>              ))
>
> but *imap-log* is still showing it querying other mailbox hierarchies
> including the broken one, 302 below:
>
>   301 STATUS "INBOX/saved/zope" (uidvalidity uidnext unseen)
>   302 STATUS "Public Folders/Aelita EMW Recycle Bin" (uidvalidity uidnext unseen)
>   303 STATUS "Public Folders/Internet Newsgroups" (uidvalidity uidnext unseen)
>   ...
>   301 OK STATUS completed.
>   302 NO Connect attempt failed: server may be down or too busy to respond.
>
>
> Is gnus ignoring the list-pattern or am I missing something?

Are you subscribed to that particular group?  Try C-k it.

> And is there a way to get gnus to recover from the "NO" response about
> a group? 

I agree that it should recover more gracefully.  Patches welcome...
I'm not sure how it could be implemented though.



  reply	other threads:[~2006-02-01 12:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31 18:20 Chris Shenton
2006-01-31 20:57 ` Chris Shenton
2006-02-01 12:49   ` Simon Josefsson [this message]
2006-02-01 14:00     ` Chris Shenton

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=iluhd7jz1kz.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).