Problem starting nnimap unplugged

Problem starting nnimap unplugged

[David S. Goldberg]

I use an nnimap server as a secondary select method.  For a trip last
week, I decided to finally give the agent a try now that I've
discovered cygwin and XEmacs running under it.  I copied over my
startup files to my cygwin home directory, modified my .gnus to call
gnus-agentize per the info, ran xemacs and gnus, and set up two
categories.  I changed the default predicate to false and in the fetch
category, predicate is set to true.  I added six groups to the fetch
category and ran J s to fetch the articles in those groups.  I
verified by looking at the agent directory structure and went home
happy.  I'm fairly certain that that's all I needed to do according to
the info.  On the plane I tried to run M-x gnus-unplugged.  Gnus
appeared to hang interminably long.  Eventually I gave up with a C-g.
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?

Thanks,
-- 
Dave Goldberg
dsg@world.std.com

Re: Problem starting nnimap unplugged

[Simon Josefsson]

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

Re: Problem starting nnimap unplugged

[ShengHuo ZHU]

Simon Josefsson <simon@josefsson.org> writes:

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

`toggle-debug-on-quit' may not exist on XEmacs, 
use (setq debug-on-quit t) instead.

`toggle-debug-on-signal' does not exist, 
use (setq debug-on-signal t).

Of course, unless you've defined your own functions with these names.

ShengHuo

-- 
(setq gnus-posting-styles 
      '((".*" (signature (format "(setq gnus-posting-styles 
      '%S)" gnus-posting-styles)))))

Re: Problem starting nnimap unplugged

[ShengHuo ZHU]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> Simon Josefsson <simon@josefsson.org> writes:
> 
> > 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).
> 
> `toggle-debug-on-quit' may not exist on XEmacs, 
> use (setq debug-on-quit t) instead.
> 
> `toggle-debug-on-signal' does not exist, 
> use (setq debug-on-signal t).

Oops, they does exist on XEmacs.

ShengHuo

-- 
(setq gnus-posting-styles 
      '((".*" (signature (format "(setq gnus-posting-styles 
      '%S)" gnus-posting-styles)))))

Re: Problem starting nnimap unplugged

[Björn Torkelsson]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> > > A backtrace from here would help (`toggle-debug-on-quit', or perhaps
> > > `toggle-debug-on-signal' is required).
> > 
> > `toggle-debug-on-quit' may not exist on XEmacs, 
> > use (setq debug-on-quit t) instead.
> > 
> > `toggle-debug-on-signal' does not exist, 
> > use (setq debug-on-signal t).
> 
> Oops, they does exist on XEmacs.

Only in recent xemacs packages (toggle-*) was added to the xemacs-base
package last october.

/torkel

Re: Problem starting nnimap unplugged

[ShengHuo ZHU]

torkel@acc.umu.se (Björn Torkelsson) writes:

> ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> 
> > > > A backtrace from here would help (`toggle-debug-on-quit', or perhaps
> > > > `toggle-debug-on-signal' is required).
> > > 
> > > `toggle-debug-on-quit' may not exist on XEmacs, 
> > > use (setq debug-on-quit t) instead.
> > > 
> > > `toggle-debug-on-signal' does not exist, 
> > > use (setq debug-on-signal t).
> > 
> > Oops, they does exist on XEmacs.
> 
> Only in recent xemacs packages (toggle-*) was added to the xemacs-base
> package last october.

I thought I did not find it when I checked it last time.  My memory
still works :-)

But sometimes my grammar checker doesn't work :-(

ShengHuo

-- 
(setq gnus-posting-styles 
      '((".*" (signature (format "(setq gnus-posting-styles 
      '%S)" gnus-posting-styles)))))

Re: Problem starting nnimap unplugged

[David S. Goldberg]

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

Actually, that wasn't necessary.  I debugged it by trying
gnus-unplugged while connected to the network and noticed that gnus
was connecting to my secondary imap server and an nntp server but not
to the agentized imap server.  I clearly didn't understand that
gnus-unplugged still tries to connect to these on the network and that
is apparently where things were hanging up.  In retrospect it should
have been obvious that gnus-unplugged would only attempt to treat
agentized groups specially but a warning to that effect in the
documentation might be in order in case I'm not the only luser who
misunderstands that.  I've now added them to the agent and things are
working OK.

Thanks,
-- 
Dave Goldberg
dsg@world.std.com