From: Simon Josefsson <jas@extundo.com>
Subject: Re: question about tunneling
Date: Fri, 29 Oct 2004 23:10:29 +0200 [thread overview]
Message-ID: <ilusm7xgri2.fsf@latte.josefsson.org> (raw)
In-Reply-To: <4nr7nh8rkr.fsf@lifelogs.com>
"Ted Zlatanov" <tzz@lifelogs.com> writes:
> I have the following tunnel script for an IMAP server:
>
> #!/bin/sh
>
> ssh HOST imapd | tee /tmp/imap-run
>
> Two problems:
>
> 1) without the tee, the tunnel simply does not work. I hope someone
> can tell me why :)
Maybe toggling imap-process-connection-type help?
> 2) occasionally I'll get a disconnect "garbage" message that Gnus
> doesn't know how to handle. Maybe that's related to (1).
Perhaps the parser is not robust when it come to non-IMAP protocol
behavior. What happens when this occur?
next prev parent reply other threads:[~2004-10-29 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 15:36 Ted Zlatanov
2004-10-29 21:10 ` Simon Josefsson [this message]
2004-11-01 19:06 ` Ted Zlatanov
2004-11-01 19:44 ` Ted Zlatanov
2004-11-01 22:03 ` Simon Josefsson
2004-11-05 16:19 ` Ted Zlatanov
2004-11-05 23:16 ` Simon Josefsson
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=ilusm7xgri2.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).