Gnus development mailing list
 help / color / mirror / Atom feed
From: Doug Alcorn <doug@lathi.net>
Subject: Tunelling nnimap through ssh shell (Was: nnimap-authinfo-file question)
Date: 05 Jun 2001 12:42:11 -0400	[thread overview]
Message-ID: <87elsyop3w.fsf_-_@balder.seapine.com> (raw)
In-Reply-To: Andi Hechtbauer's message of "31 May 2001 18:56:21 +0200"

Andi Hechtbauer <anti@spin.de> writes:

> It's easier and more convenient of course to have your ssh keys and
> ssh-agent set up right (cf. ssh(1) "public-key cryptography", 
> ssh-agent(1), and ssh-add(1)) and just 
> 
> (setq imap-shell-program '( "ssh -x -C remote.imap.host /usr/sbin/imapd" ))
> 
> (setq gnus-secondary-select-methods
>       '(
>         (nnimap "host"
>                 (nnimap-address "remote.imap.host")
>                 (nnimap-stream shell)
>                 (nnimap-list-pattern ("INBOX" "mail/*"))
>         )
> ))
> 
> in your .gnus.el; So you M-x gnus and it just opens a ssh
> connection and starts your imapd preauthenticated. No need for
> username and password at all.

Thanks for reposting this.  I was happy to read it and happier to see
it working for me.

The only problem I ran into is that my ssh shells timeout with no
activity.  The ends up with messages about the stream being currupt
and then showing the ssh connection reset message (sorry I don't have
a copy of the exact message now).

Noticing another thread about problems with nnimap connections timeing
out, would it be possible to have nnimap send a keepalive message to
the server?
-- 
 (__) Doug Alcorn (mailto:doug@lathi.net http://www.lathi.net)
 oo / PGP 02B3 1E26 BCF2 9AAF 93F1  61D7 450C B264 3E63 D543
 |_/  If you're a capitalist and you have the best goods and they're
      free, you don't have to proselytize, you just have to wait. 



  reply	other threads:[~2001-06-05 16:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29 22:28 nnimap-authinfo-file question James Felix Black
2001-05-29 22:43 ` Kai Großjohann
2001-05-30  9:27   ` Kai Großjohann
2001-05-30  9:48     ` James Felix Black
2001-05-30 19:15 ` Chris Brierley
2001-05-31 15:27   ` James Felix Black
2001-05-31 16:56   ` Andi Hechtbauer
2001-06-05 16:42     ` Doug Alcorn [this message]
2001-06-05 18:53       ` Tunelling nnimap through ssh shell (Was: nnimap-authinfo-file question) Simon Josefsson
2001-06-05 19:36         ` Doug Alcorn
2001-06-05 21:11           ` Doug Alcorn
2001-06-06  8:04             ` Andi Hechtbauer
2001-06-06 20:49               ` Josh Huber
2001-06-05 21:51         ` Kai Großjohann
2001-06-05 21:55           ` Kai Großjohann
2001-06-05 21:59           ` Paul Jarc
2001-06-05 22:27             ` Kai Großjohann
2001-06-05 22:42           ` Itai Zukerman
2001-06-05 22:50             ` Kai Großjohann
2001-06-06  2:34               ` Doug Alcorn
2001-06-06  4:37                 ` Tunelling nnimap through ssh shell Karl Kleinpaste
2001-06-06  4:41                   ` Josh Huber
2001-06-06 13:53                     ` Doug Alcorn
2001-06-30 10:03       ` Tunelling nnimap through ssh shell (Was: nnimap-authinfo-file question) Steinar Bang

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=87elsyop3w.fsf_-_@balder.seapine.com \
    --to=doug@lathi.net \
    /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).