Re: nnimap - not quite there yet?

[prj@po.cwru.edu (Paul Jarc)]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Gnus recognizes a secondary server by its presence in
> gnus-secondary-select-methods.  The treatment of a secondary server
> differs from a foreign server in that Gnus checks for new groups on
> secondary servers, but not on foreign ones.

WIBNI this behavior could be configured independently of how the
server was created?

>> Example: I added an nntp group and set the level to 3.  My
>> gnus-activate-level is set to 1.  When I run gnus-group-get-new-news
>> this new group does not get queried.  That's what I'd like to have
>> happen with my lower-level IMAP folders.
> 
> It's what should happen automatically.  If it doesn't happen, I think
> that's a bug in nnimap.

Backends don't know anything about levels.  Well, nnfoo-update-info
has access to a group's level/rank, but that doesn't seem relevant
here, and I imagine nnimap doesn't touch it anyway.

> ssh -f -L 10119:quimby.gnus.org:119 bonny -l grossjoh sleep 3600
...
> There is also an -R option for ssh, which I've never understood.

It's like -L, but backwards.  It connects to the ssh server and starts
listening to a port over there.  When someone connects to that port on
the ssh server, the connection is forwarded over the ssh connection
and hooked up to a new connection to a local port.


paul