From: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org
Subject: Re: Problem starting nnimap unplugged
Date: 12 Feb 2001 17:41:24 +0100 [thread overview]
Message-ID: <ilu8znbam6j.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <m1bofw7lxmm.fsf@blackbird.mitre.org> (dsg@world.std.com's message of "12 Feb 2001 10:38:41 -0500")
dsg@world.std.com (David S. Goldberg) writes:
> Gnus appeared to hang interminably long. Eventually I gave up with
> a C-g.
A backtrace from here would help (`toggle-debug-on-quit', or perhaps
`toggle-debug-on-signal' is required).
> My guess is that nnimap is trying to do authentication even in
> unplugged mode. When I got to the hotel and dialed up my company's
> modem pool, I was able to run gnus-unplugged with no hanging but
> nnimap did authenticate me to the server. I tried this repeatedly;
> running gnus-unplugged while connected and not. When not connected
> it hangs. Is there a workaround?
Nnimap isn't called by Gnus at all in unplugged mode. A guess would
be that somehow some of your groups contain a select method not
matching the agentized one, and thus making Gnus open another nnimap
server which would not be under the agent, and that this nnimap hangs
trying to talk to the server.
(Type `G e' on your nnimap groups in the server buffer, it should say
"nnimap:foo" or something similar. The complete select method from
g-s-s-methods should also be ok, but `(nnimap "foo")' when your server
is really called `(nnimap "foo" (nnimap-foo something...))' is bad.)
next prev parent reply other threads:[~2001-02-12 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 15:38 David S. Goldberg
2001-02-12 16:41 ` Simon Josefsson [this message]
2001-02-12 16:50 ` ShengHuo ZHU
2001-02-12 16:53 ` ShengHuo ZHU
2001-02-12 18:25 ` Björn Torkelsson
2001-02-12 18:37 ` ShengHuo ZHU
2001-02-13 16:30 ` David S. Goldberg
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=ilu8znbam6j.fsf@barbar.josefsson.org \
--to=simon@josefsson.org \
--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).